OpenHAB
/
openhab-docs
mirror of https://github.com/openhab/openhab-docs.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Updated external content (Jenkins build 152)

pull/1380/head
openHAB Build Server 2020-12-24 12:16:21 +00:00
parent 4d6d11aed0
commit 490b374986
65 changed files with 10414 additions and 519 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.vuepress/thing-types.json
View File

File diff suppressed because one or more lines are too long

59
_addons_automation/jythonscripting/readme.md
View File

@ -3,7 +3,7 @@ id: jythonscripting
label: Jython Scripting
title: Jython Scripting - Automation
type: automation
description: "This addon provides a [Jython](https://www.jython.org/) 2.7.2 for use with scripted automation and eliminates the need to download Jython and create `EXTRA_JAVA_OPTS` entries for `bootclasspath`, `python.home` and `python.path`."
description: "This add-on provides [Jython](https://www.jython.org/) 2.7.2 that can be used as a scripting language within automation rules and which eliminates the need to download Jython and create `EXTRA_JAVA_OPTS` entries for `bootclasspath`, `python.home` and `python.path`."
since: 3x
install: auto
---
@ -14,6 +14,57 @@ install: auto
# Jython Scripting
This addon provides a [Jython](https://www.jython.org/) 2.7.2 for use with scripted automation and eliminates the need to download Jython and create `EXTRA_JAVA_OPTS` entries for `bootclasspath`, `python.home` and `python.path`.
The `python.home` System property will be set to the path of the add-on.
The `python.path` System property will be set to `$OPENHAB_CONF/automation/lib/python`, but any existing `python.path` will be appended to it.
This add-on provides [Jython](https://www.jython.org/) 2.7.2 that can be used as a scripting language within automation rules and which eliminates the need to download Jython and create `EXTRA_JAVA_OPTS` entries for `bootclasspath`, `python.home` and `python.path`.
The `python.home` system property is set to the path of the add-on.
The `python.path` system property is set to `$OPENHAB_CONF/automation/lib/python`, but any existing `python.path` will be appended to it.
## Creating Jython Scripts
When this add-on is installed, you can select Jython as a scripting language when creating a script action within the rule editor of the UI.
Alternatively, you can create scripts in the `automation/jsr223` configuration directory.
If you create an empty file called `test.py`, you will see a log line with information similar to:
```text
... [INFO ] [.a.m.s.r.i.l.ScriptFileWatcher:150 ] - Loading script 'test.py'
```
To enable debug logging, use the [console logging]({{base}}/administration/logging.html) commands to
enable debug logging for the automation functionality:
```text
log:set DEBUG org.openhab.core.automation
```
## Script Examples
Jython scripts provide access to almost all the functionality in an openHAB runtime environment.
As a simple example, the following script logs "Hello, World!".
Note that `print` will usually not work since the output has no terminal to display the text.
The openHAB server uses the [SLF4J](https://www.slf4j.org/) library for logging.
```python
from org.slf4j import LoggerFactory
LoggerFactory.getLogger("org.openhab.core.automation.examples").info("Hello world!")
```
Jython can [import Java classes](https://jython.readthedocs.io/en/latest/ModulesPackages/).
Depending on the openHAB logging configuration, you may need to prefix logger names with `org.openhab.core.automation` for them to show up in the log file (or you modify the logging configuration).
::: tip Note
Be careful with using wildcards when importing Java packages (e.g., `import org.slf4j.*`).
This will work in some cases, but it might not work in some situations.
It is best to use explicit imports with Java packages.
For more details, see the Jython documentation on
[Java package scanning](https://jython.readthedocs.io/en/latest/ModulesPackages/#java-package-scanning).
:::
The script uses the [LoggerFactory](https://www.slf4j.org/apidocs/org/slf4j/Logger.html)
to obtain a named logger and then logs a message like:
```text
... [INFO ] [.openhab.core.automation.examples:-2 ] - Hello world!
```

7
_addons_bindings/avmfritz/readme.md
View File

@ -175,15 +175,16 @@ The AIN (actor identification number) can be found in the FRITZ!Box interface ->
| Channel Type ID | Item Type | Description | Available on thing |
|-----------------|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|
| incoming_call | Call | Details about incoming call. | FRITZ!Box |
| outgoing_call | Call | Details about outgoing call. | FRITZ!Box |
| active_call | Call | Details about active call. | FRITZ!Box |
| incoming_call | Call | Details about incoming call. %2$s contains the external, calling number, %1$s is the internal, receiving number. | FRITZ!Box |
| outgoing_call | Call | Details about outgoing call. %1$s contains the external, called number, %2$s is the internal, calling number. | FRITZ!Box |
| active_call | Call | Details about active call. %1$s contains the external, calling number, %2$s is empty. | FRITZ!Box |
| call_state | String | Details about current call state, either IDLE, RINGING, DIALING or ACTIVE. | FRITZ!Box |
| apply_template | String | Apply template for device(s) (channel's state options contains available templates, for an alternative way see the description below) - FRITZ!OS 7 | FRITZ!Box, FRITZ!Powerline 546E |
| mode | String | States the mode of the device (MANUAL/AUTOMATIC/VACATION) | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E, FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| locked | Contact | Device is locked for switching over external sources (OPEN/CLOSE) | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E, FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| device_locked | Contact | Device is locked for switching manually (OPEN/CLOSE) - FRITZ!OS 6.90 | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E, FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| temperature | Number:Temperature | Current measured temperature | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!DECT Repeater 100, FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT, FRITZ!DECT 440 |
| humidity | Number:Dimensionless | Current measured humidity - FRITZ!OS 7.24 | FRITZ!DECT 440 |
| energy | Number:Energy | Accumulated energy consumption | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E |
| power | Number:Power | Current power consumption | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E |
| voltage | Number:ElectricPotential | Current voltage - FRITZ!OS 7 | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E |

1
_addons_bindings/icalendar/readme.md
View File

@ -73,6 +73,7 @@ They are all read-only.
| next_title | String | Title of the next event |
| next_start | DateTime | Start of the next event |
| next_end | DateTime | End of the next event |
| last_update | DateTime | The time and date of the last successful update of the calendar |
### Channels for `eventfilter`

1270
_addons_bindings/miio/readme.md
View File

File diff suppressed because it is too large Load Diff

31
_addons_bindings/openweathermap/readme.md
View File

@ -337,12 +337,12 @@ DateTime localLastMeasurement "Timestamp of Last Measurement [%1$tY-%1$tm-%1$tdT
DateTime localTodaySunrise "Todays Sunrise [%1$tY-%1$tm-%1$tdT%1$tH:%1$tM:%1$tS]" <time> { channel="openweathermap:onecall:api:local:current#sunrise" }
DateTime localTodaySunset "Todays Sunset [%1$tY-%1$tm-%1$tdT%1$tH:%1$tM:%1$tS]" <time> { channel="openweathermap:onecall:api:local:current#sunset" }
String localCurrentCondition "Current Condition [%s]" <sun_clouds> { channel="openweathermap:onecall:api:local:current#condition" }
Image localCurrentConditionIcon "Icon" { channel="openweathermap:onecall:api:local:current#Icon" }
Image localCurrentConditionIcon "Icon" { channel="openweathermap:onecall:api:local:current#icon" }
Number:Temperature localCurrentTemperature "Current Temperature [%.1f %unit%]" <temperature> { channel="openweathermap:onecall:api:local:current#temperature" }
Number:Temperature localCurrentApparentTemperature "Current Apparent Temperature [%.1f %unit%]" <temperature> { channel="openweathermap:onecall:api:local:current#apparent-temperature" }
Number:Pressure localCurrentPressure "Current barometric Pressure [%.1f %unit%]" <pressure> { channel="openweathermap:onecall:api:local:current#pressure" }
Number:Dimensionless localCurrentHumidity "Current atmospheric Humidity [%d %unit%]" <humidity> { channel="openweathermap:onecall:api:local:current#humidity" }
Number:Temperature localCurrentDewpoint "Current Dew-point [%.1f %unit%]" <Temperature> { channea="openweathermap:onecall:api:local:eurrent#dew-point" }
Number:Temperature localCurrentDewpoint "Current dew point [%.1f %unit%]" <Temperature> { channel="openweathermap:onecall:api:local:current#dew-point" }
Number:Speed localCurrentWindSpeed "Current wind Speed [%.1f km/h]" <wind> { channel="openweathermap:onecall:api:local:current#wind-speed" }
Number:Angle localCurrentWindDirection "Current wind Direction [%d %unit%]" <wind> { channel="openweathermap:onecall:api:local:current#wind-direction" }
Number:Speed localCurrentGustSpeed "Current Gust Speed [%.1f km/h]" <wind> { channel="openweathermap:onecall:api:local:current#gust-speed" }
@ -364,7 +364,7 @@ Number:Temperature localHours01Temperature "Temperature [%.1f %unit%]" <temperat
Number:Temperature localHours01ApparentTemperature "Apparent temperature [%.1f %unit%]" <temperature> { channel="openweathermap:onecall:api:local:forecastHours01#apparent-temperature" }
Number:Pressure localHours01Pressure "Barometric pressure [%.1f %unit%]" <pressure> { channel="openweathermap:onecall:api:local:forecastHours01#pressure" }
Number:Dimensionless localHours01Humidity "Atmospheric humidity [%d %unit%]" <humidity> { channel="openweathermap:onecall:api:local:forecastHours01#humidity" }
Number:Temperature localHours01Dewpoint "Dew point [%.1f %unit%]" <Temperature> { channea="openweathermap:onecall:api:local:eurrent#dew-point" }
Number:Temperature localHours01Dewpoint "Dew point [%.1f %unit%]" <Temperature> { channel="openweathermap:onecall:api:local:current#dew-point" }
Number:Speed localHours01WindSpeed "Wind speed [%.1f km/h]" <wind> { channel="openweathermap:onecall:api:local:forecastHours01#wind-speed" }
Number:Angle localHours01WindDirection "Wind direction [%d %unit%]" <wind> { channel="openweathermap:onecall:api:local:forecastHours01#wind-direction" }
Number:Speed localHours01GustSpeed "Gust speed [%.1f km/h]" <wind> { channel="openweathermap:onecall:api:local:forecastHours01#gust-speed" }
@ -380,7 +380,7 @@ Number:Temperature localHours48Temperature "Temperature [%.1f %unit%]" <temperat
Number:Temperature localHours48ApparentTemperature "Apparent temperature [%.1f %unit%]" <temperature> { channel="openweathermap:onecall:api:local:forecastHours48#apparent-temperature" }
Number:Pressure localHours48Pressure "Barometric pressure [%.1f %unit%]" <pressure> { channel="openweathermap:onecall:api:local:forecastHours48#pressure" }
Number:Dimensionless localHours48Humidity "Atmospheric humidity [%d %unit%]" <humidity> { channel="openweathermap:onecall:api:local:forecastHours48#humidity" }
Number:Temperature localHours48Dewpoint "Dew point [%.1f %unit%]" <Temperature> { channea="openweathermap:onecall:api:local:eurrent#dew-point" }
Number:Temperature localHours48Dewpoint "Dew point [%.1f %unit%]" <Temperature> { channel="openweathermap:onecall:api:local:current#dew-point" }
Number:Speed localHours48WindSpeed "Wind speed [%.1f km/h]" <wind> { channel="openweathermap:onecall:api:local:forecastHours48#wind-speed" }
Number:Angle localHours48WindDirection "Wind direction [%d %unit%]" <wind> { channel="openweathermap:onecall:api:local:forecastHours48#wind-direction" }
Number:Speed localHours48GustSpeed "Gust speed [%.1f km/h]" <wind> { channel="openweathermap:onecall:api:local:forecastHours48#gust-speed" }
@ -404,16 +404,15 @@ Number:Temperature localTodayEveningApparent "Evening apparent Temperature [%.1f
Number:Temperature localTodayNightApparent "Night apparent Temperature [%.1f %unit%]" <temperature> { channel="openweathermap:onecall:api:local:forecastToday#apparent-night" }
Number:Pressure localTodayPressure "Barometric pressure [%.1f %unit%]" <pressure> { channel="openweathermap:onecall:api:local:forecastToday#pressure" }
Number:Dimensionless localTodayHumidity "Atmospheric humidity [%d %unit%]" <humidity> { channel="openweathermap:onecall:api:local:forecastToday#humidity" }
Number:Temperature localTodayDewpoint "Dew point [%.1f %unit%]" <Temperature> { channea="openweathermap:onecall:api:local:forecastToday#dew-point" }
Number:Temperature localTodayDewpoint "Dew point [%.1f %unit%]" <Temperature> { channel="openweathermap:onecall:api:local:forecastToday#dew-point" }
Number:Speed localTodayWindSpeed "Wind speed [%.1f km/h]" <wind> { channel="openweathermap:onecall:api:local:forecastToday#wind-speed" }
Number:Angle localTodayWindDirection "Wind direction [%d %unit%]" <wind> { channel="openweathermap:onecall:api:local:forecastToday#wind-direction" }
Number:Speed localTodayGustSpeed "Gust speed [%.1f km/h]" <wind> { channel="openweathermap:onecall:api:local:forecastToday#gust-speed" }
Number:Dimensionless localTodayPrecipProbability "Precipitation probability [%.1f]" { channel="openweathermap:onecall:api:local:forecastToday#probability" }
Number:Dimensionless localTodayPrecipProbability "Precipitation probability [%.1f]" { channel="openweathermap:onecall:api:local:forecastToday#precip-probability" }
Number:Dimensionless localTodayCloudiness "Cloudiness [%d %unit%]" <clouds> { channel="openweathermap:onecall:api:local:forecastToday#cloudiness" }
Number:Dimensionless localTodayUvindex "Current UV Index [%d]" { channel="openweathermap:onecall:api:local:forecastToday#uvindex" }
Number:Length localTodayRainVolume "Rain volume [%.1f %unit%]" <rain> { channel="openweathermap:onecall:api:local:forecastToday#rain" }
Number:Length localTodaySnowVolume "Snow volume [%.1f %unit%]" <snow> { channel="openweathermap:onecall:api:local:forecastToday#snow" }
Number:Length localTodayVisibility "Visibility [%.1f km]" <visibility> { channel="openweathermap:onecall:api:local:forecastToday#visibility" }
DateTime localTomorrowTimestamp "Timestamp of forecast [%1$tY-%1$tm-%1$td]" <time> { channel="openweathermap:onecall:api:local:forecastTomorrow#time-stamp" }
DateTime localTomorrowSunrise "Tomorrow Sunrise [%1$tY-%1$tm-%1$tdT%1$tH:%1$tM:%1$tS]" <time> { channel="openweathermap:onecall:api:local:forecastTomorrow#sunrise" }
@ -432,16 +431,15 @@ Number:Temperature localTomorrowEveningApparent "Evening apparent Temperature [%
Number:Temperature localTomorrowNightApparent "Night apparent Temperature [%.1f %unit%]" <temperature> { channel="openweathermap:onecall:api:local:forecastTomorrow#apparent-night" }
Number:Pressure localTomorrowPressure "Barometric pressure [%.1f %unit%]" <pressure> { channel="openweathermap:onecall:api:local:forecastTomorrow#pressure" }
Number:Dimensionless localTomorrowHumidity "Atmospheric humidity [%d %unit%]" <humidity> { channel="openweathermap:onecall:api:local:forecastTomorrow#humidity" }
Number:Temperature localTomorrowDewpoint "Dew point [%.1f %unit%]" <Temperature> { channea="openweathermap:onecall:api:local:forecastTomorrow#dew-point" }
Number:Temperature localTomorrowDewpoint "Dew point [%.1f %unit%]" <Temperature> { channel="openweathermap:onecall:api:local:forecastTomorrow#dew-point" }
Number:Speed localTomorrowWindSpeed "Wind speed [%.1f km/h]" <wind> { channel="openweathermap:onecall:api:local:forecastTomorrow#wind-speed" }
Number:Angle localTomorrowWindDirection "Wind direction [%d %unit%]" <wind> { channel="openweathermap:onecall:api:local:forecastTomorrow#wind-direction" }
Number:Speed localTomorrowGustSpeed "Gust speed [%.1f km/h]" <wind> { channel="openweathermap:onecall:api:local:forecastTomorrow#gust-speed" }
Number:Dimensionless localTomorrowPrecipProbability "Precipitation probability [%.1f]" { channel="openweathermap:onecall:api:local:forecastTomorrow#probability" }
Number:Dimensionless localTomorrowPrecipProbability "Precipitation probability [%.1f]" { channel="openweathermap:onecall:api:local:forecastTomorrow#precip-probability" }
Number:Dimensionless localTomorrowCloudiness "Cloudiness [%d %unit%]" <clouds> { channel="openweathermap:onecall:api:local:forecastTomorrow#cloudiness" }
Number:Dimensionless localTomorrowUvindex "Current UV Index [%d]" { channel="openweathermap:onecall:api:local:forecastTomorrow#uvindex" }
Number:Length localTomorrowRainVolume "Rain volume [%.1f %unit%]" <rain> { channel="openweathermap:onecall:api:local:forecastTomorrow#rain" }
Number:Length localTomorrowSnowVolume "Snow volume [%.1f %unit%]" <snow> { channel="openweathermap:onecall:api:local:forecastTomorrow#snow" }
Number:Length localTomorrowVisibility "Visibility [%.1f km]" <visibility> { channel="openweathermap:onecall:api:local:forecastTomorrow#visibility" }
DateTime localDay6Timestamp "Timestamp of forecast [%1$tY-%1$tm-%1$td]" <time> { channel="openweathermap:onecall:api:local:forecastDay6#time-stamp" }
DateTime localDay6Sunrise "Sunrise [%1$tY-%1$tm-%1$tdT%1$tH:%1$tM:%1$tS]" <time> { channel="openweathermap:onecall:api:local:forecastDay6#sunrise" }
@ -460,16 +458,15 @@ Number:Temperature localDay6EveningApparent "Evening apparent Temperature [%.1f
Number:Temperature localDay6NightApparent "Night apparent Temperature [%.1f %unit%]" <temperature> { channel="openweathermap:onecall:api:local:forecastDay6#apparent-night" }
Number:Pressure localDay6Pressure "Barometric pressure [%.1f %unit%]" <pressure> { channel="openweathermap:onecall:api:local:forecastDay6#pressure" }
Number:Dimensionless localDay6Humidity "Atmospheric humidity [%d %unit%]" <humidity> { channel="openweathermap:onecall:api:local:forecastDay6#humidity" }
Number:Temperature localDay6Dewpoint "Dew point [%.1f %unit%]" <Temperature> { channea="openweathermap:onecall:api:local:forecastDay6#dew-point" }
Number:Temperature localDay6Dewpoint "Dew point [%.1f %unit%]" <Temperature> { channel="openweathermap:onecall:api:local:forecastDay6#dew-point" }
Number:Speed localDay6WindSpeed "Wind speed [%.1f km/h]" <wind> { channel="openweathermap:onecall:api:local:forecastDay6#wind-speed" }
Number:Angle localDay6WindDirection "Wind direction [%d %unit%]" <wind> { channel="openweathermap:onecall:api:local:forecastDay6#wind-direction" }
Number:Speed localDay6GustSpeed "Gust speed [%.1f km/h]" <wind> { channel="openweathermap:onecall:api:local:forecastDay6#gust-speed" }
Number:Dimensionless localDay6PrecipProbability "Precipitation probability [%.1f]" { channel="openweathermap:onecall:api:local:forecastDay6#probability" }
Number:Dimensionless localDay6PrecipProbability "Precipitation probability [%.1f]" { channel="openweathermap:onecall:api:local:forecastDay6#precip-probability" }
Number:Dimensionless localDay6Cloudiness "Cloudiness [%d %unit%]" <clouds> { channel="openweathermap:onecall:api:local:forecastDay6#cloudiness" }
Number:Dimensionless localDay6Uvindex "Current UV Index [%d]" { channel="openweathermap:onecall:api:local:forecastDay6#uvindex" }
Number:Length localDay6RainVolume "Rain volume [%.1f %unit%]" <rain> { channel="openweathermap:onecall:api:local:forecastDay6#rain" }
Number:Length localDay6SnowVolume "Snow volume [%.1f %unit%]" <snow> { channel="openweathermap:onecall:api:local:forecastDay6#snow" }
Number:Length localDay6Visibility "Visibility [%.1f km]" <visibility> { channel="openweathermap:onecall:api:local:forecastDay6#visibility" }
DateTime localHistory1LastMeasurement "Timestamp of history [%1$tY-%1$tm-%1$td]" <time> { channel="openweathermap:onecall-history:api:local-history:history#time-stamp" }
DateTime localHistory1Sunrise "Sunrise [%1$tY-%1$tm-%1$tdT%1$tH:%1$tM:%1$tS]" <time> { channel="openweathermap:onecall-history:api:local-history:history#sunrise" }
@ -480,7 +477,7 @@ Number:Temperature localHistory1Temperature "Temperature [%.1f %unit%]" <tempe
Number:Temperature localHistory1ApparentTemperature "Apparent temperature [%.1f %unit%]" <temperature> { channel="openweathermap:onecall-history:api:local-history:history#apparent-temperature" }
Number:Pressure localHistory1Pressure "Barometric pressure [%.1f %unit%]" <pressure> { channel="openweathermap:onecall-history:api:local-history:history#pressure" }
Number:Dimensionless localHistory1Humidity "Atmospheric humidity [%d %unit%]" <humidity> { channel="openweathermap:onecall-history:api:local-history:history#humidity" }
Number:Temperature localHistory1Dewpoint "Dew point [%.1f %unit%]" <Temperature> { channea="openweathermap:onecall-history:api:local-history:eurrent#dew-point" }
Number:Temperature localHistory1Dewpoint "Dew point [%.1f %unit%]" <Temperature> { channel="openweathermap:onecall-history:api:local-history:current#dew-point" }
Number:Speed localHistory1WindSpeed "Wind speed [%.1f km/h]" <wind> { channel="openweathermap:onecall-history:api:local-history:history#wind-speed" }
Number:Angle localHistory1WindDirection "Wind direction [%d %unit%]" <wind> { channel="openweathermap:onecall-history:api:local-history:history#wind-direction" }
Number:Speed localHistory1GustSpeed "Gust speed [%.1f km/h]" <wind> { channel="openweathermap:onecall-history:api:local-history:history#gust-speed" }
@ -499,7 +496,7 @@ Number:Temperature localHistory1Hours01Temperature "Minimum temperature [%.1f %u
Number:Temperature localHistory1Hours01ApparentTemperature "Minimum temperature [%.1f %unit%]" <temperature> { channel="openweathermap:onecall-history:api:local-history:historyHours01#apparent-temperature" }
Number:Pressure localHistory1Hours01Pressure "Barometric pressure [%.1f %unit%]" <pressure> { channel="openweathermap:onecall-history:api:local-history:historyHours01#pressure" }
Number:Dimensionless localHistory1Hours01Humidity "Atmospheric humidity [%d %unit%]" <humidity> { channel="openweathermap:onecall-history:api:local-history:historyHours01#humidity" }
Number:Temperature localHistory1Hours01Dewpoint "Dew point [%.1f %unit%]" <Temperature> { channea="openweathermap:onecall-history:api:local-history:eurrent#dew-point" }
Number:Temperature localHistory1Hours01Dewpoint "Dew point [%.1f %unit%]" <Temperature> { channel="openweathermap:onecall-history:api:local-history:current#dew-point" }
Number:Speed localHistory1Hours01WindSpeed "Wind speed [%.1f km/h]" <wind> { channel="openweathermap:onecall-history:api:local-history:historyHours01#wind-speed" }
Number:Angle localHistory1Hours01WindDirection "Wind direction [%d %unit%]" <wind> { channel="openweathermap:onecall-history:api:local-history:historyHours01#wind-direction" }
Number:Speed localHistory1Hours01GustSpeed "Gust speed [%.1f km/h]" <wind> { channel="openweathermap:onecall-history:api:local-history:historyHours01#gust-speed" }
@ -518,7 +515,7 @@ Number:Temperature localHistory1Hours24Temperature "Minimum temperature [%.1f %u
Number:Temperature localHistory1Hours24ApparentTemperature "Minimum temperature [%.1f %unit%]" <temperature> { channel="openweathermap:onecall-history:api:local-history:historyHours24#apparent-temperature" }
Number:Pressure localHistory1Hours24Pressure "Barometric pressure [%.1f %unit%]" <pressure> { channel="openweathermap:onecall-history:api:local-history:historyHours24#pressure" }
Number:Dimensionless localHistory1Hours24Humidity "Atmospheric humidity [%d %unit%]" <humidity> { channel="openweathermap:onecall-history:api:local-history:historyHours24#humidity" }
Number:Temperature localHistory1Hours24Dewpoint "Dew point [%.1f %unit%]" <Temperature> { channea="openweathermap:onecall-history:api:local-history:eurrent#dew-point" }
Number:Temperature localHistory1Hours24Dewpoint "Dew point [%.1f %unit%]" <Temperature> { channel="openweathermap:onecall-history:api:local-history:current#dew-point" }
Number:Speed localHistory1Hours24WindSpeed "Wind speed [%.1f km/h]" <wind> { channel="openweathermap:onecall-history:api:local-history:historyHours24#wind-speed" }
Number:Angle localHistory1Hours24WindDirection "Wind direction [%d %unit%]" <wind> { channel="openweathermap:onecall-history:api:local-history:historyHours24#wind-direction" }
Number:Speed localHistory1Hours24GustSpeed "Gust speed [%.1f km/h]" <wind> { channel="openweathermap:onecall-history:api:local-history:historyHours24#gust-speed" }
@ -747,4 +744,4 @@ sitemap demo label="OpenWeatherMapOneCall" {
}
}
```
```

8
_addons_bindings/smhi/readme.md
View File

@ -41,18 +41,24 @@ You can also choose for which hours and which days you would like to get forecas
## Channels
The channels are the same for all forecasts:
The channels are the same for all forecasts, but the daily forecast provides some additional aggregated values.
For the other daily forecast channels, the values are for 12:00 UTC.
#### Basic channels
| channel | type | description |
|----------|--------|------------------------------|
| Temperature | Number:Temperature | Temperature in Celsius |
| Max Temperature | Number:Temperature | Highest temperature of the day (daily forecast only) |
| Min Temperature | Number:Temperature | Lowest temperature of the day (daily forecast only) |
| Wind direction | Number:Angle | Wind direction in degrees |
| Wind Speed | Number:Speed | Wind speed in m/s |
| Max Wind Speed | Number:Speed | Highest wind speed of the day (daily forecast only) |
| Min Wind Speed | Number:Speed | Lowest wind speed of the day (daily forecast only) |
| Wind gust speed | Number:Speed | Wind gust speed in m/s |
| Minimum precipitation | Number:Speed | Minimum precipitation intensity in mm/h |
| Maximum precipitation | Number:Speed | Maximum precipitation intensity in mm/h |
| Total precipitation | Number:Length | Total amount of precipitation during the day, in mm (daily forecast only) |
| Precipitation category* | Number | Type of precipitation |
| Air pressure | Number:Pressure | Air pressure in hPa |
| Relative humidity | Number:Dimensionless | Relative humidity in percent |

220
_addons_bindings/zwave/doc/act/zrf113_1_100.md Normal file
View File

@ -0,0 +1,220 @@
---
layout: documentation
title: ZRF113 - ZWave
---
{% include base.html %}
# ZRF113 Isolated Contact Fixture Module Release 1.1
This describes the Z-Wave device *ZRF113*, manufactured by *ACT - Advanced Control Technologies* with the thing type UID of ```act_zrf113_01_100```.
This version of the device is limited to firmware versions above 1.100
The device is in the category of *Power Outlet*, defining Small devices to be plugged into a power socket in a wall which stick there.
![ZRF113 product image](https://opensmarthouse.org/zwavedatabase/1331/image/)
The ZRF113 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data between other devices in the mesh network.
## Overview
The ZRF113 Isolated Contact Fixture Module is a component of the HomePro lighting control system. Wire the Isolated Contact Fixture Module according to the diagram above and program it from the Wireless Controller to operate loads.  Inclusion of this Switch on the ZTH100 Wireless Controller menu allows remote ON/OFF control of load connected.
This Isolated Contact Fixture Module is designed to work with other Z-Wave enabled devices. Z-Wave nodes of other types can be included on the network and will also act as repeaters if they support this function.  
As part of a Z-Wave network, the ZRF113 will also act as a wireless repeater to insure that commands intended for another device in the network are received. This is useful when the device would otherwise be out of the radio range of the wireless controller.
There are no field repairable assemblies on this unit.. If service is needed, the unit must be returned where purchased.
DANGER! SHOCK HAZARD. Read and understand these instructions before installing. This device is intended for installation in accordance with the National Electric code and local regulations in the United States, or the Canadian Electrical Code and local regulations in Canada. It is recommended that a qualified electrician perform this installation.
**INSTALLATION**
Wire this module in series with a 20 amp (maximum) load according to the diagram above. If AS101’s are used they must be wired to the same line (or neutral) also wired to the master unit as well as the load being controlled, and not wired to any other neutral. If multiple neutral wires are tied together in one box, separate the neutral wires to preserve the integrity of the ZRF113 circuit. Caution! Do not wire unit “live” (with power on the circuit) and do notallow the yellow wire to contact line voltage, neutral or ground or you will damage the device. See the ZTH100 Wireless Controller operating instructions to include this module under the command of the Wireless Controller.
**NOTE **
If you have trouble adding the ZRF113 to a group it may be that the Home ID and Node ID were not cleared from it after testing. You must first “RESET UNIT” with your controller to remove it from the network. If using the ZTH100 select “SETUP” and scroll to “RESET UNIT”
Although adding it to a group includes it in the network, removing it from a group does not remove it from the network. If removed from a group, it functions only as a repeater.
With the Wireless Controller, the ZRF113 can be switched ON and OFF remotely, and can be included (or excluded) in groups of lights that operate at the same time (a group can also be a single module), and in scenes that set a lighting mood.
Note that the Associations, and possibly other features, vary depending on the release.  The original version 1 units used 4 associations.  This release, release 1.1, uses 2.
**SPECIFICATIONS**
Power: 120 VAC, 50/60 Hz
Signal (Frequency): 908.42 MHz
Maximum Load
   Isolated Contacts: 20 amps maximum General Purpose, 277 VAC, 10 FLA, 60 LRA, 250 VAC,
   Motor: 1 H.P. maximum, 120/240 VAC
   Incandescent: TV8 (Tungsten), 120 VAC, 960W maximum
Range: Up to 100 feet line of sight between the Wireless Controller and /or the closest HomePro Receiver Module
### Inclusion Information
STEP 1.. Prepare the Controller to include a unit to the network by adding it to a group (method of adding a node to the network). Refer to controller instructions. If using a ZTH100, push MENU button, select GROUPS, push OK button, see ADD UNIT TO GROUP displayed, push OK button.
STEP 2. The ZRF113 must be in its permanently installed location. Tap the button on the face of the ZRF113 once. Some Z-Wave products include the module on the release of the button.
STEP 3. You should see an indication on your Controller that the “DEVICE WAS INCLUDED” in the network.
### Exclusion Information
“RESET UNIT” with your controller to remove it from the network. If using the ZTH100 select “SETUP” and scroll to “RESET UNIT”
Although adding it to a group includes it in the network, removing it from a group does not remove it from the network. If removed from a group, it functions only as a repeater.
### General Usage Information
## Channels
The following table summarises the channels available for the ZRF113 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Switch | switch_binary | switch_binary | Switch | Switch |
| Dimmer | switch_dimmer | switch_dimmer | DimmableLight | Dimmer |
### Switch
Switch the power on and off.
The ```switch_binary``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Dimmer
The brightness channel allows to control the brightness of a light.
It is also possible to switch the light on and off.
The ```switch_dimmer``` channel is of type ```switch_dimmer``` and supports the ```Dimmer``` item and is in the ```DimmableLight``` category.
## Device Configuration
The following table provides a summary of the 2 configuration parameters available in the ZRF113.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|-------|-------|-------------|
| 1 | Configuration Parameter 1 | Set Ignore Start Level Bit When Transmitting Dim Command |
| 19 | Configuration Parameter 19 | LED Transmission Indication |
| | Switch All Mode | Set the mode for the switch when receiving SWITCH ALL commands |
### Parameter 1: Configuration Parameter 1
Set Ignore Start Level Bit When Transmitting Dim Command
The ZRF113 can send Dim commands to Z-Wave enabled dimmers. The Dim command has a start level embedded in it. A dimmer receiving this command will start dimming from that start level. However, the command also has a bit that indicates whether the dimmer should ignore the start level. If the bit is set to 1, the dimmer will ignore the start level and instead start dimming from its current level. To clear this bit, configure this parameter to the value of 0.
NOTE: Each Configuration Parameter can be set to its default by setting the default bit in the Configuration Set command. See your controller’s instructions on how to do this (and if it supports it). All Configuration commands will be reset to their default state when the ZRF113 is excluded from the Z-Wave network by using the controller to reset the node (on the ZTH100 select “SETUP” and scroll to “RESET UNIT”).This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
The following option values may be configured, in addition to values in the range 0 to 1 -:
| Value | Description |
|--------|-------------|
| 0 | Don't Ignore Dimmer Command Start Level Bit |
| 1 | Ignore Dimmer Command Start Level Bit (Default) |
The manufacturer defined default value is ```1``` (Ignore Dimmer Command Start Level Bit (Default)).
This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```.
### Parameter 19: Configuration Parameter 19
LED Transmission Indication
The ZRF113 will flicker its LED when it is transmitting to any of its groups. This flickering can be set to not flicker at all (set to 0), to flicker the entire time it is transmitting (set to 1), or to flicker for only 1 second when it begins transmitting (set to 2). By default, the ZRF113 is set to flicker for only 1 second.
NOTE: Each Configuration Parameter can be set to its default by setting the default bit in the Configuration Set command. See your controller’s instructions on how to do this (and if it supports it). All Configuration commands will be reset to their default state when the ZRF113 is excluded from the Z-Wave network by using the controller to reset the node (on the ZTH100 select “SETUP” and scroll to “RESET UNIT”).This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
The following option values may be configured, in addition to values in the range 0 to 2 -:
| Value | Description |
|--------|-------------|
| 0 | No Flicker |
| 1 | Flicker while transmitting |
| 2 | Flicker for 1 second (Default) |
The manufacturer defined default value is ```2``` (Flicker for 1 second (Default)).
This parameter has the configuration ID ```config_19_1``` and is of type ```INTEGER```.
### Switch All Mode
Set the mode for the switch when receiving SWITCH ALL commands.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Exclude from All On and All Off groups |
| 1 | Include in All On group |
| 2 | Include in All Off group |
| 255 | Include in All On and All Off groups |
This parameter has the configuration ID ```switchall_mode``` and is of type ```INTEGER```.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The ZRF113 supports 3 association groups.
### Group 1: Lifeline
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation.
Association group 1 supports 5 nodes.
### Group 2: Group 2
Auxilliary Switch 2 Tap
If you associate a Z-Wave device into Group 2, you can turn that device on and off by tapping the top or bottom of the auxiliary switch twice. You can brighten or dim devices by tapping the top or bottom of the auxiliary switch once and then holding the switch down. The load attached to the ZRF113 is not affected.
A NOTE ABOUT DIMMERS IN A GROUP: If you combine Z-Wave enabled dimmers and other types of ZWave devices in a group, place a Z-Wave enabled dimmer into the empty group first to ensure that the dimming operates correctly.
Association group 2 supports 5 nodes.
### Group 3: Group 3
Auxilliary Switch 3 Tap
If you associate a Z-Wave device into Group 3, you can turn that device on and off by tapping the top or bottom of the auxiliary switch three times . You can brighten or dim devices by tapping the top or bottom of the auxiliary switch twice and then hold the top down for brighten or bottom for dim (bottom only if AS001). The load attached to the ZRF113 is not affected.
A NOTE ABOUT DIMMERS IN A GROUP: If you combine Z-Wave enabled dimmers and other types of ZWave devices in a group, place a Z-Wave enabled dimmer into the empty group first to ensure that the dimming operates correctly.
Association group 3 supports 5 nodes.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| |
| COMMAND_CLASS_SWITCH_MULTILEVEL_V1| |
| COMMAND_CLASS_SWITCH_ALL_V1| |
| COMMAND_CLASS_BASIC_WINDOW_COVERING_V1| |
| COMMAND_CLASS_CONFIGURATION_V1| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_ASSOCIATION_V1| |
| COMMAND_CLASS_VERSION_V1| |
### Documentation Links
* [Please allow me access to add a device to the Z-Wave DB](https://opensmarthouse.org/zwavedatabase/1331/reference/ZRF113-S100_instr.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1331).

161
_addons_bindings/zwave/doc/eco/wirelesssiren_0_0.md Normal file
View File

@ -0,0 +1,161 @@
---
layout: documentation
title: Wireless Siren - ZWave
---
{% include base.html %}
# Wireless Siren Z-Wave plus plug in siren
This describes the Z-Wave device *Wireless Siren*, manufactured by *Ecolink* with the thing type UID of ```eco_wirelesssiren_00_000```.
The device is in the category of *Siren*, defining Siren used by Alarm systems.
![Wireless Siren product image](https://opensmarthouse.org/zwavedatabase/1263/image/)
The Wireless Siren supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data between other devices in the mesh network.
## Overview
The device is as simple to use as plugging in a wall outlet.
The device can create 4 independent tones for different alerts to the user. These could include but are not limited to: Security Alarm, entry/exit, smoke/Fire, temperature and more. The Z-Wave Plus Siren can also be used as a Z-Wave Plus network extension.
### Inclusion Information
Plug in the Z-Wave Siren and verify a single beep sound is heard.
The LED on the front of the unit will turn off if successful included into a network.
### Exclusion Information
1.  Plug in the Z-Wave Siren.
2. Unplug and re-plug in your Z-Wave Plus Siren.  
The device will play a long beep and the LED will begin to breathe if the device is successfully removed from the network.
### General Usage Information
## Channels
The following table summarises the channels available for the Wireless Siren -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Switch | switch_binary | switch_binary | Switch | Switch |
| Switch 1 | switch_binary1 | switch_binary | Switch | Switch |
| Switch 2 | switch_binary2 | switch_binary | Switch | Switch |
| Switch 3 | switch_binary3 | switch_binary | Switch | Switch |
| Switch 4 | switch_binary4 | switch_binary | Switch | Switch |
### Switch
Switch the power on and off.
The ```switch_binary``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Switch 1
Switch the power on and off.
The ```switch_binary1``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Switch 2
Switch the power on and off.
The ```switch_binary2``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Switch 3
Switch the power on and off.
The ```switch_binary3``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Switch 4
Switch the power on and off.
The ```switch_binary4``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
## Device Configuration
The device has no configuration parameters defined.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The Wireless Siren supports 1 association group.
### Group 1: Lifeline
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation.
Association group 1 supports 5 nodes.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_MULTI_CHANNEL_V2| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| |
#### Endpoint 1
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
#### Endpoint 2
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
#### Endpoint 3
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
#### Endpoint 4
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
### Documentation Links
* [Manual](https://opensmarthouse.org/zwavedatabase/1263/reference/0_-_Ecolink_Siren_Z-Wave_Plus_Manual_standard.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1263).

4
_addons_bindings/zwave/doc/fibaro/fgd211_0_0.md
View File

@ -36,6 +36,10 @@ The Dimmer enters the mode of inclusion after a quick pressing three times the p
The Dimmer enters the mode of exclusion after a quick pressing three times the push-button connected to S1 terminal or push-button B located inside the housing. For bi-stable switch perform 3 position changes
### General Usage Information
## Channels
The following table summarises the channels available for the FGD211 -:

6
_addons_bindings/zwave/doc/ge/zw4008_0_0.md
View File

@ -10,7 +10,7 @@ This describes the Z-Wave device *43072/ZW4008DV*, manufactured by *Jasco Produc
The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch.
![43072/ZW4008DV product image](https://www.cd-jackson.com/zwave_device_uploads/1155/1155_default.jpg)
![43072/ZW4008DV product image](https://opensmarthouse.org/zwavedatabase/1155/image/)
The 43072/ZW4008DV supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data between other devices in the mesh network.
@ -141,9 +141,9 @@ Association group 3 supports 5 nodes.
### Documentation Links
* [ZW4008 Manual](https://www.cd-jackson.com/zwave_device_uploads/1155/B1YLc65eVlS.pdf)
* [ZW4008 Manual](https://opensmarthouse.org/zwavedatabase/1155/reference/B1YLc65eVlS.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1155).
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1155).

1255
_addons_bindings/zwave/doc/heltun/heht01_0_0.md Normal file
View File

File diff suppressed because it is too large Load Diff

19
_addons_bindings/zwave/doc/honeywell/39339_0_0.md
View File

@ -61,12 +61,13 @@ The ```scene_number``` channel is of type ```scene_number``` and supports the ``
## Device Configuration
The following table provides a summary of the 7 configuration parameters available in the 39339 (ZW3107) .
The following table provides a summary of the 8 configuration parameters available in the 39339 (ZW3107) .
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|-------|-------|-------------|
| 3 | LED Light | LED Light Control |
| 6 | Dim Up/Down Behavior | Controls whether level changes are instant or smooth |
| 7 | Dim Rate Adjustments (Z-Wave Controller) | Number of steps or levels |
| 8 | Dim Rate Adjustments (Z-Wave Controller, Timing) | Timing of steps |
| 9 | Dim Rate Adjustments (manually controlled) | Number of steps or levels |
@ -92,6 +93,22 @@ The manufacturer defined default value is ```0``` (Set parameter to factory defa
This parameter has the configuration ID ```config_3_1``` and is of type ```INTEGER```.
### Parameter 6: Dim Up/Down Behavior
Controls whether level changes are instant or smooth
This is an undocumented feature. This parameter allows you to choose between instant level changes and smooth level changes on newer Jasco/Honeywell/GE dimmers. This feature should work on dimmers that come out of the box with instant level changes, it may not work on older dimmers that smoothly change levels by default.
The following option values may be configured, in addition to values in the range 0 to 1 -:
| Value | Description |
|--------|-------------|
| 0 | Instant Level Changes |
| 1 | Smooth Level Changes |
The manufacturer defined default value is ```0``` (Instant Level Changes).
This parameter has the configuration ID ```config_6_1``` and is of type ```INTEGER```.
### Parameter 7: Dim Rate Adjustments (Z-Wave Controller)
Number of steps or levels

160
_addons_bindings/zwave/doc/honeywell/zw4103_0_0.md Normal file
View File

@ -0,0 +1,160 @@
---
layout: documentation
title: ZW4103 - ZWave
---
{% include base.html %}
# ZW4103 Z-Wave Plug in Smart Switch
This describes the Z-Wave device *ZW4103*, manufactured by *Honeywell* with the thing type UID of ```honeywell_zw4103_00_000```.
The device is in the category of *Power Outlet*, defining Small devices to be plugged into a power socket in a wall which stick there.
![ZW4103 product image](https://opensmarthouse.org/zwavedatabase/1329/image/)
The ZW4103 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data between other devices in the mesh network.
## Overview
Control, automate, and schedule your homes lighting and appliances with the Plug-In Smart Switch. Using this Smart Switch means taking control of your homes lighting and appliances regardless of if you are in a different part of your home, the couch, work or away on vacation - all from your mobile device and Z-Wave compatible hub.
The plug-in smart switch gives you wireless control of your plug-in lighting and appliances from any mobile device, computer or Z-Wave enabled remote via a Z-Wave Certified gateway/hub. Automating you lights will not only make your life easier but it will also save energy, cut costs, and boost your home’s security. Plug-in Smart Switch has 1 grounded outlet located on the left side of the module and leaves bottom outlet
Schedule timed events and customize scenes for day or night, home or away - wirelessly control from anywhere through your smartphone, tablet, PC or Z-Wave remote
* Features 1 controlled grounded outlet w/ manual ON/OFF & program button - works with all LED, CFL, halogen and incandescent bulbs and other devices
* Requires a Z-Wave Certified Hub: Compatible with the following Z-Wave Hubs: Honeywell, Ring, SmartThings, Wink, HomeSeer, Fibaro, Trane, Nexia, ADT, Vera, and more
* Simply plug the module into any in-wall outlet, then connect your light to the smart outlet located on the left side of the plug-in
* 2nd wallplate outlet still free for use
### Inclusion Information
1. Follow the instructions for your Z-Wave certified controller to include the device to the Z-Wave network.
2. Once the controller is ready to include your smart switch, single press and release the manual/program button on the smart dimmer to include it in the network.
3. Once your controller has confirmed that the smart switch has been included, refresh the Z-Wave network to optimize performance.
### Exclusion Information
1. Follow the instructions for your Z-Wave certified controller to exclude a device from the Z-Wave network.
2. Once the controller is ready to exclude your device, press and release the manual/program button on the smart switch to exclude it from the network. 
### General Usage Information
## Channels
The following table summarises the channels available for the ZW4103 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Switch | switch_binary | switch_binary | Switch | Switch |
| Scene Number | scene_number | scene_number | | Number |
### Switch
Switch the power on and off.
The ```switch_binary``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Scene Number
Triggers when a scene button is pressed.
The ```scene_number``` channel is of type ```scene_number``` and supports the ```Number``` item.
## Device Configuration
The following table provides a summary of the 1 configuration parameters available in the ZW4103.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|-------|-------|-------------|
| 3 | LED Light | Changes the behavior of the LED light |
| | Switch All Mode | Set the mode for the switch when receiving SWITCH ALL commands |
### Parameter 3: LED Light
Changes the behavior of the LED light
Values in the range 0 to 2 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_3_1``` and is of type ```INTEGER```.
### Switch All Mode
Set the mode for the switch when receiving SWITCH ALL commands.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Exclude from All On and All Off groups |
| 1 | Include in All On group |
| 2 | Include in All Off group |
| 255 | Include in All On and All Off groups |
This parameter has the configuration ID ```switchall_mode``` and is of type ```INTEGER```.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The ZW4103 supports 3 association groups.
### Group 1: Lifeline
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation.
Supports device reset locally and receives unsolicited status updates
Association group 1 supports 5 nodes.
### Group 2: Single Press
Association Group 2 supports BasicSet and is controlled by single pressing the button
Association group 2 supports 5 nodes.
### Group 3: Double Press
Association Group 3 supports BasicSet and is controlled by double pressing the button
Association group 3 supports 5 nodes.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| |
| COMMAND_CLASS_SWITCH_ALL_V1| |
| COMMAND_CLASS_SCENE_ACTIVATION_V1| |
| COMMAND_CLASS_SCENE_ACTUATOR_CONF_V1| |
| COMMAND_CLASS_CRC_16_ENCAP_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_CONFIGURATION_V1| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
### Documentation Links
* [Honeywell_ZW4103_UserManual](https://opensmarthouse.org/zwavedatabase/1329/reference/ZW4103_UserManual.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1329).

105
_addons_bindings/zwave/doc/horstmann/ssp301_0_0.md Normal file
View File

@ -0,0 +1,105 @@
---
layout: documentation
title: SSP301 - ZWave
---
{% include base.html %}
# SSP301 Plug-in switch
This describes the Z-Wave device *SSP301*, manufactured by *Horstmann Controls Limited* with the thing type UID of ```horstmann_ssp301_00_000```.
The device is in the category of *Battery*, defining Batteries, Energy Storages.
![SSP301 product image](https://opensmarthouse.org/zwavedatabase/1328/image/)
The SSP301 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data between other devices in the mesh network.
## Overview
ON/OFF mains power module - unlike the SSP302 this doesn't have energy metering
### Inclusion Information
To include the SSP 301 onto a network, put the controller into inclusion mode. Now, press and hold the button on SSP 301 for 4 to 7 seconds then release. The network status LED will start flashing (twice per second) on successful start of inclusion process.
Note: Refer to the controller's manual for controller relevant actions.
On successful inclusion the LED will turn off.
Note: Inclusion means add and exclusion means delete.
The total process can take up to 20 seconds (Refer to the “Technical specifications – Radio” section for details). If the device fails to join the network it will go back to factory default state and the Network status LED will start flashing once per second. If there is an issue with RF Communication, then re-locate the device and repeat the inclusion process again.
### Exclusion Information
To exclude the SSP 301 from a network, put the controller into exclusion mode (refer to controller instructions) and follow the same sequence as per the inclusion process for include node. After successful exclusion the network status LED will start flashing once per second, and the device will reset to factory default.
If exclusion fails, SSP 301 network status LED will turn off after about 5 seconds.
Note: Exclusion only works when the device is in direct range of the controller (no repeater allowed).
### General Usage Information
## Channels
The following table summarises the channels available for the SSP301 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Switch | switch_binary | switch_binary | Switch | Switch |
### Switch
Switch the power on and off.
The ```switch_binary``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
## Device Configuration
The device has no configuration parameters defined.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The SSP301 supports 1 association group.
### Group 1: Lifeline
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation.
Lifeline
Association group 1 supports 1 node.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_CONFIGURATION_V1| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
### Documentation Links
* [SSP301 User Manual](https://opensmarthouse.org/zwavedatabase/1328/reference/SSP_301_resize_for_web_final.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1328).

32
_addons_bindings/zwave/doc/linear/gd00z8gc_0_0.md
View File

@ -37,9 +37,41 @@ The following table summarises the channels available for the GD00Z-8-GC -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Barrier State | barrier_state | barrier_state | Door | Number |
| Alarm (burglar) | alarm_burglar | alarm_burglar | Door | Switch |
| Alarm (access) | alarm_access | alarm_access | Door | Switch |
### Barrier State
Send 0 to CLOSE the Garage Door
Send 255 to OPEN the Garage Door
Reading this value provides the Status of the Garage Door. Status values are:
0 = Closed
252 = Closing
253 = Stopped
254 = Opening
255 = Open
Indicates the state of the barrier.
The ```barrier_state``` channel is of type ```barrier_state``` and supports the ```Number``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device.
The following state translation is provided for this channel to the ```Number``` item type -:
| Value | Label |
|-------|-----------|
| 0 | Closed |
| 252 | Closing |
| 253 | Stopped |
| 254 | Opening |
| 255 | Open |
### Alarm (burglar)
Indicates if the burglar alarm is triggered.

895
_addons_bindings/zwave/doc/logic/matrixzba7140_0_0.md Normal file
View File

@ -0,0 +1,895 @@
---
layout: documentation
title: MATRIX ZBA7140 - ZWave
---
{% include base.html %}
# MATRIX ZBA7140 Matrix ZBA7140
This describes the Z-Wave device *MATRIX ZBA7140*, manufactured by *[Logic Group](http://www.logic-group.com)* with the thing type UID of ```logic_matrixzba7140_00_000```.
The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch.
![MATRIX ZBA7140 product image](https://opensmarthouse.org/zwavedatabase/1330/image/)
The MATRIX ZBA7140 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices.
The MATRIX ZBA7140 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information.
## Overview
MATRIX type ZBA7140 (from hereon called MATRIX ZBA) is a multifunction battery wall controller that can be mounted in a modular wall-box or directly ontothe wall. It is compatible with existing FUGA® frames and wall boxes.MATRIX ZBA has four configurable pushbuttons that can control other Z-Wave devices through the wireless Z-Wave network. These buttons can send ‘ON’, ‘OFF’ and ‘DIM’ commands to the associated Z-Wave devices. These devices could be light dimmers, blinds, sunscreens, etc.MATRIX ZBA can also issue scene activation commands that can be used to activate scenes in the Z-Wave Controller.MATRIX ZBA has four RGB indicator LEDs, one for each pushbutton, that indicates activation of the pushbutton, and when MATRIX ZBA is in inclusion or exclusion mode. These indicators can be configured to a desired indication colour, or they can indicate the battery level when a pushbutton is activated.MATRIX ZBA is equipped with the newest battery-saving 700-series Z-Wave chip that uses up to 65% less power and have improved wireless range. This means that the small coin-cell battery can last between 5 –10years. MATRIX ZBA is estimated toabattery lifetime, at normal use, to approximately 5 years.
### Inclusion Information
MATRIXZBAis a SmartStart enabled product and can be added into a Z-Wave network by scanning the Z-Wave QR Code present on the product with a controller providing SmartStart inclusion. No further action is required and the SmartStart product will be added automatically within 10 minutes of being switched on in the network vicinity.Find the QR code and PIN Code on the back of the module.
Find the full DSK on the product packaging.
Add MATRIX ZBA to a network with Classic Inclusion by pressing once on the switch behind the pushbutton-cover. The LED near pushbutton 1 will start blinking.
Use same procedure for removing MATRIX ZBAwith Classic Exclusion. If MATRIXZBA already belongs to a Z-Wave network, the remove process must be performed before adding it in a new network. Otherwise, the adding of the device will fail.
### Exclusion Information
Add MATRIX ZBA to a network with Classic Inclusion by pressing once on the switch behind the pushbutton-cover. The LED near pushbutton 1 will start blinking.
Use same procedure for removing MATRIX ZBAwith Classic Exclusion.
### Wakeup Information
The MATRIX ZBA7140 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour.
The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device.
MATRIX ZBA is a battery-operated device and is turned into deep sleep state most of the time to save battery. Communication with the device is limited. In order to communicate with the device, a controller is needed in the network. This controller will maintain a mailbox for the battery-operated devices and store commands that can’t be received during deep sleep state. Without such a controller, communication may become impossible and/or the battery lifetime is significantly decreased. This device will wake up every 6 hours and announce the wake-upstate by sending out a so-called Wake Up Notification. The controller can then empty the mailbox. The wake-up interval is a trade-off between maximal battery lifetime and the desired responses of the device. The device will stay awake right after inclusion for 10 seconds allowing the controller to perform certain configuration. It is possible to manually wake up the device by double-activating the button
### General Usage Information
## Channels
The following table summarises the channels available for the MATRIX ZBA7140 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Scene Number | scene_number | scene_number | | Number |
| Battery Level | battery-level | system.battery_level | Battery | Number |
### Scene Number
Triggers when a scene button is pressed.
The ```scene_number``` channel is of type ```scene_number``` and supports the ```Number``` item.
This channel provides the scene, and the event as a decimal value in the form ```<scene>.<event>```. The scene number is set by the device, and the event is as follows -:
| Event ID | Event Description |
|----------|--------------------|
| 0 | Single key press |
| 1 | Key released |
| 2 | Key held down |
| 3 | Double keypress |
| 4 | Tripple keypress |
| 5 | 4 x keypress |
| 6 | 5 x keypress |
### Battery Level
Represents the battery level as a percentage (0-100%). Bindings for things supporting battery level in a different format (e.g. 4 levels) should convert to a percentage to provide a consistent battery level reading.
The ```system.battery-level``` channel is of type ```system.battery-level``` and supports the ```Number``` item and is in the ```Battery``` category.
This channel provides the battery level as a percentage and also reflects the low battery warning state. If the battery state is in low battery warning state, this will read 0%.
## Device Configuration
The following table provides a summary of the 45 configuration parameters available in the MATRIX ZBA7140.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|-------|-------|-------------|
| 1 | Enable Central Scene notifications | This parameter can be used for enabling or disabling Central scene notifications |
| 2 | Pushbutton press threshold time | Specifies the time that a pushbutton must be activated before it is detected as pressed. |
| 3 | Pushbutton held threshold time | Specifies the time that a pushbutton must have been activated before it is accepted as “held-down”. |
| 4 | Mode of the LED indication. | This parameter specifies the mode of the LED indication. |
| 5 | LEDs colour indication, Byte 1 | Specifies the level for the red colour. (Default is 255) |
| 5 | LEDs colour indication, Byte 2 | Specifies the level for the green colour. (Default is 85) |
| 5 | LEDs colour indication, Byte 3 | Specifies the level for the blue colour. (Default is 85) |
| 5 | Not used. | This byte is not used and must be set to 0. |
| 6 | Associations groups, transmission when included secure. | This parameter specifies if commands are transmitted as a secure message for each of the association groups. |
| 7 | Pushbutton 1 functionality. | This parameter specifies the functionality of pushbutton 1. |
| 8 | Switch multilevel set single-activation values for pushbutton 1, Byte 1 | Enable/Disable |
| 8 | Switch multilevel set single-activation values for pushbutton 1, Byte 2 | Upper switch value |
| 8 | Switch multilevel set single-activation values for pushbutton 1, Byte 3 | Lower switch value |
| 8 | Switch multilevel set single-activation values for pushbutton 1, Byte 4 | Duration |
| 9 | Switch Multilevel Set double-activation values for pushbutton 1. Byte 1 | Enable/Disable |
| 9 | Switch Multilevel Set double-activation values for pushbutton 1. Byte 2 | Upper switch value |
| 9 | Switch Multilevel Set double-activation values for pushbutton 1. Byte 3 | Lower switch value |
| 9 | Switch Multilevel Set double-activation values for pushbutton 1. Byte 4 | Duration |
| 10 | Pushbutton 2 functionality. | This parameter specifies the functionality of pushbutton 2. |
| 11 | Switch multilevel set single-activation values for pushbutton 2, Byte 1 | Enable/Disable |
| 11 | Switch multilevel set single-activation values for pushbutton 2, Byte 2 | Upper switch value |
| 11 | Switch multilevel set single-activation values for pushbutton 2, Byte 3 | Lower switch value |
| 11 | Switch multilevel set single-activation values for pushbutton 2, Byte 4 | Duration |
| 12 | Switch Multilevel Set double-activation values for pushbutton 2. Byte 1 | Enable/Disable |
| 12 | Switch Multilevel Set double-activation values for pushbutton 2. Byte 2 | Upper switch value |
| 12 | Switch Multilevel Set double-activation values for pushbutton 2. Byte 3 | Lower switch value |
| 12 | Switch Multilevel Set double-activation values for pushbutton 2. Byte 4 | Duration |
| 13 | Pushbutton 3 functionality. | This parameter specifies the functionality of pushbutton 3. |
| 14 | Switch multilevel set single-activation values for pushbutton 3, Byte 1 | Enable/Disable |
| 14 | Switch multilevel set single-activation values for pushbutton 3, Byte 2 | Upper switch value. |
| 14 | Switch multilevel set single-activation values for pushbutton 3, Byte 3 | Lower switch value |
| 14 | Switch multilevel set single-activation values for pushbutton 3, Byte 3 | Duaration |
| 15 | Switch Multilevel Set double-activation values for pushbutton 3. Byte 1 | Enable/Disable |
| 15 | Switch Multilevel Set double-activation values for pushbutton 3. Byte 2 | Upper switch value |
| 15 | Switch Multilevel Set double-activation values for pushbutton 3. Byte 3 | Lower switch value |
| 15 | Switch Multilevel Set double-activation values for pushbutton 3. Byte 4 | Duration |
| 16 | Pushbutton 4 functionality. | This parameter specifies the functionality of pushbutton 4. |
| 17 | Switch multilevel set single-activation values for pushbutton 4, Byte 1 | Enable/Disable |
| 17 | Switch multilevel set single-activation values for pushbutton 4, Byte 2 | Upper switch value |
| 17 | Switch multilevel set single-activation values for pushbutton 4, Byte 3 | Lower switch value |
| 17 | Switch multilevel set single-activation values for pushbutton 4, Byte 4 | Duration |
| 18 | Switch Multilevel Set double-activation values for pushbutton 4. Byte 1 | Enable/Disable |
| 18 | Switch Multilevel Set double-activation values for pushbutton 4. Byte 2 | Upper switch value |
| 18 | Switch Multilevel Set double-activation values for pushbutton 4. Byte 3 | Lower switch value |
| 18 | Switch Multilevel Set double-activation values for pushbutton 4. Byte 4 | Duration |
| | Wakeup Interval | Sets the interval at which the device will accept commands from the controller |
| | Wakeup Node | Sets the node ID of the device to receive the wakeup notifications |
### Parameter 1: Enable Central Scene notifications
This parameter can be used for enabling or disabling Central scene notifications
The following option values may be configured, in addition to values in the range 0 to 1 -:
| Value | Description |
|--------|-------------|
| 0 | Central Scene notifications are disabled. |
| 1 | Central Scene Notifications are enabled. (Default) |
The manufacturer defined default value is ```1``` (Central Scene Notifications are enabled. (Default)).
This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```.
### Parameter 2: Pushbutton press threshold time
Specifies the time that a pushbutton must be activated before it is detected as pressed.
Specifies the time that a pushbutton must be activated before it is detected as pressed. This parameter also affects the detection of double-and triple-activations, as a new activationmust be detectedwithin this specified time for the repeatedly detection. Be aware that this parameter must be lower than the value in Parameter 3. Therefore, change this parameter with caution.
Values in the range 1 to 1000 may be set.
The manufacturer defined default value is ```400```.
This parameter has the configuration ID ```config_2_2``` and is of type ```INTEGER```.
### Parameter 3: Pushbutton held threshold time
Specifies the time that a pushbutton must have been activated before it is accepted as “held-down”.
Specifies the time that a pushbutton must have been activated before it is accepted as “held-down”. This value must be higher than the value set in Parameter 2. Resolution is milliseconds
Values in the range 1 to 5000 may be set.
The manufacturer defined default value is ```600```.
This parameter has the configuration ID ```config_3_2``` and is of type ```INTEGER```.
### Parameter 4: Mode of the LED indication.
This parameter specifies the mode of the LED indication.
This parameter specifies the mode of the LED indication.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | LED indication is turned off. |
| 1 | LEDs indicates the current level of the battery, when the device is in |
| 2 | LED colour is set by configuration parameter 5. |
The manufacturer defined default value is ```1``` (LEDs indicates the current level of the battery, when the device is in).
This parameter has the configuration ID ```config_4_1``` and is of type ```INTEGER```.
### Parameter 5: LEDs colour indication, Byte 1
Specifies the level for the red colour. (Default is 255)
This parameter specifies the colour levels for the red, green and blue colours in the 4 RGB LEDs. This parameter is not used unless configuration parameter 4 is set to the value 2. The default configuration is a white light, where red level value must be higher than the two other colours in order to get a white light.Value Description
Byte 1: Red colour level.0 -255Specifies the level for the red colour. (Default is 255)
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```255```.
This parameter has the configuration ID ```config_5_4_00000001``` and is of type ```INTEGER```.
### Parameter 5: LEDs colour indication, Byte 2
Specifies the level for the green colour. (Default is 85)
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```85```.
This parameter has the configuration ID ```config_5_4_0000FF00``` and is of type ```INTEGER```.
### Parameter 5: LEDs colour indication, Byte 3
Specifies the level for the blue colour. (Default is 85)
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```85```.
This parameter has the configuration ID ```config_5_4_00FF0000``` and is of type ```INTEGER```.
### Parameter 5: Not used.
This byte is not used and must be set to 0.
Values in the range 0 to 0 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_5_4_01000000``` and is of type ```INTEGER```.
### Parameter 6: Associations groups, transmission when included secure.
This parameter specifies if commands are transmitted as a secure message for each of the association groups.
This parameter specifies if commands are transmitted as a secure message for each of the association groups.This parameter is only used when the device is included in security mode (either S0 or S2).
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | All messages in all groups are sent as insecure. |
| 1 | Messages in association group 2 are sent as secure. |
| 2 | Messages in association group 3 are sent as secure. |
| 4 | Messages in association group 4 are sent as secure. |
| 8 | Messages in association group 5 are sent as secure. |
| 16 | Messages in association group 6 are sent as secure. |
| 32 | Messages in association group 7 are sent as secure. |
| 64 | Messages in association group 8 are sent as secure. |
| 128 | Messages in association group 9 are sent as secure. |
| 255 | All messages in all groups are sent as secure. (Default) |
The manufacturer defined default value is ```255``` (All messages in all groups are sent as secure. (Default)).
This parameter has the configuration ID ```config_6_2``` and is of type ```INTEGER```.
### Parameter 7: Pushbutton 1 functionality.
This parameter specifies the functionality of pushbutton 1.
0 Standard toggle-function, the state is switched between on and off, dimming up and down. (Default)
1 Always turn on or dim up. Using this parameter, the pushbutton can only send ‘on’ or ‘dim up’ commands. Use this in pair with another pushbutton with value 2.
2 Always turn offor dim down. Using this parameter, the pushbutton can only send ‘off’ or ‘dim down’ commands. Use this in pair with another pushbutton with value 1.
3 When the pushbutton is down; an on command is sent, and when the pushbutton is released; an off command is sent.
Values in the range 0 to 3 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_7_1``` and is of type ```INTEGER```.
### Parameter 8: Switch multilevel set single-activation values for pushbutton 1, Byte 1
Enable/Disable
Byte 1: Enable / Disable
0 Disabled – A single activation of the pushbutton will not send commands to devices in the association group.
1 Enabled – A single activation will send commands to devices in the association group. Devices will receive commands with the values set in 3 following bytes.(Default)
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Disabled –A single activation of the pushbutton will not send commands |
| 1 | Enabled –A single activation will send commands to devices in the asso |
The manufacturer defined default value is ```1``` (Enabled –A single activation will send commands to devices in the asso).
This parameter has the configuration ID ```config_8_4_00000001``` and is of type ```INTEGER```.
### Parameter 8: Switch multilevel set single-activation values for pushbutton 1, Byte 2
Upper switch value
Byte 2: Upper switch value0 –99, 255When single pressing the pushbutton for ON, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 255)
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```255```.
This parameter has the configuration ID ```config_8_4_0000FF00``` and is of type ```INTEGER```.
### Parameter 8: Switch multilevel set single-activation values for pushbutton 1, Byte 3
Lower switch value
Byte 3: Lower switch value 0 -99 When single pressing the pushbutton for OFF, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 0)
Values in the range 0 to 99 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_8_4_00FF0000``` and is of type ```INTEGER```.
### Parameter 8: Switch multilevel set single-activation values for pushbutton 1, Byte 4
Duration
Byte 4: Duration 0 -255 When single pressing the pushbutton the Switch Multilevel Set with this duration value will be send to devices in the association group.
0: Use dimmer default timer value. (Default)
1 –127: Duration in seconds.
128 –255: Duration in minutes (minus 127) from 1 –128 minutes, where 128 is 1 minute.
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_8_4_01000000``` and is of type ```INTEGER```.
### Parameter 9: Switch Multilevel Set double-activation values for pushbutton 1. Byte 1
Enable/Disable
This parameter specifies the value that are sent to the devices in the Switch Multilevel association group (group 3) when the pushbutton is double-pressed.
Byte 1: Enable / Disable0Disabled –A double activation of the pushbutton will not send commands to devices in the association group.1Enabled –A double activation will send commands to devices in the association group. Devices will receive commands with the values set in 3 following bytes. (Default)
Values in the range 0 to 1 may be set.
The manufacturer defined default value is ```1```.
This parameter has the configuration ID ```config_9_4_00000001``` and is of type ```INTEGER```.
### Parameter 9: Switch Multilevel Set double-activation values for pushbutton 1. Byte 2
Upper switch value
Byte 2: Upper switch value 0 –99, 255 When double pressing the pushbutton for ON, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 99)
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```99```.
This parameter has the configuration ID ```config_9_4_0000FF00``` and is of type ```INTEGER```.
### Parameter 9: Switch Multilevel Set double-activation values for pushbutton 1. Byte 3
Lower switch value
Byte 3: Lower switch value 0 -99 When double pressing the pushbutton for OFF, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 99)
Values in the range 0 to 99 may be set.
The manufacturer defined default value is ```99```.
This parameter has the configuration ID ```config_9_4_00FF0000``` and is of type ```INTEGER```.
### Parameter 9: Switch Multilevel Set double-activation values for pushbutton 1. Byte 4
Duration
Byte 4: Duration 0 -255 When double pressing the pushbutton the Switch Multilevel Set with this duration value will be send to devices in the association group.
0: Use dimmer default timer value. (Default)
1 –127: Duration in seconds.
128 –255: Duration in minutes (minus 127) from 1 –128 minutes, where 128 is 1 minute.
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_9_4_01000000``` and is of type ```INTEGER```.
### Parameter 10: Pushbutton 2 functionality.
This parameter specifies the functionality of pushbutton 2.
0 Standard toggle-function, the state is switched between on and off, dimming up and down. (Default)
1 Always turn on or dim up. Using this parameter, the pushbutton can only send ‘on’ or ‘dim up’ commands. Use this in pair with another pushbutton with value 2.
2 Always turn off or dim down. Using this parameter, the pushbutton can only send ‘off’ or ‘dim down’ commands. Use this in pair with another pushbutton with value1.
3 When the pushbutton is down; an on command is sent, and when the pushbutton is released; an off command is sent.
Values in the range 0 to 3 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_10_1``` and is of type ```INTEGER```.
### Parameter 11: Switch multilevel set single-activation values for pushbutton 2, Byte 1
Enable/Disable
Byte 1: Enable / Disable
0 Disabled – A single activation of the pushbutton will not send commands to devices in the association group.
1 Enabled – A single activation will send commands to devices in the association group. Devices will receive commands with the values set in 3 following bytes. (Default)
Values in the range 0 to 1 may be set.
The manufacturer defined default value is ```1```.
This parameter has the configuration ID ```config_11_4_00000001``` and is of type ```INTEGER```.
### Parameter 11: Switch multilevel set single-activation values for pushbutton 2, Byte 2
Upper switch value
Byte 2: Upper switch value 0 –99, 255 When single pressing the pushbutton for ON, a Switch Multilevel Setwith this value will be send to devices in the association group. (Default = 255)
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```255```.
This parameter has the configuration ID ```config_11_4_0000FF00``` and is of type ```INTEGER```.
### Parameter 11: Switch multilevel set single-activation values for pushbutton 2, Byte 3
Lower switch value
Byte 3: Lower switch value 0 -99 When single pressing the pushbutton for OFF, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 0)
Values in the range 0 to 99 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_11_4_00FF0000``` and is of type ```INTEGER```.
### Parameter 11: Switch multilevel set single-activation values for pushbutton 2, Byte 4
Duration
Byte 4: Duration 0 -255 When single pressing the pushbutton the Switch Multilevel Set with this duration value will be send to devices in the association group.
0: Use dimmer default timer value. (Default)
1 –127: Duration in seconds.
128 –255: Duration in minutes (minus 127) from 1 –128 minutes, where 128 is 1 minute.
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_11_4_01000000``` and is of type ```INTEGER```.
### Parameter 12: Switch Multilevel Set double-activation values for pushbutton 2. Byte 1
Enable/Disable
Byte 1: Enable / Disable
0 Disabled – A double activation of the pushbutton will not send commands to devices in the association group.
1 Enabled – A double activation will send commands to devices in the association group. Devices will receive commands with the values set in 3 following bytes. (Default)
Values in the range 0 to 1 may be set.
The manufacturer defined default value is ```1```.
This parameter has the configuration ID ```config_12_4_00000001``` and is of type ```INTEGER```.
### Parameter 12: Switch Multilevel Set double-activation values for pushbutton 2. Byte 2
Upper switch value
Byte 2: Upper switch value 0 –99, 255 When double pressing the pushbutton for ON, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 99)
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```99```.
This parameter has the configuration ID ```config_12_4_0000FF00``` and is of type ```INTEGER```.
### Parameter 12: Switch Multilevel Set double-activation values for pushbutton 2. Byte 3
Lower switch value
Byte 3: Lower switch value 0 -99 When double pressing the pushbutton for OFF, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 99)
Values in the range 0 to 99 may be set.
The manufacturer defined default value is ```99```.
This parameter has the configuration ID ```config_12_4_00FF0000``` and is of type ```INTEGER```.
### Parameter 12: Switch Multilevel Set double-activation values for pushbutton 2. Byte 4
Duration
Byte 4: Duration 0 -255 When double pressing the pushbutton the Switch Multilevel Set with this duration value will be send to devices in the association group.
0: Use dimmer default timer value. (Default)
1 –127: Duration in seconds.
128 –255: Duration in minutes (minus 127) from 1 –128 minutes, where 128 is 1 minute.
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_12_4_01000000``` and is of type ```INTEGER```.
### Parameter 13: Pushbutton 3 functionality.
This parameter specifies the functionality of pushbutton 3.
0 Standard toggle-function, the state is switched between on and off, dimming up and down. (Default)
1 Always turn on or dim up. Using this parameter, the pushbutton can only send ‘on’ or ‘dim up’ commands. Use this in pair with another pushbutton with value 2.
2 Always turn offor dim down. Using this parameter, the pushbutton can only send ‘off’ or ‘dim down’ commands. Use this in pair with another pushbutton with value 1.
3 When the pushbutton is down; an on command is sent, and when the pushbutton is released; an off command is sent.
Values in the range 0 to 3 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_13_1``` and is of type ```INTEGER```.
### Parameter 14: Switch multilevel set single-activation values for pushbutton 3, Byte 1
Enable/Disable
Byte 1: Enable / Disable
0 Disabled – A single activation of the pushbutton will not send commands to devices in the association group.
1 Enabled – A single activation will send commands to devices in the association group. Devices will receive commands with the values set in 3 following bytes. (Default)
Values in the range 0 to 1 may be set.
The manufacturer defined default value is ```1```.
This parameter has the configuration ID ```config_14_4_00000001``` and is of type ```INTEGER```.
### Parameter 14: Switch multilevel set single-activation values for pushbutton 3, Byte 2
Upper switch value.
Byte 2: Upper switch value 0 –99, 255 When single pressing the pushbutton for ON, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 255)
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```255```.
This parameter has the configuration ID ```config_14_4_0000FF00``` and is of type ```INTEGER```.
### Parameter 14: Switch multilevel set single-activation values for pushbutton 3, Byte 3
Lower switch value
Byte 3: Lower switch value 0 -99 When single pressing the pushbutton for OFF, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 0)
Values in the range 0 to 99 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_14_4_00FF0000``` and is of type ```INTEGER```.
### Parameter 14: Switch multilevel set single-activation values for pushbutton 3, Byte 3
Duaration
Byte 4: Duration 0 -255 When single pressing the pushbutton the Switch Multilevel Set with this duration value will be send to devices in the association group.
0: Use dimmer default timer value. (Default)
1 –127: Duration in seconds.
128 –255: Duration in minutes (minus 127) from 1 –128 minutes, where 128 is 1 minute.
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_14_4_01000000``` and is of type ```INTEGER```.
### Parameter 15: Switch Multilevel Set double-activation values for pushbutton 3. Byte 1
Enable/Disable
Byte 1: Enable / Disable
0 Disabled – A double activation of the pushbutton will not send commands to devices in the association group.
1 Enabled – A double activation will send commands to devices in the association group. Devices will receive commands with the values set in 3 following bytes. (Default)
Values in the range 0 to 1 may be set.
The manufacturer defined default value is ```1```.
This parameter has the configuration ID ```config_15_4_00000001``` and is of type ```INTEGER```.
### Parameter 15: Switch Multilevel Set double-activation values for pushbutton 3. Byte 2
Upper switch value
Byte 2: Upper switch value 0 –99, 255 When double pressing the pushbutton for ON, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 99)
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```99```.
This parameter has the configuration ID ```config_15_4_0000FF00``` and is of type ```INTEGER```.
### Parameter 15: Switch Multilevel Set double-activation values for pushbutton 3. Byte 3
Lower switch value
Byte 3: Lower switch value 0 -99 When double pressing the pushbutton for OFF, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 99)
Values in the range 0 to 99 may be set.
The manufacturer defined default value is ```99```.
This parameter has the configuration ID ```config_15_4_00FF0000``` and is of type ```INTEGER```.
### Parameter 15: Switch Multilevel Set double-activation values for pushbutton 3. Byte 4
Duration
Byte 4: Duration 0 -255 When double pressing the pushbutton the Switch Multilevel Set with this duration value will be send to devices in the association group.
0: Use dimmer default timer value. (Default)
1 –127: Duration in seconds.
128 –255: Duration in minutes (minus 127) from 1 –128 minutes, where 128 is 1 minute.
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_15_4_01000000``` and is of type ```INTEGER```.
### Parameter 16: Pushbutton 4 functionality.
This parameter specifies the functionality of pushbutton 4.
0 Standard toggle-function, the state is switched between on and off, dimming up and down. (Default)
1 Always turn on or dim up. Using this parameter, the pushbutton can only send ‘on’ or ‘dim up’ commands. Use this in pair with another pushbutton with value 2.
2 Always turn offor dim down. Using this parameter, the pushbutton can only send ‘of’ or ‘dim down’ commands. Use this in pair with another pushbutton with value 1.
3 When the pushbutton is down; an on command is sent, and when the pushbutton is released; an off command is sent.
Values in the range 0 to 3 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_16_1``` and is of type ```INTEGER```.
### Parameter 17: Switch multilevel set single-activation values for pushbutton 4, Byte 1
Enable/Disable
Byte 1: Enable / Disable
0 Disabled – A single activation of the pushbutton will not send commands to devices in the association group.
1 Enabled – A single activation will send commands to devices in the association group. Devices will receive commands with the values set in 3 following bytes. (Default)
Values in the range 0 to 1 may be set.
The manufacturer defined default value is ```1```.
This parameter has the configuration ID ```config_17_4_00000001``` and is of type ```INTEGER```.
### Parameter 17: Switch multilevel set single-activation values for pushbutton 4, Byte 2
Upper switch value
Byte 2: Upper switch value 0 –99, 255 When single pressing the pushbutton for ON, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 255)
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```255```.
This parameter has the configuration ID ```config_17_4_0000FF00``` and is of type ```INTEGER```.
### Parameter 17: Switch multilevel set single-activation values for pushbutton 4, Byte 3
Lower switch value
Byte 3: Lower switch value 0 -99 When single pressing the pushbutton for OFF, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 0)
Values in the range 0 to 99 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_17_4_00FF0000``` and is of type ```INTEGER```.
### Parameter 17: Switch multilevel set single-activation values for pushbutton 4, Byte 4
Duration
Byte 4: Duration 0 -255 When single pressing the pushbutton the Switch Multilevel Set with this duration value will be send to devices in the association group.
0: Use dimmer default timer value. (Default)
1 –127: Duration in seconds.
128 –255: Duration in minutes (minus 127) from 1 –128 minutes, where 128 is 1 minute.
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_17_4_01000000``` and is of type ```INTEGER```.
### Parameter 18: Switch Multilevel Set double-activation values for pushbutton 4. Byte 1
Enable/Disable
Byte 1: Enable / Disable
0 Disabled – A double activation of the pushbutton will not send commands to devices in the association group.
1 Enabled – A double activation will send commands to devices in the association group. Devices will receive commands with the values set in 3 following bytes. (Default)
Values in the range 0 to 1 may be set.
The manufacturer defined default value is ```1```.
This parameter has the configuration ID ```config_18_4_00000001``` and is of type ```INTEGER```.
### Parameter 18: Switch Multilevel Set double-activation values for pushbutton 4. Byte 2
Upper switch value
Byte 2: Upper switch value 0 –99, 255 When double pressing the pushbutton for ON, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 99)
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```99```.
This parameter has the configuration ID ```config_18_4_0000FF00``` and is of type ```INTEGER```.
### Parameter 18: Switch Multilevel Set double-activation values for pushbutton 4. Byte 3
Lower switch value
Byte 3: Lower switch value 0 -99 When double pressing the pushbutton for OFF, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 99)
Values in the range 0 to 99 may be set.
The manufacturer defined default value is ```99```.
This parameter has the configuration ID ```config_18_4_00FF0000``` and is of type ```INTEGER```.
### Parameter 18: Switch Multilevel Set double-activation values for pushbutton 4. Byte 4
Duration
Byte 4: Duration 0 -255 When double pressing the pushbutton the Switch Multilevel Set with this duration value will be send to devices in the association group.
0: Use dimmer default timer value. (Default)
1 –127: Duration in seconds.
128 –255: Duration in minutes (minus 127) from 1 –128 minutes, where 128 is 1 minute.
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_18_4_01000000``` and is of type ```INTEGER```.
### Wakeup Interval
The wakeup interval sets the period at which the device will listen for messages from the controller. This is required for battery devices that sleep most of the time in order to conserve battery life. The device will wake up at this interval and send a message to the controller to tell it that it can accept messages - after a few seconds, it will go back to sleep if there is no further communications.
This setting is defined in *seconds*. It is advisable not to set this interval too short or it could impact battery life. A period of 1 hour (3600 seconds) is suitable in most instances.
Note that this setting does not affect the devices ability to send sensor data, or notification events.
This parameter has the configuration ID ```wakeup_interval``` and is of type ```INTEGER```.
### Wakeup Node
When sleeping devices wake up, they send a notification to a listening device. Normally, this device is the network controller, and normally the controller will set this automatically to its own address.
In the event that the network contains multiple controllers, it may be necessary to configure this to a node that is not the main controller. This is an advanced setting and should not be changed without a full understanding of the impact.
This parameter has the configuration ID ```wakeup_node``` and is of type ```INTEGER```.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The MATRIX ZBA7140 supports 9 association groups.
### Group 1: Lifeline
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation.
Sends Device Reset notifications, Battery Reports, etc.
Sends Device Reset notifications, Battery Reports, Indicator Reports, Central Scene Configuration Reports and Central Scene notifications.
Association group 1 supports 5 nodes.
### Group 2: Button 1 Basic
Button 1 Basic
Nodes in this group receives Basic Set when pushbutton 1 is activated, the on or off status is decided by the internal button status and is toggled between each activation.
Association group 2 supports 5 nodes.
### Group 3: Button 1 Multilevel
Button 1 Multilevel
Nodes in this group receives Switch Multilevel Set / Switch Multilevel Start Level Change/ Switch Multilevel Stop Level Change when pushbutton 1 is operated. It can, as an example, be used for controlling light dimmers.
Association group 3 supports 5 nodes.
### Group 4: Button 2 Basic
Button 2 Basic
Association group 4 supports 5 nodes.
### Group 5: Button 2 Multilevel
Button 2 Multilevel
Association group 5 supports 5 nodes.
### Group 5: Button 4 Basic
Button 4 Basic
Association group 5 supports 8 nodes.
### Group 6: Button 3 Basic
Button 3 Basic
Association group 6 supports 5 nodes.
### Group 7: Button 3 Multilevel
Button 3 Multilevel
Association group 7 supports 5 nodes.
### Group 9: Button 4 Multilevel
Button 4 Multilevel
Association group 9 supports 5 nodes.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_TRANSPORT_SERVICE_V2| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V3| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_CENTRAL_SCENE_V3| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V2| |
| COMMAND_CLASS_SUPERVISION_V1| |
| COMMAND_CLASS_CONFIGURATION_V4| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V2| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V5| |
| COMMAND_CLASS_BATTERY_V1| |
| COMMAND_CLASS_WAKE_UP_V2| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V3| |
| COMMAND_CLASS_INDICATOR_V3| |
| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| |
| COMMAND_CLASS_SECURITY_V1| |
| COMMAND_CLASS_SECURITY_2_V1| |
### Documentation Links
* [manual](https://opensmarthouse.org/zwavedatabase/1330/reference/zba7140-user-manual-en-4.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1330).

828
_addons_bindings/zwave/doc/logic/zdb5400_1_0.md Normal file
View File

@ -0,0 +1,828 @@
---
layout: documentation
title: ZDB5400 - ZWave
---
{% include base.html %}
# ZDB5400 MATRIX 55 Switch with Dimmer and Backlight
This describes the Z-Wave device *ZDB5400*, manufactured by *[Logic Group](http://www.logic-group.com)* with the thing type UID of ```logic_zdb5400_01_000```.
This version of the device is limited to firmware versions above 1.0
The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch.
![ZDB5400 product image](https://opensmarthouse.org/zwavedatabase/1316/image/)
The ZDB5400 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data between other devices in the mesh network.
## Overview
MATRIX type ZDB5400 is a multifunction switch that can be mounted in a modular wall-box, with built-in light dimmer and four configurable pushbuttons with RGB indicators.
The pushbuttons can control other Z-Wave devices through the wireless Z-Wave network. The pushbuttons can send ’ON’, ’OFF’ and ’DIM’ commands to the associated Z-Wave devices. These devices could be other light dimmers, blinds, sun-screens, etc.
The built-in light dimmer is per default attached to pushbutton 1. This attachment can be configured, thus it can be configured to not be controlled by any the four pushbuttons, so it can be independent of the local operation and thereby only be controllable from the Z-Wave network.
Furthermore, the pushbuttons can be configured to work together in pairs; thereby it can be possible to have one pushbutton to dim the light up, and another pushbutton to dim the light down.
MATRIX can also issue scene activation commands that can be used to activate scenes in the Z-Wave Controller.
The four RGB indicators, one for each pushbutton, can be used for different purposes, for example as orientation light, status light, different kind of indications, etc. The colour of the light and the control of it is fully controllable from the Z-Wave network.
MATRIX 55 also works as a repeater for the Z-Wave network and therefore expands the Z-Wave network coverage.
### Inclusion Information
MATRIX’ add function is initiated by pressing once on the switch (I) (under the pushbutton cover). The LED inside the module will start blinking.
If MATRIX already belongs to a Z-Wave network, the remove process must be performed before adding it into a new network. Otherwise, the adding of the device will fail.
MATRIX 55 can be factory reset by holding the switch through the hole (I) for at least 10 seconds.
### Exclusion Information
MATRIX’ remove function is initiated by pressing once on the switch (I) (under the pushbutton cover). The LED inside the module will start blinking.
### General Usage Information
## Channels
The following table summarises the channels available for the ZDB5400 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Dimmer | switch_dimmer | switch_dimmer | DimmableLight | Dimmer |
| Color Control | color_color | color_color | ColorLight | Color |
| Color Temperature | color_temperature | color_temperature | ColorLight | Dimmer |
| Scene Number | scene_number | scene_number | | Number |
| Dimmer 1 | switch_dimmer1 | switch_dimmer | DimmableLight | Dimmer |
| Color Control 1 | color_color1 | color_color | ColorLight | Color |
| Color Temperature 1 | color_temperature1 | color_temperature | ColorLight | Dimmer |
| Scene Number 1 | scene_number1 | scene_number | | Number |
| Dimmer 2 | switch_dimmer2 | switch_dimmer | DimmableLight | Dimmer |
| Color Control 2 | color_color2 | color_color | ColorLight | Color |
| Color Temperature 2 | color_temperature2 | color_temperature | ColorLight | Dimmer |
| Scene Number 2 | scene_number2 | scene_number | | Number |
| Dimmer 3 | switch_dimmer3 | switch_dimmer | DimmableLight | Dimmer |
| Color Control 3 | color_color3 | color_color | ColorLight | Color |
| Color Temperature 3 | color_temperature3 | color_temperature | ColorLight | Dimmer |
| Scene Number 3 | scene_number3 | scene_number | | Number |
| Dimmer 4 | switch_dimmer4 | switch_dimmer | DimmableLight | Dimmer |
| Color Control 4 | color_color4 | color_color | ColorLight | Color |
| Color Temperature 4 | color_temperature4 | color_temperature | ColorLight | Dimmer |
| Scene Number 4 | scene_number4 | scene_number | | Number |
| Switch 5 | switch_binary5 | switch_binary | Switch | Switch |
| Dimmer 5 | switch_dimmer5 | switch_dimmer | DimmableLight | Dimmer |
### Dimmer
The brightness channel allows to control the brightness of a light.
It is also possible to switch the light on and off.
The ```switch_dimmer``` channel is of type ```switch_dimmer``` and supports the ```Dimmer``` item and is in the ```DimmableLight``` category.
### Color Control
The color channel allows to control the color of a light.
It is also possible to dim values and switch the light on and off.
The ```color_color``` channel is of type ```color_color``` and supports the ```Color``` item and is in the ```ColorLight``` category.
### Color Temperature
The color temperature channel allows to set the color
temperature of a light from 0 (cold) to 100 (warm).
The ```color_temperature``` channel is of type ```color_temperature``` and supports the ```Dimmer``` item and is in the ```ColorLight``` category.
### Scene Number
Triggers when a scene button is pressed.
The ```scene_number``` channel is of type ```scene_number``` and supports the ```Number``` item.
This channel provides the scene, and the event as a decimal value in the form ```<scene>.<event>```. The scene number is set by the device, and the event is as follows -:
| Event ID | Event Description |
|----------|--------------------|
| 0 | Single key press |
| 1 | Key released |
| 2 | Key held down |
| 3 | Double keypress |
| 4 | Tripple keypress |
| 5 | 4 x keypress |
| 6 | 5 x keypress |
### Dimmer 1
The brightness channel allows to control the brightness of a light.
It is also possible to switch the light on and off.
The ```switch_dimmer1``` channel is of type ```switch_dimmer``` and supports the ```Dimmer``` item and is in the ```DimmableLight``` category.
### Color Control 1
The color channel allows to control the color of a light.
It is also possible to dim values and switch the light on and off.
The ```color_color1``` channel is of type ```color_color``` and supports the ```Color``` item and is in the ```ColorLight``` category.
### Color Temperature 1
The color temperature channel allows to set the color
temperature of a light from 0 (cold) to 100 (warm).
The ```color_temperature1``` channel is of type ```color_temperature``` and supports the ```Dimmer``` item and is in the ```ColorLight``` category.
### Scene Number 1
Triggers when a scene button is pressed.
The ```scene_number1``` channel is of type ```scene_number``` and supports the ```Number``` item.
This channel provides the scene, and the event as a decimal value in the form ```<scene>.<event>```. The scene number is set by the device, and the event is as follows -:
| Event ID | Event Description |
|----------|--------------------|
| 0 | Single key press |
| 1 | Key released |
| 2 | Key held down |
| 3 | Double keypress |
| 4 | Tripple keypress |
| 5 | 4 x keypress |
| 6 | 5 x keypress |
### Dimmer 2
The brightness channel allows to control the brightness of a light.
It is also possible to switch the light on and off.
The ```switch_dimmer2``` channel is of type ```switch_dimmer``` and supports the ```Dimmer``` item and is in the ```DimmableLight``` category.
### Color Control 2
The color channel allows to control the color of a light.
It is also possible to dim values and switch the light on and off.
The ```color_color2``` channel is of type ```color_color``` and supports the ```Color``` item and is in the ```ColorLight``` category.
### Color Temperature 2
The color temperature channel allows to set the color
temperature of a light from 0 (cold) to 100 (warm).
The ```color_temperature2``` channel is of type ```color_temperature``` and supports the ```Dimmer``` item and is in the ```ColorLight``` category.
### Scene Number 2
Triggers when a scene button is pressed.
The ```scene_number2``` channel is of type ```scene_number``` and supports the ```Number``` item.
This channel provides the scene, and the event as a decimal value in the form ```<scene>.<event>```. The scene number is set by the device, and the event is as follows -:
| Event ID | Event Description |
|----------|--------------------|
| 0 | Single key press |
| 1 | Key released |
| 2 | Key held down |
| 3 | Double keypress |
| 4 | Tripple keypress |
| 5 | 4 x keypress |
| 6 | 5 x keypress |
### Dimmer 3
The brightness channel allows to control the brightness of a light.
It is also possible to switch the light on and off.
The ```switch_dimmer3``` channel is of type ```switch_dimmer``` and supports the ```Dimmer``` item and is in the ```DimmableLight``` category.
### Color Control 3
The color channel allows to control the color of a light.
It is also possible to dim values and switch the light on and off.
The ```color_color3``` channel is of type ```color_color``` and supports the ```Color``` item and is in the ```ColorLight``` category.
### Color Temperature 3
The color temperature channel allows to set the color
temperature of a light from 0 (cold) to 100 (warm).
The ```color_temperature3``` channel is of type ```color_temperature``` and supports the ```Dimmer``` item and is in the ```ColorLight``` category.
### Scene Number 3
Triggers when a scene button is pressed.
The ```scene_number3``` channel is of type ```scene_number``` and supports the ```Number``` item.
This channel provides the scene, and the event as a decimal value in the form ```<scene>.<event>```. The scene number is set by the device, and the event is as follows -:
| Event ID | Event Description |
|----------|--------------------|
| 0 | Single key press |
| 1 | Key released |
| 2 | Key held down |
| 3 | Double keypress |
| 4 | Tripple keypress |
| 5 | 4 x keypress |
| 6 | 5 x keypress |
### Dimmer 4
The brightness channel allows to control the brightness of a light.
It is also possible to switch the light on and off.
The ```switch_dimmer4``` channel is of type ```switch_dimmer``` and supports the ```Dimmer``` item and is in the ```DimmableLight``` category.
### Color Control 4
The color channel allows to control the color of a light.
It is also possible to dim values and switch the light on and off.
The ```color_color4``` channel is of type ```color_color``` and supports the ```Color``` item and is in the ```ColorLight``` category.
### Color Temperature 4
The color temperature channel allows to set the color
temperature of a light from 0 (cold) to 100 (warm).
The ```color_temperature4``` channel is of type ```color_temperature``` and supports the ```Dimmer``` item and is in the ```ColorLight``` category.
### Scene Number 4
Triggers when a scene button is pressed.
The ```scene_number4``` channel is of type ```scene_number``` and supports the ```Number``` item.
This channel provides the scene, and the event as a decimal value in the form ```<scene>.<event>```. The scene number is set by the device, and the event is as follows -:
| Event ID | Event Description |
|----------|--------------------|
| 0 | Single key press |
| 1 | Key released |
| 2 | Key held down |
| 3 | Double keypress |
| 4 | Tripple keypress |
| 5 | 4 x keypress |
| 6 | 5 x keypress |
### Switch 5
Switch the power on and off.
The ```switch_binary5``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Dimmer 5
The brightness channel allows to control the brightness of a light.
It is also possible to switch the light on and off.
The ```switch_dimmer5``` channel is of type ```switch_dimmer``` and supports the ```Dimmer``` item and is in the ```DimmableLight``` category.
## Device Configuration
The following table provides a summary of the 23 configuration parameters available in the ZDB5400.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|-------|-------|-------------|
| 0 | Pushbutton debounce timer | Pushbutton input debounce time in 0.01 seconds resolution. |
| 1 | Operating pushbutton(s) for dimmer. | This parameter specifies which pushbutton(s) that shall be used to control the built-in dimmer |
| 2 | Duration of dimming | This parameter specifies the duration of a full regulation of the light from 0% to 100% |
| 3 | Duration of on/off | This parameter specifies the duration when turning the light on or off |
| 4 | Dimmer mode | The dimmer can work in three different modes. |
| 5 | Dimmer minimum level | This parameter specifies the actual level of the dimmer output when set to 0% |
| 6 | Dimmer maximum level | This parameter specifies the actual level of the dimmer output when set to 99% |
| 7 | Central Scene notifications | Central Scene notifications |
| 8 | Double-activation functionality | This parameter specifies the reaction when double-activating the pushbuttons |
| 10 | Enhanced LED control | This parameter can be used for enabling the enhanced LED control |
| 11 | Pushbutton debounce timer | Pushbutton input debounce time in 0.01 seconds resolution |
| 12 | Pushbutton press threshold time | Specifies the time that a pushbutton must be activated before it is detected as pressed |
| 13 | Pushbutton held threshold time | Specifies the time that a pushbutton must have been activated before it is accepted as “held-down” |
| 14 | Global brightness control | This parameter specifies a common brightness for each of the three base colours for all four pushbutton indicators |
| 15 | Associations groups, transmission when included secure | his parameter specifies if commands are transmitted as a secure message for each of the association groups |
| 16 | Pushbutton 1 functionality | This parameter specifies the functionality of pushbutton 1 |
| 17 | Timer value for pushbutton 1 | This parameter specifies the time used in parameter 16 |
| 18 | Multi-Level Switch Set values for pushbutton 1 | Multi-Level Switch Set values for pushbutton 1 |
| 19 | Basic Set support for pushbutton 1 | This parameter specifies how received Basic Set commands are handled |
| 20 | Pushbutton 1 LED indication. | This parameter specifies how the LED indication is controlled |
| 21 | Colour commands for pushbutton 1 LED indication | This parameter specifies how Command Class Switch Color commands are handled |
| 22 | ON indication RGB-saturation for pushbutton 1 | This parameter specifies the saturation levels when ON status is indicated |
| 23 | OFF indication RGB-saturation for pushbutton 1 | This parameter specifies the saturation levels when OFF status is indicated |
### Parameter 0: Pushbutton debounce timer
Pushbutton input debounce time in 0.01 seconds resolution.
1-255   1 – 2.55 seconds.
Default is 5, which equals to a debounce-filter on 50 milliseconds (0.05 seconds).
Values in the range 1 to 255 may be set.
The manufacturer defined default value is ```5```.
This parameter has the configuration ID ```config_0_1``` and is of type ```INTEGER```.
### Parameter 1: Operating pushbutton(s) for dimmer.
This parameter specifies which pushbutton(s) that shall be used to control the built-in dimmer
This parameter specifies which pushbutton(s) that shall be used to control the built-in dimmer. The parameter is a bitmask, so each of the values can be added up in order to have several pushbuttons to operate the dimmer
0    No local operation of the dimmer
1    Pushbutton 1 controls the dimmer
2    Pushbutton 2 controls the dimmer
4    Pushbutton 3 controls the dimmer
8    Pushbutton 4 controls the dimmer.
Values in the range 0 to 0 may be set.
The manufacturer defined default value is ```1```.
This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```.
### Parameter 2: Duration of dimming
This parameter specifies the duration of a full regulation of the light from 0% to 100%
A regulation of the light with 1% will take 1/100 of the specified duration. This is used when a pushbutton is held-down for controlling the dimming, and when the dimming is fulfilled from other Z-Wave devices when specifying factory default duration.
0           Immediately
1 - 127  Duration in seconds
128-255 Duration in minutes (minus 127), where 128 is 1 minute
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```5```.
This parameter has the configuration ID ```config_2_1``` and is of type ```INTEGER```.
### Parameter 3: Duration of on/off
This parameter specifies the duration when turning the light on or off
This parameter specifies the duration when turning the light on or off
0                Immediately
1 - 127      Time in seconds.
128 - 255  Time in minutes (minus 127), where 128 is 1 minute.
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_3_1``` and is of type ```INTEGER```.
### Parameter 4: Dimmer mode
The dimmer can work in three different modes.
The dimmer can work in three different modes: on/off, leading edge or trailing edge.
The following option values may be configured, in addition to values in the range 0 to 2 -:
| Value | Description |
|--------|-------------|
| 0 | No dimming |
| 1 | Trailing edge dimming |
| 2 | Leading edge dimming |
The manufacturer defined default value is ```1``` (Trailing edge dimming).
This parameter has the configuration ID ```config_4_1``` and is of type ```INTEGER```.
### Parameter 5: Dimmer minimum level
This parameter specifies the actual level of the dimmer output when set to 0%
0 - 99 Corresponds to 0 – 99%
Values in the range 0 to 99 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_5_1``` and is of type ```INTEGER```.
### Parameter 6: Dimmer maximum level
This parameter specifies the actual level of the dimmer output when set to 99%
1 - 99 Corresponds to 1 – 99%
Values in the range 1 to 99 may be set.
The manufacturer defined default value is ```99```.
This parameter has the configuration ID ```config_6_1``` and is of type ```INTEGER```.
### Parameter 7: Central Scene notifications
Central Scene notifications
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Notifications are disabled |
| 1 | Notifications are enabled |
The manufacturer defined default value is ```1``` (Notifications are enabled).
This parameter has the configuration ID ```config_7_1``` and is of type ```INTEGER```.
### Parameter 8: Double-activation functionality
This parameter specifies the reaction when double-activating the pushbuttons
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Double-activation disabled |
| 1 | Double-activation sets light to 100% |
The manufacturer defined default value is ```1``` (Double-activation sets light to 100%).
This parameter has the configuration ID ```config_8_1``` and is of type ```INTEGER```.
### Parameter 10: Enhanced LED control
This parameter can be used for enabling the enhanced LED control
See document about MATRIX enhanced LED control
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Enhanced LED control is disabled |
| 1 | Enhanced LED control is enabled |
The manufacturer defined default value is ```0``` (Enhanced LED control is disabled).
This parameter has the configuration ID ```config_10_1``` and is of type ```INTEGER```.
### Parameter 11: Pushbutton debounce timer
Pushbutton input debounce time in 0.01 seconds resolution
1 - 255    1 – 2.55 seconds.
Default is 5, which equals to a debounce-filter on 50 milliseconds (0.05 seconds).
Values in the range 1 to 255 may be set.
The manufacturer defined default value is ```5```.
This parameter has the configuration ID ```config_11_1``` and is of type ```INTEGER```.
### Parameter 12: Pushbutton press threshold time
Specifies the time that a pushbutton must be activated before it is detected as pressed
1 - 255   1 – 2.55 seconds, Resolution is in 0.01 seconds
Default is 20, which equals to 200 milliseconds (0.2 seconds).
Values in the range 1 to 255 may be set.
The manufacturer defined default value is ```20```.
This parameter has the configuration ID ```config_12_1``` and is of type ```INTEGER```.
### Parameter 13: Pushbutton held threshold time
Specifies the time that a pushbutton must have been activated before it is accepted as “held-down”
1 - 255      1 – 2.55 seconds. Resolution is 0.01 seconds
Default is 50, which equals to 500 milliseconds (0,5 seconds).
Values in the range 1 to 255 may be set.
The manufacturer defined default value is ```50```.
This parameter has the configuration ID ```config_13_1``` and is of type ```INTEGER```.
### Parameter 14: Global brightness control
This parameter specifies a common brightness for each of the three base colours for all four pushbutton indicators
Byte 1: Red brightness
0 - 255   Brightness level for the red colour in the 4 indicator groups. (Default is 255)
Byte 2: Green brightness
0 – 255   Brightness level for the green colour in the 4 indicator groups. (Default is 255)
Byte 3: Blue brightness
0 - 255   Brightness level for the blue colour in the 4 indicator groups. (Default is 255)
Byte 4: Not used – must be set to 0.
Values in the range 0 to 0 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_14_4``` and is of type ```INTEGER```.
### Parameter 15: Associations groups, transmission when included secure
his parameter specifies if commands are transmitted as a secure message for each of the association groups
This parameter is only used when the device is included in security mode (either S0 or S2).
0 All messages in all groups are sent as insecure
1 Messages in association group 2 are sent as secure
2 Messages in association group 3 are sent as secure
4 Messages in association group 4 are sent as secure
8 Messages in association group 5 are sent as secure
16 Messages in association group 6 are sent as secure
32 Messages in association group 7 are sent as secure
64 Messages in association group 8 are sent as secure
128 Messages in association group 9 are sent as secure
256 Messages in association group 10 are sent as secure
512 Messages in association group 11 are sent as secure
1024 Messages in association group 12 are sent as secure
2048 Messages in association group 13 are sent as secure
4096 Messages in association group 14 are sent as secure
8191 Messages in all association groups are sent as secure. (Default)
NB. The above values are bitmasks and can be added up to select several options.
Values in the range 0 to 0 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_15_2``` and is of type ```INTEGER```.
### Parameter 16: Pushbutton 1 functionality
This parameter specifies the functionality of pushbutton 1
0 Standard toggle-function, the state is switched between on and off, dimming up and down.
1 Automatic turn off after the time has expired (staircase lighting function), the time is specified in the next configuration parameter.
2 Automatic turn on after the time has expired, the time is specified in the next configuration parameter.
3 Always turn off or dim down. Using this parameter, the pushbutton can only send ‘off’ or ‘dim down’ commands. Use this in pair with another pushbutton with value 4 (see chapter 5.6).
4 Always turn on or dim up. Using this parameter, the pushbutton can only send ‘on’ or ‘
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Standard toggle-function |
| 1 | Automatic turn off |
| 2 | Automatic turn on |
| 3 | Always turn off or dim down |
| 4 | Always turn on or dim up |
The manufacturer defined default value is ```0``` (Standard toggle-function).
This parameter has the configuration ID ```config_16_1``` and is of type ```INTEGER```.
### Parameter 17: Timer value for pushbutton 1
This parameter specifies the time used in parameter 16
This parameter specifies the time used in previous configuration parameter. This parameter is only applicable if previous parameter has value 1 or 2.
Specifies the time in seconds. Default is 300 = 5 minutes.
Values in the range 0 to 43200 may be set.
The manufacturer defined default value is ```300```.
This parameter has the configuration ID ```config_17_1``` and is of type ```INTEGER```.
### Parameter 18: Multi-Level Switch Set values for pushbutton 1
Multi-Level Switch Set values for pushbutton 1
Byte 1: Enable / Disable
0 Disabled – A single activation of the pushbutton will not send commands to devices in association group 4.
1 Enabled – A single activation will send commands to devices in association group 4. Devices will receive commands with the values set in Byte 2 and 3 (Default).
Byte 2: Upper switch value
0 – 99,255 When single pressing the pushbutton for ON, a Multilevel Switch Set with this value will be send to devices in association group 4. (Default = 255)
Byte 3: Lower switch value
0 - 99 When single pressing the pushbutton for OFF, a Multilevel Switch Set with this value will be send to devices in association group 4. (Default = 0)
Byte 4: Not used – must be set to 0.
Values in the range 0 to 0 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_18_4``` and is of type ```INTEGER```.
### Parameter 19: Basic Set support for pushbutton 1
This parameter specifies how received Basic Set commands are handled
0 Basic Set only controls the pushbutton indicator LEDs, ON/OFF. (Default)
1 Basic Set controls the internal switch status and the pushbutton indicator LEDs.
2 Basic Set is handled as if the user had activated the pushbutton, including transmission of commands via the association groups.
Values in the range 0 to 0 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_19_1``` and is of type ```INTEGER```.
### Parameter 20: Pushbutton 1 LED indication.
This parameter specifies how the LED indication is controlled
0 Internal LED control is disabled, only external commands control the indication.
1 The LED indication follows the switch status.
2 The LED indication follows the switch status – with inverted functionality.
3 Same as 1
4 Same as 2
5 The LED indication follows the status of the internal dimmer, ON or OFF.
6 The LED indication follows the status of the internal dimmer with inverted  functionality, ON or OFF.
7 The LED indicator is ON for 5 seconds when the pushbutton is activated. (Default).
Values in the range 0 to 0 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_20_1``` and is of type ```INTEGER```.
### Parameter 21: Colour commands for pushbutton 1 LED indication
This parameter specifies how Command Class Switch Color commands are handled
0 Direct control; the LED indication shows the received colour immediately, until the pushbutton is activated.
1 Colour command sets the colour for OFF indication. (Default).
2 Colour command sets the colour for ON indication.
Values in the range 0 to 0 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_21_1``` and is of type ```INTEGER```.
### Parameter 22: ON indication RGB-saturation for pushbutton 1
This parameter specifies the saturation levels when ON status is indicated
This parameter specifies the saturation levels for the red, green and blue LEDs, when ON status is indicated. (Default is the ON-state indicated by a 50% blue colour).
Byte 1: Colour saturation, red.
0 - 255 Specifies the saturation for the red LEDs. (Default is 0)
Byte 2: Colour saturation, green.
0 – 255 Specifies the saturation for the green LEDs. (Default is 0)
Byte 3: Colour saturation, blue.
0 - 255 Specifies the saturation for the blue LEDs. (Default is 127)
Byte 4: LED control.
0 - 255 LED indicator control; see the application note about this parameter.(Default is 0)
Values in the range 0 to 0 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_22_4``` and is of type ```INTEGER```.
### Parameter 23: OFF indication RGB-saturation for pushbutton 1
This parameter specifies the saturation levels when OFF status is indicated
This parameter specifies the saturation levels for the red, green and blue LEDs, when OFF status is indicated. (Default is the OFF-state indicated as a low white light on 5%)
Byte 1: Colour saturation, red.
0 - 255  Specifies the saturation for the red LEDs. (Default is 47).
Byte 2: Colour saturation, green.
0 – 255  Specifies the saturation for the green LEDs. (Default is 47)
Byte 3: Colour saturation, blue.
0 - 255  Specifies the saturation for the blue LEDs. (Default is 47)
Byte 4: LED control.
0 - 255  LED indicator control; see the application note about this parameter. (Default is 0)
Values in the range 0 to 0 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_23_4``` and is of type ```INTEGER```.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The ZDB5400 supports 4 association groups.
### Group 1: Lifeline
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation.
Association group 1 supports 5 nodes.
### Group 2: Button 1 Basic Report
Association group 2 supports 5 nodes.
### Group 3: Button 1 Switch Binary Set
Association group 3 supports 5 nodes.
### Group 4: Button 1 Switch Multilevel
Association group 4 supports 5 nodes.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| |
| COMMAND_CLASS_SWITCH_COLOR_V1| |
| COMMAND_CLASS_TRANSPORT_SERVICE_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_CENTRAL_SCENE_V3| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_MULTI_CHANNEL_V2| |
| COMMAND_CLASS_SUPERVISION_V1| |
| COMMAND_CLASS_CONFIGURATION_V1| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| |
| COMMAND_CLASS_SECURITY_V1| |
| COMMAND_CLASS_SECURITY_2_V1| |
#### Endpoint 1
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| |
| COMMAND_CLASS_SWITCH_COLOR_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_CENTRAL_SCENE_V3| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| |
| COMMAND_CLASS_SECURITY_V1| |
#### Endpoint 2
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| |
| COMMAND_CLASS_SWITCH_COLOR_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_CENTRAL_SCENE_V3| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| |
| COMMAND_CLASS_SECURITY_V1| |
#### Endpoint 3
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| |
| COMMAND_CLASS_SWITCH_COLOR_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_CENTRAL_SCENE_V3| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| |
| COMMAND_CLASS_SECURITY_V1| |
#### Endpoint 4
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| |
| COMMAND_CLASS_SWITCH_COLOR_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_CENTRAL_SCENE_V3| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| |
| COMMAND_CLASS_SECURITY_V1| |
#### Endpoint 5
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| |
| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| |
| COMMAND_CLASS_SECURITY_V1| |
### Documentation Links
* [ZDB5400 Manual](https://opensmarthouse.org/zwavedatabase/1316/reference/zdb5400-manual-3.pdf)
* [manual (readable)](https://opensmarthouse.org/zwavedatabase/1316/reference/772953_51628_manual-en.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1316).

276
_addons_bindings/zwave/doc/mcohome/mh3901_0_0.md Normal file
View File

@ -0,0 +1,276 @@
---
layout: documentation
title: MH3901 - ZWave
---
{% include base.html %}
# MH3901 Boiler Thermostat
This describes the Z-Wave device *MH3901*, manufactured by *[McoHome Technology Co., Ltd](http://www.mcohome.com/)* with the thing type UID of ```mcohome_mh3901_00_000```.
The device is in the category of *HVAC*, defining Air condition devices, Fans.
![MH3901 product image](https://opensmarthouse.org/zwavedatabase/1253/image/)
The MH3901 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data between other devices in the mesh network.
## Overview
MCOHome Thermostat for Water Heating is a Z-Wave enabled device for indoor temperature control.
*  Capacitive touch buttons
* Attractive appearance
* Clear display, easy to operate
### Inclusion Information
Long press on S1 + S3 
### Exclusion Information
Long press on S1 + S3 
### General Usage Information
## Channels
The following table summarises the channels available for the MH3901 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Sensor (relative humidity) | sensor_relhumidity | sensor_relhumidity | Humidity | Number |
| Sensor (temperature) | sensor_temperature | sensor_temperature | Temperature | Number:Temperature |
| Thermostat mode | thermostat_mode | thermostat_mode | Temperature | Number |
| Operating State | thermostat_state | thermostat_state | Temperature | Number |
| Setpoint (heating) | thermostat_setpoint | thermostat_setpoint | Heating | Number:Temperature |
### Sensor (relative humidity)
Indicates the current relative humidity.
The ```sensor_relhumidity``` channel is of type ```sensor_relhumidity``` and supports the ```Number``` item and is in the ```Humidity``` category. This is a read only channel so will only be updated following state changes from the device.
### Sensor (temperature)
Indicates the current temperature.
The ```sensor_temperature``` channel is of type ```sensor_temperature``` and supports the ```Number:Temperature``` item and is in the ```Temperature``` category.
### Thermostat mode
Sets the thermostat.
The ```thermostat_mode``` channel is of type ```thermostat_mode``` and supports the ```Number``` item and is in the ```Temperature``` category.
The following state translation is provided for this channel to the ```Number``` item type -:
| Value | Label |
|-------|-----------|
| 0 | Off |
| 1 | Heat |
| 2 | Cool |
| 3 | Auto |
| 4 | Aux Heat |
| 5 | Resume |
| 6 | Fan Only |
| 7 | Furnace |
| 8 | Dry Air |
| 9 | Moist Air |
| 10 | Auto Changeover |
| 11 | Heat Economy |
| 12 | Cool Economy |
| 13 | Away |
### Operating State
Sets the thermostat operating state.
The ```thermostat_state``` channel is of type ```thermostat_state``` and supports the ```Number``` item and is in the ```Temperature``` category.
The following state translation is provided for this channel to the ```Number``` item type -:
| Value | Label |
|-------|-----------|
| 0 | Idle |
| 1 | Heating |
| 2 | Cooling |
| 3 | Fan Only |
| 4 | Pending Heat |
| 5 | Pending Cool |
| 6 | Vent / Economiser |
### Setpoint (heating)
Sets the thermostat setpoint.
The ```thermostat_setpoint``` channel is of type ```thermostat_setpoint``` and supports the ```Number:Temperature``` item and is in the ```Heating``` category.
## Device Configuration
The following table provides a summary of the 8 configuration parameters available in the MH3901.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|-------|-------|-------------|
| 1 | Automatic Temperature Value Reporting | |
| 2 | Temperature Difference Setting | Base on 0.1 ºC unit; n*0.1 ºC=0.5 ºC |
| 3 | Timed report intervals | Base on 1s unit, it suggest to be set above 30s |
| 4 | Humidity Difference Reporting | |
| 5 | Association 2 SET Command Retransmition times | |
| 7 | Secret Manu P07 | |
| 8 | Secret Menu P08 | |
| 255 | Factory Reset | |
### Parameter 1: Automatic Temperature Value Reporting
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Off |
| 1 | Only report the difference |
| 2 | Regular reporting only |
| 3 | Difference reporting + interval reporting |
The manufacturer defined default value is ```1``` (Only report the difference).
This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```.
### Parameter 2: Temperature Difference Setting
Base on 0.1 ºC unit; n*0.1 ºC=0.5 ºC
Values in the range 3 to 995 may be set.
The manufacturer defined default value is ```60```.
This parameter has the configuration ID ```config_2_2``` and is of type ```INTEGER```.
### Parameter 3: Timed report intervals
Base on 1s unit, it suggest to be set above 30s
Values in the range 10 to 32767 may be set.
The manufacturer defined default value is ```60```.
This parameter has the configuration ID ```config_3_2``` and is of type ```INTEGER```.
### Parameter 4: Humidity Difference Reporting
0x00: Disabled
1-99: A Humidity difference value greater than this will be automatically reported to the gateway
Values in the range 0 to 99 may be set.
The manufacturer defined default value is ```3```.
This parameter has the configuration ID ```config_4_1``` and is of type ```INTEGER```.
### Parameter 5: Association 2 SET Command Retransmition times
0: Not resend
1-127: Resend Times
Values in the range 0 to 127 may be set.
The manufacturer defined default value is ```3```.
This parameter has the configuration ID ```config_5_1``` and is of type ```INTEGER```.
### Parameter 7: Secret Manu P07
Heating period setting unit: min, range: 10-120,
default: 20, step value: 1
Values in the range 10 to 120 may be set.
The manufacturer defined default value is ```20```.
This parameter has the configuration ID ```config_7_1``` and is of type ```INTEGER```.
### Parameter 8: Secret Menu P08
Heating time should be less than P07 value. 
Values in the range 10 to 120 may be set.
The manufacturer defined default value is ```3```.
This parameter has the configuration ID ```config_8_1``` and is of type ```INTEGER```.
### Parameter 255: Factory Reset
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 17185 | Restore default complex parameters |
| 39030 | Restore factory settings |
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_255_2``` and is of type ```INTEGER```.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The MH3901 supports 2 association groups.
### Group 1: Lifeline
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation.
Association group 1 supports 1 node.
### Group 2: Device status changes
Association group 2 supports 5 nodes.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SENSOR_MULTILEVEL_V5| |
| COMMAND_CLASS_THERMOSTAT_MODE_V1| |
| COMMAND_CLASS_THERMOSTAT_OPERATING_STATE_V1| |
| COMMAND_CLASS_THERMOSTAT_SETPOINT_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_CONFIGURATION_V1| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
### Documentation Links
* [manual](https://opensmarthouse.org/zwavedatabase/1253/reference/MH3901-Z.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1253).

230
_addons_bindings/zwave/doc/nietech/ms13z_0_0.md Normal file
View File

@ -0,0 +1,230 @@
---
layout: documentation
title: MS13Z - ZWave
---
{% include base.html %}
# MS13Z Minoston Toggle Dimmer Switch
This describes the Z-Wave device *MS13Z*, manufactured by *NIE Technology* with the thing type UID of ```nietech_ms13z_00_000```.
The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch.
![MS13Z product image](https://opensmarthouse.org/zwavedatabase/1229/image/)
The MS13Z supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data between other devices in the mesh network.
## Overview
Transform any home into a smart home with the Z-Wave Smart Switch. The switch enables you to wirelessly control to turn lights on and off, schedule a timed event or create a custom scene from anywhere in the world, at any time of the day. Take control of your home lighting with Z-Wave Smart Lighting Controls
### Inclusion Information
Make your controller/hub into the "inclusion" mode, triple press the Up/Down push button quickly to include it in the network.
### Exclusion Information
Make your controller/hub into the "exclusion" mode, triple press the Up/Down push button quickly to exclude it from the network.
### General Usage Information
## Channels
The following table summarises the channels available for the MS13Z -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Dimmer | switch_dimmer | switch_dimmer | DimmableLight | Dimmer |
| Scene Number | scene_number | scene_number | | Number |
### Dimmer
The brightness channel allows to control the brightness of a light.
It is also possible to switch the light on and off.
The ```switch_dimmer``` channel is of type ```switch_dimmer``` and supports the ```Dimmer``` item and is in the ```DimmableLight``` category.
### Scene Number
Triggers when a scene button is pressed.
The ```scene_number``` channel is of type ```scene_number``` and supports the ```Number``` item.
This channel provides the scene, and the event as a decimal value in the form ```<scene>.<event>```. The scene number is set by the device, and the event is as follows -:
| Event ID | Event Description |
|----------|--------------------|
| 0 | Single key press |
| 1 | Key released |
| 2 | Key held down |
| 3 | Double keypress |
| 4 | Tripple keypress |
| 5 | 4 x keypress |
| 6 | 5 x keypress |
## Device Configuration
The following table provides a summary of the 6 configuration parameters available in the MS13Z.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|-------|-------|-------------|
| 1 | Locally Button Function | LED flashes 2 times when the configuration parameter changed. |
| 2 | LED Indicator | LED flashes 2 times |
| 4 | Auto Turn-Off Timer | Auto Turn-Off Timer |
| 6 | Auto Turn-On Timer | Auto Turn-On Timer |
| 7 | Association Setting Parameter | Association Setting Parameter |
| 8 | Restores state after power failure | Restores state after power failure |
### Parameter 1: Locally Button Function
LED flashes 2 times when the configuration parameter changed.
Locally Button function(quickly press 7x)
Value=0 Up Button: On/Down Button: Off(Default)
Value=1 Up Button: Off/Down Button: On
Value=2 Up Button: On/Off/Down Button: On/Off
\---Parameter 1: Choose if you want the upper paddle to turn the light on or turn the light off when tapped, or if you'd like any paddle to change the state of the light.
Values: 0 – Upper paddle turns the light on, lower paddle turns the light off (default);
Values: 1 – Upper paddle turns the light off, lower paddle turns the light on;
Values: 2 – any paddle changes the state of the light.
Values in the range 0 to 2 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```.
### Parameter 2: LED Indicator
LED flashes 2 times
LED Indicator(quickly press 6x)
Value=0 On when output Off and Off when output On (default)
Value=1 On when output On and Off when output Off
Value=2 Always Off
Values in the range 0 to 2 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_2_1``` and is of type ```INTEGER```.
### Parameter 4: Auto Turn-Off Timer
Auto Turn-Off Timer
Values: 0 – 65535 (minutes); 0 (minutes) – default setting
Values in the range 0 to 65535 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_4_4``` and is of type ```INTEGER```.
### Parameter 6: Auto Turn-On Timer
Auto Turn-On Timer
Values: 0 – 65535 (minutes); 0 (minutes) – default setting
Values in the range 0 to 65535 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_6_4``` and is of type ```INTEGER```.
### Parameter 7: Association Setting Parameter
Association Setting Parameter
* Value=00 – none
* Value=01 - local
* Value=02 - 3way
* Value=03 - 3way & local
* Value=04 - z-wave hub
* Value= Value=05 - z-wave hub & local
* Value=06 - z-wave hub & 3-way
* Value=07 - z-wave hub & local & 3way
* Value=08 - timer
* Value=09 - timer & local
* Value=10 - timer & 3-way
* Value=11 - timer & 3-way & local
* Value=12 - timer & z-wave hub
* Value=13 - timer & z-wave hub & local
* Value=14 - timer & z-wave hub & 3-way
* Value=15 - all
Values in the range 0 to 15 may be set.
The manufacturer defined default value is ```1```.
This parameter has the configuration ID ```config_7_1``` and is of type ```INTEGER```.
### Parameter 8: Restores state after power failure
Restores state after power failure
Value=0 output off
Value=1 output on
Value=2 output the state after power
Values in the range 0 to 2 may be set.
The manufacturer defined default value is ```2```.
This parameter has the configuration ID ```config_8_1``` and is of type ```INTEGER```.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The MS13Z supports 2 association groups.
### Group 1: Lifeline
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation.
Association group 1 supports 1 node.
### Group 2: Send Basic Set ON / Off
Association group 2 supports 5 nodes.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| Linked to BASIC|
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_CENTRAL_SCENE_V3| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_CONFIGURATION_V1| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| |
### Documentation Links
* [User Manual](https://opensmarthouse.org/zwavedatabase/1229/reference/71GzBcTlViL.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1229).

214
_addons_bindings/zwave/doc/philio/pab04_0_0.md Normal file
View File

@ -0,0 +1,214 @@
---
layout: documentation
title: PAB04 - ZWave
---
{% include base.html %}
# PAB04 Smart Energy Flow Meter
This describes the Z-Wave device *PAB04*, manufactured by *[Philio Technology Corp](http://www.philio-tech.com/)* with the thing type UID of ```philio_pab04_00_000```.
The device is in the category of *Valve*, defining Valves used to control water or gas. e.g. a flow stop valve..
![PAB04 product image](https://opensmarthouse.org/zwavedatabase/1224/image/)
The PAB04 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data between other devices in the mesh network.
## Overview
This valves controller PAB04 is a security enabled wireless switch, based on Z-Wave Plus technology. 
Connect PAB04 with an external water meter which can output pulse signals. PAB04 is able to detect instance water flow and the accumulated water.
### Inclusion Information
Pressing On/Off button three times within 2 seconds will enter inclusion mode.
### Exclusion Information
Pressing On/Off button three times within 2 seconds will enter exclusion mode.
### General Usage Information
## Channels
The following table summarises the channels available for the PAB04 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Switch | switch_binary | switch_binary | Switch | Switch |
| Sensor (WATER_FLOW) | water_flow | water_flow | | |
| Water meter (gal) | meter_water_gallons | meter_water_gallons | Water | Number |
| Water meter (m3) | meter_water_cubic_meters | meter_water_cubic_meters | Water | Number |
### Switch
Switch the power on and off.
The ```switch_binary``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Sensor (WATER_FLOW)
Channel type information on this channel is not found.
### Water meter (gal)
Indicates the instantaneous water consumption.
The ```meter_water_gallons``` channel is of type ```meter_water_gallons``` and supports the ```Number``` item and is in the ```Water``` category. This is a read only channel so will only be updated following state changes from the device.
### Water meter (m3)
Indicates the instantaneous water consumption.
The ```meter_water_cubic_meters``` channel is of type ```meter_water_cubic_meters``` and supports the ```Number``` item and is in the ```Water``` category. This is a read only channel so will only be updated following state changes from the device.
## Device Configuration
The following table provides a summary of the 6 configuration parameters available in the PAB04.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|-------|-------|-------------|
| 1 | Unit of Water Flow | Unit of Water Flow |
| 2 | Accumulated Water Report | Accumulated Water Report |
| 3 | Instant Water Flow Percent Reported | Instant Water Flow Percent Reported |
| 4 | Pulses per Liter | Pulses per Liter |
| 5 | Relay Control Mode | Relay Control Mode |
| 6 | Periodic Auto Report Timer | Periodic Auto Report Timer |
### Parameter 1: Unit of Water Flow
Unit of Water Flow
The following option values may be configured, in addition to values in the range 1 to 2 -:
| Value | Description |
|--------|-------------|
| 1 | US Gallon |
| 2 | KL |
The manufacturer defined default value is ```2``` (KL).
This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```.
### Parameter 2: Accumulated Water Report
Accumulated Water Report
The following option values may be configured, in addition to values in the range 0 to 1 -:
| Value | Description |
|--------|-------------|
| 0 | Disable Report |
| 1 | Enable Report |
The manufacturer defined default value is ```1``` (Enable Report).
This parameter has the configuration ID ```config_2_1``` and is of type ```INTEGER```.
### Parameter 3: Instant Water Flow Percent Reported
Instant Water Flow Percent Reported
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Disabled |
The manufacturer defined default value is ```10```.
This parameter has the configuration ID ```config_3_1``` and is of type ```INTEGER```.
### Parameter 4: Pulses per Liter
Pulses per Liter
This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
Values in the range 1 to 32676 may be set.
The manufacturer defined default value is ```450```.
This parameter has the configuration ID ```config_4_2``` and is of type ```INTEGER```.
### Parameter 5: Relay Control Mode
Relay Control Mode
The following option values may be configured, in addition to values in the range 0 to 1 -:
| Value | Description |
|--------|-------------|
| 0 | Normally Closed |
| 1 | Normally Open |
The manufacturer defined default value is ```0``` (Normally Closed).
This parameter has the configuration ID ```config_5_1``` and is of type ```INTEGER```.
### Parameter 6: Periodic Auto Report Timer
Periodic Auto Report Timer
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Disabled |
The manufacturer defined default value is ```60```.
This parameter has the configuration ID ```config_6_2``` and is of type ```INTEGER```.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The PAB04 supports 1 association group.
### Group 1: Lifeline
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation.
Association group 1 supports 1 node.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| |
| COMMAND_CLASS_SENSOR_MULTILEVEL_V9| |
| COMMAND_CLASS_METER_V2| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_CONFIGURATION_V1| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
| COMMAND_CLASS_SECURITY_V1| |
### Documentation Links
* [Manual](https://opensmarthouse.org/zwavedatabase/1224/reference/PAB04_manual-V2-20200219.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1224).

211
_addons_bindings/zwave/doc/philio/psm09_0_0.md Normal file
View File

@ -0,0 +1,211 @@
---
layout: documentation
title: PSM09 - ZWave
---
{% include base.html %}
# PSM09 Recessed Door Sensor + Door lock Sensor
This describes the Z-Wave device *PSM09*, manufactured by *[Philio Technology Corp](http://www.philio-tech.com/)* with the thing type UID of ```philio_psm09_00_000```.
The device is in the category of *Sensor*, defining Device used to measure something.
![PSM09 product image](https://opensmarthouse.org/zwavedatabase/1225/image/)
The PSM09 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices.
The PSM09 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information.
## Overview
The PSM09 can detect the the door is open or not, and lock or unlock. The Recessed door sensor PSM09 is Base on Z-WaveTM technology. It is the Z-WaveTM plus product, it support the security, OTA... Those newest features of the Z-WaveTM technology. Z-WaveTM is a wireless communication protocol designed for home automation, specifically to remotely control applications in residential and light commercial environments. The technology uses a low-power RF radio embedded or retrofitted into home electronics devices and systems, such as lighting, home access control, entertainment systems and household appliances
### Inclusion Information
Have Z-WaveTM Controller entered inclusion mode. Pressing tamper key three times within 3 seconds to enter the inclusion mode. If the learning code is successful, the LED will flash slowly.
### Exclusion Information
Have Z-WaveTM Controller entered exclusion mode. Pressing tamper key three times within 3 seconds to enter the exclusion mode. If the removal is successful, the code light will flash for 30 seconds. Node ID has been excluded.
### Wakeup Information
The PSM09 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour.
The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device.
If the user want to wake-up the device immediately, please press the tamper key once. The device will wake-up 10 seconds.
### General Usage Information
## Channels
The following table summarises the channels available for the PSM09 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Alarm (access) | alarm_access | alarm_access | Door | Switch |
| Battery Level | battery-level | system.battery_level | Battery | Number |
| Battery Level | battery-level | system.battery_level | Battery | Number |
| Battery Level | battery-level | system.battery_level | Battery | Number |
### Alarm (access)
Indicates if the access control alarm is triggered.
The ```alarm_access``` channel is of type ```alarm_access``` and supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device.
The following state translation is provided for this channel to the ```Switch``` item type -:
| Value | Label |
|-------|-----------|
| OFF | OK |
| ON | Alarm |
### Battery Level
Represents the battery level as a percentage (0-100%). Bindings for things supporting battery level in a different format (e.g. 4 levels) should convert to a percentage to provide a consistent battery level reading.
The ```system.battery-level``` channel is of type ```system.battery-level``` and supports the ```Number``` item and is in the ```Battery``` category.
This channel provides the battery level as a percentage and also reflects the low battery warning state. If the battery state is in low battery warning state, this will read 0%.
### Battery Level
Represents the battery level as a percentage (0-100%). Bindings for things supporting battery level in a different format (e.g. 4 levels) should convert to a percentage to provide a consistent battery level reading.
The ```system.battery-level``` channel is of type ```system.battery-level``` and supports the ```Number``` item and is in the ```Battery``` category.
This channel provides the battery level as a percentage and also reflects the low battery warning state. If the battery state is in low battery warning state, this will read 0%.
### Battery Level
Represents the battery level as a percentage (0-100%). Bindings for things supporting battery level in a different format (e.g. 4 levels) should convert to a percentage to provide a consistent battery level reading.
The ```system.battery-level``` channel is of type ```system.battery-level``` and supports the ```Number``` item and is in the ```Battery``` category.
This channel provides the battery level as a percentage and also reflects the low battery warning state. If the battery state is in low battery warning state, this will read 0%.
## Device Configuration
The following table provides a summary of the 4 configuration parameters available in the PSM09.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|-------|-------|-------------|
| 1 | Auto report state time | |
| 2 | Door lock detect function switch | |
| 3 | Door lock detect timer | |
| 4 | Door lock detect level | |
| | Wakeup Interval | Sets the interval at which the device will accept commands from the controller |
| | Wakeup Node | Sets the node ID of the device to receive the wakeup notifications |
### Parameter 1: Auto report state time
The interval time for auto report the door/window & Lock state & battery level. 0 means turn off auto report state. Units of 30 minutes.
Values in the range 0 to 127 may be set.
The manufacturer defined default value is ```12```.
This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```.
### Parameter 2: Door lock detect function switch
0 means turn off Door lock detect funtion.
1 means turn on Door lock detect funtion.
Values in the range 0 to 1 may be set.
The manufacturer defined default value is ```1```.
This parameter has the configuration ID ```config_2_1``` and is of type ```INTEGER```.
### Parameter 3: Door lock detect timer
Units of 20 seconds.
Values in the range 1 to 127 may be set.
The manufacturer defined default value is ```3```.
This parameter has the configuration ID ```config_3_1``` and is of type ```INTEGER```.
### Parameter 4: Door lock detect level
When an error condition occurs in the door lock detection.
Can reduce its level to avoid door lock detection errors.
Values in the range 1 to 10 may be set.
The manufacturer defined default value is ```10```.
This parameter has the configuration ID ```config_4_1``` and is of type ```INTEGER```.
### Wakeup Interval
The wakeup interval sets the period at which the device will listen for messages from the controller. This is required for battery devices that sleep most of the time in order to conserve battery life. The device will wake up at this interval and send a message to the controller to tell it that it can accept messages - after a few seconds, it will go back to sleep if there is no further communications.
This setting is defined in *seconds*. It is advisable not to set this interval too short or it could impact battery life. A period of 1 hour (3600 seconds) is suitable in most instances.
Note that this setting does not affect the devices ability to send sensor data, or notification events.
This parameter has the configuration ID ```wakeup_interval``` and is of type ```INTEGER```.
### Wakeup Node
When sleeping devices wake up, they send a notification to a listening device. Normally, this device is the network controller, and normally the controller will set this automatically to its own address.
In the event that the network contains multiple controllers, it may be necessary to configure this to a node that is not the main controller. This is an advanced setting and should not be changed without a full understanding of the impact.
This parameter has the configuration ID ```wakeup_node``` and is of type ```INTEGER```.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The PSM09 supports 1 association group.
### Group 1: Lifeline
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation.
Association group 1 supports 5 nodes.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_CONFIGURATION_V1| |
| COMMAND_CLASS_ALARM_V8| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| |
| COMMAND_CLASS_BATTERY_V1| |
| COMMAND_CLASS_BATTERY_V1| |
| COMMAND_CLASS_BATTERY_V1| |
| COMMAND_CLASS_WAKE_UP_V2| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| |
| COMMAND_CLASS_SECURITY_V1| |
### Documentation Links
* [Manual](https://opensmarthouse.org/zwavedatabase/1225/reference/PSM09_UserManual_0624.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1225).

6
_addons_bindings/zwave/doc/qubino/zmnhxd_0_0.md
View File

@ -287,7 +287,7 @@ Available configuration parameters (data type is 1 Byte DEC)
**NOTE:** Device is measuring also some disturbances even if on the output is no load. To avoid disturbances:
* If measured Active Power (W) is below e.g. 5W-> the reported value in this case is 0WThis is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
The following option values may be configured, in addition to values in the range 0 to 100 -:
The following option values may be configured -:
| Value | Description |
|--------|-------------|
@ -313,7 +313,7 @@ Energy Total (kvarh), Total Energy (kVAh)
**Note:** Device is reporting only if there was a change of 0.1 in Energy
**Note:** In the future will be possible to measure and report also Active Energy on PH1, PH2 and PH3.This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
The following option values may be configured, in addition to values in the range 600 to 65535 -:
The following option values may be configured -:
| Value | Description |
|--------|-------------|
@ -333,7 +333,7 @@ Energy reports for Voltage, Current, Total Power Factor, Total Reactive Power
* 0 – reporting disabled
* 600-65536 = 600 (600 seconds – 65536 seconds). Reporting enabled. Report is sent with the time interval set by entered value.
* Note: Device is reporting only if there was a changeThis is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
The following option values may be configured, in addition to values in the range 600 to 65535 -:
The following option values may be configured -:
| Value | Description |
|--------|-------------|

110
_addons_bindings/zwave/doc/sunricher/ZV9001K4RGBW_0_0.md Normal file
View File

@ -0,0 +1,110 @@
---
layout: documentation
title: ZV9001K4-RGBW - ZWave
---
{% include base.html %}
# ZV9001K4-RGBW Z-Wave RGBW Remote Control
This describes the Z-Wave device *ZV9001K4-RGBW*, manufactured by *[Sunricher](www.sunricher.com)* with the thing type UID of ```sunricher_ZV9001K4RGBW_00_000```.
The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch.
![ZV9001K4-RGBW product image](https://opensmarthouse.org/zwavedatabase/1285/image/)
The ZV9001K4-RGBW does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information.
## Overview
The remote control is a Z-Wave device that can both control other Z-Wave devices and activate scenes in Gateways. Although it is controlling other devices, the device cannot act as Z-Wave network controller (primary or secondary) and will always need a Z-Wave network controller to be included into a Z-Wave network. It also supports the Over The Air (OTA) feature for the product’s firmware upgrade. The remote control has following functions: 1. Control of groups of other Z-Wave devices using 'ON', 'OFF', Dim and RGB color control commands. 2. Activation of scenes in Gateway mode. The encryption modes that the remote control supports are S0, S2 Authenticated, S2 Unauthenticated. When the remote control is being included into a Z-Wave network, you can use your primary controller/gateway to enable one encryption mode or disable encryption. (The primary controller/gateway shall support encryption mode configuration). 
### Inclusion Information
Step 1. Make sure the remote control does not belong to any Z-Wave network, short press any button, if LED indicator does not turn on, the remote control does not belong to any network, then continue step 2,if LED indicator turns on, it means the remote control has already been included to a network, please first set the remote control to exclusion mode (refer to the part "Exclusion" of this manual),then continue step 2. Step 2. Set primary controller/gateway into inclusion mode (Please refer to your primary controllers manual on how to turn your controller into inclusion). Step 3. Press and hold down both buttons and of Group 2 over 3 seconds, LED indicator turns on, the remote control will be set to inclusion mode, and waiting to be included, after 10s LED indicator blinks 6 times quickly to indicate successful inclusion. The remote control is a sleepy device, after inclusion it will not enter into sleepy mode immediately, and will continue activation status for 30s and wait data interaction from the gateway, the LED indicator will stay solid on, please be patient to wait LED indicator to turn off.
### Exclusion Information
There are two exclusion methods: Method 1: Exclusion from the primary controller/gateway as follows: 1. Set the primary controller/gateway into exclusion mode (Please refer to your primary controllers manual on how to set your controller into exclusion). 2. Press and hold down both buttons and of Group 2 over 3 seconds, LED indicator turns on, the remote control will be set to exclusion mode, and waiting to be excluded, after 7s LED indicator blinks 4 times quickly to indicate successful exclusion. Z-Wave RGBW Remote Control Front side 55.57 mm 71.20 mm 11 mm Back side Battery: CR2450 Before the first use, please remove the protective film 55.57 mm 71.20 mm The remote control can be fixed on the wall with 3M glue or screw. Group 2: click to turn on/off Group 2: press and hold down to increase/decrease light intensity Group 2: click to turn on/off white channel Group 2: click to get R, G, B colors one by one, press and hold down to cycle RGB colors Press and hold down both keys together for 3s to be added to or removed from Z-Wave network by Z-Wave master (primary) controller. Product Data Z-Wave Frequency Power Supply Operating temperature Relative humidity Dimensions Waterproof Grade 868.42MHz 3VDC(1xCR2450 battery) 0 to 40°C 8% to 80% 71.2x71.2x13.6mm IP20 Method 2: Factory reset the remote control will force the remote control to be excluded from a network. (please refer to the part “Factory Reset” of this manual) Note: Factory reset is not recommended for exclusion, please use this procedure only if the primary controller/gateway is missing or otherwise inoperable
### Wakeup Information
The ZV9001K4-RGBW does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour.
The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device.
The remote control is under sleepy mode for most of the time to save battery power. It can not receive wireless command under sleepy mode. Before the gateway interacts data with the remote, the remote control shall be activated manually first. Short press any button to activate the remote control for 3s, and press and hold down and buttons of Group 2 together over 1 second to activate the remote control for 7s. 
### General Usage Information
## Channels
The following table summarises the channels available for the ZV9001K4-RGBW -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Battery Level | battery-level | system.battery_level | Battery | Number |
### Battery Level
Represents the battery level as a percentage (0-100%). Bindings for things supporting battery level in a different format (e.g. 4 levels) should convert to a percentage to provide a consistent battery level reading.
The ```system.battery-level``` channel is of type ```system.battery-level``` and supports the ```Number``` item and is in the ```Battery``` category.
This channel provides the battery level as a percentage and also reflects the low battery warning state. If the battery state is in low battery warning state, this will read 0%.
## Device Configuration
The device has no configuration parameters defined.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The ZV9001K4-RGBW supports 2 association groups.
### Group 1: Group 1
Lifeline
1. Send Command Class "Device Reset Locally Notification V1" to associated devices of this group to report factory reset information when factory reset the remote control. 2. When remote control battery power value changes, send Command Class "Battery Report V1" to associated devices of this group to report power value information. 3. Short press or press and hold down any button to send scene activation command to the associated devices of this group using Command Class “Central Scene Notification V3” 
Association group 1 supports 5 nodes.
### Group 2: Group 2
Launch 1
• devices of this group using Command Class "Basic Set V2". • Press and hold down button to send light intensity increase/decrease command to associated devices of this group using Command Class "Multilevel V4". • Short press W/ button of Group 2, turn on/off white/RGB channel of associated devices of this group using Command Class “Color Switch Set”. • Press and hold down W/ button of Group 2, adjust intensity of white/RGB channel of associated devices of this group using Command Class “Color Switch Start Level Change”. Short press button to send ON/OFF command to associated
Association group 2 supports 5 nodes.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_CENTRAL_SCENE_V3| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V2| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V2| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V4| |
| COMMAND_CLASS_BATTERY_V1| |
| COMMAND_CLASS_WAKE_UP_V2| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
| COMMAND_CLASS_SECURITY_V1| |
### Documentation Links
* [sr-zv9001k4-rgbw-manual](https://opensmarthouse.org/zwavedatabase/1285/reference/SR-ZV9001K4-RGBW-Instruction-V1.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1285).

42
_addons_bindings/zwave/doc/thermofloor/pushbutton4_0_0.md
View File

@ -1,21 +1,21 @@
---
layout: documentation
title: Z-Push Button 4 - ZWave
title: Heatit Z-Push Button 4 - ZWave
---
{% include base.html %}
# Z-Push Button 4 Wall Mounted Switch
This describes the Z-Wave device *Z-Push Button 4*, manufactured by *ThermoFloor* with the thing type UID of ```thermofloor_pushbutton4_00_000```.
# Heatit Z-Push Button 4 Wall Mounted Switch
This describes the Z-Wave device *Heatit Z-Push Button 4*, manufactured by *ThermoFloor* with the thing type UID of ```thermofloor_pushbutton4_00_000```.
The device is in the category of *Wall Switch*, defining Any device attached to the wall that controls a binary status of something, for ex. a light switch.
![Z-Push Button 4 product image](https://www.cd-jackson.com/zwave_device_uploads/1162/1162_default.png)
![Heatit Z-Push Button 4 product image](https://opensmarthouse.org/zwavedatabase/1162/image/)
The Z-Push Button 4 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices.
The Heatit Z-Push Button 4 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices.
The Z-Push Button 4 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information.
The Heatit Z-Push Button 4 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the *Wakeup Information* section below for further information.
## Overview
@ -58,7 +58,7 @@ _Note: Factory reset is not recommended for removing, please use this procedure
### Wakeup Information
The Z-Push Button 4 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour.
The Heatit Z-Push Button 4 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour.
The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device.
@ -67,12 +67,14 @@ The remote control is under sleepy mode for most of the time to save battery pow
## Channels
The following table summarises the channels available for the Z-Push Button 4 -:
The following table summarises the channels available for the Heatit Z-Push Button 4 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Scene Number | scene_number | scene_number | | Number |
| Battery Level | battery-level | system.battery_level | Battery | Number |
| Dimmer [Deprecated]| switch_dimmer1 | switch_dimmer | DimmableLight | Dimmer |
| Dimmer [Deprecated]| switch_dimmer2 | switch_dimmer | DimmableLight | Dimmer |
### Scene Number
Triggers when a scene button is pressed.
@ -95,6 +97,22 @@ Represents the battery level as a percentage (0-100%). Bindings for things suppo
The ```system.battery-level``` channel is of type ```system.battery-level``` and supports the ```Number``` item and is in the ```Battery``` category.
This channel provides the battery level as a percentage and also reflects the low battery warning state. If the battery state is in low battery warning state, this will read 0%.
### Dimmer [Deprecated]
The brightness channel allows to control the brightness of a light.
It is also possible to switch the light on and off.
The ```switch_dimmer1``` channel is of type ```switch_dimmer``` and supports the ```Dimmer``` item and is in the ```DimmableLight``` category.
**Note:** This channel is marked as deprecated so should not be used.
### Dimmer [Deprecated]
The brightness channel allows to control the brightness of a light.
It is also possible to switch the light on and off.
The ```switch_dimmer2``` channel is of type ```switch_dimmer``` and supports the ```Dimmer``` item and is in the ```DimmableLight``` category.
**Note:** This channel is marked as deprecated so should not be used.
## Device Configuration
@ -105,7 +123,7 @@ The device has no configuration parameters defined.
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The Z-Push Button 4 supports 3 association groups.
The Heatit Z-Push Button 4 supports 3 association groups.
### Group 1: Lifeline
@ -169,10 +187,10 @@ Association group 3 supports 5 nodes.
### Documentation Links
* [Installers manual - English](https://www.cd-jackson.com/zwave_device_uploads/1162/Manual-Heatit-Z-Push-Button-4--FW-1-26-Ver2019-A-ENG.pdf)
* [Product Sheet - Eng.](https://www.cd-jackson.com/zwave_device_uploads/1162/fdv-heatit-z-push-button-4-eng.pdf)
* [Installers manual - English](https://opensmarthouse.org/zwavedatabase/1162/reference/Manual-Heatit-Z-Push-Button-4--FW-1-26-Ver2019-A-ENG.pdf)
* [Product Sheet - Eng.](https://opensmarthouse.org/zwavedatabase/1162/reference/fdv-heatit-z-push-button-4-eng.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1162).
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1162).

6
_addons_bindings/zwave/doc/zooz/zse29_2_0.md
View File

@ -137,7 +137,7 @@ This parameter has the configuration ID ```config_1_1``` and is of type ```INTEG
Enable / Disable Motion Reports
Enable or disable motion reports completely. If motion sensor is disabled, the device will not report motion at all to your hub.
The following option values may be configured -:
The following option values may be configured, in addition to values in the range 0 to 1 -:
| Value | Description |
|--------|-------------|
@ -170,7 +170,7 @@ Set lux level trigger with 10 being the lowest reported value and 900 being the
1 - ignore lux readings and always report motion
10-900 - set custom trigger
The following option values may be configured, in addition to values in the range 10 to 900 -:
The following option values may be configured -:
| Value | Description |
|--------|-------------|
@ -190,7 +190,7 @@ Set motion re-trigger time for the delay before the sensor reports no motion to
0 - set manually by timer knob (default)
5-720 (seconds) - set custom re-trigger time
The following option values may be configured, in addition to values in the range 0 to 720 -:
The following option values may be configured -:
| Value | Description |
|--------|-------------|

199
_addons_bindings/zwave/doc/zwaveme/zmetio3s_0_0.md Normal file
View File

@ -0,0 +1,199 @@
---
layout: documentation
title: ZME_TIO_3S - ZWave
---
{% include base.html %}
# ZME\_TIO\_3S TION 3S Ventilator
This describes the Z-Wave device *ZME_TIO_3S*, manufactured by *Z-Wave.Me* with the thing type UID of ```zwaveme_zmetio3s_00_000```.
The device is in the category of *HVAC*, defining Air condition devices, Fans.
![ZME_TIO_3S product image](https://opensmarthouse.org/zwavedatabase/1312/image/)
The ZME_TIO_3S supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data between other devices in the mesh network.
## Overview
### Inclusion Information
Press the power button  5 sec until it blinks blue 
### Exclusion Information
Press the power button 5 sec until it blinks blue 
### General Usage Information
Ventilation system 
https://rus.z-wave.me/shop/termostats/provetrivatel-tion-3s-z-wave/#item-tabs
## Channels
The following table summarises the channels available for the ZME_TIO_3S -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Power switch | switch_binary | switch_binary | Switch | Switch |
| Sensor (air temperature) | sensor_temperature | sensor_temperature | Temperature | Number:Temperature |
| Thermostat mode | thermostat_mode | thermostat_mode | Temperature | Number |
| Setpoint (heating) | thermostat_setpoint | thermostat_setpoint | Heating | Number:Temperature |
| Power switch 2 | switch_binary1 | switch_binary | Switch | Switch |
| AirType | switch_binary2 | switch_binary | Switch | Switch |
| FanSpeed | switch_dimmer3 | switch_dimmer | DimmableLight | Dimmer |
### Power switch
on/off device switch
Switch the power on and off.
The ```switch_binary``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Sensor (air temperature)
Room temperature 
Indicates the current temperature.
The ```sensor_temperature``` channel is of type ```sensor_temperature``` and supports the ```Number:Temperature``` item and is in the ```Temperature``` category.
### Thermostat mode
Heater mode of external air
Sets the thermostat.
The ```thermostat_mode``` channel is of type ```thermostat_mode``` and supports the ```Number``` item and is in the ```Temperature``` category.
The following state translation is provided for this channel to the ```Number``` item type -:
| Value | Label |
|-------|-----------|
| 0 | Off |
| 1 | Heat |
| 2 | Cool |
| 3 | Auto |
| 4 | Aux Heat |
| 5 | Resume |
| 6 | Fan Only |
| 7 | Furnace |
| 8 | Dry Air |
| 9 | Moist Air |
| 10 | Auto Changeover |
| 11 | Heat Economy |
| 12 | Cool Economy |
| 13 | Away |
### Setpoint (heating)
Heating temperature 
Sets the thermostat setpoint.
The ```thermostat_setpoint``` channel is of type ```thermostat_setpoint``` and supports the ```Number:Temperature``` item and is in the ```Heating``` category.
### Power switch 2
Switch the power on and off.
The ```switch_binary1``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### AirType
OFF - internal air
ON - external air
Switch the power on and off.
The ```switch_binary2``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### FanSpeed
6 levels of speed:
16 - 1st level 
32 - 2nd level
48 - 3rd level
64 - 4th level
80 - 5th level
96 - 6th level
The brightness channel allows to control the brightness of a light.
It is also possible to switch the light on and off.
The ```switch_dimmer3``` channel is of type ```switch_dimmer``` and supports the ```Dimmer``` item and is in the ```DimmableLight``` category.
## Device Configuration
The device has no configuration parameters defined.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The ZME_TIO_3S supports 1 association group.
### Group 1: general
main group
main group up to 8 nodes
Association group 1 supports 8 nodes.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| |
| COMMAND_CLASS_SWITCH_MULTILEVEL_V1| |
| COMMAND_CLASS_SENSOR_MULTILEVEL_V7| |
| COMMAND_CLASS_THERMOSTAT_MODE_V1| |
| COMMAND_CLASS_THERMOSTAT_SETPOINT_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_MULTI_CHANNEL_V2| |
| COMMAND_CLASS_CONFIGURATION_V1| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| |
#### Endpoint 1
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_SWITCH_BINARY_V1| |
#### Endpoint 2
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_SWITCH_BINARY_V1| |
#### Endpoint 3
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_SWITCH_MULTILEVEL_V1| |
### Documentation Links
* [user guide (Russian only)](https://opensmarthouse.org/zwavedatabase/1312/reference/ZMR_TION_3S.pdf)
* [Instruction (English)](https://opensmarthouse.org/zwavedatabase/1312/reference/sr-zv9001k4-rgbw-instruction-v1_1.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1312).

9
_thing_types/org.openhab.binding.avmfritz/src/main/resources/OH-INF/thing/channel-types.xml
View File

@ -97,6 +97,7 @@
<label>Sensor Data</label>
<channels>
<channel id="temperature" typeId="temperature"/>
<channel id="humidity" typeId="humidity"/>
</channels>
</channel-group-type>
@ -111,6 +112,14 @@
<config-description-ref uri="channel-type:avmfritz:temperature"/>
</channel-type>
<channel-type id="humidity">
<item-type>Number:Dimensionless</item-type>
<label>Current Humidity</label>
<description>Current measured humidity.</description>
<category>Humidity</category>
<state pattern="%.0f %unit%" readOnly="true"/>
</channel-type>
<channel-type id="energy">
<item-type>Number:Energy</item-type>
<label>Energy Consumption</label>

6
_thing_types/org.openhab.binding.bigassfan/src/main/resources/OH-INF/thing/thing-types.xml
View File

@ -40,6 +40,8 @@
<channel id="time" typeId="time"/>
</channels>
<representation-property>macAddress</representation-property>
<config-description-ref uri="thing-type:bigassfan:device"/>
</thing-type>
@ -63,6 +65,8 @@
<channel id="time" typeId="time"/>
</channels>
<representation-property>macAddress</representation-property>
<config-description-ref uri="thing-type:bigassfan:device"/>
</thing-type>
@ -76,6 +80,8 @@
<channel id="time" typeId="time"/>
</channels>
<representation-property>macAddress</representation-property>
<config-description-ref uri="thing-type:bigassfan:device"/>
</thing-type>

2
_thing_types/org.openhab.binding.globalcache/src/main/resources/OH-INF/thing/gc-100-06.xml
View File

@ -15,6 +15,8 @@
<channel-group id="ir-m2" typeId="ir-m2"/>
</channel-groups>
<representation-property>macAddress</representation-property>
<config-description>
<parameter name="ipAddress" type="text" required="true">
<label>Network Address</label>

2
_thing_types/org.openhab.binding.globalcache/src/main/resources/OH-INF/thing/gc-100-12.xml
View File

@ -18,6 +18,8 @@
<channel-group id="ir-m5" typeId="ir-m5"/>
</channel-groups>
<representation-property>macAddress</representation-property>
<config-description>
<parameter name="ipAddress" type="text" required="true">
<label>Network Address</label>

2
_thing_types/org.openhab.binding.globalcache/src/main/resources/OH-INF/thing/itach-cc.xml
View File

@ -14,6 +14,8 @@
<channel-group id="cc-m1" typeId="cc-m1"/>
</channel-groups>
<representation-property>macAddress</representation-property>
<config-description>
<parameter name="ipAddress" type="text" required="true">
<label>Network Address</label>

2
_thing_types/org.openhab.binding.globalcache/src/main/resources/OH-INF/thing/itach-flex.xml
View File

@ -16,6 +16,8 @@
<channel-group id="cc-m1" typeId="cc-m1"/>
</channel-groups>
<representation-property>macAddress</representation-property>
<config-description>
<parameter name="ipAddress" type="text" required="true">
<label>Network Address</label>

2
_thing_types/org.openhab.binding.globalcache/src/main/resources/OH-INF/thing/itach-ir.xml
View File

@ -14,6 +14,8 @@
<channel-group id="ir-m1" typeId="ir-m1"/>
</channel-groups>
<representation-property>macAddress</representation-property>
<config-description>
<parameter name="ipAddress" type="text" required="true">
<label>Network Address</label>

2
_thing_types/org.openhab.binding.globalcache/src/main/resources/OH-INF/thing/itach-sl.xml
View File

@ -14,6 +14,8 @@
<channel-group id="sl-m1" typeId="sl-m1"/>
</channel-groups>
<representation-property>macAddress</representation-property>
<config-description>
<parameter name="ipAddress" type="text" required="true">
<label>Network Address</label>

2
_thing_types/org.openhab.binding.globalcache/src/main/resources/OH-INF/thing/zmote.xml
View File

@ -14,6 +14,8 @@
<channel-group id="ir-m1-c1" typeId="ir-m1-c1"/>
</channel-groups>
<representation-property>macAddress</representation-property>
<config-description>
<parameter name="ipAddress" type="text" required="true">
<label>Network Address</label>

7
_thing_types/org.openhab.binding.icalendar/src/main/resources/OH-INF/thing/thing-types.xml
View File

@ -16,6 +16,7 @@
<channel id="next_title" typeId="event_next_title"/>
<channel id="next_start" typeId="event_next_start"/>
<channel id="next_end" typeId="event_next_end"/>
<channel id="last_update" typeId="last_update"/>
</channels>
<config-description>
@ -118,6 +119,12 @@
<description>Title of the found result in calendar</description>
<state readOnly="true"/>
</channel-type>
<channel-type id="last_update">
<item-type>DateTime</item-type>
<label>Last Update</label>
<description>The time the calendar was updated successfully last time</description>
<state readOnly="true"/>
</channel-type>
<channel-group-type id="result">
<label>Result Event</label>
<description>A resulting event found by filter</description>

2
_thing_types/org.openhab.binding.openweathermap/src/main/resources/OH-INF/thing/channel-types.xml
View File

@ -189,6 +189,7 @@
<channel id="apparent-night" typeId="apparent-night"/>
<channel id="pressure" typeId="system.barometric-pressure"/>
<channel id="humidity" typeId="system.atmospheric-humidity"/>
<channel id="dew-point" typeId="dew-point"/>
<channel id="wind-speed" typeId="system.wind-speed"/>
<channel id="wind-direction" typeId="system.wind-direction"/>
<channel id="gust-speed" typeId="gust-speed"/>
@ -197,7 +198,6 @@
<channel id="precip-probability" typeId="precip-probability"/>
<channel id="rain" typeId="rain"/>
<channel id="snow" typeId="snow"/>
<channel id="visibility" typeId="visibility"/>
</channels>
</channel-group-type>

69
_thing_types/org.openhab.binding.smhi/src/main/resources/OH-INF/thing/channel-types.xml
View File

@ -8,97 +8,127 @@
<item-type>Number:Pressure</item-type>
<label>Air Pressure</label>
<description>Air pressure in hPa</description>
<state readOnly="true" pattern="%.1f %unit%"/>
<state readOnly="true" pattern="%.1f hPa"/>
</channel-type>
<channel-type id="t">
<item-type>Number:Temperature</item-type>
<label>Temperature</label>
<description>Temperature</description>
<state readOnly="true" pattern="%.1f %unit%"/>
<state readOnly="true" pattern="%.1f °C"/>
</channel-type>
<channel-type id="tmax">
<item-type>Number:Temperature</item-type>
<label>Max Temperature</label>
<description>Highest temperature of the day</description>
<state readOnly="true" pattern="%.1f °C"/>
</channel-type>
<channel-type id="tmin">
<item-type>Number:Temperature</item-type>
<label>Min Temperature</label>
<description>Lowest temperature of the day</description>
<state readOnly="true" pattern="%.1f °C"/>
</channel-type>
<channel-type id="vis" advanced="true">
<item-type>Number:Length</item-type>
<label>Visibility</label>
<description>Horizontal visibility</description>
<state readOnly="true" pattern="%.1f %unit%"/>
<state readOnly="true" pattern="%.1f km"/>
</channel-type>
<channel-type id="wd">
<item-type>Number:Angle</item-type>
<label>Wind Direction</label>
<description>Wind direction</description>
<state readOnly="true" pattern="%d %unit%"/>
<state readOnly="true" pattern="%d °"/>
</channel-type>
<channel-type id="ws">
<item-type>Number:Speed</item-type>
<label>Wind Speed</label>
<description>Wind speed</description>
<state readOnly="true" pattern="%.1f %unit%"/>
<state readOnly="true" pattern="%.1f m/s"/>
</channel-type>
<channel-type id="wsmax">
<item-type>Number:Speed</item-type>
<label>Max Wind Speed</label>
<description>Highest wind speed of the day</description>
<state readOnly="true" pattern="%.1f m/s"/>
</channel-type>
<channel-type id="wsmin">
<item-type>Number:Speed</item-type>
<label>Min Wind Speed</label>
<description>Lowest wind speed of the day</description>
<state readOnly="true" pattern="%.1f m/s"/>
</channel-type>
<channel-type id="r">
<item-type>Number:Dimensionless</item-type>
<label>Relative Humidity</label>
<description>Relative humidity in percent</description>
<state readOnly="true" pattern="%d %unit%"/>
<state readOnly="true" pattern="%d %%"/>
</channel-type>
<channel-type id="tstm" advanced="true">
<item-type>Number:Dimensionless</item-type>
<label>Thunder Probability</label>
<description>Probability of thunder in percent</description>
<state readOnly="true" pattern="%d %unit%"/>
<state readOnly="true" pattern="%d %%"/>
</channel-type>
<channel-type id="tcc_mean">
<item-type>Number:Dimensionless</item-type>
<label>Total Cloud Cover</label>
<description>Mean value of total cloud cover in percent</description>
<state readOnly="true" pattern="%.1f %unit%"/>
<state readOnly="true" pattern="%.1f %%"/>
</channel-type>
<channel-type id="lcc_mean" advanced="true">
<item-type>Number:Dimensionless</item-type>
<label>Low Level Cloud Cover</label>
<description>Mean value of low level cloud cover (0-2500 m) in percent</description>
<state readOnly="true" pattern="%.1f %unit%"/>
<state readOnly="true" pattern="%.1f %%"/>
</channel-type>
<channel-type id="mcc_mean" advanced="true">
<item-type>Number:Dimensionless</item-type>
<label>Medium Level Cloud Cover</label>
<description>Mean value of medium level cloud cover (2500-6000 m) in percent</description>
<state readOnly="true" pattern="%.1f %unit%"/>
<state readOnly="true" pattern="%.1f %%"/>
</channel-type>
<channel-type id="hcc_mean" advanced="true">
<item-type>Number:Dimensionless</item-type>
<label>High Level Cloud Cover</label>
<description>Mean value of high level cloud cover (> 6000 m) in percent</description>
<state readOnly="true" pattern="%.1f %unit%"/>
<state readOnly="true" pattern="%.1f %%"/>
</channel-type>
<channel-type id="gust">
<item-type>Number:Speed</item-type>
<label>Wind Gust Speed</label>
<description>Wind gust speed</description>
<state readOnly="true" pattern="%.1f %unit%"/>
<state readOnly="true" pattern="%.1f m/s"/>
</channel-type>
<channel-type id="pmin">
<item-type>Number:Speed</item-type>
<label>Minimum Precipitation</label>
<description>Minimum precipitation intensity</description>
<state readOnly="true" pattern="%.1f %unit%"/>
<state readOnly="true" pattern="%.1f mm/h"/>
</channel-type>
<channel-type id="pmax">
<item-type>Number:Speed</item-type>
<label>Maximum Precipitation</label>
<description>Maximum precipitation intensity</description>
<state readOnly="true" pattern="%.1f %unit%"/>
<state readOnly="true" pattern="%.1f mm/h"/>
</channel-type>
<channel-type id="ptotal">
<item-type>Number:Length</item-type>
<label>Total Precipitation</label>
<description>Total amount of precipitation during the day</description>
<state readOnly="true" pattern="%.1f mm"/>
</channel-type>
<channel-type id="pmean" advanced="true">
<item-type>Number:Speed</item-type>
<label>Mean Precipitation</label>
<description>Mean precipitation intensity</description>
<state readOnly="true" pattern="%.1f %unit%"/>
<state readOnly="true" pattern="%.1f mm/h"/>
</channel-type>
<channel-type id="pmedian" advanced="true">
<item-type>Number:Speed</item-type>
<label>Median Precipitation</label>
<description>Median precipitation intensity</description>
<state readOnly="true" pattern="%.1f %unit%"/>
<state readOnly="true" pattern="%.1f mm/h"/>
</channel-type>
<channel-type id="pcat">
<item-type>Number</item-type>
@ -120,7 +150,7 @@
<item-type>Number:Dimensionless</item-type>
<label>Frozen Precipitation</label>
<description>Percent of precipitation in frozen form</description>
<state readOnly="true" pattern="%d %unit%"/>
<state readOnly="true" pattern="%d %%"/>
</channel-type>
<channel-type id="wsymb2">
<item-type>Number</item-type>
@ -190,11 +220,16 @@
<description>Forecast at noon for the specified offset</description>
<channels>
<channel id="t" typeId="t"/>
<channel id="tmax" typeId="tmax"/>
<channel id="tmin" typeId="tmin"/>
<channel id="wd" typeId="wd"/>
<channel id="ws" typeId="ws"/>
<channel id="wsmax" typeId="wsmax"/>
<channel id="wsmin" typeId="wsmin"/>
<channel id="gust" typeId="gust"/>
<channel id="pmin" typeId="pmin"/>
<channel id="pmax" typeId="pmax"/>
<channel id="ptotal" typeId="ptotal"/>
<channel id="pcat" typeId="pcat"/>
<channel id="msl" typeId="msl"/>
<channel id="r" typeId="r"/>

119
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/act/zrf113_1_100.xml Normal file
View File

@ -0,0 +1,119 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="act_zrf113_01_100" listed="false">
<label>ZRF113 Isolated Contact Fixture Module Release 1.1</label>
<description><![CDATA[
Isolated Contact Fixture Module Release 1.1<br /> <h1>Overview</h1><p>The ZRF113 Isolated Contact Fixture Module is a component of the HomePro lighting control system. Wire the Isolated Contact Fixture Module according to the diagram above and program it from the Wireless Controller to operate loads.  Inclusion of this Switch on the ZTH100 Wireless Controller menu allows remote ON/OFF control of load connected.</p><p>This Isolated Contact Fixture Module is designed to work with other Z-Wave enabled devices. Z-Wave nodes of other types can be included on the network and will also act as repeaters if they support this function.  </p><p>As part of a Z-Wave network, the ZRF113 will also act as a wireless repeater to insure that commands intended for another device in the network are received. This is useful when the device would otherwise be out of the radio range of the wireless controller.</p><p>There are no field repairable assemblies on this unit.. If service is needed, the unit must be returned where purchased.</p><p>DANGER! SHOCK HAZARD. Read and understand these instructions before installing. This device is intended for installation in accordance with the National Electric code and local regulations in the United States, or the Canadian Electrical Code and local regulations in Canada. It is recommended that a qualified electrician perform this installation.</p><p><b>INSTALLATION</b></p><p>Wire this module in series with a 20 amp (maximum) load according to the diagram above. If AS101’s are used they must be wired to the same line (or neutral) also wired to the master unit as well as the load being controlled, and not wired to any other neutral. If multiple neutral wires are tied together in one box, separate the neutral wires to preserve the integrity of the ZRF113 circuit. Caution! Do not wire unit “live” (with power on the circuit) and do notallow the yellow wire to contact line voltage, neutral or ground or you will damage the device. See the ZTH100 Wireless Controller operating instructions to include this module under the command of the Wireless Controller.</p><p><b>NOTE </b></p><p>If you have trouble adding the ZRF113 to a group it may be that the Home ID and Node ID were not cleared from it after testing. You must first “RESET UNIT” with your controller to remove it from the network. If using the ZTH100 select “SETUP” and scroll to “RESET UNIT” </p><p>Although adding it to a group includes it in the network, removing it from a group does not remove it from the network. If removed from a group, it functions only as a repeater.</p><p>With the Wireless Controller, the ZRF113 can be switched ON and OFF remotely, and can be included (or excluded) in groups of lights that operate at the same time (a group can also be a single module), and in scenes that set a lighting mood.</p><p>Note that the Associations, and possibly other features, vary depending on the release.  The original version 1 units used 4 associations.  This release, release 1.1, uses 2.</p><p><b>SPECIFICATIONS</b></p><p>Power: 120 VAC, 50/60 Hz</p><p>Signal (Frequency): 908.42 MHz</p><p>Maximum Load</p><p>   Isolated Contacts: 20 amps maximum General Purpose, 277 VAC, 10 FLA, 60 LRA, 250 VAC,</p><p>   Motor: 1 H.P. maximum, 120/240 VAC</p><p>   Incandescent: TV8 (Tungsten), 120 VAC, 960W maximum</p><p>Range: Up to 100 feet line of sight between the Wireless Controller and /or the closest HomePro Receiver Module</p> <br /> <h2>Inclusion Information</h2><p>STEP 1.. Prepare the Controller to include a unit to the network by adding it to a group (method of adding a node to the network). Refer to controller instructions. If using a ZTH100, push MENU button, select GROUPS, push OK button, see ADD UNIT TO GROUP displayed, push OK button.</p><p>STEP 2. The ZRF113 must be in its permanently installed location. Tap the button on the face of the ZRF113 once. Some Z-Wave products include the module on the release of the button.</p><p>STEP 3. You should see an indication on your Controller that the “DEVICE WAS INCLUDED” in the network.</p> <br /> <h2>Exclusion Information</h2><p>“RESET UNIT” with your controller to remove it from the network. If using the ZTH100 select “SETUP” and scroll to “RESET UNIT”</p><p>Although adding it to a group includes it in the network, removing it from a group does not remove it from the network. If removed from a group, it functions only as a repeater.</p> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>PowerOutlet</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="switch_binary" typeId="switch_binary">
<label>Switch</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY</property>
</properties>
</channel>
<channel id="switch_dimmer" typeId="switch_dimmer">
<label>Dimmer</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">ACT - Advanced Control Technologies</property>
<property name="modelId">ZRF113</property>
<property name="manufacturerId">0001</property>
<property name="manufacturerRef">5246:3133</property>
<property name="versionMin">1.100</property>
<property name="dbReference">1331</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_1_1" type="integer" groupName="configuration"
min="0" max="1">
<label>1: Configuration Parameter 1</label>
<description><![CDATA[
Set Ignore Start Level Bit When Transmitting Dim Command<br /> <h1>Overview</h1><p>The ZRF113 can send Dim commands to Z-Wave enabled dimmers. The Dim command has a start level embedded in it. A dimmer receiving this command will start dimming from that start level. However, the command also has a bit that indicates whether the dimmer should ignore the start level. If the bit is set to 1, the dimmer will ignore the start level and instead start dimming from its current level. To clear this bit, configure this parameter to the value of 0.</p><p>NOTE: Each Configuration Parameter can be set to its default by setting the default bit in the Configuration Set command. See your controller’s instructions on how to do this (and if it supports it). All Configuration commands will be reset to their default state when the ZRF113 is excluded from the Z-Wave network by using the controller to reset the node (on the ZTH100 select “SETUP” and scroll to “RESET UNIT”).</p>
]]></description>
<default>1</default>
<options>
<option value="0">Don't Ignore Dimmer Command Start Level Bit</option>
<option value="1">Ignore Dimmer Command Start Level Bit (Default)</option>
</options>
<advanced>true</advanced>
</parameter>
<parameter name="config_19_1" type="integer" groupName="configuration"
min="0" max="2">
<label>19: Configuration Parameter 19</label>
<description><![CDATA[
LED Transmission Indication<br /> <h1>Overview</h1><p>The ZRF113 will flicker its LED when it is transmitting to any of its groups. This flickering can be set to not flicker at all (set to 0), to flicker the entire time it is transmitting (set to 1), or to flicker for only 1 second when it begins transmitting (set to 2). By default, the ZRF113 is set to flicker for only 1 second.</p><p>NOTE: Each Configuration Parameter can be set to its default by setting the default bit in the Configuration Set command. See your controller’s instructions on how to do this (and if it supports it). All Configuration commands will be reset to their default state when the ZRF113 is excluded from the Z-Wave network by using the controller to reset the node (on the ZTH100 select “SETUP” and scroll to “RESET UNIT”).<br /></p>
]]></description>
<default>2</default>
<options>
<option value="0">No Flicker</option>
<option value="1">Flicker while transmitting</option>
<option value="2">Flicker for 1 second (Default)</option>
</options>
<advanced>true</advanced>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Lifeline</label>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: Group 2</label>
<description><![CDATA[
Auxilliary Switch 2 Tap<br /> <h1>Overview</h1><p>If you associate a Z-Wave device into Group 2, you can turn that device on and off by tapping the top or bottom of the auxiliary switch twice. You can brighten or dim devices by tapping the top or bottom of the auxiliary switch once and then holding the switch down. The load attached to the ZRF113 is not affected.</p><p>A NOTE ABOUT DIMMERS IN A GROUP: If you combine Z-Wave enabled dimmers and other types of ZWave devices in a group, place a Z-Wave enabled dimmer into the empty group first to ensure that the dimming operates correctly.</p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_3" type="text" groupName="association" multiple="true">
<label>3: Group 3</label>
<description><![CDATA[
Auxilliary Switch 3 Tap<br /> <h1>Overview</h1><p>If you associate a Z-Wave device into Group 3, you can turn that device on and off by tapping the top or bottom of the auxiliary switch three times . You can brighten or dim devices by tapping the top or bottom of the auxiliary switch twice and then hold the top down for brighten or bottom for dim (bottom only if AS001). The load attached to the ZRF113 is not affected.</p><p>A NOTE ABOUT DIMMERS IN A GROUP: If you combine Z-Wave enabled dimmers and other types of ZWave devices in a group, place a Z-Wave enabled dimmer into the empty group first to ensure that the dimming operates correctly.<br /></p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

84
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/eco/wirelesssiren_0_0.xml Normal file
View File

@ -0,0 +1,84 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="eco_wirelesssiren_00_000" listed="false">
<label>Wireless Siren Z-Wave plus plug in siren</label>
<description><![CDATA[
Z-Wave plus plug in siren<br /> <h1>Overview</h1><p>The device is as simple to use as plugging in a wall outlet.</p><p>The device can create 4 independent tones for different alerts to the user. These could include but are not limited to: Security Alarm, entry/exit, smoke/Fire, temperature and more. The Z-Wave Plus Siren can also be used as a Z-Wave Plus network extension.</p> <br /> <h2>Inclusion Information</h2><p>Plug in the Z-Wave Siren and verify a single beep sound is heard.</p><p>The LED on the front of the unit will turn off if successful included into a network.</p> <br /> <h2>Exclusion Information</h2><ol><li> Plug in the Z-Wave Siren.</li><li>Unplug and re-plug in your Z-Wave Plus Siren.  </li></ol><p>The device will play a long beep and the LED will begin to breathe if the device is successfully removed from the network.<br /></p> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>Siren</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="switch_binary" typeId="switch_binary">
<label>Switch</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY</property>
</properties>
</channel>
<channel id="switch_binary1" typeId="switch_binary">
<label>Switch 1</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY:1</property>
</properties>
</channel>
<channel id="switch_binary2" typeId="switch_binary">
<label>Switch 2</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY:2</property>
</properties>
</channel>
<channel id="switch_binary3" typeId="switch_binary">
<label>Switch 3</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY:3</property>
</properties>
</channel>
<channel id="switch_binary4" typeId="switch_binary">
<label>Switch 4</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY:4</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Ecolink</property>
<property name="modelId">Wireless Siren</property>
<property name="manufacturerId">014A</property>
<property name="manufacturerRef">0005:000A</property>
<property name="dbReference">1263</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Lifeline</label>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

4
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/fibaro/fgd211_0_0.xml
View File

@ -8,7 +8,7 @@
<thing-type id="fibaro_fgd211_00_000" listed="false">
<label>FGD211 Universal Dimmer 500W</label>
<description><![CDATA[
Universal Dimmer 500W<br /> <h1>Overview</h1><p>Remotely controlled Dimmer designed to operate with or without neutral lead. It may be used as a switch in systems without neutral lead.</p> <p>As a Dimmer it operates under the following loads:</p> <ul><li>conventional incandescent</li> <li>Halogen 230V</li> <li>low voltage halogen 12V (with electronic transformers)</li> <li>dimmable LED</li> <li>when used with FGB001 it may operate with any dimmable load up to 500W</li> </ul> <br /> <h2>Inclusion Information</h2><p>The Dimmer enters the mode of inclusion after a quick pressing three times the push-button connected to S1 terminal or push-button B located inside the housing. For bi-stable switch perform 3 position changes.</p> <br /> <h2>Exclusion Information</h2><p>The Dimmer enters the mode of exclusion after a quick pressing three times the push-button connected to S1 terminal or push-button B located inside the housing. For bi-stable switch perform 3 position changes</p>
Universal Dimmer 500W<br /> <h1>Overview</h1><p>Remotely controlled Dimmer designed to operate with or without neutral lead. It may be used as a switch in systems without neutral lead.</p> <p>As a Dimmer it operates under the following loads:</p> <ul><li>conventional incandescent</li> <li>Halogen 230V</li> <li>low voltage halogen 12V (with electronic transformers)</li> <li>dimmable LED</li> <li>when used with FGB001 it may operate with any dimmable load up to 500W</li> </ul> <br /> <h2>Inclusion Information</h2><p>The Dimmer enters the mode of inclusion after a quick pressing three times the push-button connected to S1 terminal or push-button B located inside the housing. For bi-stable switch perform 3 position changes.</p> <br /> <h2>Exclusion Information</h2><p>The Dimmer enters the mode of exclusion after a quick pressing three times the push-button connected to S1 terminal or push-button B located inside the housing. For bi-stable switch perform 3 position changes</p> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>WallSwitch</category>
@ -28,7 +28,7 @@ Universal Dimmer 500W<br /> <h1>Overview</h1><p>Remotely controlled Dimmer desig
<property name="vendor">Fibargroup</property>
<property name="modelId">FGD211</property>
<property name="manufacturerId">010F</property>
<property name="manufacturerRef">0100:0104,0100:0106,0100:0107,0100:0109,0100:100A,0100:300A</property>
<property name="manufacturerRef">0100:0103,0100:0104,0100:0106,0100:0107,0100:0109,0100:100A,0100:300A</property>
<property name="versionMax">1.8</property>
<property name="dbReference">117</property>
<property name="defaultAssociations">3</property>

2
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/fibaro/fgs224_5_0.xml
View File

@ -57,7 +57,7 @@ Fibaro Double Smart Module<br /> <h1>Overview</h1><h1>Description</h1> <p>The re
<property name="vendor">Fibargroup</property>
<property name="modelId">FGS224</property>
<property name="manufacturerId">010F</property>
<property name="manufacturerRef">0204:1000</property>
<property name="manufacturerRef">0204:1000,0204:3000</property>
<property name="versionMin">5.0</property>
<property name="versionMax">5.0</property>
<property name="dbReference">1275</property>

220
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/fibaro/fgt001_0_0.xml
View File

@ -1,220 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="fibaro_fgt001_00_000" listed="false">
<label>FGT001 Thermostatic Valve</label>
<description><![CDATA[
Thermostatic Valve<br /> <h1>Overview</h1><p>FIBARO Heat Controller is a remotely controlled thermostatic head to control temperature in the room. It measures the temperature and automatically adjust the heat level. It can be mounted without tools on three types of thermostatic radiator valves. It is also possible to create schedules via app to easily manage temperature throughout the week. <br />Main features:</p> <ul><li>to be installed on three types of valves: M30 x 1.5, Danfoss RTD-N and Danfoss RA-N,</li> <li>compatible with any Z-Wave or Z-Wave+ Controller,</li> <li>supports Z-Wave network Security Modes: S0 with AES-128 encryption and S2 with PRNG-based encryption,</li> <li>built-in battery recharged through standard micro-USB port,</li> <li>easy installation - no tools required,</li> <li>can use dedicated temperature sensor,</li> <li>supports heating schedules,</li> <li>automatic calibration,</li> <li>anti-freeze function,</li> <li>decalc function,</li> <li>unconstrained rotation spherical knob to set desired temperature.</li> </ul> <br /> <h2>Inclusion Information</h2><p>Add the device to the Z-Wave network:</p> <ol><li>Make sure the device is within the direct range of your Z-Wave controller.</li> <li>Set the main controller in (security/non-security) add mode.</li> <li>Use the included key to quickly triple click the button on the thermostatic head.</li> <li>The LED ring will start blinking white.</li> <li>If you are adding in S2 authenticated mode, type in the device pin code (underlined part of the public key on the label).</li> <li>Wait for the adding process to end.</li> <li>Successful adding will be confirmed by the Z-Wave controller.</li> </ol> <br /> <h2>Exclusion Information</h2><p>To remove the device from the Z-Wave network:</p> <ol><li>Make sure the device is within the direct range of your Z-Wave controller.</li> <li>Set the main controller into remove mode.</li> <li>Use the included key to quickly triple click the button on the thermostatic head.</li> <li>The LED ring will start blinking white.</li> <li>Wait for the removing process to end.</li> <li>Successful removing will be confirmed by the Z-Wave controller.</li> </ol> <br /> <h2>Wakeup Information</h2><p>FIBARO Heat Controller is a FLiRS device. The FLiRS device alternates between sleep mode and a partially awake mode in which it is listening beam signal. When device receives this beam, it immediately fully wakes up and then communicates with the controller or other Z-Wave device.</p>
]]></description>
<category>RadiatorControl</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="sensor_binary" typeId="sensor_binary">
<label>Binary Sensor</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SENSOR_BINARY</property>
</properties>
</channel>
<channel id="sensor_temperature" typeId="sensor_temperature">
<label>Sensor (temperature)</label>
<properties>
<property name="binding:*:QuantityType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=TEMPERATURE</property>
</properties>
</channel>
<channel id="thermostat_mode" typeId="fibaro_fgt001_00_000_thermostat_mode">
<label>Thermostat mode</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_THERMOSTAT_MODE</property>
</properties>
</channel>
<channel id="thermostat_setpoint_heating" typeId="thermostat_setpoint">
<label>Setpoint (heating)</label>
<properties>
<property name="binding:*:QuantityType">COMMAND_CLASS_THERMOSTAT_SETPOINT;type=HEATING</property>
</properties>
</channel>
<channel id="alarm_power" typeId="alarm_power">
<label>Alarm (power)</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=POWER_MANAGEMENT</property>
</properties>
</channel>
<channel id="alarm_system" typeId="alarm_system">
<label>Alarm (system)</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=SYSTEM</property>
</properties>
</channel>
<channel id="battery-level" typeId="system.battery-level">
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_BATTERY</property>
</properties>
</channel>
<channel id="time_offset" typeId="time_offset">
<label>Clock Time Offset</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_CLOCK</property>
</properties>
</channel>
<channel id="thermostat_mode1" typeId="fibaro_fgt001_00_000_thermostat_mode">
<label>Thermostat mode 1</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_THERMOSTAT_MODE:1</property>
</properties>
</channel>
<channel id="thermostat_setpoint_heating1" typeId="thermostat_setpoint">
<label>Setpoint (heating) 1</label>
<properties>
<property name="binding:*:QuantityType">COMMAND_CLASS_THERMOSTAT_SETPOINT:1;type=HEATING</property>
</properties>
</channel>
<channel id="alarm_power1" typeId="alarm_power">
<label>Alarm (power) 1</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM:1;type=POWER_MANAGEMENT</property>
</properties>
</channel>
<channel id="alarm_system1" typeId="alarm_system">
<label>Alarm (system) 1</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM:1;type=SYSTEM</property>
</properties>
</channel>
<channel id="battery-level1" typeId="system.battery-level">
<label>Battery Level 1</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_BATTERY</property>
</properties>
</channel>
<channel id="time_offset1" typeId="time_offset">
<label>Clock Time Offset 1</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_CLOCK:1</property>
</properties>
</channel>
<channel id="sensor_temperature2" typeId="sensor_temperature">
<label>Sensor (temperature) 2</label>
<properties>
<property name="binding:*:QuantityType">COMMAND_CLASS_SENSOR_MULTILEVEL:2;type=TEMPERATURE</property>
</properties>
</channel>
<channel id="alarm_power2" typeId="alarm_power">
<label>Alarm (power) 2</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM:2;type=POWER_MANAGEMENT</property>
</properties>
</channel>
<channel id="battery-level2" typeId="system.battery-level">
<label>Battery Level 2</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_BATTERY</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Fibargroup</property>
<property name="modelId">FGT001</property>
<property name="manufacturerId">010F</property>
<property name="manufacturerRef">1301:1000,1301:1001</property>
<property name="dbReference">749</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_1_4" type="integer" groupName="configuration"
min="10" max="10000">
<label>1: Override Schedule duration</label>
<description><![CDATA[
Duration of Override Schedule after turning knob<br /> <h1>Overview</h1><p>This parameter determines duration of Override Schedule after turning the knob while normal schedule is active (set by Schedule CC).</p> <p>Units = minutes</p>
]]></description>
<default>240</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_2_4" type="integer" groupName="configuration"
min="0" max="31">
<label>2: Additional functions</label>
<description><![CDATA[
This parameter allows to enable different additional functions of the device.<br /> <h1>Overview</h1><p>Parameter 2 values may be combined, e.g. 1+8=9 means that Open Window Detector and LED indications when controlling remotely are enabled.</p> <p>1 (bit 0) - enable Open Window Detector</p> <p>2 (bit 1) - enable fast Open Window Detector</p> <p>4 (bit 2) - increase receiver sensitivity (shortens battery life)</p> <p>8 (bit 3) - enabled LED indications when controlling remotely</p> <p>16 (bit 4) - protect from setting Full ON and Full OFF mode by turning the knob manually</p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_3_4" type="integer" groupName="configuration" readOnly="true"
min="0" max="3">
<label>3: Additional functions status (READ-ONLY)</label>
<description><![CDATA[
This parameter allows to check statuses of different additional functions.<br /> <h1>Overview</h1><p>Parameter 3 values may be combined, e.g. 1+2=3 means optional sensor works properly and open window detection was triggered.</p> <p>1 (bit 0) - optional temperature sensor connected and operational</p> <p>2 (bit 1) - open window detected</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Lifeline</label>
<description><![CDATA[
Lifeline<br /> <h1>Overview</h1><p>Z-Wave Plus Lifeline association group that reports the device status and allows for assigning single device only (main controller by default)</p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
<channel-type id="fibaro_fgt001_00_000_thermostat_mode">
<item-type>Number</item-type>
<label>Thermostat Mode</label>
<description>Sets the thermostat mode</description>
<category>Temperature</category>
<state pattern="%s">
<options>
<option value="0">Off</option>
<option value="1">Heat</option>
</options>
</state>
</channel-type>
<channel-type id="fibaro_fgt001_00_000_thermostat_mode">
<item-type>Number</item-type>
<label>Thermostat Mode</label>
<description>Sets the thermostat mode</description>
<category>Temperature</category>
<state pattern="%s">
<options>
<option value="0">Off</option>
<option value="1">Heat</option>
</options>
</state>
</channel-type>
</thing:thing-descriptions>

111
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/ge/zw4008_0_0.xml Normal file
View File

@ -0,0 +1,111 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="ge_zw4008_00_000" listed="false">
<label>43072/ZW4008DV In-Wall Smart Switch with QuickFit and SimpleWire enhancements.</label>
<description><![CDATA[
In-Wall Smart Switch with QuickFit and SimpleWire enhancements.<br /> <h1>Overview</h1><p>In-Wall Smart Switch with QuickFit and SimpleWire enhancements. Revolutionary QuickFit design features a housing depth that is up to 20 percent smaller than the previous Z-Wave models. This reduced size coupled with the elimination of heat taps provides a better fit in older style boxes and multi-gang configurations. SimpleWire technology allows line and load to automatically be configured with auto-sensing line-load terminals. All of this is coupled with Z-Wave S2 and Smart Start allows for effortless installation while being safer than ever!</p> <br /> <h2>Inclusion Information</h2><ol><li>Follow the instructions for your Z-Wave certified controller to add a device to the Z-Wave network.</li> <li>Once the controller is ready to add your device, press and release the top or bottom of the wireless smart switch (rocker).</li> </ol> <br /> <h2>Exclusion Information</h2><ol><li>Follow the instructions for your Z-Wave certified controller to remove a device from the Z-Wave network.</li> <li>Once the controller is ready to remove your device, press and release the top or bottom of the wireless smart switch (rocker).</li> </ol>
]]></description>
<category>WallSwitch</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="switch_binary" typeId="switch_binary">
<label>Switch</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY,COMMAND_CLASS_BASIC</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Jasco Products</property>
<property name="modelId">43072/ZW4008DV</property>
<property name="manufacturerId">0063</property>
<property name="manufacturerRef">4952:3036,4952:3135,4952:3136,4952:3139</property>
<property name="dbReference">1155</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_3_1" type="integer" groupName="configuration">
<label>3: LED Indication Configuration</label>
<description>Configure LED indication to default, invert, always off or always on</description>
<default>0</default>
<options>
<option value="0">LED ON when device is OFF</option>
<option value="1">LED ON when device is ON</option>
<option value="2">LED always OFF</option>
<option value="3">LED Always ON</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_19_1" type="integer" groupName="configuration">
<label>19: Alternate Exclusion</label>
<description><![CDATA[
Default - normal exclusion Active -<br /> <h1>Overview</h1><p> perform a series of button presses to help eliminate accidental exclusion</p>
]]></description>
<default>0</default>
<options>
<option value="0">Press any button on the switch</option>
<option value="1">Exclusion Info</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Lifeline</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>Zwave Plus Lifeline</p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: Group 2</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>Supports Basic Set and is controlled by pressing the ON or OFF button</p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_3" type="text" groupName="association" multiple="true">
<label>3: Group 3</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>Supports Basic Set and is controlled by double pressing the ON or OFF</p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

904
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/heltun/heht01_0_0.xml Normal file
View File

@ -0,0 +1,904 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="heltun_heht01_00_000" listed="false">
<label>HE-HT01 Wall Heating Thermostat</label>
<description><![CDATA[
Wall Heating Thermostat<br /> <h1>Overview</h1><p>The Heltun Heating Thermostat is built control the heating and mesures not only the room temperature with the build in sensor, but also humidity, lighting and the floor temperature if a sensor is attached.</p> <br /> <h2>Inclusion Information</h2><p><strong>To include the thermostat in the Z-Wave network</strong></p><ol><li>Enter “SETTINGS“ Mode by pressing and holding the Gear button for three seconds.</li><li>If you need to change the device factory default Z-Wave frequency, see the Parameter description and steps to change the value on page 12 of documentation</li><li>Scroll menu to “Parameter 2 – nEt“. The current state of the network will be displayed in the Parameter Value position (upper right). It should display “ECL“. Note: If “InC“ is displayed, the HE-HT01 must first be Excluded from an existing Z-Wave network (see “Removing from Z-Wave network“ below).</li><li>Start the Inclusion Mode from openhab.</li><li>On the HE-HT01 in the Parameter 2 press the Plus “+“ button to start the Inclusion process.</li><li>Note that lines will be moving in the Parameter value position (upper right).</li><li>“InC“ should appear at the Parameter Value position (and the icon on the main display bottom right corner) if Inclusion was successful.</li><li>If “EСL“ or “Err“ is on Value position (or icon on the main display bottom right corner), the HE-HT01 Inclusion was not successful (try repeating steps 4-7).</li></ol> <br /> <h2>Exclusion Information</h2><p><strong>To remove the thermostat in the Z-Wave network</strong></p><ol><li>Enter “SETTINGS“ Mode by pressing and holding the Gear button for three seconds.</li><li><p>Scroll menu to “Parameter 2 – nEt“ using the Heating Element button to scroll up, and the “MODE“ button to scroll down.</p></li><li><p>The current state of the network will display in the Parameter Value position (upper right). It should display “InC“. Note: If “EСL“ is displayed, the HE-HT01 is already Excluded.</p></li><li><p>Start the Exclusion Mode from the openhab.</p></li><li><p>Press the Minus “–“ button in the HE-HT01 Parameter 2 to start the Exclusion process</p></li><li><p>Note that lines will be moving in the Parameter value position (upper right).</p></li><li><p>“EСL“ should appear in the value position (and icon in the bottom right corner of the main display) if the Exclusion was successful.</p></li><li><p>If “InC“ or “Err“ in value position (or icon in the bottom right corner of the main display) are displayed, repeat the Exclusion process. </p></li></ol>Note: If the HE-HT01 has previously been part of a Z-Wave network and not Excluded since, Inclusion is not possible without first performing an Exclusion or Factory Reset procedure.<p><br /></p><p>Note: If the HE-HT01 is included in the Z-Wave network the antenna icon will appear in the bottom right corner of the main screen with signal strength bars</p> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>HVAC</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="sensor_temperature" typeId="sensor_temperature">
<label>Sensor (temperature)</label>
<properties>
<property name="binding:*:QuantityType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=TEMPERATURE</property>
</properties>
</channel>
<channel id="sensor_relhumidity" typeId="sensor_relhumidity">
<label>Sensor (relative humidity)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=RELATIVE_HUMIDITY</property>
</properties>
</channel>
<channel id="sensor_soiltemperature" typeId="sensor_soiltemperature">
<label>Sensor (soil temperature)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=SOIL_TEMPERATURE</property>
</properties>
</channel>
<channel id="sensor_luminance" typeId="sensor_luminance">
<label>Sensor (luminance)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=LUMINANCE</property>
</properties>
</channel>
<channel id="meter_watts" typeId="meter_watts">
<label>Electric meter (watts)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;type=E_W</property>
</properties>
</channel>
<channel id="meter_kwh" typeId="meter_kwh">
<label>Electric meter (kWh)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;type=E_KWh</property>
</properties>
</channel>
<channel id="meter_voltage" typeId="meter_voltage">
<label>Electric meter (volts)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;type=E_V</property>
</properties>
</channel>
<channel id="thermostat_mode" typeId="heltun_heht01_00_000_thermostat_mode">
<label>Thermostat mode</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_THERMOSTAT_MODE</property>
</properties>
</channel>
<channel id="thermostat_state" typeId="thermostat_state">
<label>Thermostat Operating State</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_THERMOSTAT_OPERATING_STATE</property>
</properties>
</channel>
<channel id="thermostat_setpoint_moist_air" typeId="thermostat_setpoint">
<label>Setpoint (moist air)</label>
<properties>
<property name="binding:*:QuantityType">COMMAND_CLASS_THERMOSTAT_SETPOINT;type=MOIST_AIR</property>
</properties>
</channel>
<channel id="thermostat_setpoint_furnace" typeId="thermostat_setpoint">
<label>Setpoint (furnace)</label>
<properties>
<property name="binding:*:QuantityType">COMMAND_CLASS_THERMOSTAT_SETPOINT;type=FURNACE</property>
</properties>
</channel>
<channel id="thermostat_setpoint_heating" typeId="thermostat_setpoint">
<label>Setpoint (heating)</label>
<properties>
<property name="binding:*:QuantityType">COMMAND_CLASS_THERMOSTAT_SETPOINT;type=HEATING</property>
</properties>
</channel>
<channel id="time_offset" typeId="time_offset">
<label>Clock Time Offset</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_CLOCK</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Heltun</property>
<property name="modelId">HE-HT01</property>
<property name="manufacturerId">0344</property>
<property name="manufacturerRef">0004:0001</property>
<property name="dbReference">1327</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_1_1" type="integer" groupName="configuration">
<label>1: Frequency Region</label>
<description><![CDATA[
Frequency Region<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>0</default>
<options>
<option value="0">EU (868.4 MHz, 869.85 MHz)</option>
<option value="1">US (908.4 MHz, 916.0 MHz)</option>
<option value="2">AU (919.8 MHz, 921.4 MHz)</option>
<option value="3">HO (919.8 MHz)</option>
<option value="4">In (865.2 MHz)</option>
<option value="5">IL (916.0 MHz)</option>
<option value="6">RU (869.0 MHz)</option>
<option value="7">Cn (868.4 MHz)</option>
<option value="8">JP (922.5 MHz, 923.9 MHz, 926.3 MHz)</option>
<option value="9">Or (920.9 MHz, 921.7 MHz, 923.1 MHz)</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_3_4" type="integer" groupName="configuration" readOnly="true"
min="0" max="4294967295">
<label>3: Hardware and Software Versions</label>
<description><![CDATA[
Hardware and Software Versions<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_4_4" type="integer" groupName="configuration" readOnly="true"
min="0" max="4294967295">
<label>4: Energy Consumption, kW</label>
<description><![CDATA[
Energy Consumption, kW<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_5_1" type="integer" groupName="configuration"
min="0" max="10">
<label>5: Display brightness control</label>
<description>Display brightness control</description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_6_1" type="integer" groupName="configuration"
min="1" max="10">
<label>6: Touch buttons sensitivity</label>
<description><![CDATA[
Touch buttons sensitivity<br /> <h1>Overview</h1><p>Touch buttons sensitivity. </p><p>1 = Lowest</p><p>10 = Highest</p>
]]></description>
<default>6</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_7_1" type="integer" groupName="configuration"
min="0" max="1">
<label>7: Relay output</label>
<description><![CDATA[
Relay output NO or NC mode<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_8_1" type="integer" groupName="configuration"
min="0" max="3">
<label>8: External input mode</label>
<description><![CDATA[
External input mode<br /> <h1>Overview</h1><p>If Parameter value = 0 no action will be taken (the input state changes will be ignored by the Thermostat logic).</p><p>If Parameter value = 1 the external input will operate in ―Toggle Switch‖ mode: if the external input is shorted (with Sx or N) the Thermostat switches to the operating mode selected in the Parameter 09 and switches to MAN mode with IDLE state (OFF) when the external input is open (released).</p><p>If Parameter value = 2 the external input will operate in ―Toggle Switch Reverse‖ mode: if the external input is shorted the Thermostat switches to MAN mode with IDLE state (OFF) and switches to the operating mode selected in the Parameter 09 when the input is open.</p><p>If Parameter value = 3 the external input will operate in ―Push Button (Momentary Switch)‖ mode: each press of button (shorten of the input) will consistently change the mode to mode selected in the Parameter 09 then to MAN mode with IDLE state.</p>
]]></description>
<default>0</default>
<options>
<option value="0">Ignore external input</option>
<option value="1">Toggle Switch</option>
<option value="2">Toggle Switch Reverse</option>
<option value="3">Push Button (Momentary Switch)</option>
</options>
</parameter>
<parameter name="config_9_1" type="integer" groupName="configuration"
min="1" max="6">
<label>9: Mode number</label>
<description><![CDATA[
Mode number for external input action<br /> <h1>Overview</h1><p>Mode number for EXT input action. This parameter allows selecting which operating mode the thermostat should go to if the external input is short-circuited.</p> <p>1=COM, 2=TIME, 3=DRY, 4=ECO, 5=VAC, 6=MAN.</p> <p><strong>Note:</strong> When thermostat goes to MAN mode it will be in IDLE state till HEATING key is not pressed manually.</p>
]]></description>
<default>6</default>
<options>
<option value="1">COM</option>
<option value="2">TIME</option>
<option value="3">DRY</option>
<option value="4">ECO</option>
<option value="5">VAC</option>
<option value="6">MAN</option>
</options>
</parameter>
<parameter name="config_10_1" type="integer" groupName="configuration"
min="1" max="100">
<label>10: Floor sensor resistance</label>
<description><![CDATA[
Floor Sensor Resistance, kohm<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>10</default>
</parameter>
<parameter name="config_11_1" type="integer" groupName="configuration"
min="1" max="7">
<label>11: Source sensor</label>
<description><![CDATA[
Source sensor<br /> <h1>Overview</h1><p>Source Sensor: <br />1=A, 2=AF, 3=F, 4=FA, 5=t, 6=tA, 7=tF. <br />A=Air sensor, AF - Air sensor + Floor sensor, F - Floor sensor, FA - Floor sensor +Air sensor, t - Time regulator, tA - Time regulator + Air sensor, tF - Time regulator + Floor sensor</p>
]]></description>
<default>3</default>
<options>
<option value="1">Air sensor</option>
<option value="2">Air and Floor sensors</option>
<option value="3">Floor sensor</option>
<option value="4">Floor and Air sensor</option>
<option value="5">Time regulator</option>
<option value="6">Time regulator and Air sensor</option>
<option value="7">Time regulator and Floor sensor</option>
</options>
</parameter>
<parameter name="config_12_2" type="integer" groupName="configuration"
min="10" max="360">
<label>12: Air temp min</label>
<description><![CDATA[
Air Temperature Minimum in degree, x10<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 21.5°C = 215</p>
]]></description>
<default>210</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_13_2" type="integer" groupName="configuration"
min="20" max="370">
<label>13: Air temp max</label>
<description><![CDATA[
Air Temperature Maximum in degree, x10<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 27°C = 270</p>
]]></description>
<default>270</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_14_2" type="integer" groupName="configuration"
min="10" max="360">
<label>14: Floor temp min</label>
<description><![CDATA[
Floor Temperature Minimum in degree, x10<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 18°C = 180</p>
]]></description>
<default>180</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_15_2" type="integer" groupName="configuration"
min="20" max="370">
<label>15: Floor temp max</label>
<description><![CDATA[
Floor Temperature Maximum in degree, x10<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 32°C = 320</p>
]]></description>
<default>320</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_16_1" type="integer" groupName="configuration"
min="-100" max="100">
<label>16: Floor temp calibration</label>
<description><![CDATA[
Floor Temperature Calibration in degree x10<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 1.5°C = 15</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_17_1" type="integer" groupName="configuration"
min="-100" max="100">
<label>17: Air temp calibration</label>
<description><![CDATA[
Air Temperature Calibration in degree x10<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 1.0°C = 10</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_18_1" type="integer" groupName="configuration"
min="2" max="100">
<label>18: Temp hysteresis</label>
<description><![CDATA[
Temperature Hysteresis in degree, x10<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 0.5 = 5</p>
]]></description>
<default>5</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_19_1" type="integer" groupName="configuration"
min="0" max="1">
<label>19: Time by controller</label>
<description><![CDATA[
Time correction by controller<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_20_1" type="integer" groupName="configuration">
<label>20: Time format</label>
<description><![CDATA[
Time format<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>0</default>
<options>
<option value="0">24 hour</option>
<option value="1">12 hour (AM / PM)</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_21_1" type="integer" groupName="configuration"
min="1" max="7">
<label>21: Week day</label>
<description><![CDATA[
Manually set week day<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_22_2" type="integer" groupName="configuration"
min="0" max="2359">
<label>22: Time</label>
<description><![CDATA[
Time: Hour and Minutes<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_23_2" type="integer" groupName="configuration"
min="10" max="240">
<label>23: Time reg on</label>
<description><![CDATA[
Time Regulation ON time, min<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>30</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_24_2" type="integer" groupName="configuration"
min="10" max="240">
<label>24: Time reg off</label>
<description><![CDATA[
Time Regulation OFF time, min<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>30</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_25_1" type="integer" groupName="configuration"
min="5" max="90">
<label>25: Dry time</label>
<description><![CDATA[
Dry time<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>30</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_26_1" type="integer" groupName="configuration"
min="1" max="6">
<label>26: Mode After Dry mode</label>
<description>Mode After Dry mode</description>
<default>1</default>
</parameter>
<parameter name="config_41_2" type="integer" groupName="configuration"
min="0" max="2359">
<label>41: Morning start time</label>
<description><![CDATA[
Morning start time<br /> <h1>Overview</h1><p>Morning start time. <br />Format: HHMM. e.g.08:00 should be sent as 0800</p>
]]></description>
<default>600</default>
</parameter>
<parameter name="config_42_2" type="integer" groupName="configuration"
min="0" max="2359">
<label>42: Day start time</label>
<description><![CDATA[
Day start time<br /> <h1>Overview</h1><p>Day start time. Format: HHMM.</p>
]]></description>
<default>900</default>
</parameter>
<parameter name="config_43_2" type="integer" groupName="configuration"
min="0" max="2359">
<label>43: Evening start time</label>
<description><![CDATA[
Evening start time<br /> <h1>Overview</h1><p>Evening start time. Format: HHMM.</p>
]]></description>
<default>1800</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_44_2" type="integer" groupName="configuration"
min="0" max="2359">
<label>44: Night Start time</label>
<description><![CDATA[
Night Start time<br /> <h1>Overview</h1><p>Night start time. Format: HHMM.</p>
]]></description>
<default>2300</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_45_2" type="integer" groupName="configuration"
min="10" max="370">
<label>45: Monday morning temp</label>
<description><![CDATA[
Monday morning temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>240</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_46_2" type="integer" groupName="configuration"
min="10" max="370">
<label>46: Monday day temp</label>
<description><![CDATA[
Monday day temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>200</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_47_2" type="integer" groupName="configuration"
min="10" max="370">
<label>47: Monday evening temp</label>
<description><![CDATA[
Monday evening temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>230</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_48_2" type="integer" groupName="configuration"
min="10" max="370">
<label>48: Monday night temp</label>
<description><![CDATA[
Monday night temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>180</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_49_2" type="integer" groupName="configuration"
min="10" max="370">
<label>49: Tuesday morning temp</label>
<description><![CDATA[
Tuesday morning temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>240</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_50_2" type="integer" groupName="configuration"
min="10" max="370">
<label>50: Tuesday day temp</label>
<description><![CDATA[
Tuesday day temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>200</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_51_2" type="integer" groupName="configuration"
min="10" max="370">
<label>51: Tuesday evening temp</label>
<description><![CDATA[
Tuesday evening temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>230</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_52_2" type="integer" groupName="configuration"
min="10" max="370">
<label>52: Tuesday night temp</label>
<description><![CDATA[
Tuesday night temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>180</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_53_2" type="integer" groupName="configuration"
min="10" max="370">
<label>53: Wednesday morning temp</label>
<description><![CDATA[
Wednesday morning temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>240</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_54_2" type="integer" groupName="configuration"
min="10" max="370">
<label>54: Wednesday day temp</label>
<description><![CDATA[
Wednesday day temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>200</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_55_2" type="integer" groupName="configuration"
min="10" max="370">
<label>55: Wednesday evening temp</label>
<description><![CDATA[
Wednesday evening temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>230</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_56_2" type="integer" groupName="configuration"
min="10" max="370">
<label>56: Wednesday night temp</label>
<description><![CDATA[
Wednesday night temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>180</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_57_2" type="integer" groupName="configuration"
min="10" max="370">
<label>57: Thursday morning temp</label>
<description><![CDATA[
Thursday morning temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>240</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_58_2" type="integer" groupName="configuration"
min="10" max="370">
<label>58: Thursday day temp</label>
<description><![CDATA[
Thursday day temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>200</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_59_2" type="integer" groupName="configuration"
min="10" max="370">
<label>59: Thursday evening temp</label>
<description><![CDATA[
Thursday evening temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>230</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_60_2" type="integer" groupName="configuration"
min="10" max="370">
<label>60: Thursday night temp</label>
<description><![CDATA[
Thursday night temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>180</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_61_2" type="integer" groupName="configuration"
min="10" max="370">
<label>61: Friday morning temp</label>
<description><![CDATA[
Friday morning temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>240</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_62_2" type="integer" groupName="configuration"
min="10" max="370">
<label>62: Friday day temp</label>
<description><![CDATA[
Friday day temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>200</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_63_2" type="integer" groupName="configuration"
min="10" max="370">
<label>63: Friday evening temp</label>
<description><![CDATA[
Friday evening temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>230</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_64_2" type="integer" groupName="configuration"
min="10" max="370">
<label>64: Friday night temp</label>
<description><![CDATA[
Friday night temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>180</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_65_2" type="integer" groupName="configuration"
min="10" max="370">
<label>65: Saturday morning temp</label>
<description><![CDATA[
Saturday morning temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>240</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_66_2" type="integer" groupName="configuration"
min="10" max="370">
<label>66: Saturday day temp</label>
<description><![CDATA[
Saturday day temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>200</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_67_2" type="integer" groupName="configuration"
min="10" max="370">
<label>67: Saturday evening temp</label>
<description><![CDATA[
Saturday evening temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>230</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_68_2" type="integer" groupName="configuration"
min="10" max="370">
<label>68: Saturday night temp</label>
<description><![CDATA[
Saturday night temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>180</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_69_2" type="integer" groupName="configuration"
min="10" max="370">
<label>69: Sunday morning temp</label>
<description><![CDATA[
Sunday morning temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>240</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_70_2" type="integer" groupName="configuration"
min="10" max="370">
<label>70: Sunday day temp</label>
<description><![CDATA[
Sunday day temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>200</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_71_2" type="integer" groupName="configuration"
min="10" max="370">
<label>71: Sunday evening temp</label>
<description><![CDATA[
Sunday evening temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>230</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_72_2" type="integer" groupName="configuration"
min="10" max="370">
<label>72: Sunday night temp</label>
<description><![CDATA[
Sunday night temp<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>180</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_141_1" type="integer" groupName="configuration"
min="1" max="120">
<label>141: Consumption reporting interval</label>
<description>Consumption meter consecutive reporting interval, minutes</description>
<default>10</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_142_1" type="integer" groupName="configuration"
min="0" max="50">
<label>142: Consumption difference</label>
<description>Consumption difference to send to controller, %</description>
<default>25</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_143_1" type="integer" groupName="configuration"
min="1" max="120">
<label>143: Sensors reporting interval</label>
<description>Sensors consecutive reporting interval, minutes</description>
<default>10</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_144_1" type="integer" groupName="configuration"
min="0" max="100">
<label>144: Temperature difference</label>
<description>Temperature difference to send to controller, value X 10</description>
<default>2</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_145_1" type="integer" groupName="configuration"
min="0" max="25">
<label>145: Humidity difference</label>
<description>Humidity difference to send to controller, %</description>
<default>2</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_146_1" type="integer" groupName="configuration"
min="0" max="99">
<label>146: Light sensor difference</label>
<description>Light sensor values difference to send to controller, %</description>
<default>50</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_171_1" type="integer" groupName="configuration">
<label>171: Basic set action</label>
<description>Mode to switch to on Basic</description>
<default>1</default>
<options>
<option value="0">No Action</option>
<option value="1">COM</option>
<option value="2">TIME</option>
<option value="3">DRY</option>
<option value="4">ECO</option>
<option value="5">VAC</option>
<option value="6">MAN</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_1001_1" type="integer" groupName="configuration"
min="0" max="59">
<label>1001: DELETE ME</label>
<description><![CDATA[
Manually set time minute<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_1002_1" type="integer" groupName="configuration"
min="1" max="10">
<label>1002: DELETE ME</label>
<description><![CDATA[
Temperature difference to send to controller, value x10<br /> <h1>Overview</h1><p>Centigrade value * 10</p> <p>e.g. 22.5 = 225</p>
]]></description>
<default>2</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_1003_1" type="integer" groupName="configuration"
min="1" max="4">
<label>1003: DELETE ME</label>
<description><![CDATA[
Active display brightness level.<br /> <h1>Overview</h1><p>Active display brightness level. Must be greater than or equal param 23</p>
]]></description>
<default>4</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_1004_1" type="integer" groupName="configuration"
min="1" max="4">
<label>1004: DELETE ME</label>
<description><![CDATA[
Inactive display brightness level.<br /> <h1>Overview</h1><p>Inactive display brightness level. Must be less than or equal param 22</p>
]]></description>
<default>3</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_1005_1" type="integer" groupName="configuration"
min="0" max="1">
<label>1005: DELETE ME</label>
<description><![CDATA[
Auto LCD brightness control<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_1006_1" type="integer" groupName="configuration"
min="0" max="5000">
<label>1006: DELETE ME</label>
<description><![CDATA[
Auto bright level 1<br /> <h1>Overview</h1><p>Auto brightness level 1 max lumens</p>
]]></description>
<default>30</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_1007_1" type="integer" groupName="configuration"
min="0" max="5000">
<label>1007: DELETE ME</label>
<description><![CDATA[
Auto bright level 2<br /> <h1>Overview</h1><p>Auto brightness level 2 max lumens</p>
]]></description>
<default>200</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_1008_1" type="integer" groupName="configuration"
min="0" max="5000">
<label>1008: DELETE ME</label>
<description><![CDATA[
Auto bright level 3<br /> <h1>Overview</h1><p>Auto brightness level 3 max lumens</p>
]]></description>
<default>3000</default>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association">
<label>1: Lifeline</label>
<description><![CDATA[
Reports full state of the device and used to communicate with the Z-Wave gateway.<br /> <h1>Overview</h1><p><br /></p>
]]></description>
</parameter>
<parameter name="group_2" type="text" groupName="association">
<label>2: Basic Set On/Off: Relay</label>
<description><![CDATA[
is assigned to the HE-HT01 operating state. It sends a Basic Set command with value 0 (Off) when it goes to IDLE state and sends 255 (ON) when it goes into HEATING state<br /> <h1>Overview</h1><p><br /></p>
]]></description>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
<channel-type id="heltun_heht01_00_000_thermostat_mode">
<item-type>Number</item-type>
<label>Thermostat Mode</label>
<description>Sets the thermostat mode</description>
<category>Temperature</category>
<state pattern="%s">
<options>
<option value="0">Off</option>
<option value="1">Heat</option>
<option value="10">Auto Changeover</option>
<option value="11">Economy Heat</option>
<option value="13">Away</option>
<option value="8">Dry Air</option>
</options>
</state>
</channel-type>
</thing:thing-descriptions>

2
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/heltun/hezwthermfl2_0_0.xml
View File

@ -81,7 +81,7 @@ Wall Heating Thermostat<br /> <h1>Overview</h1><p>The Heltun Heating Thermostat
<property name="vendor">Heltun</property>
<property name="modelId">HE-ZW-THERM-FL2</property>
<property name="manufacturerId">0344</property>
<property name="manufacturerRef">0003:0001,0004:0001</property>
<property name="manufacturerRef">0003:0001</property>
<property name="dbReference">1023</property>
<property name="defaultAssociations">1</property>
</properties>

160
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/honeywell/39339_0_0.xml Normal file
View File

@ -0,0 +1,160 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="honeywell_39339_00_000" listed="false">
<label>39339 (ZW3107) Z-Wave Plug-in Smart Dimmer</label>
<description><![CDATA[
Z-Wave Plug-in Smart Dimmer<br /> <h1>Overview</h1><p>Stay connected to your home with a Honeywell Z-Wave Smart Dimmer. Compatible with all Z‑Wave certified gateways, the smart dimmer gives you wireless control of your dimmable lights from any mobile device, computer or Z-Wave enabled remote. Setup is easy – simply plug the dimmer into any in-wall outlet, then connect your light to one of the two dual smart outlets located on either side of the dimmer. Whether you’re at home or away, access the dimmer to turn your lights on and off, or to adjust the brightness levels of the room.</p> <p>The smart dimmer incorporates reliable, dynamic illumination to your home, giving you a fully lit workspace or letting you settle down for the evening with effective, stylish accent lighting. Not only does the smart dimmer help cut energy costs, but it boosts the safety of your home by keeping rooms looking bright and lived‑in. Give your space the perfect amount of light with a Honeywell Z-Wave Smart Dimmer.</p> <h4>Features</h4> <ul><li>ALEXA COMPATIBLE (HUB REQUIRED) - Requires an Alexa supported hub for voice control with Amazon Echo Products (Alexa device and hub are sold separately).Cannot connect directly with ECHO PLUS (Only ZigBee products can connect directly to Echo Plus)</li> <li>REQUIRES A Z-WAVE CERTIFIED HUB - Compatible with the following Z-Wave Hubs: Honeywell, SmartThings, Pulse, Trane, Wink, Nexia, Honeywell, HomeSeer, Smart Security, Harmony Home Hub Extender, Vera, and Fibaro</li> <li>WIRELESSLY CONTROL &amp; SCHEDULE LIGHTS - Schedule timed events for connected lighting. Customize scenes for day or night, home or away. Wirelessly control from anywhere through your smartphone, tablet, PC or Z-Wave remote</li> <li>FULL RANGE DIMMING – Give your space the perfect amount of light with the ability to customize the brightness levels from 0 to 100%. Works ONLY with dimmable bulbs and lamps</li> <li>2 SIMULTANEOUSLY CONTROLLED POLARIZED OUTLET - features 2 polarized outlets that can be controlled at the same time (NOT SEPERATLEY) and a manual ON/OFF, dim &amp; program physical button. To setup simply plug the module into any in-wall outlet, then connect</li> </ul> <br /> <h2>Inclusion Information</h2><p>Press and release the manual/program button. (Tested to work with Network Wide Inclusion.)</p> <br /> <h2>Exclusion Information</h2><p>Press and release the manual/program button.</p>
]]></description>
<category>PowerOutlet</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="switch_dimmer" typeId="switch_dimmer">
<label>Dimmer</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL,COMMAND_CLASS_BASIC</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
</properties>
</channel>
<channel id="scene_number" typeId="scene_number">
<label>Scene Number</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_SCENE_ACTIVATION</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Honeywell</property>
<property name="modelId">39339 (ZW3107)</property>
<property name="manufacturerId">0039</property>
<property name="manufacturerRef">5044:3033</property>
<property name="dbReference">976</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_3_1" type="integer" groupName="configuration">
<label>3: LED Light</label>
<description><![CDATA[
LED Light Control<br /> <h1>Overview</h1><p>When shipped from the factory, the LED is set to turn ON when the connected light is turned On. This is the default setting and can be changed if your primary controller supports the node configuration function or by a manual method. To make the LED turn ON when the light is turned ON, change parameter 3s value to 1. To turn the LED OFF at all times, change parameter 3s value to 2.</p>
]]></description>
<default>0</default>
<options>
<option value="0">Set parameter to factory default</option>
<option value="1">LED On when light is turned On</option>
<option value="2">LED always Off</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_6_1" type="integer" groupName="configuration"
min="0" max="1">
<label>6: Dim Up/Down Behavior</label>
<description><![CDATA[
Controls whether level changes are instant or smooth<br /> <h1>Overview</h1><p>This is an undocumented feature. This parameter allows you to choose between instant level changes and smooth level changes on newer Jasco/Honeywell/GE dimmers. This feature should work on dimmers that come out of the box with instant level changes, it may not work on older dimmers that smoothly change levels by default. <br /></p>
]]></description>
<default>0</default>
<options>
<option value="0">Instant Level Changes</option>
<option value="1">Smooth Level Changes</option>
</options>
</parameter>
<parameter name="config_7_1" type="integer" groupName="configuration"
min="1" max="99">
<label>7: Dim Rate Adjustments (Z-Wave Controller)</label>
<description>Number of steps or levels</description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_8_2" type="integer" groupName="configuration"
min="1" max="255">
<label>8: Dim Rate Adjustments (Z-Wave Controller, Timing)</label>
<description>Timing of steps</description>
<default>3</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_9_1" type="integer" groupName="configuration"
min="1" max="99">
<label>9: Dim Rate Adjustments (manually controlled)</label>
<description>Number of steps or levels</description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_10_2" type="integer" groupName="configuration"
min="0" max="255">
<label>10: Dim Rate Adjustments (manually controlled, timing)</label>
<description>Timing of steps</description>
<default>3</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_11_1" type="integer" groupName="configuration"
min="1" max="99">
<label>11: Dim Rate Adjustments (All-On/Off Commands)</label>
<description>Number of steps or levels</description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_12_2" type="integer" groupName="configuration"
min="1" max="255">
<label>12: Dim Rate Adjustments (All-On/Off Command, Timing)</label>
<description>Timing of steps</description>
<default>3</default>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Lifeline</label>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: Group 2</label>
<description>Basic Set local load</description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_3" type="text" groupName="association" multiple="true">
<label>3: Group 3</label>
<description>Basic Set double click</description>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

94
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/honeywell/zw4103_0_0.xml Normal file
View File

@ -0,0 +1,94 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="honeywell_zw4103_00_000" listed="false">
<label>ZW4103 Z-Wave Plug in Smart Switch</label>
<description><![CDATA[
Z-Wave Plug in Smart Switch<br /> <h1>Overview</h1><p>Control, automate, and schedule your homes lighting and appliances with the Plug-In Smart Switch. Using this Smart Switch means taking control of your homes lighting and appliances regardless of if you are in a different part of your home, the couch, work or away on vacation - all from your mobile device and Z-Wave compatible hub.</p><p>The plug-in smart switch gives you wireless control of your plug-in lighting and appliances from any mobile device, computer or Z-Wave enabled remote via a Z-Wave Certified gateway/hub. Automating you lights will not only make your life easier but it will also save energy, cut costs, and boost your home’s security. Plug-in Smart Switch has 1 grounded outlet located on the left side of the module and leaves bottom outlet<br /></p><p>Schedule timed events and customize scenes for day or night, home or away - wirelessly control from anywhere through your smartphone, tablet, PC or Z-Wave remote</p><ul><li>Features 1 controlled grounded outlet w/ manual ON/OFF &amp; program button - works with all LED, CFL, halogen and incandescent bulbs and other devices</li><li>Requires a Z-Wave Certified Hub: Compatible with the following Z-Wave Hubs: Honeywell, Ring, SmartThings, Wink, HomeSeer, Fibaro, Trane, Nexia, ADT, Vera, and more</li><li>Simply plug the module into any in-wall outlet, then connect your light to the smart outlet located on the left side of the plug-in</li><li>2nd wallplate outlet still free for use</li></ul> <br /> <h2>Inclusion Information</h2><ol><li>Follow the instructions for your Z-Wave certified controller to include the device to the Z-Wave network.</li><li>Once the controller is ready to include your smart switch, single press and release the manual/program button on the smart dimmer to include it in the network.</li><li>Once your controller has confirmed that the smart switch has been included, refresh the Z-Wave network to optimize performance.</li></ol> <br /> <h2>Exclusion Information</h2><ol><li>Follow the instructions for your Z-Wave certified controller to exclude a device from the Z-Wave network.</li><li>Once the controller is ready to exclude your device, press and release the manual/program button on the smart switch to exclude it from the network. </li></ol> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>PowerOutlet</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="switch_binary" typeId="switch_binary">
<label>Switch</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY</property>
</properties>
</channel>
<channel id="scene_number" typeId="scene_number">
<label>Scene Number</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_SCENE_ACTIVATION</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Honeywell</property>
<property name="modelId">ZW4103</property>
<property name="manufacturerId">0039</property>
<property name="manufacturerRef">5052:3038</property>
<property name="dbReference">1329</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_3_1" type="integer" groupName="configuration"
min="0" max="2">
<label>3: LED Light</label>
<description><![CDATA[
Changes the behavior of the LED light<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>0</default>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Lifeline</label>
<description>Supports device reset locally and receives unsolicited status updates</description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: Single Press</label>
<description>Association Group 2 supports BasicSet and is controlled by single pressing the button</description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_3" type="text" groupName="association" multiple="true">
<label>3: Double Press</label>
<description>Association Group 3 supports BasicSet and is controlled by double pressing the button</description>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

60
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/horstmann/ssp301_0_0.xml Normal file
View File

@ -0,0 +1,60 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="horstmann_ssp301_00_000" listed="false">
<label>SSP301 Plug-in switch</label>
<description><![CDATA[
Plug-in switch<br /> <h1>Overview</h1><p>ON/OFF mains power module - unlike the SSP302 this doesn't have energy metering<br /></p> <br /> <h2>Inclusion Information</h2><p>To include the SSP 301 onto a network, put the controller into inclusion mode. Now, press and hold the button on SSP 301 for 4 to 7 seconds then release. The network status LED will start flashing (twice per second) on successful start of inclusion process.</p><p>Note: Refer to the controller's manual for controller relevant actions.</p><p>On successful inclusion the LED will turn off.</p><p>Note: Inclusion means add and exclusion means delete.</p><p>The total process can take up to 20 seconds (Refer to the “Technical specifications – Radio” section for details). If the device fails to join the network it will go back to factory default state and the Network status LED will start flashing once per second. If there is an issue with RF Communication, then re-locate the device and repeat the inclusion process again.</p> <br /> <h2>Exclusion Information</h2><p>To exclude the SSP 301 from a network, put the controller into exclusion mode (refer to controller instructions) and follow the same sequence as per the inclusion process for include node. After successful exclusion the network status LED will start flashing once per second, and the device will reset to factory default.</p><p>If exclusion fails, SSP 301 network status LED will turn off after about 5 seconds.</p><p>Note: Exclusion only works when the device is in direct range of the controller (no repeater allowed).</p> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>Battery</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="switch_binary" typeId="switch_binary">
<label>Switch</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Horstmann Controls Limited</property>
<property name="modelId">SSP301</property>
<property name="manufacturerId">0059</property>
<property name="manufacturerRef">000E:0001</property>
<property name="dbReference">1328</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association">
<label>1: Lifeline</label>
<description>Lifeline</description>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

201
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/idlock/idl150new_1_6.xml
View File

@ -1,201 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="idlock_idl150new_01_006" listed="false">
<label>ID-150 Z wave module for ID Lock 150 and 101</label>
<description><![CDATA[
Z wave module for ID Lock 150 and 101<br /> <h1>Overview</h1><p>The ID Lock Z-wave module is a security enabled Z-wave Plus product that is able to use encrypted Z-wave Plus messages in order to communicate to other Z-wave Plus products enabled security.</p> <p>The module is proprietary for the ID Lock 150 and also backwards compatible with the ID Lock 101. The ID Lock Z-wave module must be used in conjunction with a Security Enabled Z-wave Controller in order to fully utilize their full capability.</p> <p>The ID Lock Z-wave module can be included and operated in any Z-wave network containing certified other Z-wave products regardless of manufacturer. The ID Lock Z-wave module does not support the Basic Set Command Class.</p> <br /> <h2>Inclusion Information</h2><ol><li>Bring the controller as close as possible to the lock unit</li> <li>Set the controller to inclusion mode</li> <li>Push and hold KEY button on the inside panel on the lock until all keys on the outside light up and a audible signal is given.</li> <li>Release the KEY button on the inside panel</li> <li>Enter your Master PIN and press * </li> <li>Click 2 and then *</li> <li>Click 5, don't press *</li> <li>The LED flashes blue when inclusion is in progress</li> <li>The inclusion may take some time as security is required</li> </ol> <br /> <h2>Exclusion Information</h2><ol><li>Set the controller to Exclusion mode</li> <li>Push and hold KEY button on the inside panel on the lock until all keys on the outside light up and a audible signal is given.</li> <li>Release the KEY button on the inside panel</li> <li>Enter your Master PIN and press * </li> <li>Click 2 and then *</li> <li>Click 5, don't press *</li> <li>The LED flashes blue when exclusion is in progress</li> </ol>
]]></description>
<category>Lock</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="lock_door" typeId="lock_door">
<label>Door Lock</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_DOOR_LOCK</property>
</properties>
</channel>
<channel id="sensor_door" typeId="sensor_door">
<label>Door State</label>
<properties>
<property name="binding:*:OpenClosedType">COMMAND_CLASS_DOOR_LOCK</property>
</properties>
</channel>
<channel id="notification_access_control" typeId="notification_access_control">
<label>Access control</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_ALARM;type=ACCESS_CONTROL</property>
</properties>
</channel>
<channel id="alarm_emergency" typeId="alarm_emergency">
<label>Emergency (Contact Fire Service) [Deprecated]</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=EMERGENCY</property>
</properties>
</channel>
<channel id="alarm_burglar" typeId="alarm_burglar">
<label>Burglar alarm (tampering)</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=BURGLAR</property>
</properties>
</channel>
<channel id="alarm_raw" typeId="alarm_raw">
<label>Alarm (raw) [Deprecated]</label>
<properties>
<property name="binding:*:StringType">COMMAND_CLASS_ALARM</property>
</properties>
</channel>
<channel id="battery-level" typeId="system.battery-level">
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_BATTERY</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">ID Lock AS</property>
<property name="modelId">ID-150</property>
<property name="manufacturerId">0373</property>
<property name="manufacturerRef">0003:0001</property>
<property name="versionMin">1.6</property>
<property name="dbReference">1106</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_1_1" type="integer" groupName="configuration">
<label>1: Door lock mode</label>
<description><![CDATA[
Set if the lock is in away mode and if automatic locking should be enabled<br /> <h1>Overview</h1><p>Auto lock Mode, Manual lock mode, Activate Away Mode, Deactivate Away Mode.</p> <p>If value is 0x02 (Enable Away, Manual lock) and the door is unlocked value will be set to 0x00.</p> <p>If value is 0x03 (Enable Away, Auto lock) and the door is unlocked value will be set to 0x01.</p> <p> Default Value: 1 (Disable Away/Auto Lock Mode)</p>
]]></description>
<default>1</default>
<options>
<option value="0">Disable Away Manual Lock</option>
<option value="1">Disable Away Auto Lock</option>
<option value="2">Enable Away Manual Lock</option>
<option value="3">Enable Away Auto Lock</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_2_1" type="integer" groupName="configuration">
<label>2: RFID Mode</label>
<description>RFID Mode</description>
<default>5</default>
<options>
<option value="5">RFID activated</option>
<option value="9">RFID deactivated</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_3_1" type="integer" groupName="configuration">
<label>3: Door Hinge Position Mode</label>
<description>Tell the lock which side your hinges are on seen from the outside</description>
<default>0</default>
<options>
<option value="0">Right hinged operation</option>
<option value="1">Left hinged operation</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_4_1" type="integer" groupName="configuration">
<label>4: Door Audio Volume Level</label>
<description>Set the Audio Volume Level of the Lock</description>
<default>5</default>
<options>
<option value="0">No sound</option>
<option value="1">Level 1</option>
<option value="2">Level 2</option>
<option value="3">Level 3</option>
<option value="4">Level 4</option>
<option value="5">Level 5 (Default)</option>
<option value="6">Max. sound level</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_5_1" type="integer" groupName="configuration">
<label>5: Door ReLock Mode</label>
<description><![CDATA[
Sets if the door should relock or not<br /> <h1>Overview</h1><p>With this configuration ID Lock can automatically relock the door if an already locked door gets unlocked, but remains unopened. This is avoided by deactivating relocking.</p>
]]></description>
<default>1</default>
<options>
<option value="0">Disabled</option>
<option value="1">Enabled</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_6_1" type="integer" groupName="configuration">
<label>6: Service PIN Mode</label>
<description><![CDATA[
Sets the validity of the service PIN<br /> <h1>Overview</h1><p>A configuration get command on this parameter returns the latest set parameter value (set by Z-wave).</p> <p>This is a set only value, if changed locally on keypad these values are not changed on Z-wave module. Value 5 and 6 are for future use on door lock.</p>
]]></description>
<default>0</default>
<options>
<option value="0">Deactivated</option>
<option value="1">Valid 1 time</option>
<option value="2">Valid 2 times</option>
<option value="3">Valid 5 times</option>
<option value="4">Valid 10 times</option>
<option value="7">Always Valid</option>
<option value="8">Valid for 12h</option>
<option value="9">Valid for 24h</option>
<option value="254">Disabled</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_7_1" type="integer" groupName="configuration" readOnly="true"
min="0" max="255">
<label>7: Door Lock Model Type</label>
<description><![CDATA[
Sends information if the model of the lock is 101 or 150<br /> <h1>Overview</h1><p>This configuration is only accepted by configuration get command</p> <p>It is a read only parameter. Default value depends on the door lock model type.</p> <p>101 = ID Lock 101</p> <p>150 = ID Lock 150</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Lifeline</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>Notification Reports are sent out unsolicated to device included in the association group.</p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

6
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/linear/gd00z8gc_0_0.xml
View File

@ -14,6 +14,12 @@ Garage Door Opener<br /> <h1>Overview</h1><p>A garage door remote command transc
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="barrier_state" typeId="barrier_state">
<label>Barrier State</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_BARRIER_OPERATOR</property>
</properties>
</channel>
<channel id="alarm_burglar" typeId="alarm_burglar">
<label>Alarm (burglar)</label>
<properties>

597
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/logic/matrixzba7140_0_0.xml Normal file
View File

@ -0,0 +1,597 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="logic_matrixzba7140_00_000" listed="false">
<label>MATRIX ZBA7140 Matrix ZBA7140</label>
<description><![CDATA[
Matrix ZBA7140<br /> <h1>Overview</h1><p>MATRIX type ZBA7140 (from hereon called MATRIX ZBA) is a multifunction battery wall controller that can be mounted in a modular wall-box or directly ontothe wall. It is compatible with existing FUGA® frames and wall boxes.MATRIX ZBA has four configurable pushbuttons that can control other Z-Wave devices through the wireless Z-Wave network. These buttons can send ‘ON’, ‘OFF’ and ‘DIM’ commands to the associated Z-Wave devices. These devices could be light dimmers, blinds, sunscreens, etc.MATRIX ZBA can also issue scene activation commands that can be used to activate scenes in the Z-Wave Controller.MATRIX ZBA has four RGB indicator LEDs, one for each pushbutton, that indicates activation of the pushbutton, and when MATRIX ZBA is in inclusion or exclusion mode. These indicators can be configured to a desired indication colour, or they can indicate the battery level when a pushbutton is activated.MATRIX ZBA is equipped with the newest battery-saving 700-series Z-Wave chip that uses up to 65% less power and have improved wireless range. This means that the small coin-cell battery can last between 5 –10years. MATRIX ZBA is estimated toabattery lifetime, at normal use, to approximately 5 years.</p> <br /> <h2>Inclusion Information</h2><p>MATRIXZBAis a SmartStart enabled product and can be added into a Z-Wave network by scanning the Z-Wave QR Code present on the product with a controller providing SmartStart inclusion. No further action is required and the SmartStart product will be added automatically within 10 minutes of being switched on in the network vicinity.Find the QR code and PIN Code on the back of the module.</p><p>Find the full DSK on the product packaging.</p><p>Add MATRIX ZBA to a network with Classic Inclusion by pressing once on the switch behind the pushbutton-cover. The LED near pushbutton 1 will start blinking.</p><p>Use same procedure for removing MATRIX ZBAwith Classic Exclusion. If MATRIXZBA already belongs to a Z-Wave network, the remove process must be performed before adding it in a new network. Otherwise, the adding of the device will fail.</p> <br /> <h2>Exclusion Information</h2><p>Add MATRIX ZBA to a network with Classic Inclusion by pressing once on the switch behind the pushbutton-cover. The LED near pushbutton 1 will start blinking.</p><p>Use same procedure for removing MATRIX ZBAwith Classic Exclusion.</p> <br /> <h2>Wakeup Information</h2><p>MATRIX ZBA is a battery-operated device and is turned into deep sleep state most of the time to save battery. Communication with the device is limited. In order to communicate with the device, a controller is needed in the network. This controller will maintain a mailbox for the battery-operated devices and store commands that can’t be received during deep sleep state. Without such a controller, communication may become impossible and/or the battery lifetime is significantly decreased. This device will wake up every 6 hours and announce the wake-upstate by sending out a so-called Wake Up Notification. The controller can then empty the mailbox. The wake-up interval is a trade-off between maximal battery lifetime and the desired responses of the device. The device will stay awake right after inclusion for 10 seconds allowing the controller to perform certain configuration. It is possible to manually wake up the device by double-activating the button </p>
]]></description>
<category>WallSwitch</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="scene_number" typeId="scene_number">
<label>Scene Number</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_CENTRAL_SCENE</property>
</properties>
</channel>
<channel id="battery-level" typeId="system.battery-level">
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_BATTERY</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Logic Group</property>
<property name="modelId">MATRIX ZBA7140</property>
<property name="manufacturerId">0234</property>
<property name="manufacturerRef">0004:0129</property>
<property name="dbReference">1330</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_1_1" type="integer" groupName="configuration"
min="0" max="1">
<label>1: Enable Central Scene notifications</label>
<description><![CDATA[
This parameter can be used for enabling or disabling Central scene notifications<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>1</default>
<options>
<option value="0">Central Scene notifications are disabled.</option>
<option value="1">Central Scene Notifications are enabled. (Default)</option>
</options>
</parameter>
<parameter name="config_2_2" type="integer" groupName="configuration"
min="1" max="1000">
<label>2: Pushbutton press threshold time</label>
<description><![CDATA[
Specifies the time that a pushbutton must be activated before it is detected as pressed.<br /> <h1>Overview</h1><p>Specifies the time that a pushbutton must be activated before it is detected as pressed. This parameter also affects the detection of double-and triple-activations, as a new activationmust be detectedwithin this specified time for the repeatedly detection. Be aware that this parameter must be lower than the value in Parameter 3. Therefore, change this parameter with caution.</p>
]]></description>
<default>400</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_3_2" type="integer" groupName="configuration"
min="1" max="5000">
<label>3: Pushbutton held threshold time</label>
<description><![CDATA[
Specifies the time that a pushbutton must have been activated before it is accepted as “held-down”.<br /> <h1>Overview</h1><p>Specifies the time that a pushbutton must have been activated before it is accepted as “held-down”. This value must be higher than the value set in Parameter 2. Resolution is milliseconds</p>
]]></description>
<default>600</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_4_1" type="integer" groupName="configuration">
<label>4: Mode of the LED indication.</label>
<description><![CDATA[
This parameter specifies the mode of the LED indication.<br /> <h1>Overview</h1><p>This parameter specifies the mode of the LED indication.</p>
]]></description>
<default>1</default>
<options>
<option value="0">LED indication is turned off.</option>
<option value="1">LEDs indicates the current level of the battery, when the device is in</option>
<option value="2">LED colour is set by configuration parameter 5.</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_5_4_00000001" type="integer" groupName="configuration"
min="0" max="255">
<label>5: LEDs colour indication, Byte 1</label>
<description><![CDATA[
Specifies the level for the red colour. (Default is 255)<br /> <h1>Overview</h1><p>This parameter specifies the colour levels for the red, green and blue colours in the 4 RGB LEDs. This parameter is not used unless configuration parameter 4 is set to the value 2. The default configuration is a white light, where red level value must be higher than the two other colours in order to get a white light.Value Description</p><p>Byte 1: Red colour level.0 -255Specifies the level for the red colour. (Default is 255)</p><br />
]]></description>
<default>255</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_5_4_0000FF00" type="integer" groupName="configuration"
min="0" max="255">
<label>5: LEDs colour indication, Byte 2</label>
<description><![CDATA[
Specifies the level for the green colour. (Default is 85)<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>85</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_5_4_00FF0000" type="integer" groupName="configuration"
min="0" max="255">
<label>5: LEDs colour indication, Byte 3</label>
<description><![CDATA[
Specifies the level for the blue colour. (Default is 85)<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>85</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_5_4_01000000" type="integer" groupName="configuration"
min="0" max="4294967295">
<label>5: Not used.</label>
<description><![CDATA[
This byte is not used and must be set to 0.<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_6_2" type="integer" groupName="configuration">
<label>6: Associations groups, transmission when included secure.</label>
<description><![CDATA[
This parameter specifies if commands are transmitted as a secure message for each of the association groups.<br /> <h1>Overview</h1><p>This parameter specifies if commands are transmitted as a secure message for each of the association groups.This parameter is only used when the device is included in security mode (either S0 or S2).</p>
]]></description>
<default>255</default>
<options>
<option value="0">All messages in all groups are sent as insecure.</option>
<option value="1">Messages in association group 2 are sent as secure.</option>
<option value="2">Messages in association group 3 are sent as secure.</option>
<option value="4">Messages in association group 4 are sent as secure.</option>
<option value="8">Messages in association group 5 are sent as secure.</option>
<option value="16">Messages in association group 6 are sent as secure.</option>
<option value="32">Messages in association group 7 are sent as secure.</option>
<option value="64">Messages in association group 8 are sent as secure.</option>
<option value="128">Messages in association group 9 are sent as secure.</option>
<option value="255">All messages in all groups are sent as secure. (Default)</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_7_1" type="integer" groupName="configuration"
min="0" max="3">
<label>7: Pushbutton 1 functionality.</label>
<description><![CDATA[
This parameter specifies the functionality of pushbutton 1.<br /> <h1>Overview</h1><p>0 Standard toggle-function, the state is switched between on and off, dimming up and down. (Default)</p><p>1 Always turn on or dim up. Using this parameter, the pushbutton can only send ‘on’ or ‘dim up’ commands. Use this in pair with another pushbutton with value 2.</p><p>2 Always turn offor dim down. Using this parameter, the pushbutton can only send ‘off’ or ‘dim down’ commands. Use this in pair with another pushbutton with value 1.</p><p>3 When the pushbutton is down; an on command is sent, and when the pushbutton is released; an off command is sent.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_8_4_00000001" type="integer" groupName="configuration">
<label>8: Switch multilevel set single-activation values for pushbutton 1, Byte 1</label>
<description><![CDATA[
Enable/Disable<br /> <h1>Overview</h1><p>Byte 1: Enable / Disable <br /></p><p>0 Disabled – A single activation of the pushbutton will not send commands to devices in the association group.</p><p>1 Enabled – A single activation will send commands to devices in the association group. Devices will receive commands with the values set in 3 following bytes.(Default)</p>
]]></description>
<default>1</default>
<options>
<option value="0">Disabled –A single activation of the pushbutton will not send commands</option>
<option value="1">Enabled –A single activation will send commands to devices in the asso</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_8_4_0000FF00" type="integer" groupName="configuration"
min="0" max="255">
<label>8: Switch multilevel set single-activation values for pushbutton 1, Byte 2</label>
<description><![CDATA[
Upper switch value<br /> <h1>Overview</h1><p>Byte 2: Upper switch value0 –99, 255When single pressing the pushbutton for ON, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 255)</p>
]]></description>
<default>255</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_8_4_00FF0000" type="integer" groupName="configuration"
min="0" max="99">
<label>8: Switch multilevel set single-activation values for pushbutton 1, Byte 3</label>
<description><![CDATA[
Lower switch value<br /> <h1>Overview</h1><p>Byte 3: Lower switch value 0 -99 When single pressing the pushbutton for OFF, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 0)</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_8_4_01000000" type="integer" groupName="configuration"
min="0" max="255">
<label>8: Switch multilevel set single-activation values for pushbutton 1, Byte 4</label>
<description><![CDATA[
Duration<br /> <h1>Overview</h1><p>Byte 4: Duration 0 -255 When single pressing the pushbutton the Switch Multilevel Set with this duration value will be send to devices in the association group. <br /></p><p>0: Use dimmer default timer value. (Default)</p><p>1 –127: Duration in seconds.</p><p>128 –255: Duration in minutes (minus 127) from 1 –128 minutes, where 128 is 1 minute.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_9_4_00000001" type="integer" groupName="configuration"
min="0" max="1">
<label>9: Switch Multilevel Set double-activation values for pushbutton 1. Byte 1</label>
<description><![CDATA[
Enable/Disable<br /> <h1>Overview</h1><p>This parameter specifies the value that are sent to the devices in the Switch Multilevel association group (group 3) when the pushbutton is double-pressed.</p><p>Byte 1: Enable / Disable0Disabled –A double activation of the pushbutton will not send commands to devices in the association group.1Enabled –A double activation will send commands to devices in the association group. Devices will receive commands with the values set in 3 following bytes. (Default)</p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_9_4_0000FF00" type="integer" groupName="configuration"
min="0" max="255">
<label>9: Switch Multilevel Set double-activation values for pushbutton 1. Byte 2</label>
<description><![CDATA[
Upper switch value<br /> <h1>Overview</h1><p>Byte 2: Upper switch value 0 –99, 255 When double pressing the pushbutton for ON, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 99)</p>
]]></description>
<default>99</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_9_4_00FF0000" type="integer" groupName="configuration"
min="0" max="99">
<label>9: Switch Multilevel Set double-activation values for pushbutton 1. Byte 3</label>
<description><![CDATA[
Lower switch value<br /> <h1>Overview</h1><p>Byte 3: Lower switch value 0 -99 When double pressing the pushbutton for OFF, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 99)</p>
]]></description>
<default>99</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_9_4_01000000" type="integer" groupName="configuration"
min="0" max="255">
<label>9: Switch Multilevel Set double-activation values for pushbutton 1. Byte 4</label>
<description><![CDATA[
Duration<br /> <h1>Overview</h1><p>Byte 4: Duration 0 -255 When double pressing the pushbutton the Switch Multilevel Set with this duration value will be send to devices in the association group. <br /></p><p>0: Use dimmer default timer value. (Default)</p><p>1 –127: Duration in seconds.</p><p>128 –255: Duration in minutes (minus 127) from 1 –128 minutes, where 128 is 1 minute.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_10_1" type="integer" groupName="configuration"
min="0" max="3">
<label>10: Pushbutton 2 functionality.</label>
<description><![CDATA[
This parameter specifies the functionality of pushbutton 2.<br /> <h1>Overview</h1><p>0 Standard toggle-function, the state is switched between on and off, dimming up and down. (Default)</p><p>1 Always turn on or dim up. Using this parameter, the pushbutton can only send ‘on’ or ‘dim up’ commands. Use this in pair with another pushbutton with value 2.</p><p>2 Always turn off or dim down. Using this parameter, the pushbutton can only send ‘off’ or ‘dim down’ commands. Use this in pair with another pushbutton with value1.</p><p>3 When the pushbutton is down; an on command is sent, and when the pushbutton is released; an off command is sent.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_11_4_00000001" type="integer" groupName="configuration"
min="0" max="1">
<label>11: Switch multilevel set single-activation values for pushbutton 2, Byte 1</label>
<description><![CDATA[
Enable/Disable<br /> <h1>Overview</h1><p>Byte 1: Enable / Disable</p><p>0 Disabled – A single activation of the pushbutton will not send commands to devices in the association group.</p><p>1 Enabled – A single activation will send commands to devices in the association group. Devices will receive commands with the values set in 3 following bytes. (Default)</p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_11_4_0000FF00" type="integer" groupName="configuration"
min="0" max="255">
<label>11: Switch multilevel set single-activation values for pushbutton 2, Byte 2</label>
<description><![CDATA[
Upper switch value<br /> <h1>Overview</h1><p>Byte 2: Upper switch value 0 –99, 255 When single pressing the pushbutton for ON, a Switch Multilevel Setwith this value will be send to devices in the association group. (Default = 255)</p>
]]></description>
<default>255</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_11_4_00FF0000" type="integer" groupName="configuration"
min="0" max="99">
<label>11: Switch multilevel set single-activation values for pushbutton 2, Byte 3</label>
<description><![CDATA[
Lower switch value<br /> <h1>Overview</h1><p>Byte 3: Lower switch value 0 -99 When single pressing the pushbutton for OFF, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 0)</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_11_4_01000000" type="integer" groupName="configuration"
min="0" max="255">
<label>11: Switch multilevel set single-activation values for pushbutton 2, Byte 4</label>
<description><![CDATA[
Duration<br /> <h1>Overview</h1><p>Byte 4: Duration 0 -255 When single pressing the pushbutton the Switch Multilevel Set with this duration value will be send to devices in the association group. <br /></p><p>0: Use dimmer default timer value. (Default)</p><p>1 –127: Duration in seconds.</p><p>128 –255: Duration in minutes (minus 127) from 1 –128 minutes, where 128 is 1 minute.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_12_4_00000001" type="integer" groupName="configuration"
min="0" max="1">
<label>12: Switch Multilevel Set double-activation values for pushbutton 2. Byte 1</label>
<description><![CDATA[
Enable/Disable<br /> <h1>Overview</h1><p>Byte 1: Enable / Disable</p><p>0 Disabled – A double activation of the pushbutton will not send commands to devices in the association group.</p><p>1 Enabled – A double activation will send commands to devices in the association group. Devices will receive commands with the values set in 3 following bytes. (Default)</p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_12_4_0000FF00" type="integer" groupName="configuration"
min="0" max="255">
<label>12: Switch Multilevel Set double-activation values for pushbutton 2. Byte 2</label>
<description><![CDATA[
Upper switch value<br /> <h1>Overview</h1><p>Byte 2: Upper switch value 0 –99, 255 When double pressing the pushbutton for ON, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 99)</p>
]]></description>
<default>99</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_12_4_00FF0000" type="integer" groupName="configuration"
min="0" max="99">
<label>12: Switch Multilevel Set double-activation values for pushbutton 2. Byte 3</label>
<description><![CDATA[
Lower switch value<br /> <h1>Overview</h1><p>Byte 3: Lower switch value 0 -99 When double pressing the pushbutton for OFF, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 99)</p>
]]></description>
<default>99</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_12_4_01000000" type="integer" groupName="configuration"
min="0" max="255">
<label>12: Switch Multilevel Set double-activation values for pushbutton 2. Byte 4</label>
<description><![CDATA[
Duration<br /> <h1>Overview</h1><p>Byte 4: Duration 0 -255 When double pressing the pushbutton the Switch Multilevel Set with this duration value will be send to devices in the association group. <br /></p><p>0: Use dimmer default timer value. (Default)</p><p>1 –127: Duration in seconds.</p><p>128 –255: Duration in minutes (minus 127) from 1 –128 minutes, where 128 is 1 minute.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_13_1" type="integer" groupName="configuration"
min="0" max="3">
<label>13: Pushbutton 3 functionality.</label>
<description><![CDATA[
This parameter specifies the functionality of pushbutton 3.<br /> <h1>Overview</h1><p>0 Standard toggle-function, the state is switched between on and off, dimming up and down. (Default)</p><p>1 Always turn on or dim up. Using this parameter, the pushbutton can only send ‘on’ or ‘dim up’ commands. Use this in pair with another pushbutton with value 2.</p><p>2 Always turn offor dim down. Using this parameter, the pushbutton can only send ‘off’ or ‘dim down’ commands. Use this in pair with another pushbutton with value 1.</p><p>3 When the pushbutton is down; an on command is sent, and when the pushbutton is released; an off command is sent.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_14_4_00000001" type="integer" groupName="configuration"
min="0" max="1">
<label>14: Switch multilevel set single-activation values for pushbutton 3, Byte 1</label>
<description><![CDATA[
Enable/Disable<br /> <h1>Overview</h1><p>Byte 1: Enable / Disable <br /></p><p>0 Disabled – A single activation of the pushbutton will not send commands to devices in the association group.</p><p>1 Enabled – A single activation will send commands to devices in the association group. Devices will receive commands with the values set in 3 following bytes. (Default)</p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_14_4_0000FF00" type="integer" groupName="configuration"
min="0" max="255">
<label>14: Switch multilevel set single-activation values for pushbutton 3, Byte 2</label>
<description><![CDATA[
Upper switch value.<br /> <h1>Overview</h1><p>Byte 2: Upper switch value 0 –99, 255 When single pressing the pushbutton for ON, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 255)</p>
]]></description>
<default>255</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_14_4_00FF0000" type="integer" groupName="configuration"
min="0" max="99">
<label>14: Switch multilevel set single-activation values for pushbutton 3, Byte 3</label>
<description><![CDATA[
Lower switch value<br /> <h1>Overview</h1><p>Byte 3: Lower switch value 0 -99 When single pressing the pushbutton for OFF, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 0)</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_14_4_01000000" type="integer" groupName="configuration"
min="0" max="255">
<label>14: Switch multilevel set single-activation values for pushbutton 3, Byte 3</label>
<description><![CDATA[
Duaration<br /> <h1>Overview</h1><p>Byte 4: Duration 0 -255 When single pressing the pushbutton the Switch Multilevel Set with this duration value will be send to devices in the association group. <br /></p><p>0: Use dimmer default timer value. (Default)</p><p>1 –127: Duration in seconds.</p><p>128 –255: Duration in minutes (minus 127) from 1 –128 minutes, where 128 is 1 minute.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_15_4_00000001" type="integer" groupName="configuration"
min="0" max="1">
<label>15: Switch Multilevel Set double-activation values for pushbutton 3. Byte 1</label>
<description><![CDATA[
Enable/Disable<br /> <h1>Overview</h1><p>Byte 1: Enable / Disable</p><p>0 Disabled – A double activation of the pushbutton will not send commands to devices in the association group.</p><p>1 Enabled – A double activation will send commands to devices in the association group. Devices will receive commands with the values set in 3 following bytes. (Default)</p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_15_4_0000FF00" type="integer" groupName="configuration"
min="0" max="255">
<label>15: Switch Multilevel Set double-activation values for pushbutton 3. Byte 2</label>
<description><![CDATA[
Upper switch value<br /> <h1>Overview</h1><p>Byte 2: Upper switch value 0 –99, 255 When double pressing the pushbutton for ON, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 99)</p>
]]></description>
<default>99</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_15_4_00FF0000" type="integer" groupName="configuration"
min="0" max="99">
<label>15: Switch Multilevel Set double-activation values for pushbutton 3. Byte 3</label>
<description><![CDATA[
Lower switch value<br /> <h1>Overview</h1><p>Byte 3: Lower switch value 0 -99 When double pressing the pushbutton for OFF, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 99)</p>
]]></description>
<default>99</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_15_4_01000000" type="integer" groupName="configuration"
min="0" max="255">
<label>15: Switch Multilevel Set double-activation values for pushbutton 3. Byte 4</label>
<description><![CDATA[
Duration<br /> <h1>Overview</h1><p>Byte 4: Duration 0 -255 When double pressing the pushbutton the Switch Multilevel Set with this duration value will be send to devices in the association group. <br /></p><p>0: Use dimmer default timer value. (Default)</p><p>1 –127: Duration in seconds.</p><p>128 –255: Duration in minutes (minus 127) from 1 –128 minutes, where 128 is 1 minute.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_16_1" type="integer" groupName="configuration"
min="0" max="3">
<label>16: Pushbutton 4 functionality.</label>
<description><![CDATA[
This parameter specifies the functionality of pushbutton 4.<br /> <h1>Overview</h1><p>0 Standard toggle-function, the state is switched between on and off, dimming up and down. (Default)</p><p>1 Always turn on or dim up. Using this parameter, the pushbutton can only send ‘on’ or ‘dim up’ commands. Use this in pair with another pushbutton with value 2.</p><p>2 Always turn offor dim down. Using this parameter, the pushbutton can only send ‘of’ or ‘dim down’ commands. Use this in pair with another pushbutton with value 1.</p><p>3 When the pushbutton is down; an on command is sent, and when the pushbutton is released; an off command is sent.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_17_4_00000001" type="integer" groupName="configuration"
min="0" max="1">
<label>17: Switch multilevel set single-activation values for pushbutton 4, Byte 1</label>
<description><![CDATA[
Enable/Disable<br /> <h1>Overview</h1><p>Byte 1: Enable / Disable</p><p>0 Disabled – A single activation of the pushbutton will not send commands to devices in the association group.</p><p>1 Enabled – A single activation will send commands to devices in the association group. Devices will receive commands with the values set in 3 following bytes. (Default)</p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_17_4_0000FF00" type="integer" groupName="configuration"
min="0" max="255">
<label>17: Switch multilevel set single-activation values for pushbutton 4, Byte 2</label>
<description><![CDATA[
Upper switch value<br /> <h1>Overview</h1><p>Byte 2: Upper switch value 0 –99, 255 When single pressing the pushbutton for ON, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 255)</p>
]]></description>
<default>255</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_17_4_00FF0000" type="integer" groupName="configuration"
min="0" max="99">
<label>17: Switch multilevel set single-activation values for pushbutton 4, Byte 3</label>
<description><![CDATA[
Lower switch value<br /> <h1>Overview</h1><p>Byte 3: Lower switch value 0 -99 When single pressing the pushbutton for OFF, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 0)</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_17_4_01000000" type="integer" groupName="configuration"
min="0" max="255">
<label>17: Switch multilevel set single-activation values for pushbutton 4, Byte 4</label>
<description><![CDATA[
Duration<br /> <h1>Overview</h1><p>Byte 4: Duration 0 -255 When single pressing the pushbutton the Switch Multilevel Set with this duration value will be send to devices in the association group. <br /></p><p>0: Use dimmer default timer value. (Default)</p><p>1 –127: Duration in seconds.</p><p>128 –255: Duration in minutes (minus 127) from 1 –128 minutes, where 128 is 1 minute.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_18_4_00000001" type="integer" groupName="configuration"
min="0" max="1">
<label>18: Switch Multilevel Set double-activation values for pushbutton 4. Byte 1</label>
<description><![CDATA[
Enable/Disable<br /> <h1>Overview</h1><p>Byte 1: Enable / Disable</p><p>0 Disabled – A double activation of the pushbutton will not send commands to devices in the association group.</p><p>1 Enabled – A double activation will send commands to devices in the association group. Devices will receive commands with the values set in 3 following bytes. (Default)</p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_18_4_0000FF00" type="integer" groupName="configuration"
min="0" max="255">
<label>18: Switch Multilevel Set double-activation values for pushbutton 4. Byte 2</label>
<description><![CDATA[
Upper switch value<br /> <h1>Overview</h1><p>Byte 2: Upper switch value 0 –99, 255 When double pressing the pushbutton for ON, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 99)</p>
]]></description>
<default>99</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_18_4_00FF0000" type="integer" groupName="configuration"
min="0" max="99">
<label>18: Switch Multilevel Set double-activation values for pushbutton 4. Byte 3</label>
<description><![CDATA[
Lower switch value<br /> <h1>Overview</h1><p>Byte 3: Lower switch value 0 -99 When double pressing the pushbutton for OFF, a Switch Multilevel Set with this value will be send to devices in the association group. (Default = 99)</p>
]]></description>
<default>99</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_18_4_01000000" type="integer" groupName="configuration"
min="0" max="255">
<label>18: Switch Multilevel Set double-activation values for pushbutton 4. Byte 4</label>
<description><![CDATA[
Duration<br /> <h1>Overview</h1><p>Byte 4: Duration 0 -255 When double pressing the pushbutton the Switch Multilevel Set with this duration value will be send to devices in the association group. <br /></p><p>0: Use dimmer default timer value. (Default)</p><p>1 –127: Duration in seconds.</p><p>128 –255: Duration in minutes (minus 127) from 1 –128 minutes, where 128 is 1 minute.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Lifeline</label>
<description><![CDATA[
Sends Device Reset notifications, Battery Reports, etc.<br /> <h1>Overview</h1><p>Sends Device Reset notifications, Battery Reports, Indicator Reports, Central Scene Configuration Reports and Central Scene notifications.</p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: Button 1 Basic</label>
<description><![CDATA[
Button 1 Basic<br /> <h1>Overview</h1><p>Nodes in this group receives Basic Set when pushbutton 1 is activated, the on or off status is decided by the internal button status and is toggled between each activation.</p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_3" type="text" groupName="association" multiple="true">
<label>3: Button 1 Multilevel</label>
<description><![CDATA[
Button 1 Multilevel<br /> <h1>Overview</h1><p>Nodes in this group receives Switch Multilevel Set / Switch Multilevel Start Level Change/ Switch Multilevel Stop Level Change when pushbutton 1 is operated. It can, as an example, be used for controlling light dimmers.</p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_4" type="text" groupName="association" multiple="true">
<label>4: Button 2 Basic</label>
<description>Button 2 Basic</description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_5" type="text" groupName="association" multiple="true">
<label>5: Button 2 Multilevel</label>
<description>Button 2 Multilevel</description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_5" type="text" groupName="association" multiple="true">
<label>5: Button 4 Basic</label>
<description>Button 4 Basic</description>
<multipleLimit>8</multipleLimit>
</parameter>
<parameter name="group_6" type="text" groupName="association" multiple="true">
<label>6: Button 3 Basic</label>
<description>Button 3 Basic</description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_7" type="text" groupName="association" multiple="true">
<label>7: Button 3 Multilevel</label>
<description>Button 3 Multilevel</description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_9" type="text" groupName="association" multiple="true">
<label>9: Button 4 Multilevel</label>
<description>Button 4 Multilevel</description>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

476
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/logic/zdb5400_1_0.xml Normal file
View File

@ -0,0 +1,476 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="logic_zdb5400_01_000" listed="false">
<label>ZDB5400 MATRIX 55 Switch with Dimmer and Backlight</label>
<description><![CDATA[
MATRIX 55 Switch with Dimmer and Backlight<br /> <h1>Overview</h1><p>MATRIX type ZDB5400 is a multifunction switch that can be mounted in a modular wall-box, with built-in light dimmer and four configurable pushbuttons with RGB indicators.</p><p>The pushbuttons can control other Z-Wave devices through the wireless Z-Wave network. The pushbuttons can send ’ON’, ’OFF’ and ’DIM’ commands to the associated Z-Wave devices. These devices could be other light dimmers, blinds, sun-screens, etc.</p><p>The built-in light dimmer is per default attached to pushbutton 1. This attachment can be configured, thus it can be configured to not be controlled by any the four pushbuttons, so it can be independent of the local operation and thereby only be controllable from the Z-Wave network.</p><p>Furthermore, the pushbuttons can be configured to work together in pairs; thereby it can be possible to have one pushbutton to dim the light up, and another pushbutton to dim the light down.</p><p>MATRIX can also issue scene activation commands that can be used to activate scenes in the Z-Wave Controller.</p><p>The four RGB indicators, one for each pushbutton, can be used for different purposes, for example as orientation light, status light, different kind of indications, etc. The colour of the light and the control of it is fully controllable from the Z-Wave network.</p><p>MATRIX 55 also works as a repeater for the Z-Wave network and therefore expands the Z-Wave network coverage.</p> <br /> <h2>Inclusion Information</h2><p>MATRIX’ add function is initiated by pressing once on the switch (I) (under the pushbutton cover). The LED inside the module will start blinking. <br /></p><p>If MATRIX already belongs to a Z-Wave network, the remove process must be performed before adding it into a new network. Otherwise, the adding of the device will fail.</p><p>MATRIX 55 can be factory reset by holding the switch through the hole (I) for at least 10 seconds. <br /></p> <br /> <h2>Exclusion Information</h2><p>MATRIX’ remove function is initiated by pressing once on the switch (I) (under the pushbutton cover). The LED inside the module will start blinking.</p> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>WallSwitch</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="switch_dimmer" typeId="switch_dimmer">
<label>Dimmer</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
</properties>
</channel>
<channel id="color_color" typeId="color_color">
<label>Color Control</label>
<properties>
<property name="binding:*:HSBType">COMMAND_CLASS_SWITCH_COLOR</property>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
</properties>
</channel>
<channel id="color_temperature" typeId="color_temperature">
<label>Color Temperature</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_COLOR;colorMode=DIFF_WHITE</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
</properties>
</channel>
<channel id="scene_number" typeId="scene_number">
<label>Scene Number</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_CENTRAL_SCENE</property>
</properties>
</channel>
<channel id="switch_dimmer1" typeId="switch_dimmer">
<label>Dimmer 1</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL:1</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL:1</property>
</properties>
</channel>
<channel id="color_color1" typeId="color_color">
<label>Color Control 1</label>
<properties>
<property name="binding:*:HSBType">COMMAND_CLASS_SWITCH_COLOR:1</property>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL:1</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL:1</property>
</properties>
</channel>
<channel id="color_temperature1" typeId="color_temperature">
<label>Color Temperature 1</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_COLOR:1;colorMode=DIFF_WHITE</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL:1</property>
</properties>
</channel>
<channel id="scene_number1" typeId="scene_number">
<label>Scene Number 1</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_CENTRAL_SCENE:1</property>
</properties>
</channel>
<channel id="switch_dimmer2" typeId="switch_dimmer">
<label>Dimmer 2</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL:2</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL:2</property>
</properties>
</channel>
<channel id="color_color2" typeId="color_color">
<label>Color Control 2</label>
<properties>
<property name="binding:*:HSBType">COMMAND_CLASS_SWITCH_COLOR:2</property>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL:2</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL:2</property>
</properties>
</channel>
<channel id="color_temperature2" typeId="color_temperature">
<label>Color Temperature 2</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_COLOR:2;colorMode=DIFF_WHITE</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL:2</property>
</properties>
</channel>
<channel id="scene_number2" typeId="scene_number">
<label>Scene Number 2</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_CENTRAL_SCENE:2</property>
</properties>
</channel>
<channel id="switch_dimmer3" typeId="switch_dimmer">
<label>Dimmer 3</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL:3</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL:3</property>
</properties>
</channel>
<channel id="color_color3" typeId="color_color">
<label>Color Control 3</label>
<properties>
<property name="binding:*:HSBType">COMMAND_CLASS_SWITCH_COLOR:3</property>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL:3</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL:3</property>
</properties>
</channel>
<channel id="color_temperature3" typeId="color_temperature">
<label>Color Temperature 3</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_COLOR:3;colorMode=DIFF_WHITE</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL:3</property>
</properties>
</channel>
<channel id="scene_number3" typeId="scene_number">
<label>Scene Number 3</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_CENTRAL_SCENE:3</property>
</properties>
</channel>
<channel id="switch_dimmer4" typeId="switch_dimmer">
<label>Dimmer 4</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL:4</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL:4</property>
</properties>
</channel>
<channel id="color_color4" typeId="color_color">
<label>Color Control 4</label>
<properties>
<property name="binding:*:HSBType">COMMAND_CLASS_SWITCH_COLOR:4</property>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL:4</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL:4</property>
</properties>
</channel>
<channel id="color_temperature4" typeId="color_temperature">
<label>Color Temperature 4</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_COLOR:4;colorMode=DIFF_WHITE</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL:4</property>
</properties>
</channel>
<channel id="scene_number4" typeId="scene_number">
<label>Scene Number 4</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_CENTRAL_SCENE:4</property>
</properties>
</channel>
<channel id="switch_binary5" typeId="switch_binary">
<label>Switch 5</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY:5</property>
</properties>
</channel>
<channel id="switch_dimmer5" typeId="switch_dimmer">
<label>Dimmer 5</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL:5</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL:5</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Logic Group</property>
<property name="modelId">ZDB5400</property>
<property name="manufacturerId">0234</property>
<property name="manufacturerRef">0003:0124</property>
<property name="versionMin">1.0</property>
<property name="dbReference">1316</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_0_1" type="integer" groupName="configuration"
min="1" max="255">
<label>0: Pushbutton debounce timer</label>
<description><![CDATA[
Pushbutton input debounce time in 0.01 seconds resolution.<br /> <h1>Overview</h1><p>1-255   1 – 2.55 seconds. <br /></p><p>Default is 5, which equals to a debounce-filter on 50 milliseconds (0.05 seconds).</p>
]]></description>
<default>5</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_1_1" type="integer" groupName="configuration"
min="0" max="255">
<label>1: Operating pushbutton(s) for dimmer.</label>
<description><![CDATA[
This parameter specifies which pushbutton(s) that shall be used to control the built-in dimmer<br /> <h1>Overview</h1><p>This parameter specifies which pushbutton(s) that shall be used to control the built-in dimmer. The parameter is a bitmask, so each of the values can be added up in order to have several pushbuttons to operate the dimmer</p><p>0    No local operation of the dimmer<br />1    Pushbutton 1 controls the dimmer<br />2    Pushbutton 2 controls the dimmer<br />4    Pushbutton 3 controls the dimmer<br />8    Pushbutton 4 controls the dimmer.</p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_2_1" type="integer" groupName="configuration"
min="0" max="255">
<label>2: Duration of dimming</label>
<description><![CDATA[
This parameter specifies the duration of a full regulation of the light from 0% to 100%<br /> <h1>Overview</h1><p>A regulation of the light with 1% will take 1/100 of the specified duration. This is used when a pushbutton is held-down for controlling the dimming, and when the dimming is fulfilled from other Z-Wave devices when specifying factory default duration.</p><p>0           Immediately<br />1 - 127  Duration in seconds<br />128-255 Duration in minutes (minus 127), where 128 is 1 minute</p>
]]></description>
<default>5</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_3_1" type="integer" groupName="configuration"
min="0" max="255">
<label>3: Duration of on/off</label>
<description><![CDATA[
This parameter specifies the duration when turning the light on or off<br /> <h1>Overview</h1><p>This parameter specifies the duration when turning the light on or off</p><p>0                Immediately<br />1 - 127      Time in seconds.<br />128 - 255  Time in minutes (minus 127), where 128 is 1 minute.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_4_1" type="integer" groupName="configuration"
min="0" max="2">
<label>4: Dimmer mode</label>
<description><![CDATA[
The dimmer can work in three different modes.<br /> <h1>Overview</h1><p>The dimmer can work in three different modes: on/off, leading edge or trailing edge.</p>
]]></description>
<default>1</default>
<options>
<option value="0">No dimming</option>
<option value="1">Trailing edge dimming</option>
<option value="2">Leading edge dimming</option>
</options>
</parameter>
<parameter name="config_5_1" type="integer" groupName="configuration"
min="0" max="99">
<label>5: Dimmer minimum level</label>
<description><![CDATA[
This parameter specifies the actual level of the dimmer output when set to 0%<br /> <h1>Overview</h1><p>0 - 99 Corresponds to 0 – 99%<br /></p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_6_1" type="integer" groupName="configuration"
min="1" max="99">
<label>6: Dimmer maximum level</label>
<description><![CDATA[
This parameter specifies the actual level of the dimmer output when set to 99%<br /> <h1>Overview</h1><p>1 - 99 Corresponds to 1 – 99%<br /></p>
]]></description>
<default>99</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_7_1" type="integer" groupName="configuration">
<label>7: Central Scene notifications</label>
<description><![CDATA[
Central Scene notifications<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>1</default>
<options>
<option value="0">Notifications are disabled</option>
<option value="1">Notifications are enabled</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_8_1" type="integer" groupName="configuration">
<label>8: Double-activation functionality</label>
<description>This parameter specifies the reaction when double-activating the pushbuttons</description>
<default>1</default>
<options>
<option value="0">Double-activation disabled</option>
<option value="1">Double-activation sets light to 100%</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_10_1" type="integer" groupName="configuration">
<label>10: Enhanced LED control</label>
<description><![CDATA[
This parameter can be used for enabling the enhanced LED control<br /> <h1>Overview</h1><p>See document about MATRIX enhanced LED control</p>
]]></description>
<default>0</default>
<options>
<option value="0">Enhanced LED control is disabled</option>
<option value="1">Enhanced LED control is enabled</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_11_1" type="integer" groupName="configuration"
min="1" max="255">
<label>11: Pushbutton debounce timer</label>
<description><![CDATA[
Pushbutton input debounce time in 0.01 seconds resolution<br /> <h1>Overview</h1><p>1 - 255    1 – 2.55 seconds. <br /></p><p>Default is 5, which equals to a debounce-filter on 50 milliseconds (0.05 seconds).</p>
]]></description>
<default>5</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_12_1" type="integer" groupName="configuration"
min="1" max="255">
<label>12: Pushbutton press threshold time</label>
<description><![CDATA[
Specifies the time that a pushbutton must be activated before it is detected as pressed<br /> <h1>Overview</h1><p>1 - 255   1 – 2.55 seconds, Resolution is in 0.01 seconds</p><p>Default is 20, which equals to 200 milliseconds (0.2 seconds).</p>
]]></description>
<default>20</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_13_1" type="integer" groupName="configuration"
min="1" max="255">
<label>13: Pushbutton held threshold time</label>
<description><![CDATA[
Specifies the time that a pushbutton must have been activated before it is accepted as “held-down”<br /> <h1>Overview</h1><p>1 - 255      1 – 2.55 seconds. Resolution is 0.01 seconds</p><p>Default is 50, which equals to 500 milliseconds (0,5 seconds).</p>
]]></description>
<default>50</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_14_4" type="integer" groupName="configuration"
min="0" max="4294967295">
<label>14: Global brightness control</label>
<description><![CDATA[
This parameter specifies a common brightness for each of the three base colours for all four pushbutton indicators<br /> <h1>Overview</h1><p>Byte 1: Red brightness</p><p>0 - 255   Brightness level for the red colour in the 4 indicator groups. (Default is 255)<br /></p><p>Byte 2: Green brightness<br />0 – 255   Brightness level for the green colour in the 4 indicator groups. (Default is 255)</p><p>Byte 3: Blue brightness<br />0 - 255   Brightness level for the blue colour in the 4 indicator groups. (Default is 255)</p><p>Byte 4: Not used – must be set to 0.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_15_2" type="integer" groupName="configuration"
min="0" max="65535">
<label>15: Associations groups, transmission when included secure</label>
<description><![CDATA[
his parameter specifies if commands are transmitted as a secure message for each of the association groups<br /> <h1>Overview</h1><p>This parameter is only used when the device is included in security mode (either S0 or S2).</p><p>0 All messages in all groups are sent as insecure<br />1 Messages in association group 2 are sent as secure<br />2 Messages in association group 3 are sent as secure<br />4 Messages in association group 4 are sent as secure<br />8 Messages in association group 5 are sent as secure<br />16 Messages in association group 6 are sent as secure<br />32 Messages in association group 7 are sent as secure<br />64 Messages in association group 8 are sent as secure<br />128 Messages in association group 9 are sent as secure<br />256 Messages in association group 10 are sent as secure<br />512 Messages in association group 11 are sent as secure<br />1024 Messages in association group 12 are sent as secure<br />2048 Messages in association group 13 are sent as secure<br />4096 Messages in association group 14 are sent as secure<br />8191 Messages in all association groups are sent as secure. (Default)</p><p>NB. The above values are bitmasks and can be added up to select several options.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_16_1" type="integer" groupName="configuration">
<label>16: Pushbutton 1 functionality</label>
<description><![CDATA[
This parameter specifies the functionality of pushbutton 1<br /> <h1>Overview</h1><p>0 Standard toggle-function, the state is switched between on and off, dimming up and down.</p><p>1 Automatic turn off after the time has expired (staircase lighting function), the time is specified in the next configuration parameter.</p><p>2 Automatic turn on after the time has expired, the time is specified in the next configuration parameter.</p><p>3 Always turn off or dim down. Using this parameter, the pushbutton can only send ‘off’ or ‘dim down’ commands. Use this in pair with another pushbutton with value 4 (see chapter 5.6).</p><p>4 Always turn on or dim up. Using this parameter, the pushbutton can only send ‘on’ or ‘</p>
]]></description>
<default>0</default>
<options>
<option value="0">Standard toggle-function</option>
<option value="1">Automatic turn off</option>
<option value="2">Automatic turn on</option>
<option value="3">Always turn off or dim down</option>
<option value="4">Always turn on or dim up</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_17_1" type="integer" groupName="configuration"
min="0" max="43200">
<label>17: Timer value for pushbutton 1</label>
<description><![CDATA[
This parameter specifies the time used in parameter 16<br /> <h1>Overview</h1><p>This parameter specifies the time used in previous configuration parameter. This parameter is only applicable if previous parameter has value 1 or 2.<br /><br />Specifies the time in seconds. Default is 300 = 5 minutes.</p>
]]></description>
<default>300</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_18_4" type="integer" groupName="configuration"
min="0" max="4294967295">
<label>18: Multi-Level Switch Set values for pushbutton 1</label>
<description><![CDATA[
Multi-Level Switch Set values for pushbutton 1<br /> <h1>Overview</h1><p>Byte 1: Enable / Disable</p><p>0 Disabled – A single activation of the pushbutton will not send commands to devices in association group 4.</p><p>1 Enabled – A single activation will send commands to devices in association group 4. Devices will receive commands with the values set in Byte 2 and 3 (Default).</p><p>Byte 2: Upper switch value</p><p>0 – 99,255 When single pressing the pushbutton for ON, a Multilevel Switch Set with this value will be send to devices in association group 4. (Default = 255)</p><p>Byte 3: Lower switch value</p><p>0 - 99 When single pressing the pushbutton for OFF, a Multilevel Switch Set with this value will be send to devices in association group 4. (Default = 0)</p><p>Byte 4: Not used – must be set to 0.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_19_1" type="integer" groupName="configuration"
min="0" max="255">
<label>19: Basic Set support for pushbutton 1</label>
<description><![CDATA[
This parameter specifies how received Basic Set commands are handled<br /> <h1>Overview</h1><p>0 Basic Set only controls the pushbutton indicator LEDs, ON/OFF. (Default)</p><p>1 Basic Set controls the internal switch status and the pushbutton indicator LEDs.</p><p>2 Basic Set is handled as if the user had activated the pushbutton, including transmission of commands via the association groups.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_20_1" type="integer" groupName="configuration"
min="0" max="255">
<label>20: Pushbutton 1 LED indication.</label>
<description><![CDATA[
This parameter specifies how the LED indication is controlled<br /> <h1>Overview</h1><p>0 Internal LED control is disabled, only external commands control the indication.</p><p>1 The LED indication follows the switch status.</p><p>2 The LED indication follows the switch status – with inverted functionality.</p><p>3 Same as 1</p><p>4 Same as 2</p><p>5 The LED indication follows the status of the internal dimmer, ON or OFF.</p><p>6 The LED indication follows the status of the internal dimmer with inverted  functionality, ON or OFF.</p><p>7 The LED indicator is ON for 5 seconds when the pushbutton is activated. (Default).</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_21_1" type="integer" groupName="configuration"
min="0" max="255">
<label>21: Colour commands for pushbutton 1 LED indication</label>
<description><![CDATA[
This parameter specifies how Command Class Switch Color commands are handled<br /> <h1>Overview</h1><p>0 Direct control; the LED indication shows the received colour immediately, until the pushbutton is activated.</p><p>1 Colour command sets the colour for OFF indication. (Default).</p><p>2 Colour command sets the colour for ON indication.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_22_4" type="integer" groupName="configuration"
min="0" max="4294967295">
<label>22: ON indication RGB-saturation for pushbutton 1</label>
<description><![CDATA[
This parameter specifies the saturation levels when ON status is indicated<br /> <h1>Overview</h1><p>This parameter specifies the saturation levels for the red, green and blue LEDs, when ON status is indicated. (Default is the ON-state indicated by a 50% blue colour).</p><p>Byte 1: Colour saturation, red.<br />0 - 255 Specifies the saturation for the red LEDs. (Default is 0)</p><p>Byte 2: Colour saturation, green.<br />0 – 255 Specifies the saturation for the green LEDs. (Default is 0)</p><p>Byte 3: Colour saturation, blue.<br />0 - 255 Specifies the saturation for the blue LEDs. (Default is 127)</p><p>Byte 4: LED control.<br />0 - 255 LED indicator control; see the application note about this parameter.(Default is 0)</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_23_4" type="integer" groupName="configuration"
min="0" max="4294967295">
<label>23: OFF indication RGB-saturation for pushbutton 1</label>
<description><![CDATA[
This parameter specifies the saturation levels when OFF status is indicated<br /> <h1>Overview</h1><p>This parameter specifies the saturation levels for the red, green and blue LEDs, when OFF status is indicated. (Default is the OFF-state indicated as a low white light on 5%)</p><p>Byte 1: Colour saturation, red.<br />0 - 255  Specifies the saturation for the red LEDs. (Default is 47).</p><p>Byte 2: Colour saturation, green.<br />0 – 255  Specifies the saturation for the green LEDs. (Default is 47)</p><p>Byte 3: Colour saturation, blue.<br />0 - 255  Specifies the saturation for the blue LEDs. (Default is 47)</p><p>Byte 4: LED control.<br />0 - 255  LED indicator control; see the application note about this parameter. (Default is 0)</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Lifeline</label>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: Button 1 Basic Report</label>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_3" type="text" groupName="association" multiple="true">
<label>3: Button 1 Switch Binary Set</label>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_4" type="text" groupName="association" multiple="true">
<label>4: Button 1 Switch Multilevel</label>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

186
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/mcohome/mh3901_0_0.xml Normal file
View File

@ -0,0 +1,186 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="mcohome_mh3901_00_000" listed="false">
<label>MH3901 Boiler Thermostat</label>
<description><![CDATA[
Boiler Thermostat<br /> <h1>Overview</h1><p>MCOHome Thermostat for Water Heating is a Z-Wave enabled device for indoor temperature control.</p><ul><li> Capacitive touch buttons</li><li>Attractive appearance</li><li>Clear display, easy to operate</li></ul> <br /> <h2>Inclusion Information</h2><p>Long press on S1 + S3 </p> <br /> <h2>Exclusion Information</h2><p>Long press on S1 + S3 <br /></p> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>HVAC</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="sensor_relhumidity" typeId="sensor_relhumidity">
<label>Sensor (relative humidity)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=RELATIVE_HUMIDITY</property>
</properties>
</channel>
<channel id="sensor_temperature" typeId="sensor_temperature">
<label>Sensor (temperature)</label>
<properties>
<property name="binding:*:QuantityType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=TEMPERATURE</property>
</properties>
</channel>
<channel id="thermostat_mode" typeId="mcohome_mh3901_00_000_thermostat_mode">
<label>Thermostat mode</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_THERMOSTAT_MODE</property>
</properties>
</channel>
<channel id="thermostat_state" typeId="thermostat_state">
<label>Thermostat Operating State</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_THERMOSTAT_OPERATING_STATE</property>
</properties>
</channel>
<channel id="thermostat_setpoint_heating" typeId="thermostat_setpoint">
<label>Setpoint (heating)</label>
<properties>
<property name="binding:*:QuantityType">COMMAND_CLASS_THERMOSTAT_SETPOINT;type=HEATING</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">McoHome Technology Co., Ltd</property>
<property name="modelId">MH3901</property>
<property name="manufacturerId">015F</property>
<property name="manufacturerRef">3910:5102</property>
<property name="dbReference">1253</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_1_1" type="integer" groupName="configuration">
<label>1: Automatic Temperature Value Reporting</label>
<default>1</default>
<options>
<option value="0">Off</option>
<option value="1">Only report the difference</option>
<option value="2">Regular reporting only</option>
<option value="3">Difference reporting + interval reporting</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_2_2" type="integer" groupName="configuration"
min="3" max="995">
<label>2: Temperature Difference Setting</label>
<description>Base on 0.1 ºC unit; n*0.1 ºC=0.5 ºC</description>
<default>60</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_3_2" type="integer" groupName="configuration"
min="10" max="32767">
<label>3: Timed report intervals</label>
<description>Base on 1s unit, it suggest to be set above 30s</description>
<default>60</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_4_1" type="integer" groupName="configuration"
min="0" max="99">
<label>4: Humidity Difference Reporting</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>0x00: Disabled</p> <p>1-99: A Humidity difference value greater than this will be automatically reported to the gateway</p>
]]></description>
<default>3</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_5_1" type="integer" groupName="configuration"
min="0" max="127">
<label>5: Association 2 SET Command Retransmition times</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>0: Not resend</p> <p>1-127: Resend Times</p>
]]></description>
<default>3</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_7_1" type="integer" groupName="configuration"
min="10" max="120">
<label>7: Secret Manu P07</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>Heating period setting unit: min, range: 10-120,</p> <p>default: 20, step value: 1</p>
]]></description>
<default>20</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_8_1" type="integer" groupName="configuration"
min="10" max="120">
<label>8: Secret Menu P08</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>Heating time should be less than P07 value. </p>
]]></description>
<default>3</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_255_2" type="integer" groupName="configuration">
<label>255: Factory Reset</label>
<default>0</default>
<options>
<option value="17185">Restore default complex parameters</option>
<option value="39030">Restore factory settings</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association">
<label>1: Lifeline</label>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: Device status changes</label>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
<channel-type id="mcohome_mh3901_00_000_thermostat_mode">
<item-type>Number</item-type>
<label>Thermostat Mode</label>
<description>Sets the thermostat mode</description>
<category>Temperature</category>
<state pattern="%s">
<options>
<option value="0">Off</option>
<option value="1">Heat</option>
<option value="11">Economy Heat</option>
</options>
</state>
</channel-type>
</thing:thing-descriptions>

493
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/mcohome/mhs513_5_0.xml Normal file
View File

@ -0,0 +1,493 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="mcohome_mhs513_05_000" listed="false">
<label>MH-S513 Touch Panel Switch 3-Way</label>
<description><![CDATA[
Touch Panel Switch 3-Way<br /> <h1>Overview</h1><p>Touch Panel Switch is a wall panel built-in with Z-Wave Plus module. With its stylish design and stable performance, the panel can be used to control house-hold electrical appliances like lamp, motor, coffee machine, TV set etc. It supports basic command class, multi channel command class and multi channel association command class, also works as a repeater in a Z-Wave network.</p><p>This product can be included and operated in any Z-Wave network with other Z-Wave certified devices from any other manufacturers.<br /></p><p>Touch Panel Switch is a wall panel built-in with Z-Wave Plus module. With its stylish design and stable performance, the panel can be used to control house-hold electrical appliances like lamp, motor, coffee machine, TV set etc. It supports basic command class, multi channel command class and multi channel association command class, also works as a repeater in a Z-Wave network.</p><p>This product can be included and operated in any Z-Wave network with other Z-Wave certified devices from any other manufacturers.</p> <br /> <h2>Inclusion Information</h2><p>ADD the device into Z-Wave network:</p><p> Set controller into ADD mode. Follow instructions provided by controller manufacturer.</p><p> Press and hold any key on the panel for 8 seconds or 3 clicks in quick succession.</p><p>Note: If the ADD is successful, all INDICATION LEDs on the panel will flash 4 times.<br /></p><p>ADD the device into Z-Wave network:</p> <ol><li>Set controller into ADD mode. Follow instructions provided by controller manufacturer.</li> <li>Press and hold any key on the panel for 8 seconds or 3 clicks in quick succession.</li> </ol><p>Note: If the ADD is successful, all INDICATION LEDs on the panel will flash 4 times.</p> <br /> <h2>Exclusion Information</h2><p>REMOVE the device from Z-Wave network:</p><p> Set controller into REMOVE mode. Follow instructions provided by controller manufacturer.</p><p> Press and hold any key on the panel for 8 seconds or 3 clicks in quick succession.</p><p>Note: If the REMOVE is successful, all INDICATION LEDs on the panel will flash 4 times. The REMOVE will delete all association data.<br /></p><p>ADD the device into Z-Wave network:</p> <ol><li>Set controller into ADD mode. Follow instructions provided by controller manufacturer.</li> <li>Press and hold any key on the panel for 8 seconds or 3 clicks in quick succession.</li> </ol><p>Note: If the ADD is successful, all INDICATION LEDs on the panel will flash 4 times.</p> <br /> <h2>Wakeup Information</h2><p><br /></p><p><br /></p>
]]></description>
<category>WallSwitch</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="switch_dimmer" typeId="switch_dimmer">
<label>Dimmer</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
</properties>
</channel>
<channel id="scene_number" typeId="scene_number">
<label>Scene Number</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_CENTRAL_SCENE</property>
</properties>
</channel>
<channel id="switch_binary1" typeId="switch_binary">
<label>Switch 1</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY:1</property>
</properties>
</channel>
<channel id="switch_binary2" typeId="switch_binary">
<label>Switch 2</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY:2</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">McoHome Technology Co., Ltd</property>
<property name="modelId">MH-S513</property>
<property name="manufacturerId">015F</property>
<property name="manufacturerRef">5131:5103</property>
<property name="versionMin">5.0</property>
<property name="dbReference">1307</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_2_1" type="integer" groupName="configuration">
<label>2: Save switch state on power failure</label>
<description><![CDATA[
Save switch state on power failure<br /> <h1>Overview</h1><p>0: Switch state not saved, switch will be off when power is restored.<br />1: Switch state is saved, switch will be back to the same state when power is restored.</p>
]]></description>
<default>1</default>
<options>
<option value="0">Switch state not saved</option>
<option value="1">Switch state is saved</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_3_1" type="integer" groupName="configuration">
<label>3: ALL ON / ALL OFF</label>
<description><![CDATA[
Allow all on/off control<br /> <h1>Overview</h1><p>0: forbid ALL ON, forbid ALL OFF<br />1: forbid ALL ON, allow ALL OFF<br />2: allow ALL ON, forbid ALL OFF<br />255: allow ALL ON, allow ALL OFF</p>
]]></description>
<default>255</default>
<options>
<option value="0">Forbid All ON/OFF</option>
<option value="1">Forbid All ON. Allow ALL OFF</option>
<option value="2">Allow ALL ON. Forbid ALL OFF</option>
<option value="255">Allow ALL ON. Allow ALL OFF</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_4_1" type="integer" groupName="configuration"
min="0" max="10">
<label>4: LED backlight brightness level</label>
<description><![CDATA[
LED backlight brightness level<br /> <h1>Overview</h1><p>0: LED lighting disabled<br />1 ~ 10: Minimum to Maximum brightness<br />11 ~ 255: Same as 10 (Maximum)</p>
]]></description>
<default>10</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_5_1" type="integer" groupName="configuration">
<label>5: Switch 0 Key Mode</label>
<description><![CDATA[
Switch 0 Key Mode<br /> <h1>Overview</h1><p>0: single click to switch on/off status<br />1: Key default as off state. When it is turned on, then it will be turned off automatically after a time period, which can be set in Parameter 6<br />2: Key default as on state. When it is turned off, then it will be turned on automatically after a time period, which can be set in Parameter 6<br />3: hold &gt;3s then key is on, and off once released<br />4: single click to switch on/off status + hold &gt;3s then key is on, and off once released<br />5: Hold continuously then key is on, and off once released<br />6: When key is on, hold &gt;3s then key is off and will keep off status after released; When key is off, hold &gt;3s then key is on and will stay on status after released.</p> <p><strong>IMPORTANT NOTE: </strong>When key mode is 0x03 or 0x04, pressing for 8 seconds will NOT ADD/REMOVE from the network. You must use 3 clicks in quick succession, or change to another option if possible before removing.</p>
]]></description>
<default>0</default>
<options>
<option value="0">On/Off function</option>
<option value="1">Off Timer mode</option>
<option value="2">On Timer mode</option>
<option value="3">Delayed On momentary</option>
<option value="4">On/Off and Delayed On momentary</option>
<option value="5">Hold On momentary</option>
<option value="6">Delayed On/Off</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_6_2" type="integer" groupName="configuration"
min="0" max="65535">
<label>6: Key timer duration</label>
<description><![CDATA[
Key timer duration<br /> <h1>Overview</h1><p>0: infinite (always on, or always off, when pressed)<br />1 ~ 65535: time in seconds until returning to the default state as per Parameter 5</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_7_1" type="integer" groupName="configuration">
<label>7: External Switch Type</label>
<description><![CDATA[
External Switch Type<br /> <h1>Overview</h1><p>0: Button (Momentary buttons)<br />1: Toggle (2-state switches)</p>
]]></description>
<default>0</default>
<options>
<option value="0">Button (Momentary buttons)</option>
<option value="1">Toggle (2-state switches)</option>
</options>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_8_1" type="integer" groupName="configuration">
<label>8: Basic CC integration setting</label>
<description><![CDATA[
Basic CC integration setting<br /> <h1>Overview</h1><p>0: "Basic Set" received, key 1 responds; "Basic Get" received, key 1 sends "Basic Report"; key 1 will not send unsolicited "Basic Report"（No Endpoint）to LifeLine Association<br />1: "Basic Set" received, key 1 responds; "Basic Get" received，key 1 sends "Basic Report"; key 1 will send unsolicited "Basic Report"（No Endpoint）to LifeLine Association<br />2: "Basic Set" received, all keys respond; "Basic Get" received, not reply "Basic Report"; All keys will not send unsolicited "Basic Report"（No Endpoint）to LifeLine Association<br />3: "Basic Set" received, all keys respond; "Basic Get" received, key 1 sends "Basic Report"; All keys will not send unsolicited "Basic Report"（No Endpoint）to LifeLine Association</p> <p>This parameter works for integration with different gateways/systems. If do not know how to use, please keep as default.</p>
]]></description>
<default>0</default>
<options>
<option value="0">Key 1 No report</option>
<option value="1">Key 1 report</option>
<option value="2">All Keys no reply</option>
<option value="3">Key 1 report only</option>
</options>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_9_1" type="integer" groupName="configuration">
<label>9: External switch to control specific load</label>
<description><![CDATA[
External switch to control specific load<br /> <h1>Overview</h1><p>0: Disabled<br />1: Load 1<br />2: Load 2<br />3: Load 1 and Load 2</p> <p>Optional for MH-S511 and MH-S512</p>
]]></description>
<default>0</default>
<options>
<option value="0">Disabled</option>
<option value="1">Load 1</option>
<option value="2">Load 2</option>
<option value="3">Load 1 and Load 2</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_10_1" type="integer" groupName="configuration">
<label>10: Switch 1 Key Mode</label>
<description><![CDATA[
Switch 1 Key Mode<br /> <h1>Overview</h1><p>0: single click to switch on/off status<br />1: Key default as off state. When it is turned on, then it will be turned off automatically after a time period, which can be set in Parameter 6<br />2: Key default as on state. When it is turned off, then it will be turned on automatically after a time period, which can be set in Parameter 6<br />3: hold &gt;3s then key is on, and off once released<br />4: single click to switch on/off status + hold &gt;3s then key is on, and off once released<br />5: Hold continuously then key is on, and off once released<br />6: When key is on, hold &gt;3s then key is off and will keep off status after released; When key is off, hold &gt;3s then key is on and will stay on status after released.</p> <p><strong>IMPORTANT NOTE: </strong>When key mode is 0x03 or 0x04, pressing for 8 seconds will NOT ADD/REMOVE from the network. You must use 3 clicks in quick succession, or change to another option if possible before removing.</p>
]]></description>
<default>0</default>
<options>
<option value="0">On/Off function</option>
<option value="1">Off Timer mode</option>
<option value="2">On Timer mode</option>
<option value="3">Delayed On momentary</option>
<option value="4">On/Off and Delayed On momentary</option>
<option value="5">Hold On momentary</option>
<option value="6">Delayed On/Off</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_11_1" type="integer" groupName="configuration">
<label>11: Switch 2 Key Mode</label>
<description><![CDATA[
Switch 2 Key Mode<br /> <h1>Overview</h1><p>0: single click to switch on/off status<br />1: Key default as off state. When it is turned on, then it will be turned off automatically after a time period, which can be set in Parameter 6<br />2: Key default as on state. When it is turned off, then it will be turned on automatically after a time period, which can be set in Parameter 6<br />3: hold &gt;3s then key is on, and off once released<br />4: single click to switch on/off status + hold &gt;3s then key is on, and off once released<br />5: Hold continuously then key is on, and off once released<br />6: When key is on, hold &gt;3s then key is off and will keep off status after released; When key is off, hold &gt;3s then key is on and will stay on status after released.</p> <p><strong>IMPORTANT NOTE: </strong>When key mode is 0x03 or 0x04, pressing for 8 seconds will NOT ADD/REMOVE from the network. You must use 3 clicks in quick succession, or change to another option if possible before removing.</p>
]]></description>
<default>0</default>
<options>
<option value="0">On/Off function</option>
<option value="1">Off Timer mode</option>
<option value="2">On Timer mode</option>
<option value="3">Delayed On momentary</option>
<option value="4">On/Off and Delayed On momentary</option>
<option value="5">Hold On momentary</option>
<option value="6">Delayed On/Off</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_12_1" type="integer" groupName="configuration">
<label>12: Switch 3 Key Mode</label>
<description><![CDATA[
Switch 3 Key Mode<br /> <h1>Overview</h1><p>0: single click to switch on/off status</p><p>1: Key default as off state. When it is turned on, then it will be turned off automatically after a time period, which can be set in Parameter 6</p><p>2: Key default as on state. When it is turned off, then it will be turned on automatically after a time period, which can be set in Parameter 6<br /></p><p>3: hold &gt;3s then key is on, and off once released</p><p>4: single click to switch on/off status + hold &gt;3s then key is on, and off once released</p><p>5: Hold continuously then key is on, and off once released</p><p>6: When key is on, hold &gt;3s then key is off and will keep off status after released; When key is off, hold &gt;3s then key is on and will on status after released.</p> <p><strong>IMPORTANT NOTE: </strong>When key mode is 0x03 or 0x04, pressing for 8 seconds will NOT ADD/REMOVE from the network. You must use 3 clicks in quick succession, or change to another option if possible before removing.</p>
]]></description>
<default>0</default>
<options>
<option value="0">On/Off function</option>
<option value="1">Off Timer mode</option>
<option value="2">On Timer mode</option>
<option value="3">Delayed On momentary</option>
<option value="4">On/Off and Delayed On momentary</option>
<option value="5">Hold On momentary</option>
<option value="6">Delayed On/Off</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_14_1" type="integer" groupName="configuration"
min="0" max="3">
<label>14: Key lock local</label>
<description><![CDATA[
Key lock function (Manually)<br /> <h1>Overview</h1><p>This prevents or allows the local touch buttons to work.</p> <p>0: All keys unlocked<br />1: Key 1 locked<br />2: Key 2 locked<br />3: Keys 1 &amp; 2 locked<br />4: Key 3 locked - N/A<br />5: Keys 1 &amp; 3 locked - N/A<br />6: Keys 2 &amp; 3 locked - N/A<br />7: Keys 1 &amp; 2 &amp; 3 locked - N/A</p> <p><strong>Binary bit locations determine which keys are locked.</strong><br />BIT0: =1 Key 1 locked, operation disabled; =0 Key 1 not locked;<br />BIT1: =1 Key 2 locked, operation disabled; =0 Key 2 not locked;<br />BIT2: =1 Key 3 locked, operation disabled; =0 Key 3 not locked;<br />BIT7: Reserved</p> <p>E.g. 0x05 (00000101) From right to left Bit 0 and 2 are on so Key 1 and 3 are locked.</p> <p><strong>NOTE:</strong> Key 3 only on MH-S513.</p>
]]></description>
<default>0</default>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_15_1" type="integer" groupName="configuration"
min="0" max="3">
<label>15: Key lock remote</label>
<description><![CDATA[
Key lock function (Wirelessly)<br /> <h1>Overview</h1><p>This prevents or allows the local touch buttons to work.</p> <p>0: All keys unlocked<br />1: Key 1 locked<br />2: Key 2 locked<br />3: Keys 1 &amp; 2 locked<br />4: Key 3 locked - N/A<br />5: Keys 1 &amp; 3 locked - N/A<br />6: Keys 2 &amp; 3 locked - N/A<br />7: Keys 1 &amp; 2 &amp; 3 locked - N/A</p> <p><strong>Binary bit locations determine which keys are locked.</strong><br />BIT0: =1 Key 1 locked, operation disabled; =0 Key 1 not locked;<br />BIT1: =1 Key 2 locked, operation disabled; =0 Key 2 not locked;<br />BIT2: =1 Key 3 locked, operation disabled; =0 Key 3 not locked;<br />BIT7: Reserved</p> <p>E.g. 0x05 (00000101) From right to left Bit 0 and 2 are on so Key 1 and 3 are locked.</p> <p><strong>NOTE:</strong> Key 3 only on MH-S513.</p>
]]></description>
<default>0</default>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_16_1" type="integer" groupName="configuration"
min="0" max="3">
<label>16: Scene respond</label>
<description><![CDATA[
Scene respond<br /> <h1>Overview</h1><p>0: Scene respond disabled<br />1: Key 1 respond<br />2: Key 2 respond<br />3: Keys 1 &amp; 2 respond<br />4: Key 3 respond - N/A<br />5: Keys 1 &amp; 3 respond - N/A<br />6: Keys 2 &amp; 3 respond - N/A<br />7: Keys 1 &amp; 2 &amp; 3 respond - N/A</p> <p><strong>Binary bit locations determine which keys will respond.</strong><br />Bit0: =1 Key1 respond scene =0 Key1 not respond scene<br />Bit1: =1 Key2 respond scene =0 Key2 not respond scene<br />Bit2: =1 Key3 respond scene =0 Key3 not respond scene<br />Bit7: Reserved</p> <p>E.g. 0x05 (00000101) From right to left Bit 0 and 2 are on so Key 1 and 3 will respond.</p> <p><strong>NOTE:</strong> Key 3 only on MH-S513.</p>
]]></description>
<default>0</default>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_17_1" type="integer" groupName="configuration">
<label>17: Key 1 Scene Mode</label>
<description><![CDATA[
Key 1 Scene Activate Mode Setting<br /> <h1>Overview</h1><p>0: Scene activate function disabled<br />1: One click key1, always activate scene ID1 no matter what the status of key1 is<br />2: One click key1, only activate scene ID1 when key1's relay output is open<br />3: One click key1, only activate scene ID1 when key1's relay output is closed</p>
]]></description>
<default>0</default>
<options>
<option value="0">Scene activate function disabled</option>
<option value="1">Always Activate Scene</option>
<option value="2">Activate only when off</option>
<option value="3">Activate only when on</option>
</options>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_18_1" type="integer" groupName="configuration"
min="0" max="255">
<label>18: Key 1 Activate Scene ID</label>
<description><![CDATA[
Key 1 Activate Scene ID<br /> <h1>Overview</h1><p>0: Scene ID is invalid and will not send scene activate command (scene disabled)<br />1 ~ 255: Scene ID</p>
]]></description>
<default>0</default>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_19_1" type="integer" groupName="configuration"
min="0" max="254">
<label>19: Key 1 Activate Scene Duration</label>
<description><![CDATA[
Key 1 Activate Scene Duration<br /> <h1>Overview</h1><p>0: Instantly<br />1 ~ 127: Specify dimming duration from 1 second (0x01) to 127 seconds (0x7F) in 1-second resolution<br />128 ~ 254: Specify dimming duration from 1 minute (0x80(128)) to 127 minutes (0xFE(254)) in 1-minute resolution</p>
]]></description>
<default>0</default>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_20_1" type="integer" groupName="configuration">
<label>20: Key 2 Scene Mode</label>
<description><![CDATA[
Key 2 Scene Mode<br /> <h1>Overview</h1><p>0: Scene activate function disabled<br />1: One click key2, always activate scene ID1 no matter what the status of key2 is<br />2: One click key2, only activate scene ID1 when key2's relay output is open<br />3: One click key2, only activate scene ID1 when key2's relay output is closed</p>
]]></description>
<default>0</default>
<options>
<option value="0">Scene activate function disabled</option>
<option value="1">Always Activate Scene</option>
<option value="2">Activate only when off</option>
<option value="3">Activate only when on</option>
</options>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_21_1" type="integer" groupName="configuration"
min="0" max="255">
<label>21: Key 2 Activate Scene ID</label>
<description><![CDATA[
Key 2 Activate Scene ID<br /> <h1>Overview</h1><p>0: Scene ID is invalid and will not send scene activate command (scene disabled)<br />1 ~ 255: Scene ID</p>
]]></description>
<default>0</default>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_22_1" type="integer" groupName="configuration"
min="0" max="254">
<label>22: Key 2 Activate Scene Duration</label>
<description><![CDATA[
Key 2 Activate Scene Duration<br /> <h1>Overview</h1><p>0: Instantly<br />1 ~ 127: Specify dimming duration from 1 second (0x01) to 127 seconds (0x7F) in 1-second resolution<br />128 ~ 254: Specify dimming duration from 1 minute (0x80(128)) to 127 minutes (0xFE(254)) in 1-minute resolution</p>
]]></description>
<default>0</default>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_23_1" type="integer" groupName="configuration">
<label>23: Key 3 Scene Mode</label>
<description><![CDATA[
Key 3 Scene Mode<br /> <h1>Overview</h1><p>0: Scene activate function disabled<br /></p><p>1: One click key3, always activate scene ID1 no matter what the status of key3 is<br />2: One click key3, only activate scene ID1 when key3's relay output is open<br />3: One click key3, only activate scene ID1 when key3's relay output is closed</p>
]]></description>
<default>0</default>
<options>
<option value="0">Scene activate function disabled</option>
<option value="1">Always Activate Scene</option>
<option value="2">Activate only when off</option>
<option value="3">Activate only when on</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_24_1" type="integer" groupName="configuration"
min="0" max="255">
<label>24: Key 3 Activate Scene ID</label>
<description><![CDATA[
Key 3 Activate Scene ID<br /> <h1>Overview</h1><p>0: Scene ID is invalid and will not send scene activate command (scene disabled)<br /></p><p>1 ~ 255: Scene ID</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_25_1" type="integer" groupName="configuration"
min="0" max="254">
<label>25: Key 3 Activate Scene Duration</label>
<description><![CDATA[
Key 3 Activate Scene Duration<br /> <h1>Overview</h1><p>0: Instantly<br /></p><p>1 ~ 127: Specify dimming duration from 1 second (0x01) to 127 seconds (0x7F) in 1-second resolution<br />128 ~ 254: Specify dimming duration from 1 minute (0x80(128)) to 127 minutes (0xFE(254)) in 1-minute resolution</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_31_1" type="integer" groupName="configuration"
min="0" max="3">
<label>31: Central scene settings</label>
<description><![CDATA[
Central scene settings<br /> <h1>Overview</h1><p>This enables the central scene function for each button.</p> <p>0: All keys disabled<br />1: Key 1 enabled<br />2: Key 2 enabled<br />3: Keys 1 &amp; 2 enabled<br />4: Key 3 enabled - N/A<br />5: Keys 1 &amp; 3 enabled - N/A<br />6: Keys 2 &amp; 3 enabled - N/A<br />7: Keys 1 &amp; 2 &amp; 3 enabled - N/A</p> <p><strong>Binary bit locations determine which keys are enabled.</strong><br />BIT0: =1 Key 1 disabled; =0 Key 1 enabled;<br />BIT1: =1 Key 2 disabled; =0 Key 2 enabled;<br />BIT2: =1 Key 3 disabled; =0 Key 3 enabled;<br />BIT7: Reserved</p> <p>E.g. 0x05 (00000101) From right to left Bit 0 and 2 are on so Key 1 and 3 are enabled.</p> <p><strong>NOTE:</strong> Key 3 only on MH-S513.</p>
]]></description>
<default>0</default>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_32_1" type="integer" groupName="configuration"
min="0" max="3">
<label>32: Scene respond ID 1-50</label>
<description><![CDATA[
Scene respond ID 1-50<br /> <h1>Overview</h1><p>This enables the scene function for each button. Scene ID 1 - 50</p> <p>0: All keys disabled<br />1: Key 1 enabled<br />2: Key 2 enabled<br />3: Keys 1 &amp; 2 enabled<br />4: Key 3 enabled - N/A<br />5: Keys 1 &amp; 3 enabled - N/A<br />6: Keys 2 &amp; 3 enabled - N/A<br />7: Keys 1 &amp; 2 &amp; 3 enabled - N/A</p> <p><strong>Binary bit locations determine which keys are enabled.</strong><br />BIT0: =1 Key 1 disabled; =0 Key 1 enabled;<br />BIT1: =1 Key 2 disabled; =0 Key 2 enabled;<br />BIT2: =1 Key 3 disabled; =0 Key 3 enabled;<br />BIT7: Reserved</p> <p>E.g. 0x05 (00000101) From right to left Bit 0 and 2 are on so Key 1 and 3 are enabled.</p> <p><strong>NOTE:</strong> Key 3 only on MH-S513.</p>
]]></description>
<default>0</default>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_33_1" type="integer" groupName="configuration"
min="0" max="3">
<label>33: Scene respond ID 51-100</label>
<description><![CDATA[
Scene respond ID 51-100<br /> <h1>Overview</h1><p>This enables the scene function for each button. Scene ID 51 - 100</p> <p>0: All keys disabled<br />1: Key 1 enabled<br />2: Key 2 enabled<br />3: Keys 1 &amp; 2 enabled<br />4: Key 3 enabled - N/A<br />5: Keys 1 &amp; 3 enabled - N/A<br />6: Keys 2 &amp; 3 enabled - N/A<br />7: Keys 1 &amp; 2 &amp; 3 enabled - N/A</p> <p><strong>Binary bit locations determine which keys are enabled.</strong><br />BIT0: =1 Key 1 disabled; =0 Key 1 enabled;<br />BIT1: =1 Key 2 disabled; =0 Key 2 enabled;<br />BIT2: =1 Key 3 disabled; =0 Key 3 enabled;<br />BIT7: Reserved</p> <p>E.g. 0x05 (00000101) From right to left Bit 0 and 2 are on so Key 1 and 3 are enabled.</p> <p><strong>NOTE:</strong> Key 3 only on MH-S513.</p>
]]></description>
<default>0</default>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_34_1" type="integer" groupName="configuration"
min="0" max="3">
<label>34: Scene respond ID 101-150</label>
<description><![CDATA[
Scene respond ID 101-150<br /> <h1>Overview</h1><p>This enables the scene function for each button. Scene ID 51 - 100</p> <p>0: All keys disabled<br />1: Key 1 enabled<br />2: Key 2 enabled<br />3: Keys 1 &amp; 2 enabled<br />4: Key 3 enabled - N/A<br />5: Keys 1 &amp; 3 enabled - N/A<br />6: Keys 2 &amp; 3 enabled - N/A<br />7: Keys 1 &amp; 2 &amp; 3 enabled - N/A</p> <p><strong>Binary bit locations determine which keys are enabled.</strong><br />BIT0: =1 Key 1 disabled; =0 Key 1 enabled;<br />BIT1: =1 Key 2 disabled; =0 Key 2 enabled;<br />BIT2: =1 Key 3 disabled; =0 Key 3 enabled;<br />BIT7: Reserved</p> <p>E.g. 0x05 (00000101) From right to left Bit 0 and 2 are on so Key 1 and 3 are enabled.</p> <p><strong>NOTE:</strong> Key 3 only on MH-S513.</p>
]]></description>
<default>0</default>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_35_1" type="integer" groupName="configuration"
min="0" max="3">
<label>35: Scene respond ID 151-200</label>
<description><![CDATA[
Scene respond ID 151-200<br /> <h1>Overview</h1><p>This enables the scene function for each button. Scene ID 151 - 200</p> <p>0: All keys disabled<br />1: Key 1 enabled<br />2: Key 2 enabled<br />3: Keys 1 &amp; 2 enabled<br />4: Key 3 enabled - N/A<br />5: Keys 1 &amp; 3 enabled - N/A<br />6: Keys 2 &amp; 3 enabled - N/A<br />7: Keys 1 &amp; 2 &amp; 3 enabled - N/A</p> <p><strong>Binary bit locations determine which keys are enabled.</strong><br />BIT0: =1 Key 1 disabled; =0 Key 1 enabled;<br />BIT1: =1 Key 2 disabled; =0 Key 2 enabled;<br />BIT2: =1 Key 3 disabled; =0 Key 3 enabled;<br />BIT7: Reserved</p> <p>E.g. 0x05 (00000101) From right to left Bit 0 and 2 are on so Key 1 and 3 are enabled.</p> <p><strong>NOTE:</strong> Key 3 only on MH-S513.</p>
]]></description>
<default>0</default>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_36_1_wo" type="integer" groupName="configuration">
<label>36: Scene respond ID 201-250</label>
<description><![CDATA[
Scene respond ID 201-250<br /> <h1>Overview</h1><p>This enables the scene function for each button. Scene ID 201 - 250</p> <p>0: All keys disabled<br />1: Key 1 enabled<br />2: Key 2 enabled<br />3: Keys 1 &amp; 2 enabled<br />4: Key 3 enabled - N/A<br />5: Keys 1 &amp; 3 enabled - N/A<br />6: Keys 2 &amp; 3 enabled - N/A<br />7: Keys 1 &amp; 2 &amp; 3 enabled - N/A</p> <p><strong>Binary bit locations determine which keys are enabled.</strong><br />BIT0: =1 Key 1 disabled; =0 Key 1 enabled;<br />BIT1: =1 Key 2 disabled; =0 Key 2 enabled;<br />BIT2: =1 Key 3 disabled; =0 Key 3 enabled;<br />BIT7: Reserved</p> <p>E.g. 0x05 (00000101) From right to left Bit 0 and 2 are on so Key 1 and 3 are enabled.</p> <p><strong>NOTE:</strong> Key 3 only on MH-S513.</p>
]]></description>
<default>0</default>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_255_1_wo" type="integer" groupName="configuration">
<label>255: Factory Setting</label>
<description><![CDATA[
restore factory defaults<br /> <h1>Overview</h1><p><strong>Factory Reset.</strong></p> <p>255: Factory reset switch.</p>
]]></description>
<default>0</default>
<options>
<option value="0">Normal</option>
<option value="255">Factory Reset</option>
</options>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association">
<label>1: Lifeline</label>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: Associate with Key 1</label>
<description><![CDATA[
Associate with Key 1<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_5" type="text" groupName="association" multiple="true">
<label>5: Associate with Key 2 if any</label>
<description>Associate with Key 2 if any</description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_8" type="text" groupName="association" multiple="true">
<label>8: Associate with Key 3 if any</label>
<description>Associate with Key 3 if any</description>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

140
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/nietech/ms13z_0_0.xml Normal file
View File

@ -0,0 +1,140 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="nietech_ms13z_00_000" listed="false">
<label>MS13Z Minoston Toggle Dimmer Switch</label>
<description><![CDATA[
Minoston Toggle Dimmer Switch<br /> <h1>Overview</h1><p>Transform any home into a smart home with the Z-Wave Smart Switch. The switch enables you to wirelessly control to turn lights on and off, schedule a timed event or create a custom scene from anywhere in the world, at any time of the day. Take control of your home lighting with Z-Wave Smart Lighting Controls</p> <br /> <h2>Inclusion Information</h2><p>Make your controller/hub into the "inclusion" mode, triple press the Up/Down push button quickly to include it in the network.</p> <br /> <h2>Exclusion Information</h2><p>Make your controller/hub into the "exclusion" mode, triple press the Up/Down push button quickly to exclude it from the network.</p> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>WallSwitch</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="switch_dimmer" typeId="switch_dimmer">
<label>Dimmer</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL,COMMAND_CLASS_BASIC</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
</properties>
</channel>
<channel id="scene_number" typeId="scene_number">
<label>Scene Number</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_CENTRAL_SCENE</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">NIE Technology</property>
<property name="modelId">MS13Z</property>
<property name="manufacturerId">0312</property>
<property name="manufacturerRef">FF00:FF02</property>
<property name="dbReference">1229</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_1_1" type="integer" groupName="configuration"
min="0" max="2">
<label>1: Locally Button Function</label>
<description><![CDATA[
LED flashes 2 times when the configuration parameter changed.<br /> <h1>Overview</h1><p>Locally Button function(quickly press 7x)</p> <p>Value=0 Up Button: On/Down Button: Off(Default)<br />Value=1 Up Button: Off/Down Button: On<br />Value=2 Up Button: On/Off/Down Button: On/Off</p> <p>---Parameter 1: Choose if you want the upper paddle to turn the light on or turn the light off when tapped, or if you'd like any paddle to change the state of the light.</p> <p>Values: 0 – Upper paddle turns the light on, lower paddle turns the light off (default);</p> <p>Values: 1 – Upper paddle turns the light off, lower paddle turns the light on;</p> <p>Values: 2 – any paddle changes the state of the light.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_2_1" type="integer" groupName="configuration"
min="0" max="2">
<label>2: LED Indicator</label>
<description><![CDATA[
LED flashes 2 times<br /> <h1>Overview</h1><p>LED Indicator(quickly press 6x)</p> <p>Value=0 On when output Off and Off when output On (default)</p> <p>Value=1 On when output On and Off when output Off</p> <p>Value=2 Always Off</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_4_4" type="integer" groupName="configuration"
min="0" max="65535">
<label>4: Auto Turn-Off Timer</label>
<description><![CDATA[
Auto Turn-Off Timer<br /> <h1>Overview</h1><p>Values: 0 – 65535 (minutes); 0 (minutes) – default setting</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_6_4" type="integer" groupName="configuration"
min="0" max="65535">
<label>6: Auto Turn-On Timer</label>
<description><![CDATA[
Auto Turn-On Timer<br /> <h1>Overview</h1><p>Values: 0 – 65535 (minutes); 0 (minutes) – default setting</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_7_1" type="integer" groupName="configuration"
min="0" max="15">
<label>7: Association Setting Parameter</label>
<description><![CDATA[
Association Setting Parameter<br /> <h1>Overview</h1><ul><li>Value=00 – none</li> <li>Value=01 - local</li> <li>Value=02 - 3way</li> <li>Value=03 - 3way &amp; local</li> <li>Value=04 - z-wave hub</li> <li>Value= Value=05 - z-wave hub &amp; local</li> <li>Value=06 - z-wave hub &amp; 3-way</li> <li>Value=07 - z-wave hub &amp; local &amp; 3way</li> <li>Value=08 - timer</li> <li>Value=09 - timer &amp; local</li> <li>Value=10 - timer &amp; 3-way</li> <li>Value=11 - timer &amp; 3-way &amp; local</li> <li>Value=12 - timer &amp; z-wave hub</li> <li>Value=13 - timer &amp; z-wave hub &amp; local</li> <li>Value=14 - timer &amp; z-wave hub &amp; 3-way</li> <li>Value=15 - all</li> </ul>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_8_1" type="integer" groupName="configuration"
min="0" max="2">
<label>8: Restores state after power failure</label>
<description><![CDATA[
Restores state after power failure<br /> <h1>Overview</h1><p>Value=0 output off<br />Value=1 output on<br />Value=2 output the state after power</p>
]]></description>
<default>2</default>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association">
<label>1: Lifeline</label>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: Send Basic Set ON / Off</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

145
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/philio/pab04_0_0.xml Normal file
View File

@ -0,0 +1,145 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="philio_pab04_00_000" listed="false">
<label>PAB04 Smart Energy Flow Meter</label>
<description><![CDATA[
Smart Energy Flow Meter<br /> <h1>Overview</h1><p>This valves controller PAB04 is a security enabled wireless switch, based on Z-Wave Plus technology. <br /></p><p>Connect PAB04 with an external water meter which can output pulse signals. PAB04 is able to detect instance water flow and the accumulated water.<br /></p> <br /> <h2>Inclusion Information</h2><p>Pressing On/Off button three times within 2 seconds will enter inclusion mode.<br /></p> <br /> <h2>Exclusion Information</h2><p>Pressing On/Off button three times within 2 seconds will enter exclusion mode.<br /></p> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>Valve</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="switch_binary" typeId="switch_binary">
<label>Switch</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY</property>
</properties>
</channel>
<channel id="water_flow" typeId="water_flow">
<label>Sensor (WATER_FLOW)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=WATER_FLOW</property>
</properties>
</channel>
<channel id="meter_water_gallons" typeId="meter_water_gallons">
<label>Water meter (gal)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;type=W_Gallons</property>
</properties>
</channel>
<channel id="meter_water_cubic_meters" typeId="meter_water_cubic_meters">
<label>Water meter (m3)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;type=W_Cubic_Meters</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Philio Technology Corp</property>
<property name="modelId">PAB04</property>
<property name="manufacturerId">013C</property>
<property name="manufacturerRef">0001:0076</property>
<property name="dbReference">1224</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_1_1" type="integer" groupName="configuration"
min="1" max="2">
<label>1: Unit of Water Flow</label>
<description>Unit of Water Flow</description>
<default>2</default>
<options>
<option value="1">US Gallon</option>
<option value="2">KL</option>
</options>
</parameter>
<parameter name="config_2_1" type="integer" groupName="configuration"
min="0" max="1">
<label>2: Accumulated Water Report</label>
<description>Accumulated Water Report</description>
<default>1</default>
<options>
<option value="0">Disable Report</option>
<option value="1">Enable Report</option>
</options>
</parameter>
<parameter name="config_3_1" type="integer" groupName="configuration">
<label>3: Instant Water Flow Percent Reported</label>
<description>Instant Water Flow Percent Reported</description>
<default>10</default>
<options>
<option value="0">Disabled</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_4_2" type="integer" groupName="configuration"
min="1" max="32676">
<label>4: Pulses per Liter</label>
<description>Pulses per Liter</description>
<default>450</default>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_5_1" type="integer" groupName="configuration"
min="0" max="1">
<label>5: Relay Control Mode</label>
<description>Relay Control Mode</description>
<default>0</default>
<options>
<option value="0">Normally Closed</option>
<option value="1">Normally Open</option>
</options>
</parameter>
<parameter name="config_6_2" type="integer" groupName="configuration">
<label>6: Periodic Auto Report Timer</label>
<description>Periodic Auto Report Timer</description>
<default>60</default>
<options>
<option value="0">Disabled</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association">
<label>1: Lifeline</label>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

124
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/philio/psm09_0_0.xml Normal file
View File

@ -0,0 +1,124 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="philio_psm09_00_000" listed="false">
<label>PSM09 Recessed Door Sensor + Door lock Sensor</label>
<description><![CDATA[
Recessed Door Sensor + Door lock Sensor<br /> <h1>Overview</h1><p>The PSM09 can detect the the door is open or not, and lock or unlock. The Recessed door sensor PSM09 is Base on Z-WaveTM technology. It is the Z-WaveTM plus product, it support the security, OTA... Those newest features of the Z-WaveTM technology. Z-WaveTM is a wireless communication protocol designed for home automation, specifically to remotely control applications in residential and light commercial environments. The technology uses a low-power RF radio embedded or retrofitted into home electronics devices and systems, such as lighting, home access control, entertainment systems and household appliances</p> <br /> <h2>Inclusion Information</h2><p>Have Z-WaveTM Controller entered inclusion mode. Pressing tamper key three times within 3 seconds to enter the inclusion mode. If the learning code is successful, the LED will flash slowly.</p> <br /> <h2>Exclusion Information</h2><p>Have Z-WaveTM Controller entered exclusion mode. Pressing tamper key three times within 3 seconds to enter the exclusion mode. If the removal is successful, the code light will flash for 30 seconds. Node ID has been excluded.</p> <br /> <h2>Wakeup Information</h2><p>If the user want to wake-up the device immediately, please press the tamper key once. The device will wake-up 10 seconds.<br /></p>
]]></description>
<category>Sensor</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="alarm_access" typeId="alarm_access">
<label>Alarm (access)</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=ACCESS_CONTROL</property>
</properties>
</channel>
<channel id="battery-level" typeId="system.battery-level">
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_BATTERY</property>
</properties>
</channel>
<channel id="battery-level" typeId="system.battery-level">
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_BATTERY</property>
</properties>
</channel>
<channel id="battery-level" typeId="system.battery-level">
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_BATTERY</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Philio Technology Corp</property>
<property name="modelId">PSM09</property>
<property name="manufacturerId">013C</property>
<property name="manufacturerRef">0002:006A</property>
<property name="dbReference">1225</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_1_1" type="integer" groupName="configuration"
min="0" max="127">
<label>1: Auto report state time</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>The interval time for auto report the door/window &amp; Lock state &amp; battery level. 0 means turn off auto report state. Units of 30 minutes.</p>
]]></description>
<default>12</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_2_1" type="integer" groupName="configuration"
min="0" max="1">
<label>2: Door lock detect function switch</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>0 means turn off Door lock detect funtion.</p> <p>1 means turn on Door lock detect funtion.</p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_3_1" type="integer" groupName="configuration"
min="1" max="127">
<label>3: Door lock detect timer</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>Units of 20 seconds.</p>
]]></description>
<default>3</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_4_1" type="integer" groupName="configuration"
min="1" max="10">
<label>4: Door lock detect level</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>When an error condition occurs in the door lock detection.</p> <p>Can reduce its level to avoid door lock detection errors.</p>
]]></description>
<default>10</default>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Lifeline</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

12
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/qubino/zmnhxd_0_0.xml
View File

@ -178,8 +178,7 @@ Available configuration parameters for input switch I1<br /> <h1>Overview</h1><u
<advanced>true</advanced>
</parameter>
<parameter name="config_40_1" type="integer" groupName="configuration"
min="0" max="100">
<parameter name="config_40_1" type="integer" groupName="configuration">
<label>40: Reporting on power change</label>
<description><![CDATA[
This parameter is valid for Active Powers Total, Phase1, Phase2 and Phase3.<br /> <h1>Overview</h1><p>Available configuration parameters (data type is 1 Byte DEC)</p> <ul><li>Default value 50</li> <li>0 – reporting disabled</li> <li>1-100 = 1% - 100% reporting enabled. Power report is send only when actual power in Watts (in real time changes for more than set percentage comparing to previous Active Power, step is 1%.</li> </ul><p><strong>NOTE:</strong> if power change is less than 5 W, the report is not send (pushed).<br /><strong>NOTE:</strong> Device is measuring also some disturbances even if on the output is no load. To avoid disturbances:</p> <ul><li>If measured Active Power (W) is below e.g. 5W-&gt; the reported value in this case is 0W</li> </ul>
@ -189,10 +188,10 @@ This parameter is valid for Active Powers Total, Phase1, Phase2 and Phase3.<br /
<option value="0">reporting disabled</option>
</options>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_42_2" type="integer" groupName="configuration"
min="600" max="65535">
<parameter name="config_42_2" type="integer" groupName="configuration">
<label>42: Reporting on time interval</label>
<description><![CDATA[
Energy report time intervals<br /> <h1>Overview</h1><p>This parameter is currently valid only for Active Energy Total Import/Export (kWh), Reactive<br />Energy Total (kvarh), Total Energy (kVAh)</p> <p><strong>Available configuration parameters (data type is 2 Byte DEC)</strong></p> <ul><li>Default value 600 (600 seconds - 10 minutes)</li> <li>0 – reporting disabled</li> <li>600-65536 = 600 (600 seconds – 65536 seconds). Reporting enabled. Report is send with the time interval set by entered value.</li> </ul><p><strong>Note:</strong> Device is reporting only if there was a change of 0.1 in Energy</p> <p><strong>Note:</strong> In the future will be possible to measure and report also Active Energy on PH1, PH2 and PH3.</p>
@ -202,10 +201,10 @@ Energy report time intervals<br /> <h1>Overview</h1><p>This parameter is current
<option value="0">reporting disabled</option>
</options>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_43_2" type="integer" groupName="configuration"
min="600" max="65535">
<parameter name="config_43_2" type="integer" groupName="configuration">
<label>43: Other Values - Reporting on time interval</label>
<description><![CDATA[
Energy reports for Voltage, Current, Total Power Factor, Total Reactive Power<br /> <h1>Overview</h1><p><strong>Available configuration parameters (data type is 2 Byte DEC)</strong></p> <ul><li>Default value 600 (600 seconds - 10 minutes)</li> <li>0 – reporting disabled</li> <li>600-65536 = 600 (600 seconds – 65536 seconds). Reporting enabled. Report is sent with the time interval set by entered value.</li> <li>Note: Device is reporting only if there was a change</li> </ul>
@ -215,6 +214,7 @@ Energy reports for Voltage, Current, Total Power Factor, Total Reactive Power<br
<option value="0">reporting disabled</option>
</options>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_100_1" type="integer" groupName="configuration">

70
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/sunricher/ZV9001K4RGBW_0_0.xml Normal file
View File

@ -0,0 +1,70 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="sunricher_ZV9001K4RGBW_00_000" listed="false">
<label>ZV9001K4-RGBW Z-Wave RGBW Remote Control</label>
<description><![CDATA[
Z-Wave RGBW Remote Control<br /> <h1>Overview</h1><p>The remote control is a Z-Wave device that can both control other Z-Wave devices and activate scenes in Gateways. Although it is controlling other devices, the device cannot act as Z-Wave network controller (primary or secondary) and will always need a Z-Wave network controller to be included into a Z-Wave network. It also supports the Over The Air (OTA) feature for the product’s firmware upgrade. The remote control has following functions: 1. Control of groups of other Z-Wave devices using 'ON', 'OFF', Dim and RGB color control commands. 2. Activation of scenes in Gateway mode. The encryption modes that the remote control supports are S0, S2 Authenticated, S2 Unauthenticated. When the remote control is being included into a Z-Wave network, you can use your primary controller/gateway to enable one encryption mode or disable encryption. (The primary controller/gateway shall support encryption mode configuration). </p> <br /> <h2>Inclusion Information</h2><p>Step 1. Make sure the remote control does not belong to any Z-Wave network, short press any button, if LED indicator does not turn on, the remote control does not belong to any network, then continue step 2,if LED indicator turns on, it means the remote control has already been included to a network, please first set the remote control to exclusion mode (refer to the part "Exclusion" of this manual),then continue step 2. Step 2. Set primary controller/gateway into inclusion mode (Please refer to your primary controllers manual on how to turn your controller into inclusion). Step 3. Press and hold down both buttons and of Group 2 over 3 seconds, LED indicator turns on, the remote control will be set to inclusion mode, and waiting to be included, after 10s LED indicator blinks 6 times quickly to indicate successful inclusion. The remote control is a sleepy device, after inclusion it will not enter into sleepy mode immediately, and will continue activation status for 30s and wait data interaction from the gateway, the LED indicator will stay solid on, please be patient to wait LED indicator to turn off.</p> <br /> <h2>Exclusion Information</h2><p>There are two exclusion methods: Method 1: Exclusion from the primary controller/gateway as follows: 1. Set the primary controller/gateway into exclusion mode (Please refer to your primary controllers manual on how to set your controller into exclusion). 2. Press and hold down both buttons and of Group 2 over 3 seconds, LED indicator turns on, the remote control will be set to exclusion mode, and waiting to be excluded, after 7s LED indicator blinks 4 times quickly to indicate successful exclusion. Z-Wave RGBW Remote Control Front side 55.57 mm 71.20 mm 11 mm Back side Battery: CR2450 Before the first use, please remove the protective film 55.57 mm 71.20 mm The remote control can be fixed on the wall with 3M glue or screw. Group 2: click to turn on/off Group 2: press and hold down to increase/decrease light intensity Group 2: click to turn on/off white channel Group 2: click to get R, G, B colors one by one, press and hold down to cycle RGB colors Press and hold down both keys together for 3s to be added to or removed from Z-Wave network by Z-Wave master (primary) controller. Product Data Z-Wave Frequency Power Supply Operating temperature Relative humidity Dimensions Waterproof Grade 868.42MHz 3VDC(1xCR2450 battery) 0 to 40°C 8% to 80% 71.2x71.2x13.6mm IP20 Method 2: Factory reset the remote control will force the remote control to be excluded from a network. (please refer to the part “Factory Reset” of this manual) Note: Factory reset is not recommended for exclusion, please use this procedure only if the primary controller/gateway is missing or otherwise inoperable</p> <br /> <h2>Wakeup Information</h2><p>The remote control is under sleepy mode for most of the time to save battery power. It can not receive wireless command under sleepy mode. Before the gateway interacts data with the remote, the remote control shall be activated manually first. Short press any button to activate the remote control for 3s, and press and hold down and buttons of Group 2 together over 1 second to activate the remote control for 7s. </p>
]]></description>
<category>WallSwitch</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="battery-level" typeId="system.battery-level">
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_BATTERY</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Sunricher</property>
<property name="modelId">ZV9001K4-RGBW</property>
<property name="manufacturerId">0330</property>
<property name="manufacturerRef">0003:A30C</property>
<property name="dbReference">1285</property>
<property name="defaultAssociations">1,2</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Group 1</label>
<description><![CDATA[
Lifeline<br /> <h1>Overview</h1><p>1. Send Command Class "Device Reset Locally Notification V1" to associated devices of this group to report factory reset information when factory reset the remote control. 2. When remote control battery power value changes, send Command Class "Battery Report V1" to associated devices of this group to report power value information. 3. Short press or press and hold down any button to send scene activation command to the associated devices of this group using Command Class “Central Scene Notification V3” </p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: Group 2</label>
<description><![CDATA[
Launch 1<br /> <h1>Overview</h1><p>• devices of this group using Command Class "Basic Set V2". • Press and hold down button to send light intensity increase/decrease command to associated devices of this group using Command Class "Multilevel V4". • Short press W/ button of Group 2, turn on/off white/RGB channel of associated devices of this group using Command Class “Color Switch Set”. • Press and hold down W/ button of Group 2, adjust intensity of white/RGB channel of associated devices of this group using Command Class “Color Switch Start Level Change”. Short press button to send ON/OFF command to associated</p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

98
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/thermofloor/pushbutton4_0_0.xml Normal file
View File

@ -0,0 +1,98 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="thermofloor_pushbutton4_00_000" listed="false">
<label>Heatit Z-Push Button 4 Wall Mounted Switch</label>
<description><![CDATA[
Wall Mounted Switch<br /> <h1>Overview</h1><p>Heatit Z-Push Button 4 is a battery operated wall switch with 4 push buttons. The switch enables you to control the Z-Wave- products in your smart home system. Managing your Z-Wave products becomes easy and practical. The switch can be set up to control scenarios or work in associations with other Z-Wave products.</p> <p>Heatit Z-Push Button 4 can control up to 2 seperate association groups with up to 10 products or up to 8 scenarios through your gateway.</p> <p><strong>Functions:</strong></p> <ul><li>Battery operated wall switch</li> <li>Fits Gira System 55, Elko RS-16 and Schneider Exxact</li> <li>Controls 4 separate groups and up to 20 units</li> <li>Controls up to 16 scenarios via your gateway</li> <li>LED-diode</li> <li>Easy to install with screws or double-sided tape</li> <li>Supports encryption modes S0, S2 Authenticated Class, S2 Unauthenticated Class</li> </ul> <br /> <h2>Inclusion Information</h2><p><strong>Step 1.</strong> Make sure the remote control does not belong to any Z-Wave network, short press on any button, if LED indicator does not turn on, the remote control does not belong to any network, then continue to step 2, if LED indicator turns on, it means the remote control has already been added to a network, please first set the remote control to removing mode (see exclusion information), then continue to step 2.</p> <p><strong>Step 2.</strong> Set primary controller/gateway into adding mode.</p> <p><strong>Step 3.</strong> Press and hold down both buttons I and O of Group 2 our 3 seconds, LED indicator, the remote control will be set to adding mode, and waiting to be added, after 10s LED indicator blinks 6 times quickly to indicate successful adding.</p> <br /> <h2>Exclusion Information</h2><p>There are two removing methods.</p> <p><strong>Method 1: </strong>Removing from the primary controller/gateway as follows:</p> <ol><li>Set the primary controller/gateway into removing mode.</li> <li>Press and hold down both buttons I and O of Group 2 over 3 seconds, LED indicator turns on, the remote control will be set to removing mode, and waiting to be removed, after 7s LED indicator blinks 4 times quickly to indicate successful removing.</li> </ol><p><strong>Method 2: </strong>Factory reset the remote control will force the remote control to be removed from a network.</p> <p>A factory reset is done by press and holding down buttons I and O of Group 2 together for over 10 seconds, LED indicator turns on and then blinks 4 times quickly to indicate successful factory reset.</p> <p><em>Note: Factory reset is not recommended for removing, please use this procedure only if the primary controller/gateway is missing or otherwise inoperable.</em></p> <br /> <h2>Wakeup Information</h2><p>The remote control is under sleepy mode for most of the time to save battery power. It can not receive wireless commands under sleepy mode. Before the gateway interacts data with the remote, the remote control shall be activated manually first. Short press any button to activate the remote control for 3s, and press and hold down <strong>I</strong> and <strong>O</strong> buttons of the Group 2 together over 1 second to activate the remote control for 7s.</p>
]]></description>
<category>WallSwitch</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="scene_number" typeId="scene_number">
<label>Scene Number</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_CENTRAL_SCENE</property>
</properties>
</channel>
<channel id="battery-level" typeId="system.battery-level">
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_BATTERY</property>
</properties>
</channel>
<channel id="switch_dimmer1" typeId="switch_dimmer">
<label>Dimmer [Deprecated]</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL:1,COMMAND_CLASS_BASIC:1</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL:1</property>
</properties>
</channel>
<channel id="switch_dimmer2" typeId="switch_dimmer">
<label>Dimmer [Deprecated]</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL:2,COMMAND_CLASS_BASIC:2</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL:2</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">ThermoFloor</property>
<property name="modelId">Heatit Z-Push Button 4</property>
<property name="manufacturerId">019B</property>
<property name="manufacturerRef">0300:A306</property>
<property name="dbReference">1162</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Lifeline</label>
<description><![CDATA[
<br /> <h1>Overview</h1><ol> <li>Send Command Class "Device Reset Locally Notification V1" to associated devices of the group to report factory reset information when factory reset the remote control.</li> <li>When remote control battery power value changes, send Command Class "Battery Report V1" to associated devices of this group to report power value information.</li> <li>Short press or press and hold any button to send scene activation command to the associated devices of this group using Command Class "Central Scene Notification V3".</li> </ol>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: Launch 1</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>Short press I/O button of Group 2 to send ON/OFF command to associated devices of the group using Command Class "Basic Set V2".</p> <p>Press and hold down I/O button Group 2 to send light intensity increase/decrease command to associated devices of this group using Command Class "Multilevel V4"</p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_3" type="text" groupName="association" multiple="true">
<label>3: Launch 2</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>Short press I/O button of Group 3 to send ON/OFF command to associated devices of the group using Command Class "Basic Set V2".</p> <p>Press and hold down I/O button Group 3 to send light intensity increase/decrease command to associated devices of this group using Command Class "Multilevel V4"</p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

15
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/zooz/zse29_2_0.xml
View File

@ -78,9 +78,11 @@ Outdoor Motion Sensor v2<br /> <h1>Overview</h1><p>OUTDOOR SENSOR: Introducing t
Basic Set Report Value Sent to Associated Devices<br /> <h1>Overview</h1><p>Set the value of basic set report sent to the light associated with the sensor in Group 2 (so the light turns on to the selected brightness level). 99 is the equivalent of full brightness in Z-Wave terms.</p>
]]></description>
<default>99</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_2_1" type="integer" groupName="configuration">
<parameter name="config_2_1" type="integer" groupName="configuration"
min="0" max="1">
<label>2: Enable / Disable Motion Reports</label>
<description><![CDATA[
Enable / Disable Motion Reports<br /> <h1>Overview</h1><p>Enable or disable motion reports completely. If motion sensor is disabled, the device will not report motion at all to your hub.</p>
@ -90,7 +92,6 @@ Enable / Disable Motion Reports<br /> <h1>Overview</h1><p>Enable or disable moti
<option value="0">Motion reports disabled</option>
<option value="1">Motion reports enabled (default)</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_3_1" type="integer" groupName="configuration"
@ -100,10 +101,10 @@ Enable / Disable Motion Reports<br /> <h1>Overview</h1><p>Enable or disable moti
Motion sensitivity<br /> <h1>Overview</h1><p>Adjust motion sensitivity where 10 is the most sensitive setting. The default sensitivity is 1.</p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_4_2" type="integer" groupName="configuration"
min="10" max="900">
<parameter name="config_4_2" type="integer" groupName="configuration">
<label>4: Lux level trigger</label>
<description><![CDATA[
Lux level trigger<br /> <h1>Overview</h1><p>Set lux level trigger with 10 being the lowest reported value and 900 being the highest reported value. The sensor will report motion to the hub and associated devices only if the brightness (lux) level is below the set trigger value.</p> <p>0 - set manually by lux knob (default)</p> <p>1 - ignore lux readings and always report motion</p> <p>10-900 - set custom trigger</p>
@ -113,10 +114,10 @@ Lux level trigger<br /> <h1>Overview</h1><p>Set lux level trigger with 10 being
<option value="0">Set manually by lux knob</option>
<option value="1">Ignore lux readings and always report motion</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_5_2" type="integer" groupName="configuration"
min="0" max="720">
<parameter name="config_5_2" type="integer" groupName="configuration">
<label>5: Motion re-trigger time</label>
<description><![CDATA[
Motion re-trigger time<br /> <h1>Overview</h1><p>Set motion re-trigger time for the delay before the sensor reports no motion to the hub and associated devices after detecting the last motion activity.</p> <p>0 - set manually by timer knob (default)</p> <p>5-720 (seconds) - set custom re-trigger time</p>
@ -125,6 +126,7 @@ Motion re-trigger time<br /> <h1>Overview</h1><p>Set motion re-trigger time for
<options>
<option value="0">Set manually by timer knob</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_6_2" type="integer" groupName="configuration"
@ -134,6 +136,7 @@ Motion re-trigger time<br /> <h1>Overview</h1><p>Set motion re-trigger time for
Lux reporting frequency<br /> <h1>Overview</h1><p>Set lux reporting frequency to decide how often in minutes the sensor will measure and send brightness level data to the hub and associated devices. The default is 30 minutes and the range is 1-1440. Note: Frequent reports will affect battery life.</p>
]]></description>
<default>30</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_7_2" type="integer" groupName="configuration" readOnly="true"

113
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/zwaveme/zmetio3s_0_0.xml Normal file
View File

@ -0,0 +1,113 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="zwaveme_zmetio3s_00_000" listed="false">
<label>ZME_TIO_3S TION 3S Ventilator</label>
<description><![CDATA[
TION 3S Ventilator<br /> <h1>Overview</h1><p><br /></p> <br /> <h2>Inclusion Information</h2><p>Press the power button  5 sec until it blinks blue </p> <br /> <h2>Exclusion Information</h2><p>Press the power button 5 sec until it blinks blue <br /></p> <br /> <h2>Wakeup Information</h2><p>N/A</p>
]]></description>
<category>HVAC</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="switch_binary" typeId="switch_binary">
<label>Power switch</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY</property>
</properties>
</channel>
<channel id="sensor_temperature" typeId="sensor_temperature">
<label>Sensor (air temperature)</label>
<properties>
<property name="binding:*:QuantityType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=TEMPERATURE</property>
</properties>
</channel>
<channel id="thermostat_mode" typeId="zwaveme_zmetio3s_00_000_thermostat_mode">
<label>Thermostat mode</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_THERMOSTAT_MODE</property>
</properties>
</channel>
<channel id="thermostat_setpoint_heating" typeId="thermostat_setpoint">
<label>Setpoint (heating)</label>
<properties>
<property name="binding:*:QuantityType">COMMAND_CLASS_THERMOSTAT_SETPOINT;type=HEATING</property>
</properties>
</channel>
<channel id="switch_binary1" typeId="switch_binary">
<label>Power switch 2</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY:1</property>
</properties>
</channel>
<channel id="switch_binary2" typeId="switch_binary">
<label>AirType</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY:2</property>
</properties>
</channel>
<channel id="switch_dimmer3" typeId="switch_dimmer">
<label>FanSpeed</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL:3</property>
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL:3</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Z-Wave.Me</property>
<property name="modelId">ZME_TIO_3S</property>
<property name="manufacturerId">0115</property>
<property name="manufacturerRef">0100:0900</property>
<property name="dbReference">1312</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: general</label>
<description><![CDATA[
main group<br /> <h1>Overview</h1><p>main group up to 8 nodes<br /></p>
]]></description>
<multipleLimit>8</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
<channel-type id="zwaveme_zmetio3s_00_000_thermostat_mode">
<item-type>Number</item-type>
<label>Thermostat Mode</label>
<description>Sets the thermostat mode</description>
<category>Temperature</category>
<state pattern="%s">
<options>
<option value="0">Off</option>
<option value="1">Heat</option>
</options>
</state>
</channel-type>
</thing:thing-descriptions>

33
installation/openhabian.md
View File

@ -30,7 +30,7 @@ To that end, the project provides two things:
The following features are provided by the openHABian image out of the box:
- Hassle-free setup without a display or keyboard, connected via Ethernet or [WiFi](#wifi-based-setup-notes)
- the latest stable version of openHAB 2
- the latest stable version of openHAB
- Zulu Embedded OpenJDK Java 8, 11 or AdoptOpenJDK
- [openHABian Configuration Tool](#openhabian-configuration-tool) including updater functionality
- web based openHAB Log Viewer (based on [frontail](https://github.com/mthenw/frontail))
@ -81,7 +81,7 @@ openHABian is designed as a headless system, you will not need a display or a ke
- Enjoy!
- The device will be accessible by its IP or via the local DNS name `openhabiandevice` (or whatever you changed 'hostname' in `openhabian.conf` to)
- [Connect to the openHAB 2 dashboard](https://www.openhab.org/docs/configuration/packages.html): [http://openhabiandevice:8080](http://openhabiandevice:8080)
- Connect to the openHAB UI at [http://openhabiandevice:8080](http://openhabiandevice:8080)
- [Connect to the Samba network shares](https://www.openhab.org/docs/installation/linux.html#mounting-locally) with username `openhabian` and password `openhabian`
- Connect to the openHAB Log Viewer (frontail): [http://openhabiandevice:9001](http://openhabiandevice:9001)
- If you encounter any setup problem, [please continue here](#successful)
@ -120,7 +120,7 @@ apt-get update
apt-get install git
# download, link and create config file
git clone -b stable https://github.com/openhab/openhabian.git /opt/openhabian
git clone -b openHAB3 https://github.com/openhab/openhabian.git /opt/openhabian
ln -s /opt/openhabian/openhabian-setup.sh /usr/local/bin/openhabian-config
cp /opt/openhabian/openhabian.conf.dist /etc/openhabian.conf
```
@ -179,25 +179,25 @@ Regardless of if you want to copy some files or are on the search for a solution
Take a few minutes to study the above Tutorials and get to know the most basic commands and tools to be able to navigate on your Linux system, edit configurations, check the system state or look at log files.
It's not complicated and something that doesn't hurt on one's résumé.
### First Steps with openHAB
### First steps with openHAB
After your first setup of openHABian is successful and you are able to access the openHAB dashboard, you should dig into the possibilites.
Install [Bindings](https://www.openhab.org/addons/), discover your devices, and [configure your smart home](https://www.openhab.org/docs/configuration/).
You might want to start defining [Items](https://www.openhab.org/docs/configuration/items.html), [Sitemap](https://www.openhab.org/docs/configuration/sitemaps.html) and [HABPanel](https://www.openhab.org/docs/configuration/habpanel.html) dashboard for your home, but these are just some first hints.
Be sure to read up on the [Configuration](https://www.openhab.org/docs/configuration/) section of the documentation pages to learn more.
### Further Configuration Steps
### Further configuration steps
openHABian is supposed to provide a ready-to-use openHAB base system.
There are a few things, however, we need you to decide and act on right now at the beginning:
- **Delayed Rules Loading** openHAB startup times can be annoyingly long. There's an optimization available that *delays* loading the rules. It quickly renames rules forth and back after 2 minutes, *effectively speeding up* openHAB startup. This is setup by default, you can disable this via \[menu option: 44\].
- **Time Zone:** The time zone of your openHABian system will be determined based on your internet connection. In some cases you might have to adjust that setting.
- **Delayed Rules loading** openHAB startup times can be annoyingly long. There's an optimization available that *delays* loading the rules. It quickly renames rules forth and back after 2 minutes, *effectively speeding up* openHAB startup. This is setup by default, you can disable this via \[menu option: 44\].
- **Timezone:** The time zone of your openHABian system will be determined based on your internet connection. In some cases you might have to adjust that setting.
- **Language:** The `locale` setting of the openHABian base system is set to "en_US.UTF-8". While this setting will not do any harm, you might prefer e.g. console errors in German or Spanish. Change the locale settings accordingly. Be aware, that error solving might be easier when using the English error messages as search phrases.
- **Passwords:** Relying on default passwords is a security concern you should care about! The openHABian system is preconfigured with a few passwords you should change to ensure the security of your system. This is especially important if your system is accessible from outside your private subnet.
All of these settings **can easily be changed** via the openHABian Configuration Tool.
All of these settings can be changed via the openHABian configuration tool.
Here are the passwords in question with their respective default "username:password" values.
All password can be changed from openHABian menu.
They can be changed from openHABian menu.
### Passwords
- User password needed for SSH or sudo (e.g. "openhabian:openhabian")
@ -223,7 +223,8 @@ Standard openHABian install enables ZRAM by default (#1). Once you attach a *saf
Finally, we strongly suggest you install Amanda (#4) right after you finish your setup. Amanda is to take care to backup the whole system to be able to quickly restore it when in need.
This is not done by default because it requires a number of user inputs, but you should not skip it for your own safety !
Delayed rules load will also be enabled by default. This is renaming the rules files, then after 2 minutes it renames them back. You can toggle to use this feature in menu option 44.
`Delayed rules load` will be enabled by default in openHAB 2 but disabled in openHAB 3 (which has a new startlevel system).
This function will rename the rules files so they get ignored by the starting openHAB instance, then after 2 minutes they're renamed back. You can toggle to use this feature in menu option 44.
## Setup notes
@ -344,7 +345,7 @@ You'll find all of these in the [openHABian Configuration Tool](#openhabian-conf
- [Frontail](https://github.com/mthenw/frontail) - openHAB Log Viewer accessible from [http://openhab:9001](http://openhab:9001)
- [InfluxDB and Grafana](https://community.openhab.org/t/influxdb-grafana-persistence-and-graphing/13761/1) - persistence and graphing available from [http://openhab:3000](http://openhab:3000)
- [Eclipse Mosquitto](http://mosquitto.org) - Open Source MQTT v3.1/v3.1.1 Broker
- [Node-RED](https://nodered.org) - "Flow-based programming for the Internet of Things", with preinstalled [openHAB 2](https://flows.nodered.org/node/node-red-contrib-openhab2) and [BigTimer](https://flows.nodered.org/node/node-red-contrib-bigtimer) add-ons. Accessible from [http://openhab:1880](http://openhab:1880)
- [Node-RED](https://nodered.org) - "Flow-based programming for the Internet of Things". Access at [http://openhab:1880](http://openhab:1880).
- [Homegear](https://www.homegear.eu/index.php/Main_Page) - Homematic control unit emulation
- [KNXd](http://michlstechblog.info/blog/raspberry-pi-eibknx-ip-gateway-and-router-with-knxd) - KNX daemon running at `224.0.23.12:3671/UDP`
- [OWServer](http://owfs.org/index.php?page=owserver_protocol) - 1wire control system
@ -407,11 +408,13 @@ After the installation of openHABian was successful, you should be able to acces
If you are not able to access your system via the openHAB dashboard or SSH after more than one hour, chances are high that your hardware setup is the problem. Consult the [debug guide](openhabian-DEBUG.md) and move on from there.
<a id="switch-openhab-branch"></a>
#### Can I switch from openHAB 2 stable to the testing or unstable branch?
openHABian installs the latest stable build of openHAB 2.
If you want to switch over to the snapshot or milestone release, please do so via the openHABian Configuration Tool.
#### Can I switch openHAB 2 and 3 via openHABian branches ?
openHABian installs the latest stable build of openHAB.
The standard openHABian `stable` and `master` branches will install openHAB version 2 and the `openHAB3` branch will install the new openHAB version 3.
You can migrate between versions by selecting the corresponding 4X menu option. That should also result in an openHABian branch change.
If you want to choose from stable, snapshot or milestone releases, please do so via `openhabian-config` tool (also menu 4X).
Note this will **not** result in any openHABian branch change.
Switching from stable to newer development releases might introduce changes and incompatibilities, so please be sure to make a full openHAB backup first!
Check the Linux installation article for all needed details: [Linux: Changing Versions](https://www.openhab.org/docs/installation/linux.html#changing-versions)
<a id="headache"></a>