I have managed to configuring one sensor with Habmin. Sofar i am using the “scenes” to report a different number when opening and closing.
Any others that do have a working config?
FYI, when you add the sensors, you will need to exclude the device from the network and add it back again.
OK, thanks for the information :slight_smile
Is it possible to read the contact part as a bainary sensor (omitting the scene stuff) . When I try that, it seems like nothing at all is reported from the Z-Wave network or the binding.
But scenes works just fine, though there is problems setting some sensible default values for eg. temperature reporting interval. From PaperUI it is only allowed to set this interval to 1 - i guess that is seconds 
The device (I assume) should send a binary sensor status - I see that it will do that at least for the external input (according to the manual). Also, looking at parameter 20, it seems to indicate that an alarm notification will be sent.
So, I would grab a debug log and see what is being sent. Load it into the log viewer as it should help display this.
Ideally, it would be good to update the database once we know what all the different notifications do…
Just as a follow up from this I am pleased to say that the device included fine and worked fine first time.
The only slight issue was that I had to create an association between the ‘Control’ group 2 and my controller. But since then the device is working perfectly and now seems to wake up and sleep also which it did not do before.
Thanks Chris
Hi,
I have found a configuration that seems to make it possible to use the device as the old one. My primary mistake was that I where so focused on the Configuration Parameter section, that I didn’t look carefull enough in the Association Groups. Every now and then during configuration it just forgets the Lifeline Association.
Besides from that there is some problems with the configurationparameters. Not all parameters is allowed, found that the default suggested values for the parameters below isn’t allowed in PaperUI (it also seems to give some problems in Habmin, but not that significant:
Parameter 12. Value of ON command frame sent to 2nd association group is 255, but max. allowed i 99
Parameter 51: Temperature reports threshold is 10, but maximum allowed is 1
Parameter 70. Scene activation functionality. Is 0, but minimum allowed is set to 1.
Parameter 72. Associations in Z-Wave network Security Mode. Maximum allowed is 8.
I believe the description is fine, in reality I just can’t set the value to a decent value. Hope you can fix this in your database.
If somebody is interested in a working config, I can post it.
And once again, you are doing a wonderfull job Chris. Habmin under OH2 looks very interesting.
I installed the latest binding (which I assume is this) and things look much better now: I have the configuration parameters and Association Group visible in HABmin, and I can also see a reaction to the magnet switch.
- FGK has everything on default except association group 1 “Lifeline” is associated to my controller
- Openhab item config (got these from examples, I don’t know how to figure these out myself):
Contact zswitch "Z-Wave switch [%s]" {zwave="5:command=sensor_binary,respond_to_basic=TRUE"}
Contact zalarm "Z-Wave tamper [%s]" {zwave="5:command=alarm,respond_to_basic=TRUE"}
Number zbattery "Z-Wave battery [%s %%]" {zwave="5:command=BATTERY"}
I tried the different association options with following results:
Association to “Lifeline”:
zalarm state updates to CLOSED when magnet is introduced or removed
Association to “Control”:
zalarm and zswitch both get updated twice to OPEN/CLOSED according to the magnet position
Association to “Alarm”:
nothing
Association to “Sensor ZW3”:
zswitch get updated twice to OPEN/CLOSED according to the magnet position
Association to “Tamper ZW3”:
nothing
I only tried the switch methodically, but tamper doesn’t seem to do anything with any of them and battery updates occasionally.
I’d appreciate if someone could share a working config.
You have “respond_to_basic” on two items - this will not be good and will definately result in incorrect notifications. That said, it probably doesn’t impact on your problem with the tamper switch not working.
The tamper switch might use the new version of the alarm command class which may not be processed correctly. Can you confirm what is actually seen in the debug log when you press the tamper button?
For the battery, it’s normal that this is only updates periodically (maximum of once per hour, but it can be less).
I removed the “respond_to_basic” from both items and went through the associations again:
Lifeline: no change
Control: nothing
Alarm: no change
Sensor ZW3: no change
Here is a debug with the Lifeline association enabled and the tamper pressed and then released:
2016-08-02 16:17:49.617 [DEBUG] [eController$ZWaveReceiveThread:1530]- Receive Message = 01 0F 00 04 00 05 09 71 05 00 00 00 FF 07 00 00 74
2016-08-02 16:17:49.621 [DEBUG] [b.z.i.protocol.ZWaveController:1194]- Receive queue TAKE: Length=0
2016-08-02 16:17:49.622 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ]- Assembled message buffer = 01 0F 00 04 00 05 09 71 05 00 00 00 FF 07 00 00 74
2016-08-02 16:17:49.623 [DEBUG] [b.z.i.protocol.ZWaveController:1195]- Process Message = 01 0F 00 04 00 05 09 71 05 00 00 00 FF 07 00 00 74
2016-08-02 16:17:49.625 [DEBUG] [b.z.i.protocol.ZWaveController:194 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 05 09 71 05 00 00 00 FF 07 00 00
2016-08-02 16:17:49.648 [DEBUG] [eController$ZWaveReceiveThread:1446]- Receive queue ADD: Length=0
2016-08-02 16:17:49.648 [DEBUG] [ApplicationCommandMessageClass:40 ]- NODE 5: Application Command Request (ALIVE:DONE)
2016-08-02 16:17:49.648 [DEBUG] [ApplicationCommandMessageClass:58 ]- NODE 5: Incoming command class ALARM
2016-08-02 16:17:49.648 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:82 ]- NODE 5: Received Alarm Request
2016-08-02 16:17:49.649 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:94 ]- NODE 5: Alarm report - Value = 0
2016-08-02 16:17:49.649 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:113 ]- NODE 5: Alarm Type = General (0)
2016-08-02 16:17:49.649 [DEBUG] [b.z.i.protocol.ZWaveController:648 ]- Notifying event listeners: ZWaveAlarmValueEvent
2016-08-02 16:17:49.649 [DEBUG] [.z.internal.ZWaveActiveBinding:449 ]- ZwaveIncomingEvent
2016-08-02 16:17:49.649 [DEBUG] [.z.internal.ZWaveActiveBinding:466 ]- NODE 5: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
2016-08-02 16:17:49.650 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:66 ]- Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 05 02 84 08
2016-08-02 16:17:49.650 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:67 ]- Recv message Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 05 09 71 05 00 00 00 FF 07 00 00
2016-08-02 16:17:49.650 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:68 ]- Checking transaction complete: class=ApplicationCommandHandler, expected=SendData, cancelled=false
2016-08-02 16:18:29.605 [DEBUG] [eController$ZWaveReceiveThread:1530]- Receive Message = 01 0F 00 04 00 05 09 71 05 00 00 00 FF 07 03 00 77
2016-08-02 16:18:29.608 [DEBUG] [b.z.i.protocol.ZWaveController:1194]- Receive queue TAKE: Length=0
2016-08-02 16:18:29.610 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ]- Assembled message buffer = 01 0F 00 04 00 05 09 71 05 00 00 00 FF 07 03 00 77
2016-08-02 16:18:29.611 [DEBUG] [b.z.i.protocol.ZWaveController:1195]- Process Message = 01 0F 00 04 00 05 09 71 05 00 00 00 FF 07 03 00 77
2016-08-02 16:18:29.613 [DEBUG] [b.z.i.protocol.ZWaveController:194 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 05 09 71 05 00 00 00 FF 07 03 00
2016-08-02 16:18:29.612 [DEBUG] [eController$ZWaveReceiveThread:1446]- Receive queue ADD: Length=0
2016-08-02 16:18:29.614 [DEBUG] [ApplicationCommandMessageClass:40 ]- NODE 5: Application Command Request (ALIVE:DONE)
2016-08-02 16:18:29.615 [DEBUG] [ApplicationCommandMessageClass:58 ]- NODE 5: Incoming command class ALARM
2016-08-02 16:18:29.615 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:82 ]- NODE 5: Received Alarm Request
2016-08-02 16:18:29.616 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:94 ]- NODE 5: Alarm report - Value = 0
2016-08-02 16:18:29.621 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:113 ]- NODE 5: Alarm Type = General (0)
2016-08-02 16:18:29.621 [DEBUG] [b.z.i.protocol.ZWaveController:648 ]- Notifying event listeners: ZWaveAlarmValueEvent
2016-08-02 16:18:29.622 [DEBUG] [.z.internal.ZWaveActiveBinding:449 ]- ZwaveIncomingEvent
2016-08-02 16:18:29.626 [DEBUG] [.z.internal.ZWaveActiveBinding:466 ]- NODE 5: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
2016-08-02 16:18:29.630 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:66 ]- Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 05 02 84 08
2016-08-02 16:18:29.633 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:67 ]- Recv message Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 05 09 71 05 00 00 00 FF 07 03 00
2016-08-02 16:18:29.642 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:68 ]- Checking transaction complete: class=ApplicationCommandHandler, expected=SendData, cancelled=false
Anything new about this? I’m a bit confused whether anyone has gotten this new firmware version working with OH(1) or not. Is there anything I can do?
Looking at the log, the device is sending the ALARM message, so the item should be configured appropriately.
That’s what I thought as well. Yet something is wrong because using the Lifeline association, I’m getting “zalarm state updated to CLOSED” whenever the tamper or the switch is either opened or closed.
I think this is correct. The “new” NOTIFICATION command class (V2) sends notifications for events - I don’t think it sends an event with there is no tamper.
I see. What about the switch (magnet)? I’m getting the same “zalarm CLOSED” as well, doesn’t matter if the switch is actually closed or opened. Surely it should say the correct state?
The log says:
2016-08-08 23:40:32.567 [DEBUG] [eController$ZWaveReceiveThread:1530]- Receive Message = 01 0D 00 04 08 06 07 9C 02 06 00 00 00 00 67
2016-08-08 23:40:32.570 [DEBUG] [b.z.i.protocol.ZWaveController:1194]- Receive queue TAKE: Length=0
2016-08-08 23:40:32.571 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ]- Assembled message buffer = 01 0D 00 04 08 06 07 9C 02 06 00 00 00 00 67
2016-08-08 23:40:32.572 [DEBUG] [b.z.i.protocol.ZWaveController:1195]- Process Message = 01 0D 00 04 08 06 07 9C 02 06 00 00 00 00 67
2016-08-08 23:40:32.572 [DEBUG] [b.z.i.protocol.ZWaveController:194 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 08 06 07 9C 02 06 00 00 00 00
2016-08-08 23:40:32.573 [DEBUG] [ApplicationCommandMessageClass:40 ]- NODE 6: Application Command Request (ALIVE:DONE)
2016-08-08 23:40:32.574 [DEBUG] [ApplicationCommandMessageClass:58 ]- NODE 6: Incoming command class SENSOR_ALARM
2016-08-08 23:40:32.574 [DEBUG] [c.ZWaveAlarmSensorCommandClass:85 ]- NODE 6: Received Sensor Alarm Request
2016-08-08 23:40:32.573 [DEBUG] [eController$ZWaveReceiveThread:1446]- Receive queue ADD: Length=0
2016-08-08 23:40:32.575 [DEBUG] [c.ZWaveAlarmSensorCommandClass:104 ]- NODE 6: Alarm Report: Source=6, Type=General(0), Value=0
2016-08-08 23:40:32.576 [DEBUG] [b.z.i.protocol.ZWaveController:648 ]- Notifying event listeners: ZWaveAlarmSensorValueEvent
2016-08-08 23:40:32.576 [DEBUG] [.z.internal.ZWaveActiveBinding:449 ]- ZwaveIncomingEvent
2016-08-08 23:40:32.577 [DEBUG] [.z.internal.ZWaveActiveBinding:466 ]- NODE 6: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_ALARM, value = 0
2016-08-08 23:40:32.577 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:66 ]- Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 06 02 84 08
2016-08-08 23:40:32.582 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:67 ]- Recv message Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 08 06 07 9C 02 06 00 00 00 00
2016-08-08 23:40:32.585 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:68 ]- Checking transaction complete: class=ApplicationCommandHandler, expected=SendData, cancelled=false
2016-08-08 23:40:32.586 [DEBUG] [eController$ZWaveReceiveThread:1530]- Receive Message = 01 0D 00 04 00 06 07 9C 02 06 00 00 00 00 6F
2016-08-08 23:40:32.591 [DEBUG] [eController$ZWaveReceiveThread:1446]- Receive queue ADD: Length=1
2016-08-08 23:40:32.592 [DEBUG] [b.z.i.protocol.ZWaveController:1194]- Receive queue TAKE: Length=0
2016-08-08 23:40:32.592 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ]- Assembled message buffer = 01 0D 00 04 00 06 07 9C 02 06 00 00 00 00 6F
2016-08-08 23:40:32.592 [DEBUG] [b.z.i.protocol.ZWaveController:1195]- Process Message = 01 0D 00 04 00 06 07 9C 02 06 00 00 00 00 6F
2016-08-08 23:40:32.592 [DEBUG] [b.z.i.protocol.ZWaveController:194 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 06 07 9C 02 06 00 00 00 00
2016-08-08 23:40:32.592 [DEBUG] [ApplicationCommandMessageClass:40 ]- NODE 6: Application Command Request (ALIVE:DONE)
2016-08-08 23:40:32.592 [DEBUG] [ApplicationCommandMessageClass:58 ]- NODE 6: Incoming command class SENSOR_ALARM
2016-08-08 23:40:32.592 [DEBUG] [c.ZWaveAlarmSensorCommandClass:85 ]- NODE 6: Received Sensor Alarm Request
2016-08-08 23:40:32.593 [DEBUG] [c.ZWaveAlarmSensorCommandClass:104 ]- NODE 6: Alarm Report: Source=6, Type=General(0), Value=0
2016-08-08 23:40:32.593 [DEBUG] [b.z.i.protocol.ZWaveController:648 ]- Notifying event listeners: ZWaveAlarmSensorValueEvent
2016-08-08 23:40:32.593 [DEBUG] [.z.internal.ZWaveActiveBinding:449 ]- ZwaveIncomingEvent
2016-08-08 23:40:32.593 [DEBUG] [.z.internal.ZWaveActiveBinding:466 ]- NODE 6: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_ALARM, value = 0
2016-08-08 23:40:32.593 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:66 ]- Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 06 02 84 08
2016-08-08 23:40:32.595 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:67 ]- Recv message Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 06 07 9C 02 06 00 00 00 00
2016-08-08 23:40:32.595 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:68 ]- Checking transaction complete: class=ApplicationCommandHandler, expected=SendData, cancelled=false
2016-08-08 23:40:37.835 [DEBUG] [eController$ZWaveReceiveThread:1530]- Receive Message = 01 0D 00 04 08 06 07 9C 02 06 00 FF 00 00 98
2016-08-08 23:40:37.836 [DEBUG] [eController$ZWaveReceiveThread:1446]- Receive queue ADD: Length=1
2016-08-08 23:40:37.837 [DEBUG] [b.z.i.protocol.ZWaveController:1194]- Receive queue TAKE: Length=0
2016-08-08 23:40:37.837 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ]- Assembled message buffer = 01 0D 00 04 08 06 07 9C 02 06 00 FF 00 00 98
2016-08-08 23:40:37.837 [DEBUG] [b.z.i.protocol.ZWaveController:1195]- Process Message = 01 0D 00 04 08 06 07 9C 02 06 00 FF 00 00 98
2016-08-08 23:40:37.837 [DEBUG] [b.z.i.protocol.ZWaveController:194 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 08 06 07 9C 02 06 00 FF 00 00
2016-08-08 23:40:37.837 [DEBUG] [ApplicationCommandMessageClass:40 ]- NODE 6: Application Command Request (ALIVE:DONE)
2016-08-08 23:40:37.837 [DEBUG] [ApplicationCommandMessageClass:58 ]- NODE 6: Incoming command class SENSOR_ALARM
2016-08-08 23:40:37.838 [DEBUG] [c.ZWaveAlarmSensorCommandClass:85 ]- NODE 6: Received Sensor Alarm Request
2016-08-08 23:40:37.838 [DEBUG] [c.ZWaveAlarmSensorCommandClass:104 ]- NODE 6: Alarm Report: Source=6, Type=General(0), Value=255
2016-08-08 23:40:37.838 [DEBUG] [b.z.i.protocol.ZWaveController:648 ]- Notifying event listeners: ZWaveAlarmSensorValueEvent
2016-08-08 23:40:37.838 [DEBUG] [.z.internal.ZWaveActiveBinding:449 ]- ZwaveIncomingEvent
2016-08-08 23:40:37.838 [DEBUG] [.z.internal.ZWaveActiveBinding:466 ]- NODE 6: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_ALARM, value = 255
2016-08-08 23:40:37.838 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:66 ]- Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 06 02 84 08
2016-08-08 23:40:37.838 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:67 ]- Recv message Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 08 06 07 9C 02 06 00 FF 00 00
2016-08-08 23:40:37.838 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:68 ]- Checking transaction complete: class=ApplicationCommandHandler, expected=SendData, cancelled=false
2016-08-08 23:40:37.894 [DEBUG] [eController$ZWaveReceiveThread:1530]- Receive Message = 01 0D 00 04 00 06 07 9C 02 06 00 FF 00 00 90
2016-08-08 23:40:37.903 [DEBUG] [eController$ZWaveReceiveThread:1446]- Receive queue ADD: Length=1
2016-08-08 23:40:37.903 [DEBUG] [b.z.i.protocol.ZWaveController:1194]- Receive queue TAKE: Length=0
2016-08-08 23:40:37.903 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ]- Assembled message buffer = 01 0D 00 04 00 06 07 9C 02 06 00 FF 00 00 90
2016-08-08 23:40:37.903 [DEBUG] [b.z.i.protocol.ZWaveController:1195]- Process Message = 01 0D 00 04 00 06 07 9C 02 06 00 FF 00 00 90
2016-08-08 23:40:37.904 [DEBUG] [b.z.i.protocol.ZWaveController:194 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 06 07 9C 02 06 00 FF 00 00
2016-08-08 23:40:37.904 [DEBUG] [ApplicationCommandMessageClass:40 ]- NODE 6: Application Command Request (ALIVE:DONE)
2016-08-08 23:40:37.904 [DEBUG] [ApplicationCommandMessageClass:58 ]- NODE 6: Incoming command class SENSOR_ALARM
2016-08-08 23:40:37.904 [DEBUG] [c.ZWaveAlarmSensorCommandClass:85 ]- NODE 6: Received Sensor Alarm Request
2016-08-08 23:40:37.904 [DEBUG] [c.ZWaveAlarmSensorCommandClass:104 ]- NODE 6: Alarm Report: Source=6, Type=General(0), Value=255
2016-08-08 23:40:37.904 [DEBUG] [b.z.i.protocol.ZWaveController:648 ]- Notifying event listeners: ZWaveAlarmSensorValueEvent
2016-08-08 23:40:37.904 [DEBUG] [.z.internal.ZWaveActiveBinding:449 ]- ZwaveIncomingEvent
2016-08-08 23:40:37.904 [DEBUG] [.z.internal.ZWaveActiveBinding:466 ]- NODE 6: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_ALARM, value = 255
2016-08-08 23:40:37.906 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:66 ]- Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 06 02 84 08
2016-08-08 23:40:37.906 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:67 ]- Recv message Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 06 07 9C 02 06 00 FF 00 00
2016-08-08 23:40:37.907 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:68 ]- Checking transaction complete: class=ApplicationCommandHandler, expected=SendData, cancelled=falseThe OH1 binding might not correctly process the NOTIFICATION command - I’ll take a look at the log…
Please can you post the log using the </> button to highlight the text - not a quote as I can’t process this - sorry.
Thanks, I edited the post.
It looks ok to me - it’s sending 0 and 255 which is correct. What is the item definition for this - are you using the sensor_alarm command class - it looks like you might be using sensor_binary?
My settings right now:
Contact zswitch "Z-Wave switch [%s]" {zwave="6:command=sensor_binary"}
Contact zalarm "Z-Wave tamper [%s]" {zwave="6:command=sensor_alarm"}
Number zbattery "Z-Wave battery [%s %%]" {zwave="6:command=BATTERY"}
Previously I had the zalarm item as “command=alarm”, which gave me the constant “zalarm CLOSED” when using the magnet or the tamper. Now I get nothing from either.
Experimented some more with the associations now that I have the zalarm item as sensor_alarm. I added associations for Sensor ZW3 and Tamper ZW3 (in addition to Lifeline). I now get correct states for both tamper and magnet, but it’s printed twice as such:
2016-08-09 23:47:10.265 [INFO ] [runtime.busevents ] - zswitch state updated to CLOSED 2016-08-09 23:47:10.282 [INFO ] [runtime.busevents ] - zswitch state updated to CLOSED 2016-08-09 23:47:44.267 [INFO ] [runtime.busevents ] - zswitch state updated to OPEN 2016-08-09 23:47:44.290 [INFO ] [runtime.busevents ] - zswitch state updated to OPEN 2016-08-09 23:47:52.672 [INFO ] [runtime.busevents ] - zalarm state updated to CLOSED 2016-08-09 23:47:52.695 [INFO ] [runtime.busevents ] - zalarm state updated to CLOSED 2016-08-09 23:47:58.486 [INFO ] [runtime.busevents ] - zalarm state updated to OPEN 2016-08-09 23:47:58.496 [INFO ] [runtime.busevents ] - zalarm state updated to OPEN.
Does that help at all…?
In this log, the log shows the ALARM command class, so I would assume from what you write that ALARM = TAMPER.
From this log, I see SENSOR_ALARM so I assume SENSOR_ALARM = CONTACT.
I’m a bit confused about your association comments. You should ONLY need the lifeline association. If you add more associations, then you will likely get multiple requests which might confuse your rules, and waste power in the sensor. I do see every message being duplicated in your logs, so I’m guessing you have multiple associations configured?
I’m a bit confused about your association comments. You should ONLY need
the lifeline association. If you add more associations, then you will
likely get multiple requests which might confuse your rules, and waste
power in the sensor. I do see every message being duplicated in your
logs, so I’m guessing you have multiple associations configured?
That was just me experimenting to see what happens. Never mind about that 
What I was trying to say is that while using the Lifeline association I’m not getting any response to my zswitch and zalarm items above. If I configure the association with Sensor ZW3 or Tamper ZW3 (one at a time, no multiple associations configured) I start getting correct responses to the items BUT they are duplicated. Just an observation.