Updated external content (Jenkins build 809)
parent
1406770cc9
commit
105435f5a0
|
@ -73,6 +73,7 @@ The OpenUV Report thing that is retrieved has these channels:
|
|||
|
||||
The elevation channel will be used as an input in order to limit API queries to OpenUV. If not used,
|
||||
the binding will not consider it. When value is provided queries will only be issued if the elevation is > 0°.
|
||||
This is quite useful with a free OpenUV account (50 req/day included): in this case, and with the elevation channel configured, a 20 minutes refresh interval should be ok (in Europe the longest day is around 15 hours).
|
||||
|
||||
Thing can be extended with as many SafeExposure channels as needed for each skin type.
|
||||
|
||||
|
@ -82,13 +83,13 @@ demo.things:
|
|||
|
||||
```xtend
|
||||
Bridge openuv:openuvapi:local "OpenUV Api" [ apikey="xxxxYYYxxxx" ] {
|
||||
Thing uvreport city1 "UV In My City" [ location="52.5200066,13.4049540", refresh=10 ]{
|
||||
Thing uvreport city1 "UV In My City" [ location="52.5200066,13.4049540", refresh=20 ]{
|
||||
Channels:
|
||||
Type SafeExposure : Parents [
|
||||
index=3
|
||||
Type SafeExposure : parents [
|
||||
index="III"
|
||||
]
|
||||
Type SafeExposure : Childs [
|
||||
index=2
|
||||
Type SafeExposure : childs [
|
||||
index="II"
|
||||
]
|
||||
}
|
||||
}
|
||||
|
@ -98,9 +99,13 @@ Bridge openuv:openuvapi:local "OpenUV Api" [ apikey="xxxxYYYxxxx" ] {
|
|||
demo.items:
|
||||
|
||||
```xtend
|
||||
Number UVIndex "UV Index" {channel="openuv:uvreport:local:city1:UVIndex" }
|
||||
Number UVMax "UV Max" {channel="openuv:uvreport:local:city1:UVMaxEvent" }
|
||||
Number:ArealDensity Ozone "Ozone" {channel="openuv:uvreport:local:city1:Ozone" }
|
||||
|
||||
Number UVIndex "UV Index" { channel = "openuv:uvreport:local:city1:UVIndex" }
|
||||
Number UVMax "UV Max" { channel = "openuv:uvreport:local:city1:UVMaxEvent" }
|
||||
Number:ArealDensity Ozone "Ozone" { channel = "openuv:uvreport:local:city1:Ozone" }
|
||||
Number:Time SafeExp3 "Parents" { channel = "openuv:uvreport:local:city1:parents" }
|
||||
Number:Time SafeExp2 "Childs" { channel = "openuv:uvreport:local:city1:childs" }
|
||||
|
||||
```
|
||||
|
||||
astro.items:
|
||||
|
|
|
@ -138,13 +138,13 @@ Devices can be discovered automatically using an Inbox Scan after a gateway has
|
|||
|
||||
For any manually added device, you must configure:
|
||||
|
||||
- the associated gateway (`Parent Bridge` menu)
|
||||
- the `where` configuration parameter (`OpenWebNet Address`):
|
||||
- example for BUS/SCS:
|
||||
- light device with WHERE address Point to Point `A=2 PL=4` --> `where="24"`
|
||||
- light device with WHERE address Point to Point `A=03 PL=11` on local bus --> `where="0311#4#01"`
|
||||
- CEN scenario with WHERE address Point to Point `A=05 PL=12` --> `where="0512"`
|
||||
- CEN+ configured scenario `5`: add a `2` before --> `where="25"`
|
||||
- the associated gateway Thing (`Parent Bridge` menu)
|
||||
- the `where` configuration parameter (`OpenWebNet Address`): this is the OpenWebNet address configured for the device in the BTicino/Legrand system. This address can be found either on the device itself (Physical configuration, using jumpers in case of BUS) or through the MyHOME_Suite software (Virtual configuration). The address can have several formats depending on the device/system:
|
||||
- example for BUS/SCS system, address Point-to-point with Area (A) and Light-point (PL):
|
||||
- light device A=`2` (Area 2), PL=`4` (Light-point 4) --> `where="24"`
|
||||
- light device A=`03`, PL=`11` on local bus --> `where="0311#4#01"`
|
||||
- CEN scenario A=`05`, PL=`12` --> `where="0512"`
|
||||
- CEN+ scenario `5`: add a `2` before --> `where="25"`
|
||||
- Dry Contact or IR Interface `99`: add a `3` before --> `where="399"`
|
||||
- example for ZigBee devices: `where=765432101#9`. The ID of the device (ADDR part) is usually written in hexadecimal on the device itself, for example `ID 0074CBB1`: convert to decimal (`7654321`) and add `01#9` at the end to obtain `where=765432101#9`. For 2-unit switch devices (`zb_on_off_switch2u`), last part should be `00#9`.
|
||||
|
||||
|
@ -156,7 +156,7 @@ In BTicino MyHOME Thermoregulation (WHO=4) each **zone** has associated a thermo
|
|||
Thermo zones can be configured defining a `bus_thermo_zone` Thing for each zone with the following parameters:
|
||||
|
||||
- the `where` configuration parameter (`OpenWebNet Address`):
|
||||
- example BUS/SCS Thermo zone `1` --> `where="1"`
|
||||
- example BUS/SCS zone `1` --> `where="1"`
|
||||
- the `standAlone` configuration parameter (`boolean`, default: `true`): identifies if the zone is managed or not by a Central Unit (4 or 99 zones). `standAlone=true` means no Central Unit is present in the system.
|
||||
|
||||
Temperature sensors can be configured defining a `bus_thermo_sensor` Thing with the following parameters:
|
||||
|
|
|
@ -167,10 +167,6 @@
|
|||
<label>Wind Average Speed</label>
|
||||
<description>Average Wind Speed</description>
|
||||
<category>Wind</category>
|
||||
<tags>
|
||||
<tag>Measurement</tag>
|
||||
<tag>Wind</tag>
|
||||
</tags>
|
||||
<state pattern="%.1f %unit%" readOnly="true"/>
|
||||
</channel-type>
|
||||
<channel-type id="windSpeed" advanced="true">
|
||||
|
@ -189,10 +185,6 @@
|
|||
<label>Wind Gust</label>
|
||||
<description>Wind Gust</description>
|
||||
<category>Wind</category>
|
||||
<tags>
|
||||
<tag>Measurement</tag>
|
||||
<tag>Wind</tag>
|
||||
</tags>
|
||||
<state pattern="%.1f %unit%" readOnly="true"/>
|
||||
</channel-type>
|
||||
<channel-type id="windMaxGust" advanced="true">
|
||||
|
@ -218,10 +210,6 @@
|
|||
<label>Rain Today</label>
|
||||
<description>Rain since Midnight</description>
|
||||
<category>Rain</category>
|
||||
<tags>
|
||||
<tag>Measurement</tag>
|
||||
<tag>Rain</tag>
|
||||
</tags>
|
||||
<state pattern="%.2f %unit%" readOnly="true"/>
|
||||
</channel-type>
|
||||
<channel-type id="rainForWeek" advanced="true">
|
||||
|
@ -250,10 +238,6 @@
|
|||
<label>Last Updated Time</label>
|
||||
<description>Time of the last livedata scrape</description>
|
||||
<category>Time</category>
|
||||
<tags>
|
||||
<tag>Measurement</tag>
|
||||
<tag>Timestamp</tag>
|
||||
</tags>
|
||||
<state readOnly="true"/>
|
||||
</channel-type>
|
||||
</thing:thing-descriptions>
|
||||
|
|
Loading…
Reference in New Issue