I think the next step would be to capture the loop packets between two archive records and manually sum up the ET values. Or you could estimate the number of loop packets between archive records and if it is close to 100 call it done. Net, it seems like everything is working as expected. MQTTSubscribeDriver is creating the packets. WeeWX is summing the ET values in the packets to create the archive record. Mulling this over a bit more, I think setting contains_total = true for your etday field might be the answer. This was added for MQTT rain data that is cumulative to calculate a delta for WeeWX. rich
On Sunday, 27 December 2020 at 23:24:59 UTC-5 gjr80 wrote: > Also, remember under a traditional Davis console/logger/vantage driver > setup you will see approx 120 loop packets per five minute archive record. > So seeing an archive record value that is 100 times a loop value is not > unreasonable for a cumulative field such as ET or rain. The difference here > is that a traditional Davis console/logger/vantage driver setup you do not > see loop ET values. > > The only way to know if it it working properly is to understand who is > emitting what and then do the maths to confirm the result one way or > another. > > Gary > -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/9f9dbc9f-5157-4645-8014-33fe33a9842an%40googlegroups.com.
