On Wednesday, January 24, 2018 at 2:42:46 PM UTC-8, gjr80 wrote: > > WeeWX can run with one driver only; however, it can run with an > (essentially) unlimited number of services. So folks with an existing > station that want to include data from another source typically do so by > running the driver for their station and a service for the other source. > > > Absolutely - I would like to generate MQTT data from a variety of low-cost sensors and write them to a secondary weewx db using an extension, while 'still' using my VP2 weather station for most of the weather information.
Currently I do this by jumping through hoops a bit: - generate a JSON-formatted file on a raspi with a few sensors - have that raspi serve the file up via nginx - wrote a weewx sensor that grabs the url from the raspi and seeds my second db's archive with that data I'd like to simplify things by replacing the pi nginx and the custom 'grab a url' extension with just subscribing to an aggregated MQTT topic with data coming from that raspi, plus (someday) other sensors like things attached to nodeMCU cards and the like. So I'm hoping for a scenario that seeds a secondary db from a MQTT topic, in effect. Kinda like the MQTT 'out' extension Matthew wrote, just in reverse. -- 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]. For more options, visit https://groups.google.com/d/optout.
