| layout | title |
|---|---|
documentation |
ZD2102-5 - ZWave |
{% include base.html %}
This describes the Z-Wave device ZD2102-5, manufactured by Zipato with the thing type UID of zipato_zd2102plus_00_000.
The device is in the category of Door, defining Door sensors.
The ZD2102-5 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices.
The ZD2102-5 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.
- Door/Windows sensor that can be mounted to any door window or other opening object
- New Z-Wave 500 series chip supports multichannel operation and higher data rates (9.6/40/100kbps)
- Can be used with various Z-Wave networks/controllers, regardless of the manufacturers
- Very low power power consumption
- LED indicator
- Over-the-air firmware update
- Easy installation
Hold pressed the program switch of Door/Window Sensor for at least 1 second.
The LED on the Door/Window Sensor should go solid, if not, please try again
Hold pressed the program switch of Door/Window Sensor for at least 1 second for successful exclusion.
The ZD2102-5 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour.
The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device.
If the sensor cover is removed, the tamper switch will send signal according the Status/Signal table,and the LED will light up. Before replacing the cover, the sensor is in “Awake”mode. Same as external reed switch
The following table summarises the channels available for the ZD2102-5 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|---|---|---|---|---|
| Sensor (Alarm) | sensor_door | sensor_door | Door | Contact |
| Tamper Alarm | alarm_tamper | alarm_tamper | Switch | |
| Battery Level | battery-level | system.battery_level | Battery | Number |
Indicates if the door/window is open or closed.
The sensor_door channel is of type sensor_door and supports the Contact item and is in the Door category. This is a read only channel so will only be updated following state changes from the device.
The following state translation is provided for this channel to the Contact item type -:
| Value | Label |
|---|---|
| OPEN | Open |
| CLOSED | Closed |
Indicates if the tamper alarm is triggered.
The alarm_tamper channel is of type alarm_tamper and supports the Switch item. This is a read only channel so will only be updated following state changes from the device.
The following state translation is provided for this channel to the Switch item type -:
| Value | Label |
|---|---|
| OFF | OK |
| ON | Alarm |
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%.
The following table provides a summary of the 1 configuration parameters available in the ZD2102-5. Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|---|---|---|
| 1 | External switch | Determines if external switch can be used. |
| 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 |
Determines if external switch can be used.
The following option values may be configured -:
| Value | Description |
|---|---|
| 0 | Disabled |
| 255 | Enabled |
The manufacturer defined default value is 0 (Disabled).
This parameter has the configuration ID config_1_1 and is of type INTEGER.
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.
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 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 ZD2102-5 supports 1 association group.
Association group 1 supports 5 nodes.
| Command Class | Comment |
|---|---|
| COMMAND_CLASS_NO_OPERATION_V1 | |
| COMMAND_CLASS_BASIC_V1 | |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1 | |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1 | |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V2 | |
| COMMAND_CLASS_CONFIGURATION_V1 | |
| COMMAND_CLASS_ALARM_V4 | |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V2 | |
| COMMAND_CLASS_POWERLEVEL_V1 | |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V2 | |
| COMMAND_CLASS_BATTERY_V1 | |
| COMMAND_CLASS_WAKE_UP_V2 | |
| COMMAND_CLASS_ASSOCIATION_V2 | |
| COMMAND_CLASS_VERSION_V2 | |
| COMMAND_CLASS_SECURITY_V1 |
Did you spot an error in the above definition or want to improve the content? You can contribute to the database here.