Recent Posts

Pages: [1] 2 3 ... 10
1
If this doesn't work, my thoughts are to inform support@ecowitt.net, and if that fails to remedy, buy another unit (maybe step up to the GW1200)

But, If you have time and are incredibly bored and like a tedious task, I would be curious , if after your next reset (assuming you need to make one), if you would disable all external sensors the device is receiving from  using WSView+ or the web interface, leaving only the ones on the GW1100 itself (temp, humidity, pressure) to report.

I know, this sounds silly , especially if you just want the thing to work. For me it is a curiosity. For you it probably won't solve anything
2
What about down by the lake.
Do you have a dock you could put it on.
3
I have an Ambient Weather 2902C console and an Ecowitt GW1000 on my network. I have configured foshkplugin to get the weather data and I store it in an influxdb database using a nodered flow. I get the values through http://<ip address>:8081/JSON link in the nodered flow. Looking at the data returned from the link, I see the following 2 formats:

Code: [Select]
{"stationtype":"AMBWeatherV4.3.4", .....}and
Code: [Select]
{"PASSKEY":"xxxxx","stationtype":"GW1000B_V1.7.5", .....}The ambient data does not include values for rainratemm and yearlyrainmm; the ecowitt data includes both. Mostly the data is in the 1st format but randomly switches to the 2nd format. I would like it to get the 2nd format data. I have changed the ip address in the conf file to the GW1000 but it makes no difference. How can I force foshkplugin to get its data from the GW1000? I am using version 0.0.10Beta.

Thanks.
4
Problem now fixed.  [tup] :grin:

Tried clearing the cache and also data storage, but it had no effect on the problem.

Eventually a reset of the GW2000A (held button for >10sec) worked and all is now restarted and stable.  [tup]

Not sure what may have caused it but  the wrong IP address (xxx.xxx.xxx.37) had been used by the GW2000A previously.

Maybe somehow, somewhere it remembered and tried to use both. Seems strange, but my only explanation/guess.  :?
5
Ahh. I was trying to figure out what was up with my site. I totally removed the menubar.php and it worked.
Then I started removing things like the extremes until the was functioning again.
6
So, yes still at the drawing board.
I have these installed and was wondering if I'm missing any other scripts(s), I went through the setting of what I have or could find but I don't see anything.
If anyone knows if these are all or even the right scripts, please lmk.
get-aqi-rss.php
wxAQI.php
wxaqirssV2.php
7
From an earlier discussion with Ecowitt, the calibration to zero is the WS90 (or WS80) unit brought into an area with no wind (indoors) and the CAL button pressed and released whilst the unit remains still.
that's how we have described it in the WiKi  8-)
http://meshka.eu/Ecowitt/dokuwiki/doku.php#sensor_firmware_ws80_ws90
8
From an earlier discussion with Ecowitt, the calibration to zero is the WS90 (or WS80) unit brought into an area with no wind (indoors) and the CAL button pressed and released whilst the unit remains still.
9
The NWS had a major outage yesterday due to a chiller malfunction and over-temp issues.  They are recovering systems so should be back functioning today.

Quote
Several storage systems in the College Park data center remain down after Monday afternoon's temperature spike.
Systems have been automatically repairing themselves overnight, but NCO's NetApp Team are working to provide an estimate of when storage systems will be fully recovered.
Additional support was engaged overnight to keep IDP Applications running in Boulder healthy and to investigate mitigating impacts to WPC and OPC operations.
No ETR at this time.
Next update will be at 8am EDT.
Current Known Impacts include:
NCEP Centers' websites hosted in CP are currently inaccessible (including NCO, OPC, EMC, CPC, and NCWCP intranet sites)
WPC, OPC, and CPC's operational product suites are severely degraded
FTPPRD is inaccessible in CP (Customers are able to use nomads.ncep.noaa.gov as a viable backup in the meantime)
See the NCO IT Status Dashboard for the latest updates and more information


SDM Mary Beth
10
" if the drop out behaviour continues. If so, a factory reset might be needed (holding the reset button >10 seconds)" : today the problem persists, so I've chosen this solution.
Pages: [1] 2 3 ... 10
anything