WeeWX-MQTTSubscribe - use of - sanity check

[Colin Larsen]

Learned WeeWX folk

I'm thinking about rewriting my current weather station code to solely use MQTT to deliver data to WeeWX. At present the station runs on WeatherDuino which transmits data (via wifi) to a console which then emulates the Davis protocol via usb to a Pi running WeeWX.

I really don't use the console for anything more than connecting to the Pi, so my thought is to bypass it, send all the data from the TX unit to my MQTT server (already up and taking AQI/AQM data from sensors via wifi) and then use WeeWX-MQTTSubscribe in driver mode to supply loop packets to WeeWX.

Oh and before anyone using WeatherDuino jumps in, I have just completely redesigned the TX units to use the ESP8266 (WemosD1 mini) rather than the old Arduino board and 433 Mhz splatter TX :)

Are there any holes in my plan??

Many thanks for your thoughts

Colin

ZL2FL

[bell...@gmail.com]

It should work fine. One caveat is, if something goes ‘down’ in your infrastructure you might lose some data. 

As you set it up, if you have any questions I’m around.

rich

[Graham Eddy]

i am nearly finished doing something similar, except

  (1) i position weewx as the manager of the wx hardware via station-specific interface - weewx is the app that encapsulates the wx and provides its data as mqtt to the world (unless the wx is natively mqtt). e.g. the vantage driver is solid.

  (2) i also position weewx as manager of an abstract weather station that receives its observations from many sources - and i have chosen mqtt as the common messaging medium i.e. lots of little IoT devices provide data to weewx via mqtt. this is a different role from (1), and i know some weewx users stream to data consolidaters that can provide this abstraction instead.

  (3) i wrote my own bi-directional mqtt gateway, for use in all my mqtt apps (the paho client leaves a lot ’to the reader’ to implement in a production environment so needs a whole software layer above it). most of my former data services have been migrated to separate apps that talk to weewx via mqtt. (some of my weewx data services manipulate data within weewx so are not externalised.) i have a weewx data service built on the bi-directional gateway as the interface between weewx and mqtt world.

i expect there is a lot of overlap with the excellent MQTTSubscribe. but my requirement was for a generic gateway outside of weewx, and the weewx interface is just one of the apps built on it

[Colin Larsen]

Thanks Rich

Yes both sets of data are on the same mqtt server. I agree with the single point of failure issue, but I think I have that anyway. I may look at some sort of parallel data logging maybe? 

Graham - nice work :)

Cheers

Colin

--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/8BAB1C3E-DE3C-4D57-84FA-6B6AFBD0326C%40gmail.com.