DOME Door Pro not working

Hi - the other day I ordered a Dome water control valve and decided to take a chance on their Door Pro sensor working - looks like I took one for the team - it seemed to add OK but it does not report any state changes. If you could add this device to your long list of devices to be added someday I would appreciate it

See below and let me know if I need to send any other info to help get it supported.. Thx

Code: Select all

Aug 3, 2017, 10:33:30 AM
   Z-Wave                          controller included module: 036 - Notification Sensor
   Z-Wave                          querying module for encryption support
   Z-Wave                          starting encryption key exchange with module
   Z-Wave                          completed encryption key exchange with module
   Z-Wave                          stopped controller inclusion mode
   Z-Wave                          Syncing - started for "036 - Notification Sensor"
   Z-Wave                          Syncing - retrieved module neighbors list: 8
   Z-Wave                          Syncing - assigning return route to "036 - Notification Sensor"
   Z-Wave                          Syncing - assigned return route
   Z-Wave                          Syncing - retrieved manufacture and model names: Unknown - 021F, Notification Sensor - 00030201
   Z-Wave                          Syncing - retrieved protocol version 4.33, app version 1.57
   Z-Wave                          Syncing - retrieved class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01, base 00)
   Z-Wave                          Syncing - retrieved command classes: 80v1 84v2 85v1 86v1 8Ev1 98v1 59v1 5Av1 5Ev1 20v1 30v1 70v1 71v1 72v1 73v1 7Av1
   Z-Wave                          Syncing - retrieved encrypt commands: 80 30 84 85 86 8E 70 71 72 59 5A 7A
   Z-Wave                          Syncing - retrieved capabilities: routing, battery, beaming, security, waking
   Z-Wave                          Syncing - retrieved wake interval of 120 minutes
   Z-Wave                          Syncing - device "036 - Notification Sensor" wake interval changed to 60 minutes
   Z-Wave                          Syncing - retrieved group 1 associations: []
   Z-Wave                          Syncing - retrieved group 2 associations: []
   Z-Wave                          Syncing - retrieved group 3 associations: []
   Z-Wave                          Syncing - retrieved group 4 associations: []
   Z-Wave                          Syncing - retrieved group 5 associations: []
   Z-Wave                          Syncing - added group 1 association to interface
   Z-Wave                          Syncing - retrieved battery level of 100%
   Z-Wave                          Syncing - created device "036 - Notification Sensor"
   SQL Logger                      creating table device_history_10332240 for "036 - Notification Sensor"
   SQL Logger                      adding column "batterylevel" to table device_history_10332240 ("036 - Notification Sensor")
   SQL Logger                      adding column "batterylevel_ui" to table device_history_10332240 ("036 - Notification Sensor")
   Z-Wave                          Syncing - complete
   Z-Wave                          sent "036 - Notification Sensor" status request
   Z-Wave                          received "036 - Notification Sensor" status update battery level 100%

[matt (support)]

Try enabling Indigo's Z-Wave debug logging checkbox via the Interfaces->Z-Wave->Configure... menu item. Then, trip the sensor a few times and check the Event Log window. If it sends anything then copy/paste it into a reply for us.

This is what came in

Code: Select all

   Z-Wave Debug                    RCVD nonceFetch: node 036
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 24 0A 98 80 5B 1D AD 9A 24 4A F1 8E 25 2D A3
   Z-Wave Debug                    RCVD encryptedPacket: 00 71 05 00 00 00 FF 06 16 00 (decrypted)
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 24 09 71 05 00 00 00 FF 06 16 00 FF
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 036, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 6, valueExt 22, classSubKeyExt 7100000616
   Z-Wave Debug                    RCVD nonceFetch: node 036
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 24 0A 98 80 5B 1D AD 9A 24 4A F1 8E 25 2E A0
   Z-Wave Debug                    RCVD encryptedPacket: 00 71 05 00 00 00 FF 06 16 00 (decrypted)
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 24 09 71 05 00 00 00 FF 06 16 00 FF
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 036, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 6, valueExt 22, classSubKeyExt 7100000616
   Z-Wave Debug                    RCVD nonceFetch: node 036
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 24 0A 98 80 5B 1D AD 9A 24 4A F1 8E 25 2F A1
   Z-Wave Debug                    RCVD encryptedPacket: 00 30 03 FF 0A (decrypted)
   Z-Wave Debug                    RCVD requestBinarySensorStatus: 01 0A 00 04 00 24 04 30 03 FF 0A FF
   Z-Wave Debug                    . .  requestBinarySensorStatus: node 036, endpoint None, type 10, value 255
   Z-Wave Debug                    RCVD nonceFetch: node 036
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 24 0A 98 80 C1 5F FA 3E 0B 5C D9 95 25 30 9F
   Z-Wave Debug                    RCVD encryptedPacket: 00 71 05 00 00 00 FF 06 16 00 (decrypted)
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 24 09 71 05 00 00 00 FF 06 16 00 FF
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 036, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 6, valueExt 22, classSubKeyExt 7100000616
   Z-Wave Debug                    RCVD nonceFetch: node 036
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 24 0A 98 80 C1 5F FA 3E 0B 5C D9 95 25 31 9E
   Z-Wave Debug                    RCVD encryptedPacket: 00 30 03 FF 0A (decrypted)
   Z-Wave Debug                    RCVD requestBinarySensorStatus: 01 0A 00 04 00 24 04 30 03 FF 0A FF
   Z-Wave Debug                    . .  requestBinarySensorStatus: node 036, endpoint None, type 10, value 255
   Z-Wave Debug                    RCVD nonceFetch: node 036
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 24 0A 98 80 3E ED 22 F4 84 46 9D 58 25 32 DE
   Z-Wave Debug                    RCVD encryptedPacket: 00 71 05 00 00 00 FF 06 17 00 (decrypted)
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 24 09 71 05 00 00 00 FF 06 17 00 FF
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 036, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 6, valueExt 23, classSubKeyExt 7100000617
   Z-Wave Debug                    RCVD nonceFetch: node 036
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 24 0A 98 80 3E ED 22 F4 84 46 9D 58 25 33 DF
   Z-Wave Debug                    RCVD encryptedPacket: 00 30 03 00 0A (decrypted)
   Z-Wave Debug                    RCVD requestBinarySensorStatus: 01 0A 00 04 00 24 04 30 03 00 0A FF
   Z-Wave Debug                    . .  requestBinarySensorStatus: node 036, endpoint None, type 10, value 0


So I was hoping to create a virtual device to represent this Dome open/close sensor - then watch for and trigger off of the message it sends when it is open or closed. So I set up indigo to capture all the ones and zeros the sensor sends. (bits for what happens for open and close below). but after gazing at the HEX for a while and looking at the documentation on the Dome site for this sensor, I'm pretty sure my cat has about the same chance as figuring it out as me. And his paws are so big I'm not even sure he could use the keyboard.

The photo below is the section of the documentation I think is important - but I don't know how to map it to the message.

My question is: Can this work - and how / what would I trigger on for the open and close states. Thanks for any help and please reply so I don't have to get my cat involved - he is very lazy.

Code: Select all

Open
17.5 seconds ago from Not working Open Close Dining Room Window 036 - Notification Sensor:
0x01 0x08 0x00 0x04 0x00 0x24 0x02 0x98 0x40 0x0D

17.5 seconds ago from Not working Open Close Dining Room Window 036 - Notification Sensor:
0x01 0x0F 0x00 0x04 0x00 0x24 0x09 0x71 0x05 0x00 0x00 0x00 0xFF 0x06 0x16 0x00 0xFF

17.5 seconds ago from Not working Open Close Dining Room Window 036 - Notification Sensor:
0x01 0x23 0x00 0x04 0x00 0x24 0x1D 0x98 0x81 0x0C 0x63 0x1F 0xCB 0x97 0x4C 0xFF 0xF4 0x98 0xF6 0x5D 0x2E 0x17 0x26 0x3A 0xAF 0x84 0x88 0x4E 0x18 0x83 0x38 0x33 0x77 0xF2 0x70 0x62 0x6F

17.4 seconds ago from Not working Open Close Dining Room Window 036 - Notification Sensor:
0x01 0x08 0x00 0x04 0x00 0x24 0x02 0x98 0x40 0x0D

17.4 seconds ago from Not working Open Close Dining Room Window 036 - Notification Sensor:
0x01 0x0A 0x00 0x04 0x00 0x24 0x04 0x30 0x03 0xFF 0x0A 0xFF

17.4 seconds ago from Not working Open Close Dining Room Window 036 - Notification Sensor:
0x01 0x1E 0x00 0x04 0x00 0x24 0x18 0x98 0x81 0x3E 0x5F 0x9F 0xEC 0x23 0xCC 0x10 0x03 0xAA 0xB9 0x27 0x80 0xD9 0x4E 0xAE 0x60 0xD9 0x43 0x41 0x5D 0xEE 0x05 0xAE






Close
2.1 seconds ago from Not working Open Close Dining Room Window 036 - Notification Sensor:
0x01 0x08 0x00 0x04 0x00 0x24 0x02 0x98 0x40 0x0D

2.1 seconds ago from Not working Open Close Dining Room Window 036 - Notification Sensor:
0x01 0x0F 0x00 0x04 0x00 0x24 0x09 0x71 0x05 0x00 0x00 0x00 0xFF 0x06 0x17 0x00 0xFF

2.1 seconds ago from Not working Open Close Dining Room Window 036 - Notification Sensor:
0x01 0x23 0x00 0x04 0x00 0x24 0x1D 0x98 0x81 0xD8 0xAB 0x2E 0xA7 0x59 0xF8 0x94 0x3D 0xD1 0x04 0x78 0x61 0x7C 0x85 0xC8 0xF8 0x8B 0xBF 0x4E 0x8E 0x32 0x72 0x62 0xE2 0x44 0x38 0x7B 0x3C

2.0 seconds ago from Not working Open Close Dining Room Window 036 - Notification Sensor:
0x01 0x08 0x00 0x04 0x00 0x24 0x02 0x98 0x40 0x0D

2.0 seconds ago from Not working Open Close Dining Room Window 036 - Notification Sensor:
0x01 0x0A 0x00 0x04 0x00 0x24 0x04 0x30 0x03 0x00 0x0A 0xFF

2.0 seconds ago from Not working Open Close Dining Room Window 036 - Notification Sensor:
0x01 0x1E 0x00 0x04 0x00 0x24 0x18 0x98 0x81 0x37 0x02 0xD7 0xEA 0x77 0x67 0xE1 0x3E 0x1B 0x78 0x22 0x41 0xF0 0x4E 0xA4 0xB3 0x48 0xA2 0x28 0x40 0x40 0xAD 0xC1

[matt (support)]

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 *

Perfect - works like a charm

Or for a more elegant solution, look at my Zwave Lock Manager plugin.

It needs rebranding cos it does door and window sensors as well.


Sent from my iPhone using Tapatalk Pro

[matt (support)]

Indigo 7.2.0 is now available for download and has Z-Wave support for the Dome Door/Window Sensor (Standard and Pro).