vp2 emits packets (i think including wind readings) about every 2.7 secs; weewx accumulates these and saves/reports aggregated values each interval (default 5 mins). you could use the mqtt service/driver to publish selected packet values every 2.7 secs, and handle these youself for more realtime-oriented purposes (weewx reporting is not designed as a realtime service) in an app you write. this simple app that subscribes to the 2.7 sec vp2 packets will publish on whatever basis you like. timing (30 sec, 1 min, 2 min, 5 min, 30 min intervals) is not the only consideration, so is reliability e.g. if you hold the aggregations in memory then if the server is restarted they are lost ➔ maybe the partial aggregations need to be persisted while being accumulated for next interval publish message
the weewx components being used are the vantage driver, which acquires realtime data from vp2 and normalises the data, and the mqtt service that extracts relevant normalised data and publishes it to your realtime wind service app. the weewx reporting would continue in parallel and provide regular reports each 5 mins on website ⊣GE⊢ > On 30 Sep 2024, at 7:29 am, James Pattinson <[email protected]> wrote: > > Thanks for the responses. It’s interesting stuff. I should note that my > desire is to push this average value out over MQTT as I have a web page > displaying the real time data and when something changes I want it to be > pushed out. So I actually don’t think anything to do with templates or > cheetah will be relevant. -- 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 on the web visit https://groups.google.com/d/msgid/weewx-user/0CD8FB20-9ABF-44D4-AB81-59DF3D8492A5%40geddy.au.
