Thanks all for the info! I have a few more things I need to feel more comfortable with in basic configuration, but I'll look at all of the links and info provided. Struggled with getting cmon in my exfoliation skin for days only to find out that the instructions say to use cmon_binding when it was actually wx_binding, at least in my case. So I need to keep working the learning curve, but the input helps.
Thanks very much! On Tue, Feb 5, 2019 at 12:30 PM mwall <[email protected]> wrote: > > > On Monday, February 4, 2019 at 12:25:22 PM UTC-5, Robert Anthony Pitera > wrote: >> >> I have WeeWX up and running with my Acurite 5in1 but I also have a >> Bloomsky Sky1. I discovered there was a driver for the Bloomsky and was >> wondering if there was a way to add it into my existing WeeWX instance. I >> saw that in 2017 someone asked and it wasn't possible to use two drivers >> simultaneously but I was wondering if that limitation still existed? If >> so, has anyone found a work around for this like running two instances of >> WeeWX and somehow combing the info in the skins? >> > > it is easy to run multiple instances, but as tom notes, only one driver > per instance. > > using a service to augment data works well in some cases, such as adding > data from some one-wire sensors to the database that has data from your > weather station. > > but for multiple weather stations, or for power monitoring, tide > monitoring, water consumption, fuel consumption, air quality, or other > types of data collection, it is often better to run multiple instances of > weewx. > > https://github.com/weewx/weewx/wiki/weewx-multi > > you can always combine data into a single report with a separate, > dedicated skin and wee_reports. or you can aggregate by feeding into > influx or emoncms or something that feeds off of mqtt. > > this is how i typically configure a system that will have multiple > instances of weewx on it: > > /opt/weewx-x.y.z - weewx is installed here > /opt/weewx-skins - skins go here > /etc/weewx/ - configurations go here, one per instance > /var/lib/weewx/ - database files go here, one per instance > /etc/init.d/weewx-multi - script that starts/stops them > /etc/default/weewx-multi - list of which instances should run > > that way i can test new releases of weewx without disturbing what is > already running. i can test/update one instance without disturbing the > others. i can update/test skins without disturbing whatever is already > running. i can update skins independently of weewx itself. > > on most systems i run only two or three weewx instances, but i have a > couple of systems with 6 or 8 instances. > > m > > -- > You received this message because you are subscribed to a topic in the > Google Groups "weewx-user" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/weewx-user/BbOOM3sAtK0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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.
