belchertown skin question: reporting from multiple weewx instances

[Doug Jenkins]

Good evening fellow WeeWX users!

I was wondering if anyone was using the belchertown skin with multiple weewx instances. I am going to be setting up my new Davis Vantage Pro 2 (just came in today) with a Davis AirLink and I need to bind both the AQI and Weather data together.

From what I saw in the repos for WeatherLink Live, I can get the data via one driver, but the AirLink is not supported at the same time. Since WeeWX supports only 1 station per instance, I am going to setup a separate WeeWX instance to talk to AirLink and a separate WeeWX instance to pull in the Weather Station data from WeatherLink Live.

I desire to publish both instances to MQTT and report them out on the Belchertown skin.

Any help or suggestions with the skin to report both values is appreciated!

Doug Jenkins
largoweather.com

[vince]

My recollection is that Belchertown only supports one weewxinstance, although you 'can' bind to multiple db within 'one' instance of weewx.  I do just that to add info from multiple secondary db to my VP2 data in the default db.

You could kludge something together with having one weewx instance publish data to MQTT and have the primary one subscribe to that MQTT data if you 'really' wanted to add'em all up into one Belchertown dashboard.  I actually do that too in order to add stuff from some DS18b20 sensors to my Belchertown graphs.

Weewx supporting MQTT pub/sub is very powerful and is rock solid if your network and MQTT broker are stable.

[Doug Jenkins]

Thanks Vince, you answered my question. My plan was to run belchertown in a separate "reporting" instance with database bindings to the aqi and davis weather station databases (fed with separate weewx instances). I will have to play with the weewx.conf and skin.conf to see if I can bind certain values to certain database sources.

For MQTT, I want to publish the live values from both stations, so I will probably setup each weewx station to publish to separate topics and bring that in on the reporting weewx instance.

DDJ

--
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/3e093324-202c-4233-896d-798a06f13d02n%40googlegroups.com.

[vince]

Example from graphs.conf

[day]

    title = "Today"
    show_button = true
    button_text = "Day"
    time_length = today
    tooltip_date_format = "LLL"
    gapsize = 300000

    # an added chart from multiple db sources

    # note how 'some' elements specify a binding to a secondary db

    [[chartA]]
        title = Temperature Comparison
        connectNulls = true

        [[[outTemp]]]
            name = VP2 Temperature

        [[[extraTemp1]]]
            data_binding = pi_binding
            name = ds18b20_1
        [[[extraTemp2]]]
            data_binding = pi_binding
            name = ds18b20_2

    # an added chart with all data from a secondary db
    [[chart0]]
        title = WeeWX Memory Usage
        data_binding = mem_binding
        connectNulls = true
        [[[mem_size]]]
        [[[mem_rss]]]
        [[[mem_share]]]

[Doug Jenkins]

Thanks Vince once again :)

In my configuration work, I found that if I use the weewx-airlink and weewx-weatherlink-live extensions together, I get both the AQI and station data on the same loop. The author of the weewx-airlink extension is using a data service, which updates the LOOP record when the device is polled. 

So in essence, I am going to run the site on a single instance which simplifies my configuration :)

Thanks for the code example, I will probably use it for other sensor integration outside of the Davis Hardware.

DDJ