Z-wave alarm frames

I have just installed a number of Fibaro Dimmer 2 modules. They will send alarm frames for events such as burnt out bulb, overload, overcurrent, surge, load error. Is there a way to catch these errors in Indigo?
I tried setting the overload alarm to 10W for one of the dimmers, turning it on and it will turn off immediately, debug log:

Code: Select all

Z-Wave                          sent "Gang Bad" on
   Z-Wave Debug                    queueing energy request of "020 - Gang Bad" (activity detected)
   Z-Wave Debug                    RCVD requestDimmerStatus: 01 09 00 04 00 14 03 26 03 0F CF
   Z-Wave Debug                    . .  requestDimmerStatus: node 020, endpoint None, value 15
   Z-Wave Debug                    RCVD requestVarSensorStatus: 01 0C 00 04 00 14 06 31 05 04 22 00 5B AC
   Z-Wave Debug                    . .  requestVarSensorStatus: node 020, endpoint None, type 4, raw value 2200...
   Z-Wave Debug                    . .  requestVarSensorStatus: 9.1 W (float: 9.100000)
   Z-Wave Debug                    received "Gang Bad" power load to 9.1 W
   Z-Wave Debug                    RCVD requestVarSensorStatus: 01 0C 00 04 00 14 06 31 05 04 22 01 1E E8
   Z-Wave Debug                    . .  requestVarSensorStatus: node 020, endpoint None, type 4, raw value 2201...
   Z-Wave Debug                    . .  requestVarSensorStatus: 28.6 W (float: 28.600000)
   Z-Wave Debug                    received "Gang Bad" power load to 28.6 W
   Z-Wave Debug                    RCVD requestDimmerStatus: 01 09 00 04 00 14 03 26 03 00 C0
   Z-Wave Debug                    . .  requestDimmerStatus: node 020, endpoint None, value 0
   Z-Wave                          received "Gang Bad" status update is off
   Z-Wave Debug                    ignoring duplicate energy request of "020 - Gang Bad" (activity detected)
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 14 09 71 05 00 00 00 FF 08 08 00 62
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 020, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 8, valueExt 8, classSubKeyExt 7100000808
   Z-Wave Debug                    polling status of node "020 - Gang Bad" (post-activity energy request)
   Z-Wave Debug                    SENT requestMeterLevel: 01 0A 00 13 14 03 32 01 00 25 67 80
   Z-Wave Debug                    RCVD requestMeterLevel: 01 10 00 04 00 14 0A 32 02 21 44 00 00 00 D2 00 00 72
   Z-Wave Debug                    . .  requestMeterLevel: node 020, endpoint None, meterType 01, raw value 4400...
   Z-Wave Debug                    . .  requestMeterLevel: 2.10 kWh (float: 2.100000)
   Z-Wave Debug                    SENT requestMeterLevel: 01 0A 00 13 14 03 32 01 10 25 68 9F
   Z-Wave Debug                    RCVD requestMeterLevel: 01 0E 00 04 00 14 08 32 02 21 32 01 1E 00 00 D5
   Z-Wave Debug                    . .  requestMeterLevel: node 020, endpoint None, meterType 01, raw value 3201...
   Z-Wave Debug                    . .  requestMeterLevel: 28.6 W (float: 28.600000)
   Z-Wave Debug                    RCVD requestVarSensorStatus: 01 0C 00 04 00 14 06 31 05 04 22 00 00 F7
   Z-Wave Debug                    . .  requestVarSensorStatus: node 020, endpoint None, type 4, raw value 2200...
   Z-Wave Debug                    . .  requestVarSensorStatus: 0.0 W (float: 0.000000)
   Z-Wave Debug                    received "Gang Bad" power load to 0.0 W


[jay (support)]

Yes, you can use the Z-Wave Command Received trigger event to match raw incoming commands.

Thanks. I was hoping there was a way to make the SQL logger or similar trigger on all z-wave alarm frames. Without knowing what the alarm frame from the device actually looks like, I wouldn't know how to create triggers. I could provoke the overload alarm I mentioned by lowering the load limit, but for example the overtemperature alarm seems hard to trigger without "cooking" the device.

I suppose this could be handled through a small plugin or something that allows creating a general trigger for zwave alarm frames.

Attaching info reg. some of the alarms from the Fibaro dimmer 2 from the manual.

I did some testing in a plugin and was able to catch the alarm frames and output an error message to the indigo log (for testing). Considering making a plugin if possible (if this functionality/triggers isn't planned in Indigo? )

So far I've tested with catching command class 0x71 with some of the devices I have that will send notification/alarm commands

Aeotec multisensor tamper alarm:

Code: Select all

   Z-Wave                          received "028 - Tamper" status update is on
   Zwave Alarm Handler Debug       ------ Zwave Alarm test debug
   Zwave Alarm Handler Debug       Alarm Command received:
   Zwave Alarm Handler Debug       Raw command: 01 11 00 04 00 1C 0B 71 05 00 00 00 FF 07 03 00 00 00 72
   Zwave Alarm Handler Debug       Node:    28
   Zwave Alarm Handler Debug       Alarm type:  7
   Zwave Alarm Handler Debug       Alarm event:  3
   Zwave Alarm Handler Debug       ----- End Zwave Alarm test debug
   Zwave Alarm Error               Zwave alarm received for node id 28, Alarm type: 7, Alarm event: 3

Front door open:

Code: Select all

   Zwave Alarm Handler Debug       ------ Zwave Alarm test debug
   Zwave Alarm Handler Debug       Alarm Command received:
   Zwave Alarm Handler Debug       Raw command: 01 0F 00 04 00 18 09 71 05 00 00 00 FF 06 16 00 7E
   Zwave Alarm Handler Debug       Node:    24
   Zwave Alarm Handler Debug       Alarm type:  6
   Zwave Alarm Handler Debug       Alarm event:  22
   Zwave Alarm Handler Debug       ----- End Zwave Alarm test debug
   Zwave Alarm Error               Zwave alarm received for node id 24, Alarm type: 6, Alarm event: 22

Front door closed:

Code: Select all

   Zwave Alarm Handler Debug       ------ Zwave Alarm test debug
   Zwave Alarm Handler Debug       Alarm Command received:
   Zwave Alarm Handler Debug       Raw command: 01 0F 00 04 00 18 09 71 05 00 00 00 FF 06 17 00 7F
   Zwave Alarm Handler Debug       Node:    24
   Zwave Alarm Handler Debug       Alarm type:  6
   Zwave Alarm Handler Debug       Alarm event:  23
   Zwave Alarm Handler Debug       ----- End Zwave Alarm test debug
   Zwave Alarm Error               Zwave alarm received for node id 24, Alarm type: 6, Alarm event: 23

Front door tamper on:

Code: Select all

   Z-Wave                          received "Dorsensor 1 Tamperswitch" status update is on
   Zwave Alarm Handler Debug       ------ Zwave Alarm test debug
   Zwave Alarm Handler Debug       Alarm Command received:
   Zwave Alarm Handler Debug       Raw command: 01 0F 00 04 00 18 09 71 05 00 00 00 FF 07 03 00 6A
   Zwave Alarm Handler Debug       Node:    24
   Zwave Alarm Handler Debug       Alarm type:  7
   Zwave Alarm Handler Debug       Alarm event:  3
   Zwave Alarm Handler Debug       ----- End Zwave Alarm test debug
   Zwave Alarm Error               Zwave alarm received for node id 24, Alarm type: 7, Alarm event: 3

Front door tamper off:

Code: Select all

   Z-Wave                          received "Dorsensor 1 Tamperswitch" status update is off
   Zwave Alarm Handler Debug       ------ Zwave Alarm test debug
   Zwave Alarm Handler Debug       Alarm Command received:
   Zwave Alarm Handler Debug       Raw command: 01 0F 00 04 00 18 09 71 05 00 00 00 FF 07 00 00 69
   Zwave Alarm Handler Debug       Node:    24
   Zwave Alarm Handler Debug       Alarm type:  7
   Zwave Alarm Handler Debug       Alarm event:  0
   Zwave Alarm Handler Debug       ----- End Zwave Alarm test debug
   Zwave Alarm Error               Zwave alarm received for node id 24, Alarm type: 7, Alarm event: 0

Fibaro dimmer load error (burnt out bulb detection by removing 2 of 3 bulbs):

Code: Select all

   Zwave Alarm Handler Debug       ------ Zwave Alarm test debug
   Zwave Alarm Handler Debug       Alarm Command received:
   Zwave Alarm Handler Debug       Raw command: 01 0F 00 04 00 14 09 71 05 00 00 00 FF 08 09 00 63
   Zwave Alarm Handler Debug       Node:    20
   Zwave Alarm Handler Debug       Alarm type:  8
   Zwave Alarm Handler Debug       Alarm event:  9
   Zwave Alarm Handler Debug       ----- End Zwave Alarm test debug
   Zwave Alarm Error               Zwave alarm received for node id 20, Alarm type: 8, Alarm event: 9

Fibaro dimmer overload error:

Code: Select all

   Zwave Alarm Handler Debug       ------ Zwave Alarm test debug
   Zwave Alarm Handler Debug       Alarm Command received:
   Zwave Alarm Handler Debug       Raw command: 01 0F 00 04 00 14 09 71 05 00 00 00 FF 08 08 00 62
   Zwave Alarm Handler Debug       Node:    20
   Zwave Alarm Handler Debug       Alarm type:  8
   Zwave Alarm Handler Debug       Alarm event:  8
   Zwave Alarm Handler Debug       ----- End Zwave Alarm test debug
   Zwave Alarm Error               Zwave alarm received for node id 20, Alarm type: 8, Alarm event: 8

It shouldn' be a problem to make some triggers that can filter out alarm types and/or alarm events, but not sure yet how this should be handled best, and if any of the other information in the received Zwave command is relevant. Any input?

My ZWave lock manager has some of this functionality at the moment, though unintentionally as I haven't yet tightened it down to just locks yet.

It is monitoring for lock alarm and status updates, which mainly come as 0x71 alarms.

Without stepping on your toes / putting you off trying your own plugin, it would be very easy to duplicate that section of code as I continue building it, to provide a separate plugin that does this but using the same 'framework'?

I'd be happy to share on this if you wanted?


Sent from my iPhone using Tapatalk

Thanks howartp. As we talked about on PM I already had some ideas reg. triggering and (optional) integration with my notification plugin (due for an update btw). I'm planning to make a beta for the basics of this at least and we'll see where it goes from there
If you don't mind I'll have a look at the code for your plugins. I will be publishing my code on github, available for "borrowing" in other usages/plugins.

An alpha test of the plugin has been posted