Not sure why it required a reboot on the raspberry, but I guess I had tried
several things.
Took a while for the graph to regenerate as it will pulling archive records
from the WMR200.
I had also update the weewx andriod app.
Mike
--
You received this message because you are subscribed
I think my issue with sql database, it look like there are future dates in
the database.
This started end of last week where the temp was report ~33f but it was
really ~80f,
so I tried stopping and restarting the services, and ended up rebooting the
raspberry.
That is when I started seeing
w.
Thanks for everyone's assistance.
On Wed, Dec 27, 2017 at 7:15 AM, Mike Dame <wa4...@gmail.com> wrote:
> Tried a delete from archive after midnight 12/25 that did not work after
> drop and rebuild still did not start. So per request, I have attached the
> message logs from the 22nd till
So it will not restart, I copied back the backup database. I tried with and
without the sql drop, now the database will not start... :(
pi@raspberrypi:~ $ sudo cp -p /var/tmp/weewx.sdb.backup
/var/lib/weewx/weewx.sdb
pi@raspberrypi:~ $ sudo sqlite3 /var/lib/weewx/weewx.sdb
SQLite version 3.8.7.1
tRecord(2017-12-25 00:00:00 CST (1514181600))
On Monday, December 25, 2017 at 8:53:02 PM UTC-6, Mike Dame wrote:
>
> Last night I rebooted my raspberry running that is running "weewx
> v3.8.0". And the report are dated two days ahead, so today is the 25th of
> Dec, re
, 2017 at 8:53:02 PM UTC-6, Mike Dame wrote:
>
> Last night I rebooted my raspberry running that is running "weewx
> v3.8.0". And the report are dated two days ahead, so today is the 25th of
> Dec, reported that the temps are from 27th of Dec. I have double checked
> th
Last night I rebooted my raspberry running that is running "weewx v3.8.0".
And the report are dated two days ahead, so today is the 25th of Dec,
reported that the temps are from 27th of Dec. I have double checked the
system clock is correct on the raspberry and the time on the "WMR200a" is
