Matt,
I followed your instructions. Thank you for that. It turns out that with some patience, the device IS working.
- Code: Select all
Jun 12, 2019 at 9:00:49 AM
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 0B 09 71 05 00 00 00 FF 07 08 00 72
Z-Wave Debug . . requestAlarmSensorStatus: node 011, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 8, classSubKeyExt 7100000708
Z-Wave Debug . . requestAlarmSensorStatus: defnStatusByte 255
Z-Wave received "010 - Motion Sensor" status update is on
Jun 12, 2019 at 9:09:39 AM
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 0B 0A 71 05 00 00 00 FF 07 00 01 08 6F
Z-Wave Debug . . requestAlarmSensorStatus: node 011, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700
Z-Wave Debug . . requestAlarmSensorStatus: defnStatusByte 0
Z-Wave received "010 - Motion Sensor" status update is off
But it took almost
10 minutes for the device to go back from the ON state to the OFF state!
That seems like an extraordinary time for a motion sensor to go from the ON to OFF state right after being triggered and then placed into a dark drawer with no movement.
So I did some Googling and found this:
https://cache-m2.smarthome.com/manuals/ ... -guide.pdfPage 2 shows an advanced configuration that allows the setting of, among other things, the timeout in seconds.
I don't see a way in Indigo to set this up however. Is that possible?