> Is this check only done at startup? Yes. It’s a check only at startup during a catchup phase meant to insert archive records that might have been generated by the device since the time of the last archive record inserted in the weewx database.
My reply was a narrow one, responding only to how weewx might determine an archive record is in the future and, therefore, inappropriate. I’m not endorsing the idea of simply ignoring the record and moving on. If the underlying problem is that the driver can’t rely on station time, perhaps it should ignore station time and substitute current time for it. Some drivers have this option. > On Sep 15, 2020, at 12:24 AM, YB322 <[email protected]> wrote: > > Is this check only done at startup? I am seeing this happen during the > ecowitt update sent via the station itself. The interceptor driver is > receiving an update from the station with a timestamp in the future. Once it > is processed no more updates are added to the database until after the time > of the incorrect time stamp. After this point the normal operation continues > and updates are added to the DB until another incorrect timestamp is > received. > > Thanks for taking the time to respond, appreciate it. > > Adam >> On Tuesday, 15 September 2020 at 12:22:47 pm UTC+10 [email protected] >> wrote: >> This is done already for catchup at startup time. See engine.py “Reject any >> records with a timestamp in the future.” It uses the current time and >> allows archive_delay seconds for clock drift. >> >> >>>> On Sep 14, 2020, at 6:54 PM, vince <[email protected]> wrote: >>>> >>> >>>>> On Monday, September 14, 2020 at 5:03:23 PM UTC-7, YB322 wrote: >>>>> It is clearly something with the station itself, but not sure why it is >>>>> randomly throwing a time in the future, think it is some kind of bug in >>>>> the latest firmware as I have now seen a couple of other posts with the >>>>> same issue. >>>>> >>>>> I am not an expert at Python but would it be possible to have a check and >>>>> drop the packet if date time is more than an hour into the future? >>>>> >>>> >>>> If you have two things with different date+time, how would you know which >>>> one is reporting a timestamp in the future (or in the past) ? >>>> >>>> >>> -- >>> 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]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/d8f135c6-cbf0-43d6-a76a-25a0d34e2a0do%40googlegroups.com. > > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/7a029865-1d35-409a-98cb-b3581bd259d5n%40googlegroups.com. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/00232CEB-95DA-4114-842C-CD536A58DC89%40johnkline.com.
