--- layout: documentation title: DW-SS - ZWave --- {% include base.html %} # DW-SS Door/Window Contact This describes the Z-Wave device *DW-SS *, manufactured by *Ring* with the thing type UID of ```ring_dwss_00_000```. The device is in the category of *Door*, defining Door sensors. ![DW-SS product image](https://www.cd-jackson.com/zwave_device_uploads/893/893_default.jpg) The DW-SS 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 DW-SS 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 Ring Alarm Contact Sensor: Expand your Ring Alarm system to secure each door and window in your home, and get alerts as soon as they open. ### Inclusion Information 1. Activate inclusion mode on controller 2. Pull tab/quickly disconnect and reconnect battery 3. Device should appear in Inbox ### Exclusion Information 1. Initiate exclusion mode on controller 2. Open contact sensor’s cover Remove and replace battery quickly Reset: 1. Open contact sensor’s cover 2. Press and hold the reset button on sensor circuitry 3. Remove and replace battery quickly – Blue LED will start to blink rapidly 4. Wait for the blue LED to stop blinking ### Wakeup Information The DW-SS 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. By opening the top cover, the sensor will get to tamper state and stay awake. ## Channels The following table summarises the channels available for the DW-SS -: | Channel | Channel Id | Category | Item Type | |---------|------------|----------|-----------| | Binary Sensor | sensor_binary | Door | Switch | | Alarm (burglar) | alarm_burglar | Door | Switch | | Battery Level | battery-level | Battery | Number | ### Binary Sensor Indicates if a sensor has triggered. The ```sensor_binary``` channel supports the ```Switch``` 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 ```Switch``` item type -: | Value | Label | |-------|-----------| | ON | Triggered | | OFF | Untriggered | ### Alarm (burglar) Indicates if the burglar alarm is triggered. The ```alarm_burglar``` channel supports the ```Switch``` 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 ```Switch``` item type -: | Value | Label | |-------|-----------| | OFF | OK | | ON | Alarm | ### Battery Level Represents the battery level as a percentage (0-100%). Bindings for things supporting battery level in a different format (e.g. 4 levels) should convert to a percentage to provide a consistent battery level reading. The ```battery-level``` channel supports the ```Number``` item and is in the ```Battery``` category. ## Device Configuration The following table provides a summary of the 1 configuration parameters available in the DW-SS . Detailed information on each parameter can be found in the sections below. | Param | Name | Description | |-------|-------|-------------| | 1 | Wait time | Time between sending unsolicited battery reports | | | 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: Wait time Time between sending unsolicited battery reports 255 to 4200 seconds **in 255 second increments** that the sensor should wait between sending unsolicited battery reports.  The default configuration value for parameter 1 is defaulted to 4200 seconds on exclusion. Values in the range 255 to 4200 may be set. The manufacturer defined default value is ```4200```. This parameter has the configuration ID ```config_1_2``` 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 DW-SS supports 2 association groups. ### Group 1: Lifeline The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation. Controller Updates Association group 1 supports 1 node. ### Group 2: Basic Report Basic report of either 0x00 for CLOSED or 0xFF for OPEN When a node is associated with Group 2, the sensor will send a basic report of either 0x00 for “Closed” or 0xFF for “Open.” Association group 2 supports 1 node. ## Technical Information ### Endpoints #### Endpoint 0 | Command Class | Comment | |---------------|---------| | COMMAND_CLASS_NO_OPERATION_V1| | | COMMAND_CLASS_BASIC_V1| | | COMMAND_CLASS_SENSOR_BINARY_V1| Linked to BASIC| | COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| | | COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| | | COMMAND_CLASS_ZWAVEPLUS_INFO_V1| | | COMMAND_CLASS_CONFIGURATION_V1| | | COMMAND_CLASS_ALARM_V8| | | COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| | | COMMAND_CLASS_POWERLEVEL_V1| | | COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| | | COMMAND_CLASS_BATTERY_V1| | | COMMAND_CLASS_WAKE_UP_V2| | | COMMAND_CLASS_ASSOCIATION_V2| | | COMMAND_CLASS_VERSION_V2| | ### Documentation Links * [Manual](https://www.cd-jackson.com/zwave_device_uploads/893/Ring-Contact-Sensor---Manual.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/893).