I can see how you arrived at the conclusion. But, we wouldn’t be having this discussion if the driver did not generate out of order loop packets. So for my perspective, I’d like to determine how an extension should deal with this specific use case. Some additional information, https://github.com/weewx-mqtt/subscribe/issues/10 On Monday, 18 May 2026 at 06:31:45 UTC-4 Karen K wrote:
> The general question is how to aggregate measurements from several sources > into one WeeWX instance. Especially, if data does not arrive in time. WeeWX > is not designed for that. It is designed for one base data source and some > additional data, that arrive without their own timestamp. > > The only solution I see is to write an extension that writes into a > separate database, while using WeeWX's database module for that. So you can > use those measurements in skins, but you can also write different > timestamps. > > -- 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 visit https://groups.google.com/d/msgid/weewx-user/1d27088d-cf0b-49b8-9a70-8099aed53636n%40googlegroups.com.
