That's correct. Before weewx starts asking for LOOP packets it figures out what the start and end of the archive interval will be. It uses this information to figure out when to stop asking for LOOP packets and, instead, ask for an archive record. See the call to _get_console_time() on line 594 <https://github.com/weewx/weewx/blob/9c5f105af5c5c77b0a5f060794dee21f60325bf9/bin/weewx/engine.py#L594> in the function pre_loop(), which is expected to return a wall clock time.
An alternative would be to delay figuring this information out until the first LOOP packet has been received. On Sat, Sep 24, 2022 at 4:59 PM Bill Morrow <[email protected]> wrote: > On Sat, Sep 24, 2022, 20:47 Tom Keffer, <[email protected]> wrote: > >> Still, if the effort to set things up is not too expensive, I'd say, "Try >> it!" >> > > Ok! I should be able to set up a test system without too much trouble. > > Just to be sure I understand correctly: the archive process' idea of > timestamping is internal - it doesn't pay attention to the timestamp in a > loop packet? > -- You received this message because you are subscribed to the Google Groups "weewx-development" 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-development/CAPq0zEAenqKk-fDAuJPOoBngsEcEdSdq3vgtr0giyOgS87kEFg%40mail.gmail.com.
