Thank you for the helpful suggestions, but neither approach worked. This is only a minor nuisance, with the larger item of the cause for the 75 minutes worth of missing data remaining unknown. As far as I have observed thus far using the Atmocom device, + the RPi 3B+, the weewx driver and weewx, this was the first gap in the data that has occurred over the past several weeks.
I have written to Relko Vazic: Has there been any firmware updates for the Atmocom device (Firmware Updates Over the Air)? and by any chance, was there one between (unixepoch) 1553838600 & 1553843100 (as recorded in /var/lib/weewx/weewx.sdb); or as ~/atmocom/wxdb/wx201903.db has recorded in it between 20190329 01:42:41 & 03:05:50 UTC-4? This gap in data can also be seen on WU for KMEELLSW50 <https://www.wunderground.com/dashboard/pws/KMEELLSW50>. This was not caused by a local electrical outage as my other unit (WS-2902A) has been uploading to WU KMEELLSW49 <https://www.wunderground.com/dashboard/pws/KMEELLSW49> without issue. Other than that, I'm unsure what else to rule out. On Friday, March 29, 2019 at 11:47:41 AM UTC-4, Thomas Keffer wrote: > > It does seem like there is a bug that prevents you from editing the > display format. Try using the dropdown list, and selecting "Unix epoch to > date." It will show the time in UTC. > > The other alternative is to use the tool "sqlite3". For example, > > sqlite3 weewx.sdb > sqlite> SELECT datetime(dateTime,'unixepoch','localtime'), barometer FROM > archive LIMIT 5; > > This is what I use. > > -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.
