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

pull/1969/head
openHAB Build Server 2022-10-23 03:38:05 +00:00
parent e5fa242342
commit cee9b45b2a
19 changed files with 363 additions and 154 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_bindings/hue/readme.md
View File

@ -16,15 +16,15 @@ install: auto
# Philips Hue Binding
This binding integrates the [Philips Hue Lighting system](https://www.meethue.com).
The integration happens through the Hue bridge, which acts as an IP gateway to the ZigBee devices.
The integration happens through the Hue Bridge, which acts as an IP gateway to the ZigBee devices.
![Philips Hue](doc/hue.jpg)
## Supported Things
The Hue bridge is required as a "bridge" for accessing any other Hue device.
The Hue Bridge is required as a "bridge" for accessing any other Hue device.
It supports the ZigBee LightLink protocol as well as the upwards compatible ZigBee 3.0 protocol.
There are two types of Hue bridges, generally referred to as v1 (the rounded version) and v2 (the squared version).
There are two types of Hue Bridges, generally referred to as v1 (the rounded version) and v2 (the squared version).
Only noticeable difference between the two generation of bridges is the added support for Apple HomeKit in v2.
Both bridges are fully supported by this binding.
@ -32,7 +32,7 @@ Almost all available Hue devices are supported by this binding.
This includes not only the "Friends of Hue", but also products like the LivingWhites adapter.
Additionally, it is possible to use OSRAM Lightify devices as well as other ZigBee LightLink compatible products, including the IKEA TRÅDFRI lights (when updated).
Beside bulbs and luminaires the Hue binding also supports some ZigBee sensors. Currently only Hue specific sensors are tested successfully (Hue Motion Sensor and Hue Dimmer Switch).
Please note that the devices need to be registered with the Hue bridge before it is possible for this binding to use them.
Please note that the devices need to be registered with the Hue Bridge before it is possible for this binding to use them.
The Hue binding supports all seven types of lighting devices defined for ZigBee LightLink ([see page 24, table 2](https://www.nxp.com/docs/en/user-guide/JN-UG-3091.pdf).
These are:
@ -80,28 +80,35 @@ They are presented by the following ZigBee Device ID and _Thing type_:
The Hue Dimmer Switch has 4 buttons and registers as a Non-Colour Controller switch, while the Hue Tap (also 4 buttons) registers as a Non-Colour Scene Controller in accordance with the ZLL standard.
Also, Hue bridge support CLIP Generic Status Sensor and CLIP Generic Flag Sensor.
Also, Hue Bridge support CLIP Generic Status Sensor and CLIP Generic Flag Sensor.
These sensors save state for rules and calculate what actions to do.
CLIP Sensor set or get by JSON through IP.
Finally, the Hue binding also supports the groups of lights and rooms set up on the Hue bridge.
Finally, the Hue binding also supports the groups of lights and rooms set up on the Hue Bridge.
## Discovery
The Hue bridge is discovered through UPnP in the local network.
The Hue Bridge is discovered through mDNS in the local network.
Auto-discovery is enabled by default.
To disable it, you can add the following line to `<openHAB-conf>/services/runtime.cfg`:
```
discovery.hue:background=false
```
Once it is added as a Thing, its authentication button (in the middle) needs to be pressed in order to authorize the binding to access it.
Once the binding is authorized, it automatically reads all devices and groups that are set up on the Hue bridge and puts them into the Inbox.
Once the binding is authorized, it automatically reads all devices and groups that are set up on the Hue Bridge and puts them into the Inbox.
## Thing Configuration
The Hue bridge requires the IP address as a configuration value in order for the binding to know where to access it.
The Hue Bridge requires the IP address as a configuration value in order for the binding to know where to access it.
In the thing file, this looks e.g. like
```
Bridge hue:bridge:1 [ ipAddress="192.168.0.64" ]
```
A user to authenticate against the Hue bridge is automatically generated.
A user to authenticate against the Hue Bridge is automatically generated.
Please note that the generated user name cannot be written automatically to the `.thing` file, and has to be set manually.
The generated user name can be found, after pressing the authentication button on the bridge, with the following console command: `hue <bridgeUID> username`.
The user name can be set using the `userName` configuration value, e.g.:
@ -111,16 +118,18 @@ Bridge hue:bridge:1 [ ipAddress="192.168.0.64", userName="qwertzuiopasdfghjklyxc
```
| Parameter | Description |
|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| ipAddress | Network address of the Hue bridge. **Mandatory** |
| port | Port of the Hue bridge. Optional, default value is 80 or 443, derived from protocol, otherwise user-defined. |
| userName | Name of a registered Hue bridge user, that allows to access the API. **Mandatory** |
| pollingInterval | Seconds between fetching light values from the Hue bridge. Optional, the default value is 10 (min="1", step="1"). |
| sensorPollingInterval | Milliseconds between fetching sensor-values from the Hue bridge. A higher value means more delay for the sensor values, but a too low value can cause congestion on the bridge. Optional, the default value is 500. Default value will be considered if the value is lower than 50. Use 0 to disable the polling for sensors. |
|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| ipAddress | Network address of the Hue Bridge. **Mandatory**. |
| port | Port of the Hue Bridge. Optional, default value is 80 or 443, derived from protocol, otherwise user-defined. |
| protocol | Protocol to connect to the Hue Bridge ("http" or "https"), default value is "https"). |
| useSelfSignedCertificate | Use self-signed certificate for HTTPS connection to Hue Bridge. **Advanced**, default value is `true`. |
| userName | Name of a registered Hue Bridge user, that allows to access the API. **Mandatory** |
| pollingInterval | Seconds between fetching light values from the Hue Bridge. Optional, the default value is 10 (min="1", step="1"). |
| sensorPollingInterval | Milliseconds between fetching sensor-values from the Hue Bridge. A higher value means more delay for the sensor values, but a too low value can cause congestion on the bridge. Optional, the default value is 500. Default value will be considered if the value is lower than 50. Use 0 to disable the polling for sensors. |
### Devices
The devices are identified by the number that the Hue bridge assigns to them (also shown in the Hue App as an identifier).
The devices are identified by the number that the Hue Bridge assigns to them (also shown in the Hue App as an identifier).
Thus, all it needs for manual configuration is this single value like
```
@ -145,13 +154,13 @@ The following device types also have an optional configuration value to specify
| Parameter | Description |
|-----------|-------------------------------------------------------------------------------|
| lightId | Number of the device provided by the Hue bridge. **Mandatory** |
| lightId | Number of the device provided by the Hue Bridge. **Mandatory** |
| fadetime | Fade time in Milliseconds to a new state (min="0", step="100", default="400") |
### Groups
The groups are identified by the number that the Hue bridge assigns to them.
The groups are identified by the number that the Hue Bridge assigns to them.
Thus, all it needs for manual configuration is this single value like
```
@ -164,7 +173,7 @@ The group type also have an optional configuration value to specify the fade tim
| Parameter | Description |
|-----------|-------------------------------------------------------------------------------|
| groupId | Number of the group provided by the Hue bridge. **Mandatory** |
| groupId | Number of the group provided by the Hue Bridge. **Mandatory** |
| fadetime | Fade time in Milliseconds to a new state (min="0", step="100", default="400") |
@ -194,7 +203,7 @@ The devices support some of the following channels:
| last_updated | DateTime | This channel the date and time when the sensor was last updated. | 0820, 0830, 0840, 0850, 0106, 0107, 0302 |
| battery_level | Number | This channel shows the battery level. | 0820, 0106, 0107, 0302 |
| battery_low | Switch | This channel indicates whether the battery is low or not. | 0820, 0106, 0107, 0302 |
| scene | String | This channel activates the scene with the given ID String. The ID String of each scene is assigned by the Hue bridge. | bridge, group |
| scene | String | This channel activates the scene with the given ID String. The ID String of each scene is assigned by the Hue Bridge. | bridge, group |
To load a hue scene inside a rule for example, the ID of the scene will be required.
You can list all the scene IDs with the following console commands: `hue <bridgeUID> scenes` and `hue <groupThingUID> scenes`.
@ -381,11 +390,3 @@ if (receivedEvent == "1000.0")) {
//do stuff
}
```
### UPnP Discovery: Inbox 'Grace Period'
The Hue Bridge can sometimes be late in sending its UPnP 'ssdp:alive' notifications even though it has not really gone offline.
This means that the Hue Bridge could be repeatedly removed from, and (re)added to, the InBox.
Which would lead to confusion in the UI, and repeated logger messages.
To prevent this, the binding tells the OpenHAB core to wait for a further period of time ('grace period') before actually removing the Bridge from the Inbox.
The 'grace period' has a default value of 50 seconds, but it can be fine tuned in the main UI via Settings | Bindings | Hue | Configure.

8
_addons_bindings/zwave/doc/aeon/zw099_0_0.md
View File

@ -40,8 +40,8 @@ The following table summarises the channels available for the ZW099 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Dimmer | switch_dimmer | switch_dimmer | DimmableLight | Dimmer |
| Power Consumption (kWh) | meter_kwh | meter_kwh | Energy | Number |
| Energy Consumption (watts) | meter_watts | meter_watts | Energy | Number |
| Electric meter (kWh) | meter_kwh | meter_kwh | Energy | Number |
| Electric meter (watts) | meter_watts | meter_watts | Energy | Number |
| Night mode color | color_color | color_color | ColorLight | Color |
### Dimmer
@ -50,12 +50,12 @@ The brightness channel allows to control the brightness of a light.
The ```switch_dimmer``` channel is of type ```switch_dimmer``` and supports the ```Dimmer``` item and is in the ```DimmableLight``` category.
### Power Consumption (kWh)
### Electric meter (kWh)
Indicates the energy consumption (kWh).
The ```meter_kwh``` channel is of type ```meter_kwh``` and supports the ```Number``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device.
### Energy Consumption (watts)
### Electric meter (watts)
Indicates the instantaneous power consumption.
The ```meter_watts``` channel is of type ```meter_watts``` and supports the ```Number``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device.

59
_addons_bindings/zwave/doc/ecobright/ecodim07_0_0.md
View File

@ -1,30 +1,60 @@
---
layout: documentation
title: EcoDim07 - ZWave
title: ECO-DIM.06 or ECO-DIM.07 - ZWave
---
{% include base.html %}
# EcoDim07 Smart Dimmer Switch 200W LED
This describes the Z-Wave device *EcoDim07*, manufactured by *EcoBright* with the thing type UID of ```ecobright_ecodim07_00_000```.
# ECO-DIM.06 or ECO-DIM.07 Smart Dimmer LED
This describes the Z-Wave device *ECO-DIM.06 or ECO-DIM.07*, manufactured by *EcoBright* with the thing type UID of ```ecobright_ecodim07_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.
![EcoDim07 product image](https://opensmarthouse.org/zwavedatabase/1114/image/)
![ECO-DIM.06 or ECO-DIM.07 product image](https://opensmarthouse.org/zwavedatabase/1114/image/)
The EcoDim07 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.
The ECO-DIM.06 or ECO-DIM.07 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
ECO-DIM.06: Plug-in dimmer Z-Wave 0-100W
Plug the Z-Wave plug-in dimmer into the socket and insert the euro plug of your LED lamp into this plug-in dimmer. You can then dim the LED lamps and press on/off with the push/turn button. Unique is the MIN adjustment option, with which you can set the minimum light level yourself!
ECO-DIM.07: Smart LED dimmer Z-Wave 0-200W
Remotely controlled multi level push / turn dimmer that can be controlled through Z-Wave and Zigbee (by setting a hardware switch). The dimmer is suitable for 0-200W LED lights where the MIN and MAX values can be set with hardware dials. The dimmer can be installed in a 2 wire setup (no N-wire required) and has a soft start system.
### Inclusion Information
ECO-DIM.06:
1. Step 1. Remove the device from a previous Z-Wave network if it has already been added to one, otherwise pairing mode will be fail.
2. Step 2. From your Z-Wave Controller interface, choose to add lighting and enter the pairing mode
3. Step 3. Double Press the reset button.
4. Step 4. The indicator will start blinking blue and will stay solid for 10s when pairing succeeds. Timeout 15mins.
ECO-DIM.07:
Make sure the right switch is set to Z-Wave. Power on the dimmer, press and hold the reset button for over 4 seconds.
### Exclusion Information
ECO-DIM.06:
Method 1. From your Z-Wave hub interface, choose to delete or reset the device as instructed.
Method 2. Remove from the Device, see below instructions.
* Step 1. Press the reset button for 3 times.
* Step 2. The indicator will start blinking purple and will stay solid for 10s when removing is completed. Timeout 3mins.
ECO-DIM.07:
There are two exclusion methods:
1. Exclusion from the primary controller / gateway:
@ -49,11 +79,13 @@ Switch on the lights with the push / turn button. When the lights are on put a s
## Channels
The following table summarises the channels available for the EcoDim07 -:
The following table summarises the channels available for the ECO-DIM.06 or ECO-DIM.07 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Dimmer | switch_dimmer | switch_dimmer | DimmableLight | Dimmer |
| Electric meter (watts) | meter_watts | meter_watts | Energy | Number |
| Electric meter (kWh) | meter_kwh | meter_kwh | Energy | Number |
### Dimmer
The brightness channel allows to control the brightness of a light.
@ -61,11 +93,21 @@ The brightness channel allows to control the brightness of a light.
The ```switch_dimmer``` channel is of type ```switch_dimmer``` and supports the ```Dimmer``` item and is in the ```DimmableLight``` category.
### Electric meter (watts)
Indicates the instantaneous power consumption.
The ```meter_watts``` channel is of type ```meter_watts``` and supports the ```Number``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device.
### Electric meter (kWh)
Indicates the energy consumption (kWh).
The ```meter_kwh``` channel is of type ```meter_kwh``` and supports the ```Number``` item and is in the ```Energy``` 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 2 configuration parameters available in the EcoDim07.
The following table provides a summary of the 2 configuration parameters available in the ECO-DIM.06 or ECO-DIM.07.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
@ -111,7 +153,7 @@ This parameter has the configuration ID ```config_2_1``` and is of type ```INTEG
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 EcoDim07 supports 1 association group.
The ECO-DIM.06 or ECO-DIM.07 supports 1 association group.
### Group 1: Lifeline
@ -145,6 +187,7 @@ Association group 1 supports 1 node.
### Documentation Links
* [Smart Dimmer Switch 200W LED Manual](https://opensmarthouse.org/zwavedatabase/1114/reference/EcoDim.pdf)
* [ECO-DIM.06 manual](https://opensmarthouse.org/zwavedatabase/1114/reference/z-wave-stekkerdimmer-eco-dim.06-handleiding.pdf)
---

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

@ -323,7 +323,7 @@ This parameter has the configuration ID ```config_27_1``` and is of type ```INTE
S1 switch - scenes sent
This parameter determines which actions result in sending scene IDs assigned to them
The following option values may be configured, in addition to values in the range 0 to 15 -:
The following option values may be configured -:
| Value | Description |
|--------|-------------|
@ -342,7 +342,7 @@ This parameter has the configuration ID ```config_28_1``` and is of type ```INTE
S2 switch - scenes sent
This parameter determines which actions result in sending scene IDs assigned to them
The following option values may be configured, in addition to values in the range 0 to 15 -:
The following option values may be configured -:
| Value | Description |
|--------|-------------|

30
_addons_bindings/zwave/doc/kwikset/ged1800_0_0.md
View File

@ -136,18 +136,18 @@ Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|-------|-------|-------------|
| 31 | Buzzer | Internal Buzzer |
| 31 | Auto Lock | Automatically re-locks door 30 seconds after unlocking. |
| 31 | Status LED | Door lock status LED blinks every 6 seconds |
| 33 | SKU (1st half) | First 4 byes of SKU |
| 31 | Auto Lock | Automatically re-locks door 30 seconds after unlocking. |
| 31 | Buzzer | Internal Buzzer |
| 33 | SKU (1st half) | First 4 bytes of SKU |
| 34 | SKU (2nd half) | Last 4 bytes of SKU |
| 40 | Factory Default | Reset to factory default settings |
| | Lock Timeout | Sets the time after which the door will auto lock |
### Parameter 31: Buzzer
### Parameter 31: Status LED
Internal Buzzer
Internal buzzer enabled.  Factory default is ON.  It is recommended that the buzzer is left ON during programming.
Door lock status LED blinks every 6 seconds
Door lock status LED blinks every 6 seconds.  Factory default is ON.
The following option values may be configured -:
| Value | Description |
@ -157,7 +157,7 @@ The following option values may be configured -:
The manufacturer defined default value is ```1``` (ON).
This parameter has the configuration ID ```config_31_1``` and is of type ```INTEGER```.
This parameter has the configuration ID ```config_31_1_00000001``` and is of type ```INTEGER```.
This is a read only parameter.
@ -174,14 +174,14 @@ The following option values may be configured -:
The manufacturer defined default value is ```0``` (OFF).
This parameter has the configuration ID ```config_31_1_01000000``` and is of type ```INTEGER```.
This parameter has the configuration ID ```config_31_1_00000002``` and is of type ```INTEGER```.
This is a read only parameter.
### Parameter 31: Status LED
### Parameter 31: Buzzer
Door lock status LED blinks every 6 seconds
Door lock status LED blinks every 6 seconds.  Factory default is ON.
Internal Buzzer
Internal buzzer enabled.  Factory default is ON.  It is recommended that the buzzer is left ON during programming.
The following option values may be configured -:
| Value | Description |
@ -191,13 +191,13 @@ The following option values may be configured -:
The manufacturer defined default value is ```1``` (ON).
This parameter has the configuration ID ```config_31_1_10000000``` and is of type ```INTEGER```.
This parameter has the configuration ID ```config_31_1_00000004``` and is of type ```INTEGER```.
This is a read only parameter.
### Parameter 33: SKU (1st half)
First 4 byes of SKU
First 4 bytes of SKU
The configuration parameters 33 and 34 are used to set and get the SKU part numbers. The SKU is made up of 8 bytes. Each parameter consists of four bytes of data. Parameter 33 contains the first four most significant bytes of the SKU, while parameter 34 contains the four least significant bytes of the SKU.
When setting the SKU, it must be done in two set commands, one for each parameter. The order of programming the SKU does not matter. Setting parameter 33 will program the first four bytes of the SKU. Setting parameter 34 will program the last 4 bytes of the SKU. Most printable values are accepted for the set command.
@ -207,7 +207,7 @@ Values in the range 32 to 126 may be set.
The manufacturer defined default value is ```32```.
This parameter has the configuration ID ```config_33_4``` and is of type ```INTEGER```.
This parameter has the configuration ID ```config_33_4_7FFF0000``` and is of type ```INTEGER```.
### Parameter 34: SKU (2nd half)
@ -222,7 +222,7 @@ Values in the range 32 to 126 may be set.
The manufacturer defined default value is ```32```.
This parameter has the configuration ID ```config_34_4``` and is of type ```INTEGER```.
This parameter has the configuration ID ```config_34_4_0000FFFF``` and is of type ```INTEGER```.
### Parameter 40: Factory Default

6
_addons_bindings/zwave/doc/kwikset/ged2150_0_0.md
View File

@ -53,6 +53,7 @@ The following table summarises the channels available for the GED2150 -:
| Alarm (access) | alarm_access | alarm_access | Door | Switch |
| Alarm (burglar) | alarm_burglar | alarm_burglar | Door | Switch |
| Alarm (power) | alarm_power | alarm_power | Energy | Switch |
| Alarm (raw) | alarm_raw | alarm_raw | | String |
| Battery Level | battery-level | system.battery_level | Battery | Number |
| Clock Time Offset | time_offset | time_offset | Time | Number |
@ -103,6 +104,11 @@ The following state translation is provided for this channel to the ```Switch```
| OFF | OK |
| ON | Alarm |
### Alarm (raw)
Provides alarm parameters as json string.
The ```alarm_raw``` channel is of type ```alarm_raw``` and supports the ```String``` item. This is a read only channel so will only be updated following state changes from the device.
This channel sets, and provides the alarm state as a JSON string. It is designed for use in rules.
### 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.

26
_addons_bindings/zwave/doc/simontech/iomastersimon_0_0.md
View File

@ -68,30 +68,12 @@ The following table summarises the channels available for the 10000306-039 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Dimmer | switch_dimmer | switch_dimmer | DimmableLight | Dimmer |
| Scene Number | scene_number | scene_number | | Number |
| Blinds Control | blinds_control | blinds_control | Blinds | Rollershutter |
### Dimmer
The brightness channel allows to control the brightness of a light.
It is also possible to switch the light on and off.
### Blinds Control
Provides start / stop control of blinds.
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 |
The ```blinds_control``` channel is of type ```blinds_control``` and supports the ```Rollershutter``` item and is in the ```Blinds``` category.

14
_addons_bindings/zwave/doc/zooz/zen30_0_0.md
View File

@ -114,12 +114,11 @@ The ```switch_binary1``` channel is of type ```switch_binary``` and supports the
## Device Configuration
The following table provides a summary of the 29 configuration parameters available in the ZEN30.
The following table provides a summary of the 28 configuration parameters available in the ZEN30.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|-------|-------|-------------|
| 0 | Enable/Disable Scene Control - Relay Button | Enable or disable scene control functionality for quick double tap triggers on the relay button. |
| 1 | LED Indicator Mode for Dimmer | LED Indicator Mode for Dimmer |
| 2 | LED Indicator Control for Relay | LED Indicator Control for Relay |
| 3 | LED Indicator Color for Dimmer | Choose the color of the LED indicators for the dimmer |
@ -149,17 +148,6 @@ Detailed information on each parameter can be found in the sections below.
| 29 | Scene Control - Relay Button | Enable (default) or disable scene control functionality for quick double tap triggers on the relay button. |
| 30 | Programming on the Dimmer Paddles | Enable or disable programming functionality on the dimmer paddles. If this setting is disabled, then inclusion, exclusion, smart bulb mode no longer work when dimmer paddles are activated (factory reset and scene control will still work) - that means you |
### Parameter 0: Enable/Disable Scene Control - Relay Button
Enable or disable scene control functionality for quick double tap triggers on the relay button.
Values in the range 0 to 1 may be set.
The manufacturer defined default value is ```1```.
This parameter has the configuration ID ```config_0_1``` and is of type ```INTEGER```.
### Parameter 1: LED Indicator Mode for Dimmer
LED Indicator Mode for Dimmer

34
_addons_ios/homekit/readme.md
View File

@ -258,6 +258,38 @@ Examples:
Dimmer dimmer_light_3 "Dimmer Light 3" {homekit="Lighting, Lighting.Brightness" [dimmerMode="filterOnExceptBrightness100"]}
```
### Color Temperature
Color temperature can be represented various ways in OpenHAB. Given the base bulb configured like this:
```xtend
Group gLight "CCT Light" { homekit="Lighting" }
Switch light_switch (gLight) { homekit="Lighting.OnState" }
```
The color temperature might be configured in any of these ways:
```xtend
// Number item presumed in mireds
Number light_temp (gLight) { homekit="Lighting.ColorTemperature" }
// Number item explicitly in mireds
Number:Temperature light_temp "Temp [%.0f mired]" { homekit="Lighting.ColorTemperature" }
// Number item explicitly in Kelvin
Number:Temperature light_temp "Temp [%.0f K]" { homekit="Lighting.ColorTemperature" }
// Dimmer item, with allowed range given in mireds
Dimmer light_temp { homekit="Lighting.ColorTemperature"[ minValue=50, maxValue=400 ]}
// Dimmer item, with allowed range given in Kelvin
Dimmer light_temp { homekit="Lighting.ColorTemperature"[ minValue="2700 K", maxValue="5000 K" ]}
// Dimmer item, where 0% represents "warm" instead of "cool" (i.e. if it's backed by a channel
// that's ultimately interpreting the value in Kelvin instead of mireds)
Dimmer light_temp { homekit="Lighting.ColorTemperature"[ minValue="2700 K", maxValue="5000 K", inverted=true ]}
```
### Windows Covering (Blinds) / Window / Door
HomeKit Windows Covering, Window and Door accessory types have following mandatory characteristics:
@ -689,7 +721,7 @@ Support for this is planned for the future release of openHAB HomeKit binding.
| | | Hue | Dimmer, Color | Hue |
| | | Saturation | Dimmer, Color | Saturation in % (1-100) |
| | | Brightness | Dimmer, Color | Brightness in % (1-100). See "Usage of dimmer modes" for configuration details. |
| | | ColorTemperature | Number | Color temperature represented in reciprocal megaKelvin. The default value range is from 50 to 400. Color temperature should not be used in combination with hue, saturation and brightness. It supports following configuration parameters: minValue, maxValue |
| | | ColorTemperature | Number, Dimmer | Color temperature. If the item is a Number with no units, it is represented in mireds. The default value range is from 50 to 400 (2500 K to 20,000 K). If the item is a Dimmer, it will be transformed linearly to mireds. Color temperature should not be used in combination with hue, saturation and brightness. It supports following configuration parameters: minValue, maxValue, inverted |
| Fan | | | | Fan |
| | ActiveStatus | | Switch, Dimmer | Accessory current working status. A value of "ON"/"OPEN" indicates that the accessory is active and is functioning without any errors. |
| | | CurrentFanState | Number | Current fan state. values: 0=INACTIVE, 1=IDLE, 2=BLOWING AIR |

29
_thing_types/org.openhab.binding.hue/src/main/resources/OH-INF/thing/bridge.xml
View File

@ -6,7 +6,7 @@
<!-- Hue Bridge -->
<bridge-type id="bridge">
<label>Hue Bridge</label>
<description>The Hue bridge represents the Philips Hue bridge.</description>
<description>The Hue Bridge represents the Philips Hue Bridge.</description>
<channels>
<channel id="scene" typeId="scene"/>
@ -21,26 +21,41 @@
<parameter name="ipAddress" type="text" required="true">
<context>network-address</context>
<label>Network Address</label>
<description>Network address of the Hue bridge.</description>
<description>Network address of the Hue Bridge.</description>
</parameter>
<parameter name="port" type="integer" required="false" min="1" max="65535">
<label>Port</label>
<description>Port of the Hue bridge.</description>
<description>Port of the Hue Bridge.</description>
</parameter>
<parameter name="protocol" type="text">
<label>Protocol</label>
<description>Protocol to connect to the Hue Bridge (http or https).</description>
<default>https</default>
<options>
<option value="http">HTTP</option>
<option value="https">HTTPS</option>
</options>
</parameter>
<parameter name="useSelfSignedCertificate" type="boolean">
<label>Use Self-Signed Certificate</label>
<description>Use self-signed certificate for HTTPS connection to Hue Bridge.</description>
<default>true</default>
<advanced>true</advanced>
</parameter>
<parameter name="userName" type="text">
<context>password</context>
<label>Username</label>
<description>Name of a registered Hue bridge user, that allows to access the API.</description>
<description>Name of a registered Hue Bridge user, that allows to access the API.</description>
</parameter>
<parameter name="pollingInterval" type="integer" min="1" step="1" unit="s">
<label>Polling Interval</label>
<description>Seconds between fetching values from the Hue bridge. Default is 10.</description>
<description>Seconds between fetching values from the Hue Bridge. Default is 10.</description>
<default>10</default>
</parameter>
<parameter name="sensorPollingInterval" type="integer" min="0" step="1" unit="ms">
<label>Sensor Polling Interval</label>
<description>Milliseconds between fetching sensor-values from the Hue bridge. A higher value means more delay for
the sensor values, but a too low value can cause congestion on the Hue bridge. Use 0 to disable the polling for
<description>Milliseconds between fetching sensor-values from the Hue Bridge. A higher value means more delay for
the sensor values, but a too low value can cause congestion on the Hue Bridge. Use 0 to disable the polling for
sensors. Default is 500.</description>
<default>500</default>
</parameter>

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

@ -22,13 +22,13 @@ Smart Dimmer 6<br /> <h1>Overview</h1><p>Aeotec Smart Dimmer 6 is a low-cost Z-W
</properties>
</channel>
<channel id="meter_kwh" typeId="meter_kwh">
<label>Power Consumption (kWh)</label>
<label>Electric meter (kWh)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;type=E_KWh</property>
</properties>
</channel>
<channel id="meter_watts" typeId="meter_watts">
<label>Energy Consumption (watts)</label>
<label>Electric meter (watts)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;type=E_W</property>
</properties>

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

@ -0,0 +1,134 @@
<?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_firefighter5_00_000" listed="false">
<label>FF-ZWAVE5-ECO Firefighter Audio Detector</label>
<description><![CDATA[
Firefighter Audio Detector<br /> <h1>Overview</h1><p><strong>Overview:</strong></p> <p>The Ecolink Audio detector sensor listens to existing smoke or CO detectors in the home and sends signal to your Z-Wave network. In most homes, with hardwired interconnected smoke detectors, only one sensor is needed for whole home coverage.</p> <ul><li>provides fire and CO (carbon monoxide) status</li> <li>Transmits Fire and CO alarm status</li> <li>Reports tamper condition when cover is open</li> </ul><p>This device implements Z-Wave Plus functionality, Network Wide Inclusion, and Explorer frames.  This device is asleep most of the time but can respond to queries on a Wake Up Notification; however for test purposes, the device will stay awake while tampered for testing Z-Wave Plus command class functionality.</p> <p><strong>LED Status:</strong></p> <p>The FireFighter sensor is equipped with a multi-color LED.  The state of the LED will change based on the state of the device.</p> <table><tr><td>Insert Battery</td> <td>One (or two, if in CO mode) RED blink, then one GREEN blink</td> </tr><tr><td>Device not included </td> <td>Green light breathing (slow blink)</td> </tr><tr><td>Learn button pressed</td> <td>Solid Yellow (red+green) while in learn mode</td> </tr><tr><td>Sound detected</td> <td>Flash YELLOW for the duration of the sound</td> </tr><tr><td>Fire Alarm Detected</td> <td>Solid RED for 3 seconds, then blink red while tone detected</td> </tr><tr><td>Case Opened</td> <td>Red/Green breathing until case closed (while added to a network)</td> </tr></table><p><br /><strong>CO Alarm Detection:</strong></p> <p>In addition to smoke alarm detection, the FireFighter sensor can detect the presence of a carbon monoxide alarm. By default, the sensor is not guaranteed to detect a CO alarm.  The device can be configured to more reliably detect a CO alarm in exchange for a reduced battery life. This mode can be changed by holding down the tamper switch and the learn button for 10 seconds. The device should then be reset (remove battery and replace) in order to determine the current device setting.</p> <p>RED + GREEN           = Device will not reliably detect CO, but standard battery life</p> <p>RED + RED + GREEN = Device will more reliably detect CO, but with reduced battery life</p> <p><strong>Factory Default:</strong></p> <p>The FireFighter sensor can be restored back to factory default settings which will remove its Z-Wave Plus node ID from the sensor (but not the controller) with the following steps.  Please use this procedure only when the network primary controller is missing or otherwise inoperable.</p> <ol><li>Put the battery into the sensor</li> <li>Do no press the tamper switch</li> <li>Hold the learn button down for 10 seconds until the LED turns RED</li> <li>Release the learn button and wait for the sensor's green LED to "breath" on and off continuously. The sensor is now ready to be added to a Z-Wave Plus network, and all settings have been restored.</li> </ol><p><strong>Testing:</strong></p> <p>To test the RF transmission from the mounted position you can generate a tamper by removing the cover. This will send a signal to the controller. To test the audio detection, press and hold the smoke detector's test button. Ensure the FireFighter cover is on and that you wear hearing protection.</p> <br /> <h2>Inclusion Information</h2><p>Open the FireFighter case and press the learn button on the device for one second.  If the LED starts blinking continually, the sensor has not been added and you need to repeat the process after putting the controller into inclusion mode again.</p> <br /> <h2>Exclusion Information</h2><p>Open the FireFighter case and press the learn button on the device for one second.  If successfully removed from the Z-Wave Plus network, the device's Green LED should blink slowly and continuously.</p> <br /> <h2>Wakeup Information</h2><p>The sensor will wake up every so often to send a Wake-Up Notification to allow the life line master node controller that the sensor is now available for any queued messages that the controller may have for the sensor.  The time between Wake-Up Notifications can be configured with the Wake-Up Notification command class to be between 1 hour and 1 week with interval steps of 200 seconds.  The sensor will also send a wakeup notification whenever the case is closed.</p>
]]></description>
<category>SmokeDetector</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="sensor_general" typeId="sensor_general">
<label>Sensor (general)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_SENSOR_MULTILEVEL;type=GENERAL</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="alarm_burglar" typeId="alarm_burglar">
<label>Alarm (burglar)</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=BURGLAR</property>
</properties>
</channel>
<channel id="alarm_smoke" typeId="alarm_smoke">
<label>Alarm (smoke)</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=SMOKE</property>
</properties>
</channel>
<channel id="alarm_co" typeId="alarm_co">
<label>Alarm (CO)</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=CARBON_MONOXIDE</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_tamper" typeId="alarm_tamper">
<label>Tamper 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">Ecolink</property>
<property name="modelId">FF-ZWAVE5-ECO</property>
<property name="manufacturerId">014A</property>
<property name="manufacturerRef">0005:000F</property>
<property name="dbReference">1221</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: Mode: Smoke Alarm/Combo Smoke CO alarm</label>
<description><![CDATA[
Sensor Mode<br /> <h1>Overview</h1><p>Enables the sensor to detect smoke alarm signals from a smoke detector or alarm signals from a smoke alarm and carbon monoxide alarm combo device. Allowed parameter values:</p> <p>0xA5  = Smoke alarm detection only</p> <p>0xFF   = Smoke and carbon monoxide alarm detection</p>
]]></description>
<default>-91</default>
<options>
<option value="165">Smoke alarm detection only</option>
<option value="255">Smoke and carbon monoxide alarm detection</option>
</options>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Lifeline</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>Will receive unsolicited messages relating to Fire notifications, CO notifications, case tampering notifications, low-battery notifications, and temperature notifications.</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>

18
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/ecobright/ecodim07_0_0.xml
View File

@ -6,9 +6,9 @@
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="ecobright_ecodim07_00_000" listed="false">
<label>EcoDim07 Smart Dimmer Switch 200W LED</label>
<label>ECO-DIM.06 or ECO-DIM.07 Smart Dimmer LED</label>
<description><![CDATA[
Smart Dimmer Switch 200W LED<br /> <h1>Overview</h1><p>Remotely controlled multi level push / turn dimmer that can be controlled through Z-Wave and Zigbee (by setting a hardware switch). The dimmer is suitable for 0-200W LED lights where the MIN and MAX values can be set with hardware dials. The dimmer can be installed in a 2 wire setup (no N-wire required) and has a soft start system.</p> <br /> <h2>Inclusion Information</h2><p>Make sure the right switch is set to Z-Wave. Power on the dimmer, press and hold the reset button for over 4 seconds.</p> <br /> <h2>Exclusion Information</h2><p>There are two exclusion methods:</p> <p>1. Exclusion from the primary controller / gateway:</p> <p>Twice press the reset button, the dimmer will be set to exclusion mode, waiting to be excluded.</p> <p>2. Factory reset the dimmer (forcing it to be excluded from a network):</p> <p>Press and hold down the reset button for over 4 seconds, the dimmer will be reset to factory defaults after the BLUE LED indicator blinks.</p>
Smart Dimmer LED<br /> <h1>Overview</h1><p>ECO-DIM.06: Plug-in dimmer Z-Wave 0-100W</p><p>Plug the Z-Wave plug-in dimmer into the socket and insert the euro plug of your LED lamp into this plug-in dimmer. You can then dim the LED lamps and press on/off with the push/turn button. Unique is the MIN adjustment option, with which you can set the minimum light level yourself!</p><p>ECO-DIM.07: Smart LED dimmer Z-Wave 0-200W</p><p>Remotely controlled multi level push / turn dimmer that can be controlled through Z-Wave and Zigbee (by setting a hardware switch). The dimmer is suitable for 0-200W LED lights where the MIN and MAX values can be set with hardware dials. The dimmer can be installed in a 2 wire setup (no N-wire required) and has a soft start system.</p> <br /> <h2>Inclusion Information</h2><p>ECO-DIM.06:</p><ol><li>Step 1. Remove the device from a previous Z-Wave network if it has already been added to one, otherwise pairing mode will be fail.</li><li>Step 2. From your Z-Wave Controller interface, choose to add lighting and enter the pairing mode</li><li>Step 3. Double Press the reset button.</li><li>Step 4. The indicator will start blinking blue and will stay solid for 10s when pairing succeeds. Timeout 15mins.</li></ol><p>ECO-DIM.07:<br /></p><p>Make sure the right switch is set to Z-Wave. Power on the dimmer, press and hold the reset button for over 4 seconds.</p> <br /> <h2>Exclusion Information</h2><p>ECO-DIM.06:</p><p>Method 1. From your Z-Wave hub interface, choose to delete or reset the device as instructed.</p><p>Method 2. Remove from the Device, see below instructions.</p><ul><li>Step 1. Press the reset button for 3 times.</li><li>Step 2. The indicator will start blinking purple and will stay solid for 10s when removing is completed. Timeout 3mins.</li></ul><p><br /></p><p>ECO-DIM.07:</p><p>There are two exclusion methods:</p> <p>1. Exclusion from the primary controller / gateway:</p> <p>Twice press the reset button, the dimmer will be set to exclusion mode, waiting to be excluded.</p> <p>2. Factory reset the dimmer (forcing it to be excluded from a network):</p> <p>Press and hold down the reset button for over 4 seconds, the dimmer will be reset to factory defaults after the BLUE LED indicator blinks.</p> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>WallSwitch</category>
@ -21,12 +21,24 @@ Smart Dimmer Switch 200W LED<br /> <h1>Overview</h1><p>Remotely controlled multi
<property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL</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>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">EcoBright</property>
<property name="modelId">EcoDim07</property>
<property name="modelId">ECO-DIM.06 or ECO-DIM.07</property>
<property name="manufacturerId">0431</property>
<property name="manufacturerRef">0202:0001,0202:0002</property>
<property name="dbReference">1114</property>

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

@ -230,6 +230,7 @@ S1 switch - scenes sent<br /> <h1>Overview</h1><p>This parameter determines whic
<option value="4">Key pressed 3 times</option>
<option value="8">Key Hold Down and Key Released</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_29_1" type="integer" groupName="configuration">
@ -245,6 +246,7 @@ S2 switch - scenes sent<br /> <h1>Overview</h1><p>This parameter determines whic
<option value="4">Key pressed 3 times</option>
<option value="8">Key Hold Down and Key Released</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_30_1" type="integer" groupName="configuration">

60
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/kwikset/ged1800_0_0.xml
View File

@ -58,33 +58,7 @@ SmartCode 10 Touchpad Electronic Deadbolt<br /> <h1>Overview</h1><ul><li>Dramati
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_31_1" type="integer" groupName="configuration" readOnly="true">
<label>31: Buzzer</label>
<description><![CDATA[
Internal Buzzer<br /> <h1>Overview</h1><p>Internal buzzer enabled.  Factory default is ON.  It is recommended that the buzzer is left ON 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">
<parameter name="config_31_1_00000001" type="integer" groupName="configuration" readOnly="true">
<label>31: Status LED</label>
<description><![CDATA[
Door lock status LED blinks every 6 seconds<br /> <h1>Overview</h1><p>Door lock status LED blinks every 6 seconds.  Factory default is ON.</p>
@ -97,16 +71,42 @@ Door lock status LED blinks every 6 seconds<br /> <h1>Overview</h1><p>Door lock
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_33_4" type="integer" groupName="configuration">
<parameter name="config_31_1_00000002" 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_00000004" type="integer" groupName="configuration" readOnly="true">
<label>31: Buzzer</label>
<description><![CDATA[
Internal Buzzer<br /> <h1>Overview</h1><p>Internal buzzer enabled.  Factory default is ON.  It is recommended that the buzzer is left ON 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_33_4_7FFF0000" type="integer" groupName="configuration">
<label>33: SKU (1st half)</label>
<description><![CDATA[
First 4 byes of SKU<br /> <h1>Overview</h1><p>The configuration parameters 33 and 34 are used to set and get the SKU part numbers. The SKU is made up of 8 bytes. Each parameter consists of four bytes of data. Parameter 33 contains the first four most significant bytes of the SKU, while parameter 34 contains the four least significant bytes of the SKU.</p> <p>When setting the SKU, it must be done in two set commands, one for each parameter. The order of programming the SKU does not matter. Setting parameter 33 will program the first four bytes of the SKU. Setting parameter 34 will program the last 4 bytes of the SKU. Most printable values are accepted for the set command.</p> <p>When getting the SKU, it must be done in two get commands, one for each parameter. The order of getting the SKU does not matter. Getting parameter 33 will retrieve the first four bytes of the SKU. Getting parameter 34 will retrieve the last 4 bytes of the SKU.</p>
First 4 bytes of SKU<br /> <h1>Overview</h1><p>The configuration parameters 33 and 34 are used to set and get the SKU part numbers. The SKU is made up of 8 bytes. Each parameter consists of four bytes of data. Parameter 33 contains the first four most significant bytes of the SKU, while parameter 34 contains the four least significant bytes of the SKU.</p> <p>When setting the SKU, it must be done in two set commands, one for each parameter. The order of programming the SKU does not matter. Setting parameter 33 will program the first four bytes of the SKU. Setting parameter 34 will program the last 4 bytes of the SKU. Most printable values are accepted for the set command.</p> <p>When getting the SKU, it must be done in two get commands, one for each parameter. The order of getting the SKU does not matter. Getting parameter 33 will retrieve the first four bytes of the SKU. Getting parameter 34 will retrieve the last 4 bytes of the SKU.</p>
]]></description>
<default>32</default>
<advanced>true</advanced>
</parameter>
<parameter name="config_34_4" type="integer" groupName="configuration">
<parameter name="config_34_4_0000FFFF" type="integer" groupName="configuration">
<label>34: SKU (2nd half)</label>
<description><![CDATA[
Last 4 bytes of SKU<br /> <h1>Overview</h1><p>The configuration parameters 33 and 34 are used to set and get the SKU part numbers. The SKU is made up of 8 bytes. Each parameter consists of four bytes of data. Parameter 33 contains the first four most significant bytes of the SKU, while parameter 34 contains the four least significant bytes of the SKU.</p> <p>When setting the SKU, it must be done in two set commands, one for each parameter. The order of programming the SKU does not matter. Setting parameter 33 will program the first four bytes of the SKU. Setting parameter 34 will program the last 4 bytes of the SKU. Most printable values are accepted for the set command.</p> <p>When getting the SKU, it must be done in two get commands, one for each parameter. The order of getting the SKU does not matter. Getting parameter 33 will retrieve the first four bytes of the SKU. Getting parameter 34 will retrieve the last 4 bytes of the SKU.</p>

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

@ -38,6 +38,12 @@ SmartCode 10 Touchpad Electronic Deadbolt<br /> <h1>Overview</h1><ul><li>Compati
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=POWER_MANAGEMENT</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>

13
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/simontech/iomastersimon_0_0.xml
View File

@ -14,17 +14,12 @@ IO Master Simon 100<br /> <h1>Overview</h1><p>Do you need a Master that will all
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="switch_dimmer" typeId="switch_dimmer">
<label>Dimmer</label>
<channel id="blinds_control" typeId="blinds_control">
<label>Blinds Control</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>
<property name="binding:Command:StopMoveType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
<property name="binding:Command:UpDownType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
</properties>
</channel>
</channels>

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

@ -60,13 +60,6 @@ Dimmer &amp; Dry Contact Relay<br /> <h1>Overview</h1><p>Features</p> <ul><li>Ma
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_0_1" type="integer" groupName="configuration">
<label>0: Enable/Disable Scene Control - Relay Button</label>
<description>Enable or disable scene control functionality for quick double tap triggers on the relay button.</description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_1_1" type="integer" groupName="configuration">
<label>1: LED Indicator Mode for Dimmer</label>
<description><![CDATA[