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/A03520F5-88EE-499D-BBA7-5F717CBD6B2A%40johnkline.com.
