Ecolink DWZWAVE2-ECO

Has anyone had success in getting the Ecolink DWZWAVE2-ECO Door/Window Sensor to work with Indigo 7? I an get it to synchronize with Indigo just fine, but I never see any open/close entries in the event log when I trigger the sensor. Any guidance/help would be appreciated.

I bought 2 of them about a year ago and have had no problem including them and using them. Attached is a picture of the "Settings" page for one of them. You might try excluding it and then including it again.

[matt (support)]

Also try turning on Indigo's debug Z-Wave logging checkbox via the Interfaces->Z-Wave->Configure... menu item, then open/close the sensor several times. If anything is logged then copy/paste both that and the results of a device sync with the module into a reply for me.

When I select write device details to event log here is the output...
Z-Wave Indigo Device "018 - Notification Sensor" Z-Wave Properties:
Indigo Z-Wave Version: 2.0.68
Node ID: 18
Model: Notification Sensor
Model ID: 00040002
Manufacturer: Ecolink
Manufacturer ID: 014A
Protocol Version: 4.05
Application Version: 10.01
Model Definition Version: 0
Library Type: 6
Class Name: Notification Sensor
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 20v1 80v1 84v2 85v1 86v1 30v1 70v1 71v1 72v1 73v1 59v1 5Ev1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking
Neighbors: 1, 2, 3, 4, 6, 7, 8, 9, 10, 13, 14
Associations: 1:[1] 2:[]
Config Values: - none -

Here is the output when Z-Wave debug is turned on and I trigger the sensor...
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 11 00 04 00 12 0B 71 05 00 00 00 FF 06 17 00 00 00 69
Z-Wave Debug . . requestAlarmSensorStatus: node 018, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 6, valueExt 23, classSubKeyExt 7100000617
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 12 04 30 03 00 FF 2B
Z-Wave Debug . . requestBinarySensorStatus: node 018, endpoint None, type 255, value 0
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 11 00 04 00 12 0B 71 05 00 00 00 FF 06 16 00 00 00 68
Z-Wave Debug . . requestAlarmSensorStatus: node 018, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 6, valueExt 22, classSubKeyExt 7100000616
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 12 04 30 03 FF FF D4
Z-Wave Debug . . requestBinarySensorStatus: node 018, endpoint None, type 255, value 255

Configure screen image in attachment

Device sync details...
Z-Wave Syncing - started for "018 - Notification Sensor"
Z-Wave Syncing - retrieved module neighbors list: 1, 2, 3, 4, 6, 7, 8, 9, 10, 13, 14
Z-Wave Syncing - assigning return route to "018 - Notification Sensor"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Ecolink - 014A, Notification Sensor - 00040002
Z-Wave Syncing - retrieved protocol version 4.05, app version 10.01
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01, base 00)
Z-Wave Syncing - retrieved command classes: 20v1 80v1 84v2 85v1 86v1 30v1 70v1 71v1 72v1 73v1 59v1 5Ev1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, battery, beaming, waking
Z-Wave Syncing - retrieved wake interval of 60 minutes
Z-Wave Syncing - device "018 - Notification Sensor" wake interval changed to 60 minutes
Z-Wave Syncing - retrieved group 1 associations: [1]
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Syncing - retrieved battery level of 100%
Z-Wave Syncing - complete
Z-Wave sent "018 - Notification Sensor" status request
Z-Wave received "018 - Notification Sensor" status update battery level 100%

[matt (support)]

There are a couple of approaches you can take to get this working now.

One is that you could use the Match Raw Packet trigger type (after selecting Z-Wave Command Received), and choose your device in the From popup menu. For the open trigger try a Match Bytes field like this:

* 0x71 0x05 0x00 0x00 0x00 0xFF 0x06 0x16 *

And for the close trigger try:

* 0x71 0x05 0x00 0x00 0x00 0xFF 0x06 0x17 *

Alternatively, you could use Peter's Zwave Lock Manager plugin. It can be used with Z-Wave door/window sensors as well as locks.

Thank you Matt, I appreciate the support. Peter's Wave Lock Manager was the easiest way to go and it worked like a charm, responses for Open/Close now reflect in the log!