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 876)

pull/1839/head
openHAB Build Server 2022-04-03 04:53:49 +00:00
parent adce95b7fb
commit ad1a1bb262
18 changed files with 677 additions and 64 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

8
_addons_automation/jrubyscripting/readme.md
View File

@ -3,7 +3,7 @@ id: jrubyscripting
label: JRuby Scripting
title: JRuby Scripting - Automation
type: automation
description: "This add-on provides [JRuby](https://www.jruby.org/) 9.3.2 that can be used as a scripting language within automation rules."
description: "This add-on provides [JRuby](https://www.jruby.org/) scripting language for automation rules."
since: 3x
logo: images/addons/jrubyscripting.png
install: manual
@ -15,7 +15,7 @@ install: manual
# JRuby Scripting
This add-on provides [JRuby](https://www.jruby.org/) 9.3.2 that can be used as a scripting language within automation rules.
This add-on provides [JRuby](https://www.jruby.org/) scripting language for automation rules.
## JRuby Scripting Configuration
@ -29,8 +29,8 @@ Alternatively, JRuby configuration parameters may be set by creating a `jruby.cf
| org.openhab.automation.jrubyscripting:rubylib | $OPENHAB_CONF/automation/lib/ruby/ | Search path for user libraries. Separate each path with a colon (semicolon in Windows). |
| org.openhab.automation.jrubyscripting:local_context | singlethread | The local context holds Ruby runtime, name-value pairs for sharing variables between Java and Ruby. See [this](https://github.com/jruby/jruby/wiki/RedBridge#Context_Instance_Type) for options and details |
| org.openhab.automation.jrubyscripting:local_variables | transient | Defines how variables are shared between Ruby and Java. See [this](https://github.com/jruby/jruby/wiki/RedBridge#local-variable-behavior-options) for options and details |
| org.openhab.automation.jrubyscripting:gems | | A comma separated list of [Ruby Gems](https://rubygems.org/) to install. |
| org.openhab.automation.jrubyscripting:require | | A comma separated list of script names to be required by the JRuby Scripting Engine at the beginning of user scripts. |
| org.openhab.automation.jrubyscripting:gems | | A comma separated list of [Ruby Gems](https://rubygems.org/) to install. |
| org.openhab.automation.jrubyscripting:require | | A comma separated list of script names to be required by the JRuby Scripting Engine at the beginning of user scripts. |
## Ruby Gems

24
_addons_bindings/tado/readme.md
View File

@ -42,7 +42,7 @@ Afterwards the discovery will show all zones and mobile devices associated with
### Channels
Name | Type | Description | Read/Write
-|-|-|-|-
-|-|-|-
`homePresence` | String | Current presence value of the tado home. `HOME` and `AWAY` can be set | RW
## `zone` Thing
@ -85,16 +85,34 @@ Name | Type | Description | Read/Write | Zone type
`acPower` | Switch | Indicates if the Air-Conditioning is Off or On | R | `AC`
`hvacMode` | String | Active mode, one of `OFF`, `HEAT`, `COOL`, `DRY`, `FAN`, `AUTO` | RW | `HEATING` and `DHW` support `OFF` and `HEAT`, `AC` can support more
`targetTemperature` | Number:Temperature | Set point | RW | `HEATING`, `AC`, `DHW`
`fanspeed` | String | Fan speed, one of `AUTO`, `LOW`, `MIDDLE`, `HIGH` | RW | `AC`
`swing` | Switch | Swing on/off | RW | `AC`
`fanspeed`<sup>1)</sup> | String | Fan speed, one of `AUTO`, `LOW`, `MIDDLE`, `HIGH` | RW | `AC`
`fanLevel`<sup>1)</sup> | String | Fan speed, one of <sup>3)</sup> `AUTO`, `SILENT`, `LEVEL1`, `LEVEL2`, `LEVEL3`, `LEVEL4`, `LEVEL5` | RW | `AC`
`swing`<sup>2)</sup> | Switch | Swing on/off | RW | `AC`
`verticalSwing`<sup>2)</sup> | String | Vertical swing state, one of <sup>3)</sup> `OFF`, `ON`, `UP`, `MID_UP`, `MID`, `MID_DOWN`, `DOWN`, `AUTO` | RW | `AC`
`horizontalSwing`<sup>2)</sup> | String | Horizontal swing state, one of <sup>3)</sup> `OFF`, `ON`, `LEFT`, `MID_LEFT`, `MID`, `MID_RIGHT`, `RIGHT`, `AUTO` | RW | `AC`
`overlayExpiry` | DateTime | End date and time of a timer | R | `HEATING`, `AC`, `DHW`
`timerDuration` | Number | Timer duration in minutes | RW | `HEATING`, `AC`, `DHW`
`operationMode` | String | Operation mode the zone is currently in. One of `SCHEDULE` (follow smart schedule), `MANUAL` (override until ended manually), `TIMER` (override for a given time), `UNTIL_CHANGE` (active until next smart schedule block or until AWAY mode becomes active) | RW | `HEATING`, `AC`, `DHW`
`batteryLowAlarm` | Switch | A control device in the Zone has a low battery (if applicable) | R | Any Zone
`openWindowDetected` | Switch | An open window has been detected in the Zone | R | Any Zone
`light` | Switch | State (`ON`, `OFF`) of the control panel light (if applicable) | RW | `AC`
The `RW` items are used to either override the schedule or to return to it (if `hvacMode` is set to `SCHEDULE`).
<sup>1)</sup> Simpler A/C units have fan speed settings in the range [`LOW`, `MIDDLE`, `HIGH`].
However, more sophisticated devices have settings in the range [`SILENT`, `LEVEL1`, `LEVEL2`, `LEVEL3`, `LEVEL4`].
So you need to choose the respective channel type name that matches the features of your device.
<sup>2)</sup> Simpler A/C units have a single switch type swing function that is either `ON` or `OFF`.
However, more sophisticated devices may have either a vertical swing, a horizontal swing, or both, which could also have more complex settings.
For example the horizontal swing function could simply be `ON` or it could have more complex settings in the range [`LEFT`, `MID_LEFT`, `MID`, `MID_RIGHT`, `RIGHT`].
So you need to choose the respective channel type name that matches the features of your device.
<sup>3)</sup> The _'one of'_ list contains all possible state values supported within the tado° binding.
However, in reality different A/C units might only support a **_subset_** of those values.
And indeed the subset of supported values might depend on the current state of the `acPower` and `hvacMode` channels.
In that case, if you send a channel command value to an A/C unit which does not (currently) support that particular state value, then openHAB will report a '422' run-time error in the log.
### Item Command Collection
Item changes are not immediately applied, but instead collected and only when no change is done for 5 seconds (by default - see `hvacChangeDebounce` above), the combined HVAC change is sent to the server.

58
_addons_bindings/wemo/readme.md
View File

@ -25,7 +25,8 @@ The Binding also supports the Crock-Pot Smart Slow Cooker, Mr. Coffee Smart Coff
## Discovery
The WeMo devices are discovered through UPnP discovery service in the network. Devices will show up in the inbox and can be easily added as Things.
The WeMo devices are discovered through UPnP discovery service in the network.
Devices will show up in the inbox and can be easily added as Things.
## Binding Configuration
@ -33,23 +34,48 @@ The binding does not need any configuration.
## Thing Configuration
For manual Thing configuration, one needs to know the UUID of a certain WeMo device.
In the thing file, this looks e.g. like
For manual Thing configuration, one needs to know the UDN of a certain WeMo device.
It can most easily be obtained by performing an auto-discovery before configuring the thing manually.
```
wemo:socket:Switch1 [udn="Socket-1_0-221242K11xxxxx"]
```
Most devices share the `udn` configuration parameter:
For a WeMo Link bridge and paired LED Lights, please use the following Thing definition
| Configuration Parameter | Description |
|-------------------------|------------------------------------|
| udn | The UDN identifies the WeMo device |
```
Bridge wemo:bridge:Bridge-1_0-231445B01006A0 [udn="Bridge-1_0-231445B010xxxx"] {
MZ100 94103EA2B278xxxx [ deviceID="94103EA2B278xxxx" ]
MZ100 94103EA2B278xxxx [ deviceID="94103EA2B278xxxx" ]
}
```
### WeMo LED Light
For LED Lights paired to a WeMo Link bridge, please use the following configuration parameter:
| Configuration Parameter | Description |
|-------------------------|-------------------------------------------------|
| deviceID | The device ID identifies one certain WeMo light |
### WeMo Insight Switch
The WeMo Insight Switch has some additional parameters for controlling the behavior for channel `currentPower`.
This channel reports the current power consumption in Watt.
The internal theoretical accuracy is 5 mW, i.e. three decimals.
These raw values are reported with high frequency, often multiple updates can occur within a single second.
For example, the sequence of 40.440 W, 40.500 W and 40.485 W would result in the channel being updated with values rounded to nearest integer, respectively 40 W, 41 W and 40 W.
When persisting items linked to this channel, this can result in a significant amount of data being stored.
To mitigate this issue, a sliding window with a moving average calculation has been introduced.
This window is defined with a one minute default period.
This is combined with a delta trigger value, which is defaulted to 1 W.
This means that the channel is only updated when one of the following conditions are met:
1. The rounded value received is equal to the rounded average for the past minute, i.e. this value has stabilized. This introduces a delay for very small changes in consumption, but on the other hand it prevents excessive logging and persistence caused by temporary small changes and rounding.
2. The rounded value received is more than 1 W from the previous value. So when changes are happening fast, the channel will also be updated fast.
| Configuration Parameter | Description |
|----------------------------|---------------------------------------------------------------------------------------|
| udn | The UDN identifies the WeMo Insight Switch |
| currentPowerSlidingSeconds | Sliding window in seconds for which moving average power is calculated (0 = disabled) |
| currentPowerDeltaTrigger | Delta triggering immediate channel update (in Watt) |
The moving average calculation can be disabled by setting either `currentPowerSlidingSeconds` or `currentPowerDeltaTrigger` to 0.
This will cause the channel to be updated the same way as in openHAB versions prior to 3.3.
## Channels
@ -67,6 +93,7 @@ Devices support some of the following channels:
| timespan | Number | Time in seconds over which onTotal applies. Typically 2 weeks except first used. | Insight |
| averagePower | Number:Power | Average power consumption in Watts. | Insight |
| currentPower | Number:Power | Current power consumption of an Insight device. 0 if switched off. | Insight |
| currentPowerRaw | Number:Power | Current power consumption of an Insight device with full precision (5 mW accuracy, three decimals). 0 if switched off. | Insight |
| energyToday | Number:Energy | Energy in Wh used today. | Insight |
| energyTotal | Number:Energy | Energy in Wh used in total. | Insight |
| standbyLimit | Number:Power | Minimum energy draw in W to register device as switched on (default 8W, configurable via WeMo App). | Insight |
@ -109,7 +136,6 @@ Devices support some of the following channels:
| autoOffTime | DateTime | Time when the heater switches off | Heater |
| heatingRemaining | Number | Shows the remaining heating time | Heater |
## Full Example
demo.things:
@ -117,6 +143,7 @@ demo.things:
```
wemo:socket:Switch1 "DemoSwitch" @ "Office" [udn="Socket-1_0-221242K11xxxxx"]
wemo:motion:Sensor1 "MotionSensor" @ "Entrance" [udn="Sensor-1_0-221337L11xxxxx"]
wemo:insight:Insight1 "Insight" @ "Attic" [udn="Insight-1_0-xxxxxxxxxxxxxx", currentPowerSlidingSeconds=120, currentPowerDeltaTrigger=2]
Bridge wemo:bridge:Bridge-1_0-231445B010xxxx [udn="Bridge-1_0-231445B010xxxx"] {
MZ100 94103EA2B278xxxx "DemoLight1" @ "Living" [ deviceID="94103EA2B278xxxx" ]
@ -200,7 +227,6 @@ Number currentTemp { channel="wemo:heater:HeaterB-1_0-231445B010xxxx:cu
Number targetTemp { channel="wemo:heater:HeaterB-1_0-231445B010xxxx:targetTemp" }
DateTime autoOffTime { channel="wemo:heater:HeaterB-1_0-231445B010xxxx:autoOffTime" }
String heaterRemaining { channel="wemo:heater:HeaterB-1_0-231445B010xxxx:heaterRemaining" }
```
demo.sitemap:
@ -281,8 +307,6 @@ sitemap demo label="Main Menu"
Setpoint item=targetTemp
Text item=autoOffTime
Number item=heaterRemaining
}
}
```

41
_addons_bindings/zwave/doc/benext/80822002_0_0.md
View File

@ -1,21 +1,21 @@
---
layout: documentation
title: BEN_80822002 - ZWave
title: Panic Button - ZWave
---
{% include base.html %}
# BEN_80822002 Keyfob with red panic button, lock button and unlock button
This describes the Z-Wave device *BEN_80822002*, manufactured by *[BeNext](http://www.benext.eu/)* with the thing type UID of ```benext_80822002_00_000```.
# Panic Button Keyfob with red panic button, lock button and unlock button (BEN_80822002)
This describes the Z-Wave device *Panic Button*, manufactured by *[BeNext](http://www.benext.eu/)* with the thing type UID of ```benext_80822002_00_000```.
The device is in the category of *Remote Control*, defining Any portable or hand-held device that controls the status of something, e.g. remote control, keyfob etc..
![BEN_80822002 product image](https://opensmarthouse.org/zwavedatabase/1380/image/)
![Panic Button product image](https://opensmarthouse.org/zwavedatabase/1380/image/)
The BEN_80822002 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 Panic Button 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 BEN_80822002 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 Panic Button 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
@ -43,7 +43,7 @@ Inclusion usually takes a few minutes, but sometimes last longer, up to some hou
### Wakeup Information
The BEN_80822002 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 Panic Button 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.
@ -68,12 +68,12 @@ There is no factory reset procedure. This is confirmed by the manufacturer. The
## Channels
The following table summarises the channels available for the BEN_80822002 -:
The following table summarises the channels available for the Panic Button -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Lock (ON) or unlock (OFF) pressed | switch_binary | switch_binary | Switch | Switch |
| Binary Sensor | sensor_binary | sensor_binary | | Switch |
| Status of the alarm (on or off), asked every time at the wake up of the device. | sensor_binary | sensor_binary | | Switch |
| Alarm toggle, switches from ON to OFF, or OFF to ON when pressed | alarm_general | alarm_general | Alarm | Switch |
| Battery Level | battery-level | system.battery_level | Battery | Number |
@ -85,7 +85,9 @@ 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.
### Binary Sensor
### Status of the alarm (on or off), asked every time at the wake up of the device.
Indicates if a sensor has triggered.
The ```sensor_binary``` channel is of type ```sensor_binary``` and supports the ```Switch``` item. This is a read only channel so will only be updated following state changes from the device.
@ -118,7 +120,7 @@ This channel provides the battery level as a percentage and also reflects the lo
## Device Configuration
The following table provides a summary of the 6 configuration parameters available in the BEN_80822002.
The following table provides a summary of the 6 configuration parameters available in the Panic Button.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
@ -135,12 +137,10 @@ Detailed information on each parameter can be found in the sections below.
### Parameter 1: Set to default
Set all configuration values to default values (factory default)
When you write 255 (0xFF) to this parameter, all configurable values are set back to their defaults. After some time, at the next wake up, the device will "answer" that by making the value -86 again (input is 0 to 255, but output is -128 to  +127, in 2's complement notation)
When you write -1 (0xFF) to this parameter, all configurable values are set back to their defaults. After some time, at the next wake up, the device will "answer" that by making the value -86 again. Press "reinitialise" in the OpenHAB GUI, and then wake up the device (by pressing the SOS-button at least 5 seconds) in order to see the results in OpenHAB. 
If this value is -86 (0xAA), the configuration of the device is default.
If this value is 85 (0x55), the configuration of the device has been changed.
Note:  If this value is on -86, and you make a change in the other configuration parameters, the OpenHab PaperUI prevent this, as the number must be between 0 and 255. You can circumvent that by making this parameter for instance 1 (or any other value,  not 55 and greater than 0)
If this value is 85 (0x55), the configuration of the device has been changed.This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
Values in the range 0 to 0 may be set.
The manufacturer defined default value is ```0```.
@ -180,17 +180,18 @@ This parameter has the configuration ID ```config_3_1``` and is of type ```INTEG
### Parameter 4: Buttons mapped
Specifies what message will be sent in case of a key is pressed
**_Alarm mode_ if 0: 
**_Alarm mode_ if 0: (recommended)
** SOS button sends an ALARM_REPORT to nodes in group 1
LOCK button sends a BASIC_SET with value 255 to nodes in group 1
UNLOCK button sends a BASIC_SET with value 0 to nodes in group 1
**_Control mode_ if 1-255:
**_Control mode_ if 1-255: (do not use, unless you know what you do)
** SOS button sends a BASIC_SET with value 255 to nodes in group 1
LOCK button sends a BASIC_SET with value 255 to nodes in group 2
UNLOCK button sends a BASIC_SET with value 0 to nodes in group 2**
**
UNLOCK button sends a BASIC_SET with value 0 to nodes in group 2
Alarm mode is the preferred mode, giving you access to all buttons. The control mode is possible, but strange to use in OpenHAB due to the fact that alarm_general channel is then used for the LOCK/UNLOCK button.This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
Values in the range 0 to 0 may be set.
The manufacturer defined default value is ```0```.
@ -248,7 +249,7 @@ This parameter has the configuration ID ```wakeup_node``` and is of type ```INTE
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 BEN_80822002 supports 2 association groups.
The Panic Button supports 2 association groups.
### Group 1: Alarm

130
_addons_bindings/zwave/doc/climax/wss4ezw_0_0.md Normal file
View File

@ -0,0 +1,130 @@
---
layout: documentation
title: WSS-4E-ZW - ZWave
---
{% include base.html %}
# WSS-4E-ZW Smart Scenario Switch
This describes the Z-Wave device *WSS-4E-ZW*, manufactured by *Climax Technology, Ltd.* with the thing type UID of ```climax_wss4ezw_00_000```.
The device is in the category of *Remote Control*, defining Any portable or hand-held device that controls the status of something, e.g. remote control, keyfob etc..
![WSS-4E-ZW product image](https://opensmarthouse.org/zwavedatabase/1478/image/)
The WSS-4E-ZW 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.
## Overview
WSS-4E-ZW is a Z-Wave Four-Button Scenario Switch designed to control a group of pre-programmed home automation devices by simply pressing the scenario buttons under the same Z-Wave network
### Inclusion Information
1. Remove the cover by using a screwdriver.
2. Insert the battery then replace the cover.
3. Put the Z-Wave control panel into Inclusion mode (please refer to the Z-Wave control panel manual).
4. Within 1.5 seconds, press the Function Button 3 times.
5. Refer to the operation manual of the Z-Wave gateway or control panel to complete the adding process.
6. If the device has already been added (included) into another Z-Wave Gateway/Control Panel, or if the device is unable to be added into the current Z-Wave Gateway/Control Panel, try removing it first (see Removing Device).
### Exclusion Information
1. Put the Z-Wave gateway or control panel into Exclusion mode (please refer to the Z-Wave or control panel manual).
2. Within 1.5 seconds, press the Function Button 3 times and the device will be removed from the Z-Wave network.
### General Usage Information
Press and hold the Function Button of the device for 10 seconds to factory reset.
## Channels
The following table summarises the channels available for the WSS-4E-ZW -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Scene Number | scene_number | scene_number | | Number |
| Alarm | alarm_general | alarm_general | Alarm | Switch |
| 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.
### Alarm
Indicates if an alarm is triggered.
The ```alarm_general``` channel is of type ```alarm_general``` and supports the ```Switch``` item and is in the ```Alarm``` 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%.
## 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 WSS-4E-ZW 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.
Group 1 for “LifeLine”
Group 1 for “LifeLine”:
Scene Activation CC
(COMMAND\_CLASS\_SCENE_ACTIVATION)
Battery CC (COMMAND\_CLASS\_BASIC)
Device Reset Locally CC
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_SCENE_ACTIVATION_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_ALARM_V4| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| |
| COMMAND_CLASS_BATTERY_V1| |
| COMMAND_CLASS_WAKE_UP_V2| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
### Documentation Links
* [WSS-4E-ZW-(OTA)_20210105.pdf](https://opensmarthouse.org/zwavedatabase/1478/reference/WSS-4E-ZW-OTA_20210105.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/1478).

10
_addons_bindings/zwave/doc/heltun/heht01_0_0.md
View File

@ -66,9 +66,9 @@ The following table summarises the channels available for the HE-HT01 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Ait Temperature | sensor_temperature | sensor_temperature | Temperature | Number:Temperature |
| Air Temperature | air_temperature | sensor_temperature | Temperature | Number:Temperature |
| Relative Humidity | sensor_relhumidity | sensor_relhumidity | Humidity | Number |
| Floor Temperature | sensor_temperature | sensor_temperature | Temperature | Number:Temperature |
| Floor Temperature | floor_temperature | sensor_temperature | Temperature | Number:Temperature |
| Luminance | sensor_luminance | sensor_luminance | | Number |
| Electric meter (watts) | meter_watts | meter_watts | Energy | Number |
| Electric meter (kWh) | meter_kwh | meter_kwh | Energy | Number |
@ -80,10 +80,10 @@ The following table summarises the channels available for the HE-HT01 -:
| Setpoint (heating) | thermostat_setpoint | thermostat_setpoint | Heating | Number:Temperature |
| Clock Time Offset | time_offset | time_offset | Time | Number |
### Ait Temperature
### Air 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.
The ```air_temperature``` channel is of type ```sensor_temperature``` and supports the ```Number:Temperature``` item and is in the ```Temperature``` category.
### Relative Humidity
Indicates the current relative humidity.
@ -93,7 +93,7 @@ The ```sensor_relhumidity``` channel is of type ```sensor_relhumidity``` and sup
### Floor 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.
The ```floor_temperature``` channel is of type ```sensor_temperature``` and supports the ```Number:Temperature``` item and is in the ```Temperature``` category.
### Luminance
Indicates the current light reading.

3
_addons_bindings/zwave/doc/kwikset/914trl_0_0.md
View File

@ -184,9 +184,10 @@ The following option values may be configured, in addition to values in the rang
| Value | Description |
|--------|-------------|
| 0 | Default |
| 1 | Factory Default |
The manufacturer defined default value is ```0```.
The manufacturer defined default value is ```0``` (Default).
This parameter has the configuration ID ```config_40_1_wo``` and is of type ```INTEGER```.
This is a write only parameter.

13
_addons_bindings/zwave/doc/oomi/ft132_0_0.md
View File

@ -17,9 +17,12 @@ The FT132 supports routing. This allows the device to communicate using other ro
## Overview
Fantech Dual Nano Switch is a Z-Wave Smart Switch specifically used to enable Z-Wave command and control (on/off) of any wall switches. 
In the event of power failure, non-volatile memory retains all programmed information relating to the unit’s operating status. 
It can connect to 2 external manual switches to control the load ON/OFF independently. Its surface has a pin socket, which can be used for connecting to the touch panel, so you can also use the touch panel to control the Dual Nano Switch. 
Fantech Dual Nano Switch is a Z-Wave Smart Switch specifically used to enable Z-Wave command and control (on/off) of any wall switches.
In the event of power failure, non-volatile memory retains all programmed information relating to the unit’s operating status.
It can connect to 2 external manual switches to control the load ON/OFF independently. Its surface has a pin socket, which can be used for connecting to the touch panel, so you can also use the touch panel to control the Dual Nano Switch.
The Dual Nano Switch is also a security Z-Wave device and supports Over The Air (OTA) feature for the products firmware upgrade.
### Inclusion Information
@ -30,6 +33,10 @@ If you want your In-Wall Smart Switch (Dual) as a non-secure device in your Z-Wa
If at some stage, your primary controller is missing or inoperable, you may wish to reset all ofyour In-Wall Smart Switch (Dual)’s settings to their factory defaults. To do this, press and holdthe Action Button for 20 seconds and then release it. Your In-Wall Smart Switch (Dual) will nowbe reset to its original settings, and the green LED will be solid for 2 seconds and then remain thecolourful gradient status as a confirmation.
### General Usage Information
## Channels
The following table summarises the channels available for the FT132 -:

2
_addons_persistences/jdbc/readme.md
View File

@ -55,7 +55,7 @@ This service can be configured in the file `services/jdbc.cfg`.
| Property | Default | Required | Description |
| ------------------------- | ------------------------------------------------------------ | :-------: | ------------------------------------------------------------ |
| url | | Yes | JDBC URL to establish a connection to your database. Examples:<br/><br/>`jdbc:derby:./testDerby;create=true`<br/>`jdbc:h2:./testH2`<br/>`jdbc:hsqldb:./testHsqlDb`<br/>`jdbc:mariadb://192.168.0.1:3306/testMariadb`<br/>`jdbc:mysql://192.168.0.1:3306/testMysql?serverTimezone=UTC`<br/>`jdbc:postgresql://192.168.0.1:5432/testPostgresql`<br/>`jdbc:sqlite:./testSqlite.db`.<br/><br/>If no database is available it will be created; for example the url `jdbc:h2:./testH2` creates a new H2 database in openHAB folder. Example to create your own MySQL database directly:<br/><br/>`CREATE DATABASE 'yourDB' CHARACTER SET utf8 COLLATE utf8_general_ci;` |
| url | | Yes | JDBC URL to establish a connection to your database. Examples:<br/><br/>`jdbc:derby:./testDerby;create=true`<br/>`jdbc:h2:./testH2`<br/>`jdbc:hsqldb:./testHsqlDb`<br/>`jdbc:mariadb://192.168.0.1:3306/testMariadb`<br/>`jdbc:mysql://192.168.0.1:3306/testMysql?serverTimezone=UTC`<br/>`jdbc:postgresql://192.168.0.1:5432/testPostgresql`<br/>`jdbc:timescaledb://192.168.0.1:5432/testPostgresql`<br/>`jdbc:sqlite:./testSqlite.db`.<br/><br/>If no database is available it will be created; for example the url `jdbc:h2:./testH2` creates a new H2 database in openHAB folder. Example to create your own MySQL database directly:<br/><br/>`CREATE DATABASE 'yourDB' CHARACTER SET utf8 COLLATE utf8_general_ci;` |
| user | | if needed | database user name |
| password | | if needed | database user password |
| errReconnectThreshold | 0 | No | when the service is deactivated (0 means ignore) |

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

@ -45,6 +45,10 @@
<channel typeId="targetTemperature" id="targetTemperature"></channel>
<channel typeId="fanspeed" id="fanspeed"></channel>
<channel typeId="swing" id="swing"></channel>
<channel typeId="light" id="light"></channel>
<channel typeId="fanLevel" id="fanLevel"></channel>
<channel typeId="horizontalSwing" id="horizontalSwing"></channel>
<channel typeId="verticalSwing" id="verticalSwing"></channel>
<channel typeId="overlayExpiry" id="overlayExpiry"></channel>
<channel typeId="timerDuration" id="timerDuration"></channel>
@ -195,6 +199,65 @@
<description>State of AC swing (only if supported by AC)</description>
</channel-type>
<channel-type id="light">
<item-type>Switch</item-type>
<label>Light</label>
<description>State of control panel light (only if supported by AC)</description>
</channel-type>
<channel-type id="fanLevel">
<item-type>String</item-type>
<label>Fan Speed</label>
<description>AC fan level (only if supported by AC)</description>
<state readOnly="false">
<options>
<option value="SILENT">SILENT</option>
<option value="LEVEL1">LEVEL1</option>
<option value="LEVEL2">LEVEL2</option>
<option value="LEVEL3">LEVEL3</option>
<option value="LEVEL4">LEVEL4</option>
<option value="LEVEL5">LEVEL5</option>
<option value="AUTO">AUTO</option>
</options>
</state>
</channel-type>
<channel-type id="horizontalSwing">
<item-type>String</item-type>
<label>Horizontal Swing</label>
<description>State of AC horizontal swing (only if supported by AC)</description>
<state readOnly="false">
<options>
<option value="AUTO">AUTO</option>
<option value="LEFT">LEFT</option>
<option value="MID_LEFT">MID-LEFT</option>
<option value="MID">MID</option>
<option value="MID_RIGHT">MID-RIGHT</option>
<option value="RIGHT">RIGHT</option>
<option value="ON">ON</option>
<option value="OFF">OFF</option>
</options>
</state>
</channel-type>
<channel-type id="verticalSwing">
<item-type>String</item-type>
<label>Vertical Swing</label>
<description>State of AC vertical swing (only if supported by AC)</description>
<state readOnly="false">
<options>
<option value="AUTO">AUTO</option>
<option value="UP">UP</option>
<option value="MID_UP">UP</option>
<option value="MID">MID</option>
<option value="MID_DOWN">MID-DOWN</option>
<option value="DOWN">DOWN</option>
<option value="ON">ON</option>
<option value="OFF">OFF</option>
</options>
</state>
</channel-type>
<channel-type id="operationMode">
<item-type>String</item-type>
<label>Zone Operation Mode</label>

10
_thing_types/org.openhab.binding.wemo/src/main/resources/OH-INF/thing/channels.xml
View File

@ -74,12 +74,20 @@
<channel-type id="currentPower">
<item-type>Number:Power</item-type>
<label>Power</label>
<label>Current Power</label>
<description>The current power consumption</description>
<category>Energy</category>
<state pattern="%.0f %unit%"/>
</channel-type>
<channel-type id="currentPowerRaw" advanced="true">
<item-type>Number:Power</item-type>
<label>Current Power Raw</label>
<description>The current power consumption with full precision</description>
<category>Energy</category>
<state pattern="%.3f %unit%"/>
</channel-type>
<channel-type id="energyToday" advanced="true">
<item-type>Number:Energy</item-type>
<label>Energy Today</label>

3
_thing_types/org.openhab.binding.wemo/src/main/resources/OH-INF/thing/insight.xml
View File

@ -17,6 +17,7 @@
<channel id="timespan" typeId="timespan"/>
<channel id="averagePower" typeId="averagePower"/>
<channel id="currentPower" typeId="currentPower"/>
<channel id="currentPowerRaw" typeId="currentPowerRaw"/>
<channel id="energyToday" typeId="energyToday"/>
<channel id="energyTotal" typeId="energyTotal"/>
<channel id="standByLimit" typeId="standByLimit"/>
@ -25,7 +26,7 @@
<representation-property>udn</representation-property>
<config-description-ref uri="thing-type:wemo:device"/>
<config-description-ref uri="thing-type:wemo:insight"/>
</thing-type>
</thing:thing-descriptions>

151
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/benext/80822002_0_0.xml Normal file
View File

@ -0,0 +1,151 @@
<?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="benext_80822002_00_000" listed="false">
<label>Panic Button Keyfob with red panic button, lock button and unlock button (BEN_80822002)</label>
<description><![CDATA[
Keyfob with red panic button, lock button and unlock button (BEN_80822002)<br /> <h1>Overview</h1><p>The BeNext Panic Button is a small panic button meant for wearing as a necklace. It has a big red SOS button, and a lock and unlock button. In newer versions, the buttons are colored. <br />The device is only available in the EU region. </p> <br /> <h2>Inclusion Information</h2><ol><li>Press and hold the red SOS button 2 seconds until the LED starts blinking.<br /></li><li>Release the button.</li><li>The LED blinks 2 times every second indicating the inclusion process is going on.</li><li>When included succesfully, the LED is on for one second.</li></ol><p>When classic inclusion fails, network wide inclusion will be tried. </p><p>Inclusion usually takes a few minutes, but sometimes last longer, up to some hours. In the last case, manually wake up the devices several times (by pressing the red SOS button for 5 seconds), until the configuration is finished.</p> <br /> <h2>Exclusion Information</h2><ol><li>Press and hold the red SOS button (5 to 10 seconds) until the LED starts blinking triple every 1,5 second. </li><li>Then release the button.</li><li>The LED blinks 3 times every 1,5 second indicating the exclusion process is going on.</li><li>When excluded successfully, the LED is on for one second. </li></ol> <br /> <h2>Wakeup Information</h2><p>Hold the red SOS Button for approximately 5 seconds. As a side effect, the SOS alarm will be toggled.</p>
]]></description>
<category>RemoteControl</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="basic_switch_binary" typeId="switch_binary">
<label>Lock (ON) or unlock (OFF) pressed</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_BASIC</property>
</properties>
</channel>
<channel id="sensor_binary" typeId="sensor_binary">
<label>Status of the alarm (on or off), asked every time at the wake up of the device.</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SENSOR_BINARY</property>
</properties>
</channel>
<channel id="alarm_general" typeId="alarm_general">
<label>Alarm toggle, switches from ON to OFF, or OFF to ON when pressed</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;NOGET</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">BeNext</property>
<property name="modelId">Panic Button</property>
<property name="manufacturerId">008A</property>
<property name="manufacturerRef">0014:0101</property>
<property name="dbReference">1380</property>
<property name="commandClass:COMMAND_CLASS_ALARM">getSupported=false</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: Set to default</label>
<description><![CDATA[
Set all configuration values to default values (factory default)<br /> <h1>Overview</h1><p>When you write -1 (0xFF) to this parameter, all configurable values are set back to their defaults. After some time, at the next wake up, the device will "answer" that by making the value -86 again. Press "reinitialise" in the OpenHAB GUI, and then wake up the device (by pressing the SOS-button at least 5 seconds) in order to see the results in OpenHAB. </p><p>If this value is -86 (0xAA), the configuration of the device is default.<br />If this value is 85 (0x55), the configuration of the device has been changed.</p>
]]></description>
<default>0</default>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_2_1" type="integer" groupName="configuration">
<label>2: Min time to press panic button</label>
<description><![CDATA[
Minimum time to press the panic button before an alarm will be send<br /> <h1>Overview</h1><p>The time the panic button must be pressed before an alarm message is sent out. Unit is 10 ms, so 100 is 1 second.</p><p>In case of 0, send an alarm message immediately. <br />In case of 1 - 255, send an alarm message after this value * 10 ms</p><p>Default is  100 (1 second).</p>
]]></description>
<default>100</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_3_1" type="integer" groupName="configuration">
<label>3: Min LED on time after panic</label>
<description><![CDATA[
Minimum time that LED will be on after an alarm message<br /> <h1>Overview</h1><p>Specifies the minimum time the LED is on after an alarm message has been sent.  Unit is 10 ms, so 100 = 1 second. </p><p>Default is 100 (1 second). </p>
]]></description>
<default>100</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_4_1" type="integer" groupName="configuration">
<label>4: Buttons mapped</label>
<description><![CDATA[
Specifies what message will be sent in case of a key is pressed<br /> <h1>Overview</h1><p><b><i>Alarm mode</i> if 0: (recommended)<br /></b>SOS button sends an ALARM_REPORT to nodes in group 1 <br />LOCK button sends a BASIC_SET with value 255 to nodes in group 1<br />UNLOCK button sends a BASIC_SET with value 0 to nodes in group 1<br /></p><p><b><i>Control mode</i> if 1-255: (do not use, unless you know what you do)<br /></b>SOS button sends a BASIC_SET with value 255 to nodes in group 1<br />LOCK button sends a BASIC_SET with value 255 to nodes in group 2<br />UNLOCK button sends a BASIC_SET with value 0 to nodes in group 2</p><p>Alarm mode is the preferred mode, giving you access to all buttons. The control mode is possible, but strange to use in OpenHAB due to the fact that alarm_general channel is then used for the LOCK/UNLOCK button.</p>
]]></description>
<default>0</default>
<advanced>true</advanced>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_5_1" type="integer" groupName="configuration">
<label>5: Min time to press control buttons</label>
<description><![CDATA[
Minimum time the control buttons must be pressed before a message is sent<br /> <h1>Overview</h1><p>Specifies the minimum time the lock and unlock buttons must be pressed, before a control message is sent to the controller. Unit is 10 ms, so 100 is 1 second.</p><p>Default is 10 (that is 100 ms)</p>
]]></description>
<default>10</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_6_1" type="integer" groupName="configuration">
<label>6: Min LED on time after control</label>
<description><![CDATA[
Minimum time that LED will be on after a control message<br /> <h1>Overview</h1><p>The time the LED will be on after a control message has been sent out. Unit is 10 ms, so for instance 100 is 1 second.</p><p>In case of 0, LED will be on while sending the message<br />In case of 1 - 255, LED will be on during send time + <i>this value </i>* 10 ms.<br /><br />
Default is 50 (500 ms)</p>
]]></description>
<default>50</default>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Alarm</label>
<description><![CDATA[
Alarm mode group<br /> <h1>Overview</h1><p>This group is used for the alarm mode. <br /><br />Pressing the SOS button or the lock and unlock button will generate a message in group 1 . <br />Pressing lock and unlock only generates a  message in group 1 when in alarm mode<br /><br /></p>
]]></description>
<multipleLimit>8</multipleLimit>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: Control</label>
<description><![CDATA[
Lock and unlock button report group in control mode<br /> <h1>Overview</h1><p>Lock and unlock button are reported in group 2, when config parameter 4 is set to a value other than 0 (control mode).  <br />In control mode, SOS button is reported in group 1.</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>
</thing:thing-descriptions>

74
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/climax/wss4ezw_0_0.xml Normal file
View File

@ -0,0 +1,74 @@
<?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="climax_wss4ezw_00_000" listed="false">
<label>WSS-4E-ZW Smart Scenario Switch</label>
<description><![CDATA[
Smart Scenario Switch<br /> <h1>Overview</h1><p>WSS-4E-ZW is a Z-Wave Four-Button Scenario Switch designed to control a group of pre-programmed home automation devices by simply pressing the scenario buttons under the same Z-Wave network<br /></p> <br /> <h2>Inclusion Information</h2><ol><li>Remove the cover by using a screwdriver.</li><li>Insert the battery then replace the cover.</li><li>Put the Z-Wave control panel into Inclusion mode (please refer to the Z-Wave control panel manual).</li><li>Within 1.5 seconds, press the Function Button 3 times.</li><li>Refer to the operation manual of the Z-Wave gateway or control panel to complete the adding process.</li><li>If the device has already been added (included) into another Z-Wave Gateway/Control Panel, or if the device is unable to be added into the current Z-Wave Gateway/Control Panel, try removing it first (see Removing Device).</li></ol> <br /> <h2>Exclusion Information</h2><ol><li>Put the Z-Wave gateway or control panel into Exclusion mode (please refer to the Z-Wave or control panel manual).</li><li>Within 1.5 seconds, press the Function Button 3 times and the device will be removed from the Z-Wave network.</li></ol> <br /> <h2>Wakeup Information</h2><p>This function uses the Z-Wave Wake Up Command Class. The Wake Up Command Class allows the battery-powered Light Switch to notify the Control Panel/Gateway that it is awake and ready to receive any queued commands. The wake up interval time period is programmed automatically according to Control Panel’s setting when The Light Switch is included. The recommended setting of the interval time is between 30 to 60 minutes.<br /></p>
]]></description>
<category>RemoteControl</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="scene_number" typeId="scene_number">
<label>Scene Number</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_SCENE_ACTIVATION</property>
</properties>
</channel>
<channel id="alarm_general" typeId="alarm_general">
<label>Alarm</label>
<properties>
<property name="binding:*:OnOffType">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">Climax Technology, Ltd.</property>
<property name="modelId">WSS-4E-ZW</property>
<property name="manufacturerId">018E</property>
<property name="manufacturerRef">0004:001C</property>
<property name="dbReference">1478</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[
Group 1 for “LifeLine”<br /> <h1>Overview</h1><p>Group 1 for “LifeLine”:</p><p>Scene Activation CC</p><p>(COMMAND_CLASS_SCENE_ACTIVATION)</p><p> Battery CC (COMMAND_CLASS_BASIC)</p><p> Device Reset Locally CC</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>

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

@ -14,10 +14,10 @@ Wall Heating Thermostat<br /> <h1>Overview</h1><p>The Heltun Heating Thermostat
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="sensor_temperature" typeId="sensor_temperature">
<label>Ait Temperature</label>
<channel id="air_temperature" typeId="sensor_temperature">
<label>Air Temperature</label>
<properties>
<property name="binding:*:QuantityType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=TEMPERATURE</property>
<property name="binding:*:DecimalType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=TEMPERATURE</property>
</properties>
</channel>
<channel id="sensor_relhumidity" typeId="sensor_relhumidity">
@ -26,10 +26,10 @@ Wall Heating Thermostat<br /> <h1>Overview</h1><p>The Heltun Heating Thermostat
<property name="binding:*:DecimalType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=RELATIVE_HUMIDITY</property>
</properties>
</channel>
<channel id="sensor_temperature" typeId="sensor_temperature">
<channel id="floor_temperature" typeId="sensor_temperature">
<label>Floor Temperature</label>
<properties>
<property name="binding:*:QuantityType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=SOIL_TEMPERATURE</property>
<property name="binding:*:DecimalType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=SOIL_TEMPERATURE</property>
</properties>
</channel>
<channel id="sensor_luminance" typeId="sensor_luminance">

135
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/kwikset/914trl_0_0.xml Normal file
View File

@ -0,0 +1,135 @@
<?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="kwikset_914trl_00_000" listed="false">
<label>914TRL Touchpad Electronic Deadbolt</label>
<description><![CDATA[
Touchpad Electronic Deadbolt<br /> <h1>Overview</h1><p>The following table provides a reference of the Alarm_Number related messages.</p> <p>Alarm Type    Alarm Level            Notification Event  </p> <p>021              001                      Lock Secured using Keyed cylinder or inside thumb-turn  </p> <p>022              001                      Lock Un-Secured using Keyed cylinder or inside thumb-turn  </p> <p>026              001                      Lock Auto Secured – Bolt Jammed (Not fully extended)</p> <p>027              001                      Lock Auto Secured – Successful (Fully extended)  </p> <p>017              001                      Lock Secured at Keypad – Bolt Jammed (Not fully extended)   </p> <p>018              000 or User-ID#*   Lock Secured at Keypad – Successful (Fully extended)   </p> <p>019              User-ID#*              Lock Un-Secured by User (User-ID) at Keypad  </p> <p>023              001                      Lock Secured by Controller – Bolt Jammed (Not fully extended)   </p> <p>024              001                      Lock Secured by Controller – Successful (Fully extended)   </p> <p>025              001                      Lock Un-Secured by Controller – Successful (Fully retracted)  </p> <p>112              User-ID#*              New User Code (User-ID#) added to the lock  </p> <p>032              001                      All User Codes deleted from lock   </p> <p>161              001                      Failed User Code attempt at Keypad  </p> <p>162              User-ID#*             Attempted access by user (User-ID#) outside of scheduled   </p> <p>167              001                      Low battery level   </p> <p>168              001                      Critical battery level   </p> <p>169              001                      Battery level too low to operate lock  </p> <p>* User-ID# values: 001 to 030</p> <br /> <h2>Inclusion Information</h2><p> Press button “A” on the lock one time to include it in your system.</p> <br /> <h2>Exclusion Information</h2><p> Press button “A” on the lock one time to exclude it in your system.</p>
]]></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="alarm_number" typeId="alarm_number">
<label>Alarm [Deprecated]</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_ALARM</property>
</properties>
</channel>
<channel id="alarm_raw" typeId="alarm_raw">
<label>Alarm Raw</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">Black &amp; Decker</property>
<property name="modelId">914TRL</property>
<property name="manufacturerId">0090</property>
<property name="manufacturerRef">0001:0001</property>
<property name="dbReference">283</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_31_1_00100000" type="integer" groupName="configuration" readOnly="true">
<label>31: Auto Buzzer</label>
<description><![CDATA[
Beeping sound enabled.<br /> <h1>Overview</h1><p>Beeping sound enabled. When disabled, keypad buttons light red or amber when pressed.</p> <p>ON position is factory default.</p> <p>Note: It is recommended that the beeping sound is enabled during programming.</p>
]]></description>
<default>1</default>
<options>
<option value="0">Off</option>
<option value="1">On</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_31_1_01000000" type="integer" groupName="configuration" readOnly="true">
<label>31: Auto Lock</label>
<description><![CDATA[
Automatically re-locks door 30 seconds after unlocking.<br /> <h1>Overview</h1><p>Lock automatically re-locks door 30 seconds after unlocking. OFF position is factory default. If this switch is turned on, it will be disabled if all codes are deleted from the lock.</p>
]]></description>
<default>0</default>
<options>
<option value="0">Off</option>
<option value="1">On</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_31_1_10000000" type="integer" groupName="configuration" readOnly="true">
<label>31: Lock LED Status</label>
<description><![CDATA[
Door lock status LED blinks every 6 seconds.<br /> <h1>Overview</h1><p>Door lock status LED blinks every 6 seconds. ON position is factory default.</p>
]]></description>
<default>1</default>
<options>
<option value="0">Off</option>
<option value="1">On</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_40_1_wo" type="integer" groupName="configuration">
<label>40: Factory Default</label>
<description><![CDATA[
Reset to factory default settings.<br /> <h1>Overview</h1><p>Reset factory default settings, except for the anti-theft setting.</p>
]]></description>
<default>0</default>
<options>
<option value="0">Default</option>
<option value="1">Factory Default</option>
</options>
<advanced>true</advanced>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Group 1</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/oomi/ft132_0_0.xml
View File

@ -8,7 +8,7 @@
<thing-type id="oomi_ft132_00_000" listed="false">
<label>FT132 Dual Nano Switch with Energy Metering</label>
<description><![CDATA[
Dual Nano Switch with Energy Metering<br /> <h1>Overview</h1><p>Fantech Dual Nano Switch is a Z-Wave Smart Switch specifically used to enable Z-Wave command and control (on/off) of any wall switches. <br />In the event of power failure, non-volatile memory retains all programmed information relating to the unit’s operating status. <br />It can connect to 2 external manual switches to control the load ON/OFF independently. Its surface has a pin socket, which can be used for connecting to the touch panel, so you can also use the touch panel to control the Dual Nano Switch. <br />The Dual Nano Switch is also a security Z-Wave device and supports Over The Air (OTA) feature for the products firmware upgrade.</p> <br /> <h2>Inclusion Information</h2><p>If you want your In-Wall Smart Switch (Dual) as a non-secure device in your Z-Wave network,press the Action Button once on In-Wall Smart Switch (Dual) when you pair it to your gateway. Ifinclusion is successful, the green LED will be on for 2 seconds, and then return to a solidindication. If inclusion is unsuccessful, the red LED will be on for 2 seconds and then return to acolourful gradient.</p> <br /> <h2>Exclusion Information</h2><p>If at some stage, your primary controller is missing or inoperable, you may wish to reset all ofyour In-Wall Smart Switch (Dual)’s settings to their factory defaults. To do this, press and holdthe Action Button for 20 seconds and then release it. Your In-Wall Smart Switch (Dual) will nowbe reset to its original settings, and the green LED will be solid for 2 seconds and then remain thecolourful gradient status as a confirmation.</p>
Dual Nano Switch with Energy Metering<br /> <h1>Overview</h1><p>Fantech Dual Nano Switch is a Z-Wave Smart Switch specifically used to enable Z-Wave command and control (on/off) of any wall switches.</p><p>In the event of power failure, non-volatile memory retains all programmed information relating to the unit’s operating status.</p><p>It can connect to 2 external manual switches to control the load ON/OFF independently. Its surface has a pin socket, which can be used for connecting to the touch panel, so you can also use the touch panel to control the Dual Nano Switch.</p><p>The Dual Nano Switch is also a security Z-Wave device and supports Over The Air (OTA) feature for the products firmware upgrade.</p> <br /> <h2>Inclusion Information</h2><p>If you want your In-Wall Smart Switch (Dual) as a non-secure device in your Z-Wave network,press the Action Button once on In-Wall Smart Switch (Dual) when you pair it to your gateway. Ifinclusion is successful, the green LED will be on for 2 seconds, and then return to a solidindication. If inclusion is unsuccessful, the red LED will be on for 2 seconds and then return to acolourful gradient.</p> <br /> <h2>Exclusion Information</h2><p>If at some stage, your primary controller is missing or inoperable, you may wish to reset all ofyour In-Wall Smart Switch (Dual)’s settings to their factory defaults. To do this, press and holdthe Action Button for 20 seconds and then release it. Your In-Wall Smart Switch (Dual) will nowbe reset to its original settings, and the green LED will be solid for 2 seconds and then remain thecolourful gradient status as a confirmation.</p> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>WallSwitch</category>
@ -135,7 +135,7 @@ Dual Nano Switch with Energy Metering<br /> <h1>Overview</h1><p>Fantech Dual Nan
<property name="vendor">Fantem</property>
<property name="modelId">FT132</property>
<property name="manufacturerId">016A</property>
<property name="manufacturerRef">0003:008C,0203:0084</property>
<property name="manufacturerRef">0003:0011,0003:008C,0203:0084</property>
<property name="dbReference">852</property>
<property name="defaultAssociations">1</property>
</properties>