Matt, I backed the Interceptor .17 out because using it caused that crash I mentioned yesterday. So I am running .12.
So yeah, looks like for both Wind and Temp, there are gaps: ~~~ 1.11847092596965|40.37 0.0|40.46 0.0| 0.0|40.64 0.0|40.28 0.0|40.28 0.0| | | <BIIIIIIIIG SNIP> | | | 0.0|37.58 0.0|37.76 ~~~ I have snipped the null data to be more concise, but both devices have no data overnight. I find it odd that both devices were experiencing difficulties at exactly the same time, don't you? That's way too coincidental. Devices having issues shouldn't have issues together. -SR On Friday, November 18, 2016 at 9:03:32 AM UTC-8, mwall wrote: > > On Friday, November 18, 2016 at 11:37:38 AM UTC-5, Sam Roza wrote: >> >> So it was offline all night long, and then mysteriously at 0745, it >> stasrted reporting again. I took no action on the station for it to begin >> reporting, it just magically started doing so. >> > > > if you query the database what do you see? for example: > > sqlite3 /var/lib/weewx/weewx.sdb > sqlite> select dateTime,barometer,rain,outTemp,windSpeed from archive > > the last temperature/humidity packet is at 01:02:33 > > the last wind packet is at 01:06:04 > > the rain and base station (barometer) packets are received regularly > throughout > > so that indicates issues with the sensors contacting gateway > > also, it looks like you are running two difference weewx/interceptor > instances. when you start up at 09:51:48 and 09:53:41 it is running > interceptor 0.17a, but when you start up at 10:04:00 it is running > interceptor 0.12. > > m > -- 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.
