Indigo Domotics

Matt,

I did what you asked, and I'm now receiving the following debug event log

Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 76 09 71 05 00 00 00 FF 06 17 00 11
Z-Wave Debug . . requestAlarmSensorStatus: node 118, 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 76 04 30 03 00 0A BA
Z-Wave Debug . . requestBinarySensorStatus: node 118, endpoint None, type 10, value 0
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 76 09 71 05 00 00 00 FF 06 16 00 10
Z-Wave Debug . . requestAlarmSensorStatus: node 118, 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 76 04 30 03 FF 0A 45
Z-Wave Debug . . requestBinarySensorStatus: node 118, endpoint None, type 10, value 255

However the device state does not change, it still remains "Off".

Okay, that looks much better. With my change to add the model ID being reported to Indigo's device definition list that module will work in the next release of Indigo (7.4.1.).

Matt,

Great, thanks.

Indigo 7.4.1 is now available and includes this model ID for matching the correct device definition.