Re: [weewx-user] Skin with multiple bindings - an odd restriction

['Cameron D' via weewx-user]

Thanks Tom,
the workaround in the index template file works well for my purposes.

Sorry - I searched for it, but either used the wrong search terms or didn't 
look back quite far enough.
Cameron.
On Sunday, 12 November 2023 at 11:11:57 pm UTC+10 Tom Keffer wrote:

> This is a known issue with the Seasons skin. See Issue #803 
> .
>
> Unfortunately, the self-provisioning feature only checks the default 
> binding (wx_binding), not any other bindings. You have to include the plot 
> manually.
>
> -tk
>
> On Sat, Nov 11, 2023 at 7:05 AM 'Cameron D' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> I have been running a dual-weewx setup for nearly a year, having added an 
>> Ecowitt system mainly for air quality, with a separate custom DB.
>> I have been running two separate skins, based on Seasons, with a few 
>> charts including binding from the other DB.
>> I thought I should really do it properly, and just set up a single skin 
>> with everything I wanted, but I am having problems when there are no data 
>> required from the default binding.
>>
>> Initially I thought that it was failing *whenever *there was no  data 
>> from  the default binding, but it seems stranger than that.
>> The simplest example is co2:  The following stanza fails to produce 
>> anything:
>>
>> [[[dayco2]]]
>> data_binding = "ecowitt_binding"
>> co2
>>
>> However, the following works...
>>
>> [[[dayco2]]]
>> data_binding = "ecowitt_binding"
>> co2
>> barometer
>>
>> Note that I am using the ecowitt binding for all data, and the ecowitt 
>> barometer fields are empty, so the plot I get is only for the CO2.
>>
>> So, from the combinations that I have tried,  it seems that
>>
>>1. you *can *do a plot containing data only in the secondary binding 
>>- sometimes
>>2. you *cannot *do a plot if none of the data names exist in the 
>>default binding.
>>3. At least one of the data types named inside square brackets *must 
>>exist in  the default binding*, irrespective of whichever binding 
>>supplies the data.
>>4. I could not  trick it by specifying a known name, such as 
>>"inTemp" and then overriding with "data_type = co2"
>>
>> -- 
>> 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/1fe20e91-1de5-459c-8a45-77deb7c2753fn%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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/91b12bdb-61d2-4bcf-9236-2aba38fd380cn%40googlegroups.com.

Re: [weewx-user] Skin with multiple bindings - an odd restriction

[Tom Keffer]

This is a known issue with the Seasons skin. See Issue #803
.

Unfortunately, the self-provisioning feature only checks the default
binding (wx_binding), not any other bindings. You have to include the plot
manually.

-tk

On Sat, Nov 11, 2023 at 7:05 AM 'Cameron D' via weewx-user <
weewx-user@googlegroups.com> wrote:

> I have been running a dual-weewx setup for nearly a year, having added an
> Ecowitt system mainly for air quality, with a separate custom DB.
> I have been running two separate skins, based on Seasons, with a few
> charts including binding from the other DB.
> I thought I should really do it properly, and just set up a single skin
> with everything I wanted, but I am having problems when there are no data
> required from the default binding.
>
> Initially I thought that it was failing *whenever *there was no  data
> from  the default binding, but it seems stranger than that.
> The simplest example is co2:  The following stanza fails to produce
> anything:
>
> [[[dayco2]]]
> data_binding = "ecowitt_binding"
> co2
>
> However, the following works...
>
> [[[dayco2]]]
> data_binding = "ecowitt_binding"
> co2
> barometer
>
> Note that I am using the ecowitt binding for all data, and the ecowitt
> barometer fields are empty, so the plot I get is only for the CO2.
>
> So, from the combinations that I have tried,  it seems that
>
>1. you *can *do a plot containing data only in the secondary binding -
>sometimes
>2. you *cannot *do a plot if none of the data names exist in the
>default binding.
>3. At least one of the data types named inside square brackets *must
>exist in  the default binding*, irrespective of whichever binding
>supplies the data.
>4. I could not  trick it by specifying a known name, such as
>"inTemp" and then overriding with "data_type = co2"
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/1fe20e91-1de5-459c-8a45-77deb7c2753fn%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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zED62n_R_9zp4YHymAbCrgy5uN%3DU6JJ2jFci--%2Bc4mQPSw%40mail.gmail.com.

[weewx-user] Skin with multiple bindings - an odd restriction

['Cameron D' via weewx-user]

I have been running a dual-weewx setup for nearly a year, having added an 
Ecowitt system mainly for air quality, with a separate custom DB.
I have been running two separate skins, based on Seasons, with a few charts 
including binding from the other DB.
I thought I should really do it properly, and just set up a single skin 
with everything I wanted, but I am having problems when there are no data 
required from the default binding.

Initially I thought that it was failing *whenever *there was no  data from  
the default binding, but it seems stranger than that.
The simplest example is co2:  The following stanza fails to produce 
anything:

[[[dayco2]]]
data_binding = "ecowitt_binding"
co2

However, the following works...

[[[dayco2]]]
data_binding = "ecowitt_binding"
co2
barometer

Note that I am using the ecowitt binding for all data, and the ecowitt 
barometer fields are empty, so the plot I get is only for the CO2.

So, from the combinations that I have tried,  it seems that

   1. you *can *do a plot containing data only in the secondary binding - 
   sometimes
   2. you *cannot *do a plot if none of the data names exist in the default 
   binding.
   3. At least one of the data types named inside square brackets *must 
   exist in  the default binding*, irrespective of whichever binding 
   supplies the data.
   4. I could not  trick it by specifying a known name, such as 
   "inTemp" and then overriding with "data_type = co2"

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1fe20e91-1de5-459c-8a45-77deb7c2753fn%40googlegroups.com.