- Platform information:
- Hardware: Raspberry PI 3B+ CPU = 1.4 GHz / Architecture = 64Bit / RAM = 1 GB/Storage = 32 GB
- OS: Linux (OpenHabian)
- Java Runtime Environment: 1.8.0_152-b76
- openHAB version: 2.4
I have 5 Kwikset Z-Wave Door locks and I’m trying to get things setup so that if someone unlocks or locks the door without using OpenHab, OpenHab gets updated.
A lot of posts that I’ve seen recommend putting the controller into Association groups/Lifeline Association Groups on the locks.
I used Habmin to do that and think I have it setup correctly but it still doesn’t work.
I have noticed that when I look at event.log the alarm status is coming through in close proximity to when I manually lock\unlock the door.
2019-01-08 15:42:18.808 [vent.ItemStateChangedEvent] - Lock_LivingRoom_BasementDoor_Alarm changed from 0 to 21
2019-01-08 15:42:18.822 [vent.ItemStateChangedEvent] - Lock_LivingRoom_BasementDoor_AlarmRaw changed from {"type":"0","value":"0"} to {"type":"21","value":"1"}
But there is never any event indicating that the door lock changed from ON to OFF.
Several posts suggested turning up debugging on ZWave. This is what I get in openhab.log
2019-01-08 15:42:18.775 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 19: Application Command Request (ALIVE:DONE)
2019-01-08 15:42:18.777 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 19: resetResendCount initComplete=true isDead=false
2019-01-08 15:42:18.779 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 19: Decapsulating COMMAND_CLASS_SECURITY
2019-01-08 15:42:18.783 [DEBUG] [mmandclass.ZWaveSecurityCommandClass] - NODE 19: SECURITY_RXD 71 05 15 01
2019-01-08 15:42:18.785 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 19: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2019-01-08 15:42:18.787 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 19: Received COMMAND_CLASS_ALARM V1 NOTIFICATION_REPORT
2019-01-08 15:42:18.788 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 19: ALARM report - 21 = 1
2019-01-08 15:42:18.790 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 19: Alarm Type = null (21)
2019-01-08 15:42:18.792 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2019-01-08 15:42:18.793 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 19: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 1
2019-01-08 15:42:18.796 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 19: Alarm converter processing ALARM
2019-01-08 15:42:18.797 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 19: Updating channel state zwave:device:9fca719e:node19:alarm_number to 21 [DecimalType]
2019-01-08 15:42:18.800 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 19: Alarm converter processing ALARM
2019-01-08 15:42:18.803 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 19: Updating channel state zwave:device:9fca719e:node19:alarm_raw to {"type":"21","value":"1"} [StringType]
2019-01-08 15:42:18.807 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 19: Commands processed 1.
2019-01-08 15:42:18.808 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 19: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@ca38ac.
The only way I ever see the change register is if I wait for my polling interval to elapse (currently set at 10 minutes) but there’s no shortage of documentation or posts advising against speeding up the polling interval so I don’t want to rely on polling if I can avoid it.