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

pull/1131/head
openHAB Build Server 2019-10-16 18:54:57 +00:00
parent 71e0e6dd5e
commit e1045d0018
6 changed files with 12 additions and 786 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_addons_bindings/daikin/readme.md
View File

@ -103,7 +103,7 @@ Selection item=DaikinACUnit_Mode mappings=["AUTO"="Auto", "DEHUMIDIFIER"="Dehumi
Selection item=DaikinACUnit_Fan mappings=["AUTO"="Auto", "SILENCE"="Silence", "LEVEL_1"="Level 1", "LEVEL_2"="Level 2", "LEVEL_3"="Level 3", "LEVEL_4"="Level 4", "LEVEL_5"="Level 5"] visibility=[DaikinACUnit_Power==ON]
Text item=DaikinACUnit_IndoorTemperature
Text item=DaikinACUnit_OutdoorTemperature
# Additional items for BRP1B61
# Additional items for BRP15B61
Switch item=DaikinACUnit_Zone1 visibility=[DaikinACUnit_Power==ON]
Switch item=DaikinACUnit_Zone2 visibility=[DaikinACUnit_Power==ON]
Switch item=DaikinACUnit_Zone3 visibility=[DaikinACUnit_Power==ON]

61
_addons_bindings/zwave/doc/zwaveme/_4_38.md
View File

@ -1,61 +0,0 @@
---
layout: documentation
title: WeatherStation - ZWave
---
{% include base.html %}
# WeatherStation Based on Z-Wave.me Z-Uno
This describes the Z-Wave device *WeatherStation*, manufactured by *Z-Wave.Me* with the thing type UID of ```zwaveme__04_038```.
This version of the device is limited to firmware versions above 4.38
The device is in the category of *Sensor*, defining Device used to measure something.
The WeatherStation 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
### Wakeup Information
The WeatherStation 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.
## Channels
The following table summarises the channels available for the WeatherStation -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Temperature [Deprecated]| 0 | 0 | | |
### Temperature [Deprecated]
Channel type information on this channel is not found.
## 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 device does not support associations.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SENSOR_MULTILEVEL_V1| |
| COMMAND_CLASS_CONFIGURATION_V1| |
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1002).

141
_addons_bindings/zwave/doc/zwaveme/zuno_1_0.md
View File

@ -1,141 +0,0 @@
---
layout: documentation
title: ZUNO1S1D1AI1DI - ZWave
---
{% include base.html %}
# ZUNO1S1D1AI1DI ZUNO1S1D1AI1DI
This describes the Z-Wave device *ZUNO1S1D1AI1DI*, manufactured by *Z-Wave.Me* with the thing type UID of ```zwaveme_zuno_01_000```.
This version of the device is limited to firmware versions above 1.0
The ZUNO1S1D1AI1DI 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
Zuno with following Configuration
1.) Binary Switch
2.) Dimmer
3.) Temperatur
4.) Door open/close Contact
### Inclusion Information
Push 3 times
### Exclusion Information
Push 3 times
## Channels
The following table summarises the channels available for the ZUNO1S1D1AI1DI -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Switch | switch_binary | switch_binary | Switch | Switch |
| | | | | |
| Temperatur | temperature | temperature | | |
| Dimmer | switch_dimmer1 | switch_dimmer | DimmableLight | Dimmer |
| Dimmer | switch_dimmer2 | switch_dimmer | DimmableLight | Dimmer |
| Temperatur | temperature3 | temperature | | |
| | 4 | | | |
### Switch
Switch the power on and off.
The ```switch_binary``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
###
Channel type information on this channel is not found.
### Temperatur
Channel type information on this channel is not found.
### Dimmer
The brightness channel allows to control the brightness of a light.
It is also possible to switch the light on and off.
The ```switch_dimmer1``` channel is of type ```switch_dimmer``` and supports the ```Dimmer``` item and is in the ```DimmableLight``` category.
### Dimmer
The brightness channel allows to control the brightness of a light.
It is also possible to switch the light on and off.
The ```switch_dimmer2``` channel is of type ```switch_dimmer``` and supports the ```Dimmer``` item and is in the ```DimmableLight``` category.
### Temperatur
Channel type information on this channel is not found.
###
Channel type information on this channel is not found.
## 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 device does not support associations.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC|
| COMMAND_CLASS_SENSOR_MULTILEVEL_V1| |
| COMMAND_CLASS_SENSOR_MULTILEVEL_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_MULTI_CHANNEL_V2| |
| COMMAND_CLASS_CONFIGURATION_V1| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| |
#### Endpoint 1
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_BASIC_V1| Linked to BASIC|
| COMMAND_CLASS_SENSOR_MULTILEVEL_V1| |
#### Endpoint 2
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| Linked to BASIC|
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SENSOR_BINARY_V1| |
#### Endpoint 3
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_MULTILEVEL_V1| |
#### Endpoint 4
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC|
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/494).

172
_addons_bindings/zwave/doc/zwaveme/zunoswitch_2_11.md
View File

@ -1,172 +0,0 @@
---
layout: documentation
title: z_uno - ZWave
---
{% include base.html %}
# z_uno switch
This describes the Z-Wave device *z_uno*, manufactured by *Z-Wave.Me* with the thing type UID of ```zwaveme_zunoswitch_02_011```.
This version of the device is limited to firmware version 2.11
The device is in the category of *Power Outlet*, defining Small devices to be plugged into a power socket in a wall which stick there.
![z_uno product image](https://www.cd-jackson.com/zwave_device_uploads/916/916_default.jpg)
The z_uno 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
* relay switch
### Inclusion Information
Push 3 times
### Exclusion Information
Push 3 times
## Channels
The following table summarises the channels available for the z_uno -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Switch | switch_binary | switch_binary | Switch | Switch |
| Sensor (distance) | sensor_distance | sensor_distance | | |
| Switch 1 | switch_binary1 | switch_binary | Switch | Switch |
| Switch 2 | switch_binary2 | switch_binary | Switch | Switch |
| Switch 3 | switch_binary3 | switch_binary | Switch | Switch |
| Switch 4 | switch_binary4 | switch_binary | Switch | Switch |
| Switch 5 | switch_binary5 | switch_binary | Switch | Switch |
| Switch 6 | switch_binary6 | switch_binary | Switch | Switch |
### Switch
Switch the power on and off.
The ```switch_binary``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Sensor (distance)
Channel type information on this channel is not found.
### Switch 1
Switch the power on and off.
The ```switch_binary1``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Switch 2
Switch the power on and off.
The ```switch_binary2``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Switch 3
Switch the power on and off.
The ```switch_binary3``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Switch 4
Switch the power on and off.
The ```switch_binary4``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Switch 5
Switch the power on and off.
The ```switch_binary5``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Switch 6
Switch the power on and off.
The ```switch_binary6``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
## Device Configuration
The device has no configuration parameters defined.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The device does not support associations.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| |
| COMMAND_CLASS_SENSOR_MULTILEVEL_V7| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_MULTI_CHANNEL_V2| |
| COMMAND_CLASS_CONFIGURATION_V1| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| |
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
#### Endpoint 1
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC|
#### Endpoint 2
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC|
#### Endpoint 3
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC|
#### Endpoint 4
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC|
#### Endpoint 5
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC|
#### Endpoint 6
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| Linked to BASIC|
### Documentation Links
* [Z-Wave.Me Z-Uno Module](https://www.cd-jackson.com/zwave_device_uploads/916/ZMExZUNOM.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/916).

404
_addons_bindings/zwave/doc/zwaveme/zunoweather_2_15.md
View File

@ -1,404 +0,0 @@
---
layout: documentation
title: Z-Uno Weather 2.1.5.1 - ZWave
---
{% include base.html %}
# Z-Uno Weather 2.1.5.1 Weather Station with Temperature, Pressure, Light-Level and Humidity
This describes the Z-Wave device *Z-Uno Weather 2.1.5.1*, manufactured by *Z-Wave.Me* with the thing type UID of ```zwaveme_zunoweather_02_015```.
This version of the device is limited to firmware versions above 2.15
The device is in the category of *Sensor*, defining Device used to measure something.
The Z-Uno Weather 2.1.5.1 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
### Inclusion Information
Press 3-Times Service button. Refer to https://z-uno.z-wave.me/getting-started/include-in-network.
### Exclusion Information
Refer to https://z-uno.z-wave.me/getting-started/include-in-network.
### Wakeup Information
The Z-Uno Weather 2.1.5.1 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.
Press Service Button once.
## Channels
The following table summarises the channels available for the Z-Uno Weather 2.1.5.1 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Temperature | temperature | temperature | | |
| Humidity | humidity | humidity | | |
| Luminance | luminance | luminance | | |
| Barometric pressure | barpressure | barpressure | | |
| Battery Level | battery-level | system.battery_level | Battery | Number |
### Temperature
Temperature in Degrees Celsius.
Channel type information on this channel is not found.
### Humidity
Humidity in percent.
Channel type information on this channel is not found.
### Luminance
Luminance in lux.
Channel type information on this channel is not found.
### Barometric pressure
Pressure in kilopascal.
Channel type information on this channel is not found.
### Battery Level
Represents the battery level as a percentage (0-100%). Bindings for things supporting battery level in a different format (e.g. 4 levels) should convert to a percentage to provide a consistent battery level reading.
The ```system.battery-level``` channel is of type ```system.battery-level``` and supports the ```Number``` item and is in the ```Battery``` category.
This channel provides the battery level as a percentage and also reflects the low battery warning state. If the battery state is in low battery warning state, this will read 0%.
## Device Configuration
The following table provides a summary of the 18 configuration parameters available in the Z-Uno Weather 2.1.5.1.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|-------|-------|-------------|
| 1 | Debug Mode | Debug mode for on-the-fly changes |
| 2 | Service LED | Blink with service LED during operation |
| 3 | Security S0 | Enable or disable Security S0 during inclusion (requires re-inclusion) |
| 11 | Min. Waittime for Multilevel-Sensor Reports | Minimal time between Sensor Multilevel reports. |
| 12 | Legacy Sensor Binary | Change channel type from Notification to legacy Sensor Binary for compatibility. |
| 20 | OTA Confirmation | Confirmation of OTA operations |
| 64 | Luminance Resolution | Mode for luminance measurements. |
| 65 | Luminance Compensation | Compensation value for luminance. |
| 66 | Temperature Compensation | Compensation value for Temperature |
| 67 | Pressure Compensation | Compensation for barometric pressure. |
| 68 | Humidity Compensation | Compensation value for humidity. |
| 69 | Temperature Oversampling | Oversampling factor for temperature measurement. |
| 70 | Pressure Oversampling | Oversampling factor for pressure measurement |
| 71 | Humidity Oversampling | Oversampling factor for humidity measurement |
| 72 | Luminance Report Delta | Minimum delta to report luminance changes. |
| 73 | Temperature Report Delta | Minimum delta to report temperature changes. |
| 74 | Pressure Report Delta | Minimum delta to report pressure changes. |
| 75 | Humidity Report Delta | Minimum delta to report humidity changes. |
| | Wakeup Interval | Sets the interval at which the device will accept commands from the controller |
| | Wakeup Node | Sets the node ID of the device to receive the wakeup notifications |
### Parameter 1: Debug Mode
Debug mode for on-the-fly changes
Debug mode to apply channels, associations and power mode changes on the fly without exclusion-inclusion sequence. **Use for debugging only!**
Refer to https://z-uno.z-wave.me/z-wave/configuration-parameters/This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Disabled |
| 1 | Enabled |
The manufacturer defined default value is ```0``` (Disabled).
This parameter has the configuration ID ```config_1_1_00000001``` and is of type ```INTEGER```.
### Parameter 2: Service LED
Blink with service LED during operation
This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Disabled |
| 1 | Enabled |
The manufacturer defined default value is ```1``` (Enabled).
This parameter has the configuration ID ```config_2_1_00000001``` and is of type ```INTEGER```.
### Parameter 3: Security S0
Enable or disable Security S0 during inclusion (requires re-inclusion)
This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Disabled |
| 1 | Enabled |
The manufacturer defined default value is ```1``` (Enabled).
This parameter has the configuration ID ```config_3_1_00000001``` and is of type ```INTEGER```.
### Parameter 11: Min. Waittime for Multilevel-Sensor Reports
Minimal time between Sensor Multilevel reports.
Minimal time (in seconds) between Sensor Multilevel reports. See zunoSendReport(). Values less than 30 should not be used to conform to Z-Wave Plus, use them for debug only! 0 means send immediately. This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```30```.
This parameter has the configuration ID ```config_11_1_000000FF``` and is of type ```INTEGER```.
### Parameter 12: Legacy Sensor Binary
Change channel type from Notification to legacy Sensor Binary for compatibility.
Change channel type from Notification to legacy Sensor Binary to help Fibaro Home Center, Vera and some other controllers having problems with the latest Z-Wave Plus to understand the channel typeThis is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Disabled |
| 1 | Enabled |
The manufacturer defined default value is ```0``` (Disabled).
This parameter has the configuration ID ```config_12_1_00000001``` and is of type ```INTEGER```.
### Parameter 20: OTA Confirmation
Confirmation of OTA operations
Confirmation of OTA operations (for bootloader and sketch upgrades). Refer to https://z-uno.z-wave.me/z-wave/ota/This is an advanced parameter and will therefore not show in the user interface without entering advanced mode.
Values in the range 0 to 255 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_20_4_7FFFFFFF_wo``` and is of type ```INTEGER```.
This is a write only parameter.
### Parameter 64: Luminance Resolution
Mode for luminance measurements.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Low (4 lux) |
| 1 | High (1lx) |
| 2 | Very High (0.5lx) |
The manufacturer defined default value is ```0``` (Low (4 lux)).
This parameter has the configuration ID ```config_64_1_0000FFFF``` and is of type ```INTEGER```.
### Parameter 65: Luminance Compensation
Compensation value for luminance.
Compensation value for luminance. Keep in mind that luminance ranges from 0 to 65535. The compensation value will be added and an overflow can be the result.
Values in the range 0 to 65535 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_65_2_0000FFFF``` and is of type ```INTEGER```.
### Parameter 66: Temperature Compensation
Compensation value for Temperature
Compensation value for temperature in 1/100 °C (i.e. 10=0.1°C, 100=1°C, 1000=10°C).
Values in the range 0 to 10000 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_66_2_0000FFFF``` and is of type ```INTEGER```.
### Parameter 67: Pressure Compensation
Compensation for barometric pressure.
Compensation value for pressure in 1/100 kPa (i.e. 10=0.1kPa, 100=1kPa, 1000=10kPa).
Values in the range 0 to 10000 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_67_1_0000FFFF``` and is of type ```INTEGER```.
### Parameter 68: Humidity Compensation
Compensation value for humidity.
Compensation value for humidity in percent.
Values in the range 0 to 100 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_68_1_0000FFFF``` and is of type ```INTEGER```.
### Parameter 69: Temperature Oversampling
Oversampling factor for temperature measurement.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Skipped |
| 1 | 1x |
| 2 | 2x |
| 3 | 4x |
| 4 | 8x |
| 5 | 16x |
The manufacturer defined default value is ```0``` (Skipped).
This parameter has the configuration ID ```config_69_1_0000FFFF``` and is of type ```INTEGER```.
### Parameter 70: Pressure Oversampling
Oversampling factor for pressure measurement
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Skipped |
| 1 | 1x |
| 2 | 2x |
| 3 | 4x |
| 4 | 8x |
| 5 | 16x |
The manufacturer defined default value is ```1``` (1x).
This parameter has the configuration ID ```config_70_1_0000FFFF``` and is of type ```INTEGER```.
### Parameter 71: Humidity Oversampling
Oversampling factor for humidity measurement
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Skipped |
| 1 | 1x |
| 2 | 2x |
| 3 | 4x |
| 4 | 8x |
| 5 | 16x |
The manufacturer defined default value is ```1``` (1x).
This parameter has the configuration ID ```config_71_1_0000FFFF``` and is of type ```INTEGER```.
### Parameter 72: Luminance Report Delta
Minimum delta to report luminance changes.
Values in the range 0 to 65535 may be set.
The manufacturer defined default value is ```10```.
This parameter has the configuration ID ```config_72_2_0000FFFF``` and is of type ```INTEGER```.
### Parameter 73: Temperature Report Delta
Minimum delta to report temperature changes.
Values in the range 0 to 10000 may be set.
The manufacturer defined default value is ```50```.
This parameter has the configuration ID ```config_73_2_0000FFFF``` and is of type ```INTEGER```.
### Parameter 74: Pressure Report Delta
Minimum delta to report pressure changes.
Values in the range 0 to 10000 may be set.
The manufacturer defined default value is ```100```.
This parameter has the configuration ID ```config_74_2_0000FFFF``` and is of type ```INTEGER```.
### Parameter 75: Humidity Report Delta
Minimum delta to report humidity changes.
Values in the range 0 to 100 may be set.
The manufacturer defined default value is ```1```.
This parameter has the configuration ID ```config_75_1_000000FF``` and is of type ```INTEGER```.
### Wakeup Interval
The wakeup interval sets the period at which the device will listen for messages from the controller. This is required for battery devices that sleep most of the time in order to conserve battery life. The device will wake up at this interval and send a message to the controller to tell it that it can accept messages - after a few seconds, it will go back to sleep if there is no further communications.
This setting is defined in *seconds*. It is advisable not to set this interval too short or it could impact battery life. A period of 1 hour (3600 seconds) is suitable in most instances.
Note that this setting does not affect the devices ability to send sensor data, or notification events.
This parameter has the configuration ID ```wakeup_interval``` and is of type ```INTEGER```.
### Wakeup Node
When sleeping devices wake up, they send a notification to a listening device. Normally, this device is the network controller, and normally the controller will set this automatically to its own address.
In the event that the network contains multiple controllers, it may be necessary to configure this to a node that is not the main controller. This is an advanced setting and should not be changed without a full understanding of the impact.
This parameter has the configuration ID ```wakeup_node``` and is of type ```INTEGER```.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The device does not support associations.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_SENSOR_MULTILEVEL_V7| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_CONFIGURATION_V1| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| |
| COMMAND_CLASS_BATTERY_V1| |
| COMMAND_CLASS_WAKE_UP_V2| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| |
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1115).

18
_addons_ios/alexa-skill/readme.md
View File

@ -59,6 +59,11 @@ Here are some of the most common generic errors you may encounter while using th
* Alexa will respond with "I couldn't find a device or group named _device_ in your profile"
* It indicates that, either a device currently setup in your Alexa account, no longer exists in your openHAB server, or vice-versa.
* To resolve this error, make sure to run a discovery update either through the Alexa app or just by asking "Alexa, discover" on your echo device. Keep in mind that previously discovered devices that have been removed from the openHAB configuration will show as offline under your Alexa account and not be automatically removed. To prevent potential device name conflicts, it is highly recommended to remove these devices through the Alexa app.
* If all your Alexa-enabled devices in openHAB aren't discovered or getting updated:
* Check that your [server is available](#server-not-accessible).
* Look for any relevant errors in your openHAB server logs.
* If only new devices aren't found, make sure your last Alexa-related config changes are valid.
* If necessary, stagger the discovery process by adding a couple devices at a time to isolate the culprit.
#### Device Not Responding
* Alexa will respond with "_device_ isn't responding, please check its network connection and power supply", and in some rare occasions, no response or acknowledgement will be given.
@ -75,7 +80,7 @@ Here are some of the most common generic errors you may encounter while using th
#### Server Not Accessible
* Alexa will respond with "Sorry the hub that _device_ is connected to is not responding, please check its network connection and power supply"
* It indicates that your openHAB server is not accessible through [myopenHAB](https://myopenhab.org) cloud service.
* To resolve this error, make sure that your server is running and showing online under your myopenHAB account. For users that have setup their own custom skill, make sure that the proper server base URL was added to the lambda function config.js.
* To resolve this error, make sure that your server is running, your openHAB cloud service is configured with mode set to "Notifications & Remote Access", and showing online under your myopenHAB account. For users that have setup their own custom skill, make sure that the proper server base URL was added to the lambda function config.js.
#### Temperature Out Of Range
* Alexa will respond with "I can only set the temperature between _minValue_ and _maxValue_"
@ -521,10 +526,10 @@ Number:Temperature Temperature2 "Temperature" {alexa="TemperatureSenso
* each name formatted as `<@assetIdOrName>`
* defaults to item label name
* nonControllable=`<boolean>`
* when set to true, supportedModes and ordered parameters are ignored
* defaults to false
* supportedModes=`<modes>`
* each mode formatted as `<modeValue>=<@assetIdOrName1>:<@assetIdOrName2>:...`
* requires two modes to be specified at least
* defaults to item state description options `supportedModes="value1=label1,..."`, if defined, otherwise no supported modes
* ordered=`<boolean>`
* defaults to false
@ -546,7 +551,6 @@ Number:Temperature Temperature2 "Temperature" {alexa="TemperatureSenso
* each name formatted as `<@assetIdOrName>`
* defaults to item label name
* nonControllable=`<boolean>`
* when set to true, supportedRange and presets parameters are ignored
* defaults to false
* supportedRange=`<minValue:maxValue:precision>`
* defaults to `"0:100:1"` for Dimmer/Rollershutter, `"0:10:1"` for Number* item types
@ -586,20 +590,20 @@ Number:Temperature Temperature2 "Temperature" {alexa="TemperatureSenso
| InputController | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :x: | :x: | :heavy_check_mark: | :heavy_check_mark: | :x: | :x: | :heavy_check_mark: |
| LockController (lock) | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :x: | :heavy_check_mark: | :x: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
| LockController (unlock) | :x: | :x: | :heavy_check_mark: | :x: | :x: | :x: | :x: | :x: | :heavy_check_mark: | :heavy_check_mark: |
| ModeController | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :x: | :heavy_check_mark: |
| ModeController | :x: | :x: | :x: | :x: | :x: | :x: | :x: | :x: | :x: | :heavy_check_mark: |
| MotionSensor | :x: | :heavy_check_mark: | :x: | :x: | :x: | :x: | :x: | :x: | :x: | :heavy_check_mark: |
| PercentageController | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
| PlaybackController | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :x: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :x: | :x: | :heavy_check_mark: |
| PowerController | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
| PowerLevelController | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
| RangeController | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :x: | :heavy_check_mark: |
| RangeController | :x: | :x: | :x: | :x: | :x: | :x: | :x: | :x: | :x: | :heavy_check_mark: |
| SceneController | :x: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :x: | :heavy_check_mark: | :heavy_check_mark: |
| SecurityPanelController | :heavy_check_mark: | :heavy_check_mark: | :x: | :x: | :x: | :x: | :heavy_check_mark: | :x: | :x: | :heavy_check_mark: |
| Speaker | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :x: | :x: | :heavy_check_mark: | :heavy_check_mark: | :x: | :x: | :heavy_check_mark: |
| StepSpeaker | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :x: | :x: | :heavy_check_mark: | :heavy_check_mark: | :x: | :x: | :heavy_check_mark: |
| TemperatureSensor | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
| ThermostatController | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
| ToggleController | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :x: | :heavy_check_mark: |
| ToggleController | :x: | :x: | :x: | :x: | :x: | :x: | :x: | :x: | :x: | :heavy_check_mark: |
##### Display Categories
* Alexa has certain categories that effect how voice control and their mobile/web UI's display or control endpoints. An example of this is when you create "Smart Device Groups" in the Alex app and associate a specific Echo or Dot to that Group (typically a room). When a user asks to turn the lights ON, Alexa looks for devices in that group that have the category "LIGHT" to send the command to.
@ -769,7 +773,7 @@ Switch OutletPlug "Outlet Plug" {alexa="PowerController.powerState" [category="S
```
Number CurrentHumidity "Current Humidity" {alexa="CurrentHumidity"}
Number CurrentHumidity "Current Humidity" {alexa="RangeController.rangeValue" [friendlyNames="Humidity", nonControllable=true, unitOfMeasure="Percent"]}
Number CurrentHumidity "Current Humidity" {alexa="RangeController.rangeValue" [friendlyNames="Humidity", nonControllable=true, supportedRange="0:100:1", unitOfMeasure="Percent"]}
```
* CurrentTemperature
```