Just followed your instructions and will post the new log file after it's had a chance to run a while as suggested.
On Sunday, October 16, 2016 at 6:59:57 AM UTC-7, Tom Keffer wrote: > > On Sun, Oct 16, 2016 at 6:18 AM, mwall <[email protected] > <javascript:>> wrote: > >> On Sunday, October 16, 2016 at 8:19:38 AM UTC-4, Tom Keffer wrote: >>> >>> Me too. What do you think of my theory that the console is >>> (occasionally) waiting more than 5 minutes to emit a LOOP packet? >>> >> >> the log indicates that the driver is getting data regularly. take a look >> at the entries between some of the 10 minute add records. >> >> there is a yield just before each "next read in X second". when the data >> are stale, the yielded packet contains only dateTime, usUnits, channel, >> sensor_id, rssi, sensor_battery, but no weather data. >> > > That should be enough to give the engine a chance to break the loop. > > Tim: I have attached an instrumented version of > engine.py > that should shed some light on this mystery. Please set your old version > of > engine.py > aside, and replace it with this one. Assuming you download this version > into > ~/Downloads > , the process would be: > > cd /usr/share/weewx/weewx > mv engine.py engine.py.orig > cp ~/Downloads/engine.py engine.py > > > Make sure debug=1, then restart weewx, then send the log from the restart, > through the first couple of reports (should take about 20 minutes). The log > will be big, so just attach it as a file. > > -tk > > > > > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
