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
"morr...@gmail.com" writes:
> We're just recovering from Hurricane Fiona here. My weewx server was off
> for 14 hours becasue of the power outage.
>
> I'm thinking of caching readings in my DIY Moteino based weather station,
> or the base station which accepts data from it via 915MHz radios, a
On Sat, Sep 24, 2022, 20:47 Tom Keffer, 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 interna
Off the top of my head, the one area of concern is that on startup the
archiving process does check the wall time clock to figure out the bounds
of the archive record it is working on. It might be possible to change that
to using the timestamp of the first LOOP packet, but there's also likely to
be
We're just recovering from Hurricane Fiona here. My weewx server was off
for 14 hours becasue of the power outage.
I'm thinking of caching readings in my DIY Moteino based weather station,
or the base station which accepts data from it via 915MHz radios, and then
bursting them to weewx when it