| layout | title |
|---|---|
documentation |
TZDW-100 - ZWave |
{% include base.html %}
This describes the Z-Wave device TZDW-100, manufactured by Telldus Technologies AB with the thing type UID of telldus_tzdw100_00_000.
The device is in the category of Sensor, defining Device used to measure something.
The TZDW-100 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 TZDW-100 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.
This magnet sensor contains the latest Z-Wave technology with the ability to remotely control other Z-Wave units available in your network. The fact that it is battery operated and so small you can virtually place it anywhere you want – on doors, windows or drawers, without the need of wiring. Screw or tape up the holder and then click the sensor in place. Done! The sensor is designed to be seen as little as possible and we have made it significantly smaller than other sensors. It consists of two parts that will merge into a stylish unit when the sensor is closed
Press the button on the device three times fast.
Press the button on the device three times fast.
The TZDW-100 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 the button on the sensor one time short to wake up the device.
The following table summarises the channels available for the TZDW-100 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|---|---|---|---|---|
| Door Sensor | sensor_door | sensor_door | Door | Contact |
| Alarm | alarm_general | alarm_general | Alarm | 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 an alarm is triggered.
The alarm_general channel is of type alarm_general and supports the Switch item and is in the Alarm category. This is a read only channel so will only be updated following state changes from the device.
The following state translation is provided for this channel to the Switch item type -:
| Value | Label |
|---|---|
| OFF | OK |
| ON | Alarm |
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 8 configuration parameters available in the TZDW-100. Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|---|---|---|
| 1 | Group 2 Command Type | Select what type of command to be sent to nodes in association group 2 |
| 2 | Group 2 Value | Select what value that should be sent to association group 2 |
| 3 | Group 2 Signal Type | Type of commands to association group 2 |
| 4 | Group 3 Command Type | Select what type of command to be sent to nodes in association group 3 |
| 5 | Group 3 Value | Select what value that should be sent to association group 3 |
| 6 | Group 3 Signal Type | Type of commands to association group 3 |
| 7 | LED-Indicator | LED-Indicator |
| 8 | Lifeline command Type | Select the type of command to be sent in the Lifeline |
| 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 |
Select what type of command to be sent to nodes in association group 2
The following option values may be configured -:
| Value | Description |
|---|---|
| 0 | Basic |
| 1 | Switch Binary |
| 2 | Switch All |
| 3 | Switch Multilevel |
The manufacturer defined default value is 0 (Basic).
This parameter has the configuration ID config_1_1 and is of type INTEGER.
Select what value that should be sent to association group 2
The following option values may be configured -:
| Value | Description |
|---|---|
| 255 | Last value |
The manufacturer defined default value is 255 (Last value).
This parameter has the configuration ID config_2_1 and is of type INTEGER.
Type of commands to association group 2
The following option values may be configured -:
| Value | Description |
|---|---|
| 0 | Normal |
| 1 | Inverted |
The manufacturer defined default value is 0 (Normal).
This parameter has the configuration ID config_3_1 and is of type INTEGER.
Select what type of command to be sent to nodes in association group 3
The following option values may be configured -:
| Value | Description |
|---|---|
| 0 | Basic |
| 1 | Switch Binary |
| 2 | Switch All |
| 3 | Switch Multilevel |
The manufacturer defined default value is 0 (Basic).
This parameter has the configuration ID config_4_1 and is of type INTEGER.
Select what value that should be sent to association group 3
The following option values may be configured -:
| Value | Description |
|---|---|
| 255 | Last value |
The manufacturer defined default value is 255 (Last value).
This parameter has the configuration ID config_5_1 and is of type INTEGER.
Type of commands to association group 3
The following option values may be configured -:
| Value | Description |
|---|---|
| 0 | Normal |
| 1 | Inverted |
The manufacturer defined default value is 0 (Normal).
This parameter has the configuration ID config_6_1 and is of type INTEGER.
LED-Indicator
The following option values may be configured -:
| Value | Description |
|---|---|
| 0 | Off |
| 1 | On |
The manufacturer defined default value is 1 (On).
This parameter has the configuration ID config_7_1 and is of type INTEGER.
Select the type of command to be sent in the Lifeline
The following option values may be configured -:
| Value | Description |
|---|---|
| 0 | Notification |
| 1 | Sensor binary |
The manufacturer defined default value is 0 (Notification).
This parameter has the configuration ID config_8_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 TZDW-100 supports 3 association groups.
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation. Lifeline - Sensor status
Association group 1 supports 1 node.
Sensor open and closed
Association group 2 supports 10 nodes.
Sensor Open Only
Association group 3 supports 10 nodes.
| Command Class | Comment |
|---|---|
| COMMAND_CLASS_NO_OPERATION_V1 | |
| COMMAND_CLASS_BASIC_V1 | |
| COMMAND_CLASS_SENSOR_BINARY_V2 | Linked to BASIC |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1 | |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V2 | |
| COMMAND_CLASS_CONFIGURATION_V1 | |
| COMMAND_CLASS_ALARM_V4 | |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1 | |
| 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_MULTI_CHANNEL_ASSOCIATION_V2 |
Did you spot an error in the above definition or want to improve the content? You can contribute to the database here.