The original post suggested the multiple sites might each rsync their db occasionally up to the central site, so Rich’s suggestion should be lighter if he gets it to production ready. Matthew has suggested in the past that using multiple db and one skin reading them might be less reliable than putting multi-site data into one big db, but I’ve had zero issues with multiple db and one consolidated skin for many years now. Definitely works either way.
On Saturday, February 21, 2026 at 4:00:24 PM UTC-8 Graham Eddy wrote: > the question, as i understood it, was to present from single copy of data > already existing, rather than to store multiple copies of the same data in > multiple databases. > i use mqtt extensively for data acquisition, creating single truths in > databases. then i have a presentation layer over the top of all to create a > single (complex) portal (which has more than just weewx data). > as vince and others point out, there is more than one way to ’skin a cat’ > and it depends on your requirements > *⊣GE⊢* > > On 22 Feb 2026, at 5:30 am, Vince Skahan <[email protected]> wrote: > > For just a few readings from just a few stations, MQTT is the simplest way: > > > > > -- 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/716f3397-bf1e-433a-a3ba-2f8e185c0d9en%40googlegroups.com.
