> If you mean does WeeWX determine if any incoming archive record has (for example) a new daily max for some field and then save that data, then yes that is what StdArchive does.
So if a hardware sends a loop packet with all the readings in a one-minute-interval, and stores these exact values in its own storage in a separate entry, one entry per minute, the weewx database values are exactly the same, regardless if they were received as loop data as if they were backfilled? Including timestamps and Values for min/max in archive_day_xxxx, which may differ from the min/max value found in all weewx archive records of that particular day, with timestamps between possible timestamps of archve values? gjr80 schrieb am Dienstag, 9. Februar 2021 um 11:32:28 UTC+1: > On Tuesday, 9 February 2021 at 19:43:50 UTC+10 [email protected] wrote: > >> Thanks Gary. >> So if the driver "wants" to control the archive interval, it is >> overriden? For my personal reality, 1 Minute is too short. >> > > Simply put, if WeeWX is using hardware record generation and the driver > has an archive_interval property then the driver value is used. > > The hardware supported by most drivers I have seen that have an > archive_interval property has the ability to store the archive interval in > the hardware, the driver reads this value on startup and that is what is > provided by the driver via the archive_interval property. Ultimately such > hardware gives the user some ability to set this ‘hardware’ archive > interval separately, maybe through a front panel setting or using separate > software such as the wee_device utility or some hardware specific software. > For example, the Davis stations can have the archive interval set via > wee_device —set-interval or via front panel buttons. > > > If one or more archive records are provided WeeWX accepts and uses them >> How does this work in detail? does weewx take care of min/max if there >> are more hardware archive records than weewx archive records? >> > > The WeeWX StdArchive service is responsible for taking loop packets and > archive records from the driver and (1) saving archive records to database > and (2) updating the daily summary tables as necessary. This is greatly > simplified but essentially what happens. Not sure what you mean by “does > weewx take care of min/max if there are more hardware archive records than > weewx archive records?” If you mean does WeeWX determine if any incoming > archive record has (for example) a new daily max for some field and then > save that data, then yes that is what StdArchive does. > > Gary > -- 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/7a181c02-c983-497d-b548-504c7fcd72ecn%40googlegroups.com.
