Re: [weewx-development] 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

On Saturday, December 14, 2019 at 6:57:13 PM UTC-5, Tom Keffer wrote: > > > For stations with an internal clock, it's possible the time will drift a > few seconds, maybe even archive_delay seconds ahead. We don't want to > reject records just because of that. > done at commit f0bb3259 --

Re: [weewx-development] 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

> i put the change in engine.py instead of wmr300.py - that way it will fix > this problem for every driver, not just wmr300. changed at > weewx-development commit e9962fe8 > For stations with an internal clock, it's possible the time will drift a few seconds, maybe even archive_delay seconds

Re: [weewx-development] 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

leon, i put the change in engine.py instead of wmr300.py - that way it will fix this problem for every driver, not just wmr300. changed at weewx-development commit e9962fe8 can you test it with the appropriate DST settings and historical data on your station? m -- You received this

Re: [weewx-development] 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

tom, i did a patch on the wmr300 driver, but perhaps this would be better done in the engine? rejecting packets/records that have a dateTime in the future is pretty generic doing it in the engine would prevent problems from any driver... m -- You received this message because you are

Re: [weewx-development] 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

On Saturday, December 14, 2019 at 5:20:04 PM UTC-5, Leon Shaner wrote: > > That coupled with the refusal to insert the future-data records would have > avoided loss of data. > leon, i put in a fix at commit 10d00a23. this is on the development branch. this will reject any historical record

Re: [weewx-development] 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

Tom, One more thing to add... An interesting "one-time" artifact of changing the WMR300 from EDT to EST is the history replay is adding a handful of entries added one hour in the future. Probably a bug/RFE here that WMR 300 historical replay should refuse to insert future-dated timestamps

Re: [weewx-development] 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

Tom, Yep that was it.  WMR300 apparently needs to not only be manually switched from "dst" to "st" but the hour also had to decremented. Now upon weewx restart it takes almost no time to process the very few "missed" records vs. what amounted to erroneously "replaying" an hours worth of

Re: [weewx-development] 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

Tom, I think I see the problem.   The wmr300 history code is adding "future" records. Note the "disagreement" in the time of the log entry vs. the time of the record being added: /*Dec 14 13:11:16*/ nixie weewx[14125] INFO weewx.drivers.wmr300: New historical record for 2019-12-14

Re: [weewx-development] Re: V4.0.0b4 is up

Thanks Tom. WeeWx appears to be running - I'm getting output to home/weewx/public_html/index.html . Now to tackle the damn 'b's, should keep me busy for a few hours. I plan on waiting a bit before adding cmom, I have been having trouble with the old system stopping, I suspect because of a

Re: [weewx-development] 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

Log attached. Thomas Keffer wrote on 12/14/19 2:19 PM: The log sure would be useful... On Sat, Dec 14, 2019 at 11:19 AM Leon Shaner > wrote: Hey WeeWX'ers... I've been getting a series of the following error for about an hour each time I restart WeeWx

Re: [weewx-development] 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

The log sure would be useful... On Sat, Dec 14, 2019 at 11:19 AM Leon Shaner wrote: > Hey WeeWX'ers... > > I've been getting a series of the following error for about an hour each > time I restart WeeWx since syncing to the latest development branch several > weeks ago: > > Dec 14 13:12:14

Re: [weewx-development] Re: V4.0.0b4 is up

Silly me. I forgot to save the characters to the buffer! Try the attached. Those damn 'b's are because you are printing bytes or bytearrays, not strings. If you want to get rid of them, you need to convert to a string (which is unicode under Python3). This illustrates: >>> print(b'abc) b'abc'

[weewx-development] 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

Hey WeeWX'ers... I've been getting a series of the following error for about an hour each time I restart WeeWx since syncing to the latest development branch several weeks ago: Dec 14 13:12:14 nixie weewx[14125] ERROR weewx.manager: Unable to add record 2019-12-14 13:12:00 EST (1576347120) to

Re: [weewx-development] Re: V4.0.0b4 is up

This is the result with latest ultimeter.py and debug_serial = 1 Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.engine: retrying... Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.engine: Using configuration file /home/weewx/weewx.conf Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Debug

Re: [weewx-development] Re: V4.0.0b4 is up

I think this problem may be related to this thread , which was never resolved. Hopefully, we'll get it this time. Try this version, but before you do, not only set debug=1 at the top of weewx.conf, but also set debug_serial