I solved the 'upgrade/update' problem by rolling all my skins into extension-installable custom ones. Don't use any default skins at all.
But sure. I got into the same A-needs-B-which-needs-C-which-needs-A mess with multiple skins that I wrote all assuming the other ones and their required extensions were there. debug=1 logs helped of course in battling through it. FWIW - I did learn that occasionally trying to do a full install from scratch step-by-step finds those things pretty quickly though. Eventually I said heck with it and just got it all working once and then did a cron job to back up / compress / save all of my weewx-data tree nightly for stashing in 'multiple' places just in case, plus a 'weectl extension list' output so I knew what else I had installed. On Tuesday, June 3, 2025 at 1:17:12 PM UTC-7 matthew wall wrote: > it is brittle because of the dependency of one weewx instance upon > another. not saying it won't work, it just introduces a coupling. > > i prefer to have each weewx instance do its own thing, ideally using a > generic, unmodified skin. > > then make an aggregated instance to unify everything, whether that is > weewx, influx+grafana, mqtt+homeassistant, or any other aggregation. > > that way i can upgrade/update weewx instances without too much concern, > and focus only on the aggregated report for anything customized i have done. > > i once ran a computer with 5 different types of hardware on it - one weewx > instance for each weather station. then i ran the report generator as a > cron job to pull all of the data into a single skin so i could compare > sensors from all the stations. > > of course, eventually sunlight won and broke down the plastics in all of > the anemometers, and salt air got into the battery compartments. but it was > fun for a few years. > > i guess the uv damage was the real source of 'brittle' ;) > > > > On Jun 3, 2025, at 13:10, vince <[email protected]> wrote: > > > > Not understanding why this is brittle. Weewx has supported multiple db > since v3 if my hazy memory is correct. Thats a lot of years of very stable. > > > > I use the weewx-multi plus MQTT solution here so I can feed a Home > Assistant dashboard containing other things via MQTT, but that broker in > the middle adds complexity a simple two-station weewx probably doesn’t > require. > > On Monday, June 2, 2025 at 4:00:13 PM UTC-7 matthew wall wrote: > > i should also add that you *could* make one of your two weewx instances > 'know' about the other one by adding data bindings. then refer to the two > bindings in the weewx skin used by that instance. however, i would suggest > *not* doing this, because it creates a brittle coupling that you probably > don't want to maintain. better to keep the instances independent, then join > the data using a separate mechanism. > > > > > > -- > > 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/ec515105-0b9e-4cc3-a0c0-6263bcd77c25n%40googlegroups.com > . > > -- 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/1c7b25fb-0717-4baa-a924-fcfdf0c488a7n%40googlegroups.com.
