Weiser 914 Door lock reporting as dead

[Steven_Reimer]

Regarding my Weiser (Kwikset) 914TRL Touchpad Electronic Deadbolt

I tried to setup some months ago prior to secure communication being available. Now attempting with v2.2.0~20171005035626-1.

I have excluded, and re-included it and it shows in shows in habmin as online, but when I try to lock or unlock the log says it’s dead

What are my next steps?

2017-10-16 17:23:34.938 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Command received zwave:device:daf1f88d:node25:lock_door --> OFF
2017-10-16 17:23:34.939 [DEBUG] [mmandclass.ZWaveDoorLockCommandClass] - NODE 25: Creating new message for application command DOORLOCK_SET
2017-10-16 17:23:34.939 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2017-10-16 17:23:34.939 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-10-16 17:23:34.939 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 13 19 03 62 01 00 25 07 BD
2017-10-16 17:23:34.939 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 25: Sending REQUEST Message = 01 0A 00 13 19 03 62 01 00 25 07 BD
2017-10-16 17:23:35.739 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
2017-10-16 17:23:35.740 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-10-16 17:23:35.740 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
2017-10-16 17:23:35.740 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
2017-10-16 17:23:35.741 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, c
allback=0, payload=01
2017-10-16 17:23:35.741 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 25: Sent Data successfully placed on stack.
2017-10-16 17:23:39.241 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 05 00 13 07 01 EF
2017-10-16 17:23:39.245 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-10-16 17:23:39.245 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 13 07 01 00 00 ED
2017-10-16 17:23:39.245 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 13 07 01 00 00 ED
2017-10-16 17:23:39.245 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=07 01
2017-10-16 17:23:39.245 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 25: SendData Request. CallBack ID = 7, Status = Transmission complete, no ACK received(1)
2017-10-16 17:23:39.245 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 25: Node is DEAD. Dropping message.
2017-10-16 17:23:39.245 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2017-10-16 17:23:39.246 [DEBUG] [curityCommandClassWithInitialization] - NODE 25: updating lastSentMessageTimestamp
2017-10-16 17:23:39.246 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 25: Node advancer - VERSION: Transaction complete (SendData:Request) success(false)
2017-10-16 17:23:39.246 [DEBUG] [curityCommandClassWithInitialization] - NODE 25: updating lastSentMessageTimestamp
2017-10-16 17:23:39.246 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 25: Response processed after 3525ms/4208ms.
2017-10-16 17:23:46.405 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Command received zwave:device:daf1f88d:node25:lock_door --> ON
2017-10-16 17:23:46.405 [DEBUG] [mmandclass.ZWaveDoorLockCommandClass] - NODE 25: Creating new message for application command DOORLOCK_SET
2017-10-16 17:23:46.405 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2017-10-16 17:23:46.405 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-10-16 17:23:46.405 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 13 19 03 62 01 FF 25 08 4D
2017-10-16 17:23:46.406 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 25: Sending REQUEST Message = 01 0A 00 13 19 03 62 01 FF 25 08 4D
2017-10-16 17:23:47.312 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
2017-10-16 17:23:47.315 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-10-16 17:23:47.315 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
2017-10-16 17:23:47.315 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
2017-10-16 17:23:47.315 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
2017-10-16 17:23:47.316 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 25: Sent Data successfully placed on stack.
2017-10-16 17:23:50.846 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 05 00 13 08 01 E0
2017-10-16 17:23:50.848 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-10-16 17:23:50.848 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 13 08 01 00 00 E2
2017-10-16 17:23:50.849 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 13 08 01 00 00 E2
2017-10-16 17:23:50.849 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=08 01
2017-10-16 17:23:50.849 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 25: SendData Request. CallBack ID = 8, Status = Transmission complete, no ACK received(1)
2017-10-16 17:23:50.849 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 25: Node is DEAD. Dropping message.
2017-10-16 17:23:50.849 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2017-10-16 17:23:50.849 [DEBUG] [curityCommandClassWithInitialization] - NODE 25: updating lastSentMessageTimestamp
2017-10-16 17:23:50.849 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 25: Node advancer - VERSION: Transaction complete (SendData:Request) success(false)
2017-10-16 17:23:50.850 [DEBUG] [curityCommandClassWithInitialization] - NODE 25: updating lastSentMessageTimestamp
2017-10-16 17:23:50.850 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 25: Response processed after 3558ms/4208ms.

[rlkoshak (Rich Koshak)]

You must use the binding from the following thread. The security command class is still in development and under testing and must be downloaded separately.

OH2 Z-Wave refactoring and testing... and SECURITY

The latest version of the development binding dated 8th Sep 2018 is here. Toward the end of last year I spent some time doing some initial refactoring of the ZWave binding in OH2. This focussed on rewriting the way transactions work as this is an enabler for other areas of the code. At the same time I also restructured the different layers of the binding to make things cleaner, and done some changes to support a system of autocoding the command classes directly from the Z-Wave standard which s…

[Steven_Reimer]

Thanks, I’m already using the unstable apt branch. I’ll have to decide whether to wait for a merge into the main branch or manual add this.