Aeotec Z-Wave Plus Dry Contact Sensor ZW097-A

This sensor syncs with Indigo and shows up as a routing slave and allows you to adjust wake up interval but does not function at all. Nothing in log.

Z-Wave Indigo Device "Aeon Labs Dry Contact" Z-Wave Properties:
Indigo Z-Wave Version: 1.0.354
Node ID: 79
Model: Routing Slave
Model ID: 01020061
Manufacturer: Aeon Labs
Manufacturer ID: 0086
Protocol Version: 4.05
Application Version: 1.04
Model Definition Version: 0
Library Type: 3
Class Name: Routing Slave
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 80v1 30v1 84v2 85v1 86v1 70v1 71v1 72v1 73v1 59v1 7Av1 5Ev1
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking
Neighbors: 23, 37
Associations: 1:[1]
Config Values: - none -

[matt (support)]

Added to the feature request list.

If you turn on debug logging (Interfaces->Z-Wave->Configure... menu item) does anything show in the Event Log as you trigger the sensor? If so, copy/paste the Event Log contents showing the result (and annotate for me what you were doing for each message). Also re-define/sync it again and copy/paste the Event Log results for the define/sync.

Hi Matt,

Here is sensor contact closed
Z-Wave Debug RCVD basicSetState: 01 09 00 04 00 4F 03 20 01 FF 60
Z-Wave Debug . . basicSetState: node 079, endpoint None, value 255 (no node dispatch)

Here is sensor after opening contact
Z-Wave Debug RCVD basicSetState: 01 09 00 04 00 4F 03 20 01 00 9F
Z-Wave Debug . . basicSetState: node 079, endpoint None, value 0 (no node dispatch)

Redefine/Sync Z-Wave Debug
intiatingSyncUI (timeout in 300 seconds)
Z-Wave Syncing - started for device "Aeon Labs Dry Contact"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 4F 01 01 36
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 00 00 40 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0E
Z-Wave Debug . . getNodeNeighbors: nodeId 079, neighbors: 23, 37
Z-Wave Syncing - retrieved module neighbors list: 23, 37
Z-Wave Syncing - requesting neighbor list update of "079 - Aeon Labs Dry Contact"
Z-Wave Debug SENT requestNeighborUpdate: 01 04 00 48 4F FC
Z-Wave Debug RCVD requestNeighborUpdate: 06 (ACK)
Z-Wave Debug RCVD requestNeighborUpdate: 01 05 00 48 01 21 92
Z-Wave Debug . . requestNeighborUpdate: node 079, update starting
Z-Wave Debug RCVD nodeAwake: 01 08 00 04 00 4F 02 84 07 3D
Z-Wave Debug . . nodeAwake: node 079 (queued awake processing because sync in progress)

Jun 27, 2015, 4:13:57 PM
Z-Wave Debug RCVD requestNeighborUpdate: 01 05 00 48 01 21 92
Z-Wave Debug . . requestNeighborUpdate: node 079, update starting
Z-Wave Debug RCVD requestNeighborUpdate: 01 05 00 48 01 22 91
Z-Wave Debug . . requestNeighborUpdate: node 079, update finished
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 4F 01 01 36
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 00 00 40 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0E
Z-Wave Debug . . getNodeNeighbors: nodeId 079, neighbors: 23, 37
Z-Wave Syncing - neighbor list update complete (no change)
Z-Wave Syncing - assigning return route to "079 - Aeon Labs Dry Contact"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 4F 01 F2
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 079, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 4F 04 02 D0
Z-Wave Debug RCVD requestNodeInfo: 01 19 00 49 84 4F 13 04 07 01 5E 86 72 85 59 73 71 84 30 80 70 98 7A EF 5A 82 90
Z-Wave Debug . . requestNodeInfo: node 079, combined class list: 80v1 30v1 84v1 85v1 86v1 70v1 71v1 72v1 73v1 98v1 59v1 7Av1 5Ev1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 4F 02 72 04 05 03 D8
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 4F 08 72 05 00 86 01 02 00 61 21
Z-Wave Debug . . requestManufactureInfo: node 079, manufacturerId 0086, productId 01020061
Z-Wave Debug . . requestManufactureInfo: Aeon Labs, Routing Slave
Z-Wave Syncing - retrieved manufacture and model names: Aeon Labs - 0086, Routing Slave - 01020061
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 4F 02 86 11 05 04 3E
Z-Wave Debug RCVD requestVersInfoGen: 01 0F 00 04 00 4F 09 86 12 03 04 05 01 04 61 00 40
Z-Wave Debug . . requestVersInfoGen: node 079, protoVers 4.05, appVers 1.04
Z-Wave Syncing - retrieved protocol version 4.05, app version 1.04
Z-Wave Debug RCVD requestVersInfoGen: 01 0F 00 04 00 4F 09 86 12 03 04 05 01 04 61 00 40
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 4F 03 86 13 84 05 05 BB
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 4F 04 86 14 84 02 AE
Z-Wave Debug . . requestVersInfoCmdClass: node 079, class command 84 using version 2
Z-Wave Debug . . requestVersInfoCmdClass: node 079, combined class list: 80v1 30v1 84v2 85v1 86v1 70v1 71v1 72v1 73v1 98v1 59v1 7Av1 5Ev1
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : -- : -- (04 : 07 : 01, base 00)
Z-Wave Syncing - retrieved command classes: 80v1 30v1 84v2 85v1 86v1 70v1 71v1 72v1 73v1 98v1 59v1 7Av1 5Ev1
Z-Wave Debug SENT requestWakeInterval: 01 09 00 13 4F 02 84 05 05 06 2A
Z-Wave Debug RCVD requestWakeInterval: 01 0C 00 04 00 4F 06 84 06 00 0E 10 01 23
Z-Wave Debug . . requestWakeInterval: node 079, interval 60 minutes, wakeTarget 001
Z-Wave Syncing - retrieved wake interval of 60 minutes
Z-Wave Debug SENT setWakeInterval: 01 0D 00 13 4F 06 84 04 00 0E 10 01 05 07 35
Z-Wave Syncing - device "079 - Aeon Labs Dry Contact" wake interval changed to 60 minutes
Z-Wave Debug SENT requestAssociationGroupCount: 01 09 00 13 4F 02 85 05 05 08 25
Z-Wave Debug RCVD requestAssociationGroupCount: 01 09 00 04 00 4F 03 85 06 01 3C
Z-Wave Debug . . requestAssociationGroupCount: node 079, group count: 1
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 4F 03 85 02 01 05 09 20
Z-Wave Debug RCVD requestAssociations: 01 09 00 04 00 4F 03 85 06 01 3C (unsolicited2 -- requeuing)
Z-Wave Debug RCVD requestAssociations: 01 09 00 04 00 4F 03 85 06 01 3C (unsolicited3 -- requeuing)
Z-Wave Debug RCVD requestAssociationGroupCount: 01 09 00 04 00 4F 03 85 06 01 3C
Z-Wave Debug RCVD requestAssociations: 01 0C 00 04 00 4F 06 85 03 01 05 00 01 3D
Z-Wave Debug . . requestAssociations: node 079, group: 1, num associations: 1, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 079, group: 1, associations: [1]
Z-Wave Syncing - retrieved group 1 associations: [1]
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 4F 02 80 02 05 0A 25
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 4F 03 80 03 64 59
Z-Wave Debug . . requestBatteryLevel: node 079, level 100
Z-Wave Syncing - retrieved battery level of 100%
Z-Wave Syncing - complete
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 4F 02 80 02 05 0B 24
Z-Wave Debug terminatingSyncUI
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 4F 03 80 03 64 59
Z-Wave Debug . . requestBatteryLevel: node 079, level 100
Z-Wave received "079 - Aeon Labs Dry Contact" status update battery level 100%
Z-Wave Debug SENT goToSleep: 01 09 00 13 4F 02 84 08 04 0C 2C
Z-Wave Debug RCVD packet: 01 05 00 13 0C 00 E5 (hex)

[matt (support)]

Got it, thanks. I don't have an ETA but based on the log we'll definitely be able to get it added.

I'm also trying to incorporate one of these into my network. I submitted the device information before searching here, so sorry for the dupe. Would love to get this working at some point.

What a coincidence!

I bought one of these a few days ago and tried to add it to my Indigo system this morning. Appears to report battery status, but not the contact closure. Was just about to ask about this on the forum.

Looking forward to the sensor being supported! Thanks...

[matt (support)]

This thread is old but I wanted to follow-up that Indigo 7.0 is now available (has been for a while). It includes supports for dozens of new Z-Wave devices, including the Gen 5 Aeotec modules.