ZCOMBO Configuration

Hello all,

I have a ZCOMBO device as part of my system and wonder if any of you with one are also seeing the following in your log?

2016-02-25 03:19:59.836 [ERROR] [z.i.p.c.ZWaveAlarmCommandClass] - NODE 2: Unknown Alarm Type = 13, ignoring report.
2016-02-25 04:20:19.874 [ERROR] [z.i.p.c.ZWaveAlarmCommandClass] - NODE 2: Unknown Alarm Type = 13, ignoring report.
2016-02-25 05:20:42.027 [ERROR] [z.i.p.c.ZWaveAlarmCommandClass] - NODE 2: Unknown Alarm Type = 13, ignoring report.
2016-02-25 06:21:04.576 [ERROR] [z.i.p.c.ZWaveAlarmCommandClass] - NODE 2: Unknown Alarm Type = 13, ignoring report.
2016-02-25 07:21:23.529 [ERROR] [z.i.p.c.ZWaveAlarmCommandClass] - NODE 2: Unknown Alarm Type = 13, ignoring report.
2016-02-25 08:21:45.140 [ERROR] [z.i.p.c.ZWaveAlarmCommandClass] - NODE 2: Unknown Alarm Type = 13, ignoring report.

This appears several times a day in my log. There isn’t an audible alarm associated with it.

Any idea what it means?

Thanks

I see this too. I’ve not spent any time yet to research what that means. Hopefully someone can answer.

Alarm 13 is an “Appliance Alarm” - no idea what that is, but given it’s happeneing exactly every hour, it’s either a lifeline, or a low importance alarm.

Is it possible to get a debug log of the hex data that’s received - it will be logged a few lines before the message…

I’ve turned debug on and will upload as soon as I have entries…

Here’s a log from this morning after enabling debug and restarting.

zcombo.json (9.5 KB)

Thanks, but I guess you’ve filtered this file? Unfortunately, it doesn’t contain the information I was after…

Sorry about that, I though you were looking for something with Node 2:

Here’s an event with several preceding lines.

2016-02-27 09:12:32.816 [DEBUG] [b.z.i.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2016-02-27 09:12:32.824 [DEBUG] [.z.internal.ZWaveActiveBinding] - ZwaveIncomingEvent
2016-02-27 09:12:32.825 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass] - NODE 3: Went to sleep
2016-02-27 09:12:32.826 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass] - NODE 3: Is sleeping
2016-02-27 09:12:32.827 [DEBUG] [WaveController$ZWaveSendThread] - NODE 3: Response processed after 52ms/273ms.
2016-02-27 09:13:17.243 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:14:47.268 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:16:17.279 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:17:47.292 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:19:17.301 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:20:47.313 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:22:17.322 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:23:47.327 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:25:17.340 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:26:47.344 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:28:17.350 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:29:47.359 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:31:17.363 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:32:47.371 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:34:17.377 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:35:47.387 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:37:17.405 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:38:47.415 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:40:17.425 [DEBUG] [z.internal.ZWaveNetworkMonitor] - Network Monitor: No nodes to ping!
2016-02-27 09:41:46.749 [DEBUG] [eController$ZWaveReceiveThread] - Receive Message = 01 0A 00 04 00 02 04 71 05 0D FF 71
2016-02-27 09:41:46.760 [DEBUG] [eController$ZWaveReceiveThread] - Receive queue ADD: Length=1
2016-02-27 09:41:46.760 [DEBUG] [b.z.i.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-02-27 09:41:46.777 [DEBUG] [o.b.z.i.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 04 00 02 04 71 05 0D FF 71
2016-02-27 09:41:46.779 [DEBUG] [b.z.i.protocol.ZWaveController] - Process Message = 01 0A 00 04 00 02 04 71 05 0D FF 71
2016-02-27 09:41:46.780 [DEBUG] [b.z.i.protocol.ZWaveController] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 02 04 71 05 0D FF
2016-02-27 09:41:46.782 [DEBUG] [ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:PING)
2016-02-27 09:41:46.784 [DEBUG] [ApplicationCommandMessageClass] - NODE 2: Incoming command class ALARM
2016-02-27 09:41:46.785 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass] - NODE 2: Received Alarm Request
2016-02-27 09:41:46.786 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass] - NODE 2: Alarm report - Value = 255
2016-02-27 09:41:46.787 [ERROR] [z.i.p.c.ZWaveAlarmCommandClass] - NODE 2: Unknown Alarm Type = 13, ignoring report.

Additional info that may/may not help…

This is what I see in my logs after pressing the test button on the ZCOMBO.

zcombo_alarm.json (5.7 KB)

Thanks - this is what I was after. It’s just a standard alarm from - I wanted to see if there was any more information in it.

I suspect that it might be a lifeline type of alarm given it comes out every hour (almost exactly) - that’s a guess though :wink:

Lifeline?

Like a network broadcast message, just announcing it is there and alive?

Yep - that sort of thing… If everyone is getting this ‘alarm’ exactly every hour, then either everyone has a common problem, or it’s some sort of notification. For something you rely on, it makes a lot of sense as you could set up a rule to alert you if you don’t get this for longer than (say) 2 or 3 hours.

Again - without any documentation about the device (which I tried to find, but it was far from useful!) I can’t say for sure…

The alert is exactly what I was thinking if it’s a broadcast message.

And yes, information on this device is hard to come by. A couple of days ago I called tech support at First Alert and asked what the message was and was told I would need to call the maker of my zwave stick because that’s where the message is coming from.

Went round and round for an hour while he went thru documents, and the closest he could get to any zwave info was the blurb on this document at BRK Electronics.

Yep - I found almost exactly the same document - not especially useful…

Per another automation forum in which I participate, signal 13 is a heartbeat. Interestingly, some of the posters there have said their signal 13 shows up every 20 minutes while others have said it shows up every 60 minutes. I have one of these units (sending a heartbeat signal every 60 minutes).

Indeed, it would be possible to setup a notification rule if OH does not receive a heartbeat signal every 61 minutes. Prior to switching to OpenHab, I had my previous system doing just that.

I can add that I’m getting them one per hour as well.

Where does one look to see what the signals mean? Presumably there are alarms 1 through 12 as well?

My reading of the zwave wiki page does not list anything in the supported parameters so I assumed, incorrectly, that the Alarm command class would work like a switch and therefore assigned it to a switch which seems to be the wrong choice.

So from what I’m seeing here it may make more sense to assign it to a Number Item but then question becomes what number would represent the actual alarm? How does one discover this short of lighting a fire under one to actually set it off (manually triggering a test doesn’t seem to do much.

Also, is it possible with the Alarm command class to send a command to one (e.g. the upstairs unit goes off, so trigger the alarms on the other floors)?

Thanks

I’m not sure how to translate this from their system to here exactly, but here’s what I’m seeing:

0 = no notification
1 = alarm smoke silenced
1.255 = alarm smoke
2 = alarm CO silenced
2.255 = alarm CO
9 = alarm malfunctioned
9.255 = alarm malfunction silenced
12 = alarm test silenced
12.255 = alarm test
13.255 = alarm heartbeat
14 = alarm CO sensor end-of-life silenced
14.255 = alarm CO sense end-of-life

I’m not sure how they discover these signals - though I do know their bread and butter is ZWave.

I am not aware of a way to trigger other alarm units in the house. I would love that too!

Thanks! I can work with this.

Great info @Brian!

Well, I took a stab at trying to catch alarm 13 but am doing it wrong. This is what I have:

Items:

Contact Hallway_ZCOMBO “ZCOMBO - Hallway [MAP(zcombo.map):%s]” {zwave=“2:0:command=alarm”}
Number Hallway_ZCOMBO_Heartbeat “Heartbeat [%s]” {zwave=“2:0:command=alarm=13”}
DateTime Hallway_ZCOMBO_Last “Last contact [%1$tm-%1$td %1$tH:%1$tM]”

Rules:

rule "ZCOMBO Heartbeat"
when
Item Hallway_ZCOMBO_Heartbeat received update
then
postUpdate(Hallway_ZCOMBO_Last, new DateTimeType())
end

rule “Smoke Alarm"
when
Item Hallway_ZCOMBO received update
then
if (Hallway_ZCOMBO.state == OPEN) {
sendMail('xxxxxxxxxxx”,“Hallway”,“SMOKE ALARM is sounding!”)
sendMail('xxxxxxxxxxx",“Hallway”,“SMOKE ALARM is sounding!”)
}
if (Hallway_ZCOMBO.state == CLOSED) {
sendMail('xxxxxxxxxxx",“Hallway”,“SMOKE ALARM stopped!”)
sendMail(“xxxxxxxxxxx”,“Hallway”,“SMOKE ALARM stopped!”)
}
end

The rule to update the time to display in my sitemap does update if I press the test button on the smoke detector, but not when alarm 13 triggers.

And the 2nd rule does send me an email and text when the alarm is triggered and then stops.

I’m assuming that my item is wrong.

Thoughts?

Can you do a zwave binding like that (I.e. alarm=13)?

I haven’t tried it yet but I would create a Number item to receive the alarm number and rules to update dummy switches, contacts, etc. as well as the the logic to send alertsband such.

For alarm 13 I would set a timer for 70 minutes and keep rescheduling it when I receive alarm 13. The body of the timer will have an alert to tell me there is a problem.

Well, I’ve struck out on reading alarm 13…

I’ve tried the following number bindings without success:

//doesn’t compile - could not be parsed - not a valid argument
//Number Hallway_ZCOMBO_Heartbeat “Heartbeat [%s]” {zwave=“2:0:command=13”}

//doesn’t compile - could not be parsed - not a valid argument
//Number Hallway_ZCOMBO_Heartbeat “Heartbeat [%s]” {zwave=“2:0:command=alarm_type=13”}

//compiles ok - doesn’t work
//Number Hallway_ZCOMBO_Heartbeat “Heartbeat [%s]” {zwave=“2:0:command=alarm=13”}

//compiles ok - doesn’t work
//Number Hallway_ZCOMBO_Heartbeat “Heartbeat [%s]” {zwave=“2:0:command=alarm, alarm_type=13”}

I’ve also tried modifying the rule that works for catching the alarm like this, and it doesn’t update hourly.

rule "Smoke Alarm"
when
   Item Hallway_ZCOMBO received update
then
   if (Hallway_ZCOMBO.state == OPEN) {
      sendMail("xxxx","Hallway","ALARM is sounding!")	
      sendMail("xxxx","Hallway","ALARM is sounding!")	
   }
   if (Hallway_ZCOMBO.state == CLOSED) {
      sendMail("xxxx","Hallway","ALARM stopped!")	
      sendMail("xxxx","Hallway","ALARM stopped!")	
   }

   //update last contact
   postUpdate(Hallway_ZCOMBO_Last, new DateTimeType())
end