Driver periodically fails to update weather data #41
Comments
|
some issues with driver 0.3.1 and weewx 4.5.1 too. |
The problem you are experiencing is quite different and has nothing to do with the original issue posted by @Laephis. I have moved your problem to issue #42. Please continue any discussion there. |
|
@Laephis. A few questions. You mentioned in #36 that you are not running the SDR driver but you did not mention whether you are running the GW1000 driver as a driver or as a service with some other driver? (the log extract above would show it but unfortunately you did not include the entire WeeWX startup). My first thoughts are that perhaps one or more sensors are not being picked up by the GW1000. What hardware does your Ecowitt setup comprise? Have you modified the Seasons skin to display the GW1000 sensor status data? If so what does it show? It would be useful to see the output of the following commands: and (depending on your system you might need to replace These commands will show details on the sensors linked to the GW1000 as well as the current data from the linked sensors. One other thing, does your GW1000 send data to Ecowitt.net? If so does Ecowitt.net show any missing data? |
|
@gjr80 Thanks for taking the time to look into this, appreciate the response and I'll try my best to answer your questions. I have an HP3501 kit (with associated sensors) in addition to the GW1000. (I got the latter in order to be able to do more with the data with things like weewx, cumulusmx, etc.) I don't recall doing any modification to the Seasons skin, mostly because I just use belchertown to display the data on a tablet. The screenshot I attached previously is what it looks like when it's not working (just displays "N/A") Here's the output of the commands you listed: Finally, yes, I do send data to Ecowitt.net. (But normally have the website set to display the HP3501 device.) I checked and noticed missing data on June 7 and 8 for the GW1000, but the HP3501 device did not have any missing data. Does this mean the problem is likely with the GW1000? If so, sorry to have sent you down this rabbit hole. The strange thing is that everything has been 100% correct all day yesterday and today, so I can't make sense of it. |
|
Thanks. I only have a GW1000 and a handful of discrete sensors (WH31, WH32, WH43, WH51 and WH57) so once consoles, 5/7-in-1 and rain gauges get involved I'm a little in the dark. So what sensor provides your outside temperature/humidity? The The reason I asked about the modified Sensors page was that if modified it would show us a plot of your sensor battery state and signal level. If you haven't made that change (or implemented anything similar in Belchertown) don't worry, that doesn't prove the cause but adds to the picture. Checking against Ecowitt.net is useful as it receives it data independent of WeeWX so if we see a corresponding outage there it is suggestive of a hardware problem rather than a WeeWX/GW1000 driver problem. When you say there was missing GW1000 data on 7 and 8 June was that on Ecowitt.net? If so that lends support to the theory the GW1000 lost contact with one or more sensors (I have a WH51 that is some 25metres from my two GW1000 with an internal wall, window and external brick wall in the path and I have periodic lost contact with the sensor. Since it worked faultlessly for weeks I have a theory that once the battery gets down a bit the signal is more unreliable but that is only supposition.). Another thing you could check is the WS View app if you have it installed. When the outdoor temp/humidity disappear do they also disappear from the WS View app. Also have a look at the More -> Sensors ID page. Is there any signal level showing against your outdoor temp/humidity sensor? (this might be a bit imperfect as the GW1000 signal level is a quasi signal level - it just shows how many of the last four expected packets were received from the sensor). If there are issues on the WS View app then that is also suggestive of a hardware issue. |
|
Nothing for over three months, closing now. Can be re-opened if required. |
I've been experiencing occasional periods of time where WeeWX isn't receiving data while using the gw1000 driver. I've tried to look for patterns, but nothing has jumped out at me yet. Sometimes restarting the weewx service or rebooting my pi resolves it, sometimes it doesn't. Then it all shows up again. The problem appears isolated to the outside temp, heat index, wind chill, humidity, and barometer readings. The other sensors continue to work and are never affected by this. I've attached some screenshots showing examples of problem. Also, here's ~15 minutes of data from the debug log file after first starting up (and experiencing the issue.) The only change I've made to the system (other than to update the driver to 0.3.1 and weewx to 4.5.1) is a couple firmware updates on the gw1000.
The text was updated successfully, but these errors were encountered: