I saw this conversation, https://groups.google.com/g/weewx-development/c/TXH8pgRs51c/m/jJrnulyiAQAJ, and thought I should circle back and update this thread on where I am at.
1. I have decreased the polling time to 10 seconds and all is behaving well. 2. I really wanted to capture the time of the closest strike. So, I wrote a small service that captures min, max, first, and last observation values and times in the archive period. It’s still very much beta code and is in my ‘extras’ repository https://github.com/bellrichm/WeeWX-Extras/blob/master/bin/user/observationtime.py; so has limited documentation and needs to be manually installed. 3. I am experimenting with my extra rtl-sdr dongle and ‘capturing’ strikes ‘real time’. Of course we are past thunderstorm season now… But it is interesting what else I came ‘capturing’, water meter, gas meter, electric meter….. 4. I am think of updating MQTTSubscribe to deal with dependent fields. This would eliminate the need for the ‘corrections’ configuration, which would make configuring the order of services in the [Engine] section easier. rich -- 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/09175833-c770-4ff0-a088-cee647ac4279n%40googlegroups.com.
