Siren starts sounding randomly

Setup, Configuration and Use Beginners
, ,
1

My POP smoke detector and siren is randomly sounding starting this night waking the family. I can see in the openHAB app that it is not triggered by the smoke detector. I guess it is some other device triggering it. In HABmin I have set some other devices to point to the smoke detector as Lifeline under Association group. My thought was to make the smoke detector as some sort of hub since it is closer to some sensors than the controller and the detector has the ability to route messages. Im I wrong in using the lifeline like so? Can that be the cause of the siren sounding?

Does the network arrange it self in the heal so I don’t have to worry about it?

Here is the log when the siren started sounding:

2017-04-28 07:53:23.923 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 1C 03 25 03 FF 34 
2017-04-28 07:53:23.932 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT 6
2017-04-28 07:53:23.939 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage inputMessage: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=28, callback=0, payload=00 1C 03 25 03 FF 
2017-04-28 07:53:23.944 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lockMessage: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=28, callback=0, payload=00 1C 03 25 03 FF 
2017-04-28 07:53:23.949 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=28, callback=0, payload=00 1C 03 25 03 FF 
2017-04-28 07:53:23.951 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2017-04-28 07:53:23.953 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 28: Application Command Request (ALIVE:DONE)
2017-04-28 07:53:23.954 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 28: resetResendCount initComplete=true isDead=false
2017-04-28 07:53:23.956 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 28: Incoming command class COMMAND_CLASS_SWITCH_BINARY, endpoint 0
2017-04-28 07:53:23.957 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 28: SECURITY not supported
2017-04-28 07:53:23.959 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 28: Received COMMAND_CLASS_SWITCH_BINARY V1 SWITCH_BINARY_REPORT
2017-04-28 07:53:23.960 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 28: Switch Binary report, value = 255
2017-04-28 07:53:23.962 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2017-04-28 07:53:23.963 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 28: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-04-28 07:53:23.965 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 28: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SWITCH_BINARY, value = 255
2017-04-28 07:53:23.968 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 28: Updating channel state zwave:device:152b12ad:node28:switch_binary to ON [OnOffType]
2017-04-28 07:53:23.974 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 28: Commands processed 1.
2017-04-28 07:53:23.975 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 28: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@13f016b.
2

Yes, lifeline should only be set to the controller.
BTW, battery operated devices like the POPP smoke detector do not act as a repeater, only mains powered devices.

3

Thanks @sihui. Sometimes when looking at the Network viewer it looks like my POP smoke sensor is routing stuff. But I see now that the Basic class is …ROUTING_SLAVE.

What about the triggered siren? Can I somehow “debug” what triggered the switch for the siren? Right now I cannot have the batteries in the siren because it goes of all the time!

4

Take a look into your events.log, the event shortly before the “siren on” event should be the problem.
Delete all associations (on your other devices) which do NOT point to the controller.

5

The event log looks like:

2017-04-30 14:19:00.794 [ConfigStatusInfoEvent     ] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=group_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]
2017-04-30 14:26:25.564 [ItemStateChangedEvent     ] - Siren_switch_node_28 changed from OFF to ON
2017-04-30 14:26:50.574 [ItemCommandEvent          ] - Item 'Siren_switch_node_28' received command ON

As you can see there is no event just before the siren is set to ON. The event on 14:25:50 is me trying to turn it of from HABmin but the state there was OFF and the command sent was ON.

I can still see that some devices have Node 28 as Lifeline in Association groups even though I have changed it. Now setting the controller as Lifeline that property is pending. And is pending even though I have manually woken up those devices. They are all on battery. Do you think that the association is the problem @sihui?

6

I’m pretty sure that is your problem.

Try it multiple times, sometimes it takes a while. And don’t forget that simply triggering the devices don’t wake them up, you have to manually push a button for that …

7

Now the siren seems to be quiet. It took some hard work to set all devices to controller as Lifeline. You were right @sihui, big thanks!

1 Like