Take a look at the wiki for https://github.com/weewx/weewx/wiki/dashboards for some ways to do this. There are others. Lots of others.
For just a few readings from just a few stations, MQTT is the simplest way: - run a mosquitto broker on your central site - have each weewx instance publish MQTT to a unique topic such as station1/loop, station2/loop, etc. - have the central weewx MQTTsubscribe to the desired topics and save to one weewx db Nice thing is MQTTsubscribe can run as a driver, so you could use that to get data from the incoming MQTT topics into one central weewx db. You'll have to map those items to weewx db elements, so if you have a lot of readings from many stations, you'll need to add db columns 'once'. You'd have to of course create your own weewx skin to create whatever HTML and graphs you want, but you'd be totally weewx with the exception of running a Mosquitto MQTT broker (easy to do) on your central site. That said, if you want to have 'all' possible readings from 'many' stations then it's probably best to publish to influxdb and display with something like grafana or maybe even Home Assistant. That will get you almost infinite extensibility but it's far more work to learn, set up, and set up securely.(note - I never looked into how to secure a grafana dashboard from Internet bots. I was fortunately LAN-only). On Saturday, February 21, 2026 at 1:19:32 AM UTC-8 Tomasz Lewicki wrote: > I have the following idea and problem at the same time. I would like to > build a small network of weather stations in the area, say 5-10 units. Of > course, they will all be powered by Weewx and Raspberry Pi. Apart from the > fact that each one will publish data on the internet independently of the > others (one domain, separate subdomains), I am thinking about a collective > presentation of data from the stations - only selected parameters, e.g., > temperature, wind, precipitation. > > Each Weewx instance is a separate weewx.sdb database with an identical > structure. If I understand correctly, I would have to create a separate > (collective) database in which the indexes of individual parameters would > be different for each station, e.g., temp_pws01, temp_pws02, etc. The idea > is that such a comparison would not be generated in real time, as in a > standard Weewx installation, i.e., every 5-10 minutes, but, say, 4 times a > day. I figured that the databases from each station would be sent via rsync > to a remote server, and then specific columns would be extracted from them > “somehow” and copied to a new, shared database, from which a summary would > be made. Can the final step be done with Weewx, or do I need to use other > tools? > > The question is, has anyone done something like this before and could > point me in the right direction? > > *Translated with DeepL.com > <https://www.deepl.com/?utm_campaign=product&utm_source=web_translator&utm_medium=web&utm_content=copy_free_translation> > > (free version)* > -- 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 visit https://groups.google.com/d/msgid/weewx-user/61b304c0-e38b-4e9a-85d8-d6b5cda8ea95n%40googlegroups.com.
