Aeotec Dry Contact Sensor

Hardware
1

Has anyone had any luck with the Aeotec Dry Contact Sensor Gen 5? I have a Z-Stick Gen5, so I (naively) assumed that it would just work, but while trying to add the node to my z wave network I get this error:

2017-06-22 22:05:07.489 Info, Add Device
2017-06-22 22:05:07.489 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x11, 0x60
2017-06-22 22:05:07.490 Detail, Notification: ControllerCommand - Starting
2017-06-22 22:05:07.490 Detail, 
2017-06-22 22:05:07.491 Info, contrlr, Sending (Command) message (Callback ID=0x11, Expected Re    ply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x11, 0x60
2017-06-22 22:05:08.491 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-06-22 22:05:08.491 Detail, contrlr, Removing current message
2017-06-22 22:05:08.491 Detail, contrlr, Notification: Notification - TimeOut
2017-06-22 22:05:08.492 Detail, Notification: ControllerCommand - Error - Failed

Any pointers would be helpful.

2

I just picked up this sensor and had a slightly difficult time setting it up as well. I was able to get it working with the following steps.

I put the battery in the sensor, then put my Z Wave Stick Gen5 into secure inclusion mode. I then pressed the action button on the dry contact sensor twice quickly. The red light on the sensor flashed a bit confirming it was included in the network.

I restarted HASS and the sensor showed up, specifically in the Z Wave configuration panel.

To work properly with HASS, I selected the dry contact node in the Z Wave configuration panel and set the “Report Type” configuration to “Binary Sensor”.

I hope this helps.

3

This didn’t work for me.

Developer Tools -> States doesn’t show a change. The light comes on the aeotec, but no state changes.

OZW logs show:

2018-01-16 21:44:09.326 Detail,
2018-01-16 21:44:09.326 Info, Node027, Received Basic set from node 27: level=255. Treating it as a Basic report.
2018-01-16 21:44:09.327 Detail, Node027, Refreshed Value: old value=0, new value=255, type=byte
2018-01-16 21:44:09.327 Detail, Node027, Changes to this value are not verified
2018-01-16 21:44:09.327 Detail, Node027, Notification: ValueChanged
2018-01-16 21:44:12.438 Detail, Node027,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x1b, 0x03, 0x20, 0x01, 0x00, 0xcb
2018-01-16 21:44:12.438 Detail,
2018-01-16 21:44:12.439 Info, Node027, Received Basic set from node 27: level=0. Treating it as a Basic report.
2018-01-16 21:44:12.439 Detail, Node027, Refreshed Value: old value=255, new value=0, type=byte
2018-01-16 21:44:12.439 Detail, Node027, Changes to this value are not verified
2018-01-16 21:44:12.440 Detail, Node027, Notification: ValueChanged
2018-01-16 21:44:13.217 Detail, Node027,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x1b, 0x03, 0x20, 0x01, 0xff, 0x34

Is there a way set a binary sensor by it’s level?

4

Does home assistant get a state change notification?

5

Nothing.
The only thing I see, is from OZW logs, the level= being 255 or 0.

6

Then your report type is not set properly.

You may have to wake the device in order to set the property as well.