Help with Kwikset HomeConnect 620 and Aeotec Z-wave stick

As mentioned earlier, I don’t have a zwave lock :wink: How far away is the lock from the controller, How close is it to your nearest powered Zwave node? The zwave debug file will provide if communication is happening.

Actually I have not used the sematic model either, but I do not think “point” and “switch” are mutually exclusive. The channel is set up with the binding as ON_OFF

I recently moved and I’m adding a security system. I started to use openHab a year or so ago but got interrupted with the move.
The physical lock is sitting on the desk with the openHabian raspberry pi with z stick. Less than a foot separation.
This is my first zwave node. I’ve setup wifi nodes with no trouble. I’m am getting too many wifi devices so I decided to expand to zwave and add a couple of locks and some motion detectors. Next is a zigbee momentary switch for my driveway gate opener. It will use a 5 year old digi xstick for the coordinator which I used it on a old system so I’m expecting problems with it as well. But just one step at a time and those are apparently small steps.

I deleted the thing and items once again and also did a factory reset on the KS lock. Rebuilt the thing and item. No perceptible change.
I did notice that I still have two zwave bindings.

269 │ Active │ 80 │ 3.4.0.202208090348 │ openHAB Add-ons :: Bundles :: ZWave Binding
270 │ Active │ 80 │ 3.3.0 │ openHAB Add-ons :: Bundles :: ZWave Binding

Looks like one for version 3.4 and one for 3.3. The 3.4 is the new one I just added.

Here is the debug output from doing a couple of open/close from the item:
Nothing jumps out at me but then I don’t have any experience looking at this stuff.

==> /var/log/openhab/events.log <==
2022-08-13 18:57:52.489 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' received command OFF
2022-08-13 18:57:52.491 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' predicted to become OFF
2022-08-13 18:57:52.498 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' changed from ON to OFF
==> /var/log/openhab/openhab.log <==
2022-08-13 18:57:54.009 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling...
2022-08-13 18:57:54.010 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling deferred until initialisation complete
2022-08-13 18:57:54.505 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Command received zwave:device:cd2ff9fc7d:node4:lock_door --> ON [OnOffType]
2022-08-13 18:57:54.506 [DEBUG] [mmandclass.ZWaveDoorLockCommandClass] - NODE 4: Creating new message for application command DOORLOCK_SET, value 255
2022-08-13 18:57:54.507 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY required on COMMAND_CLASS_DOOR_LOCK
2022-08-13 18:57:54.508 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Command Class COMMAND_CLASS_DOOR_LOCK is required to be secured
2022-08-13 18:57:54.509 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Bump transaction 304 priority from Get to Immediate
2022-08-13 18:57:54.510 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Adding to device queue
2022-08-13 18:57:54.511 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Transaction already in queue - removed original
2022-08-13 18:57:54.512 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Added 304 to queue - size 2
2022-08-13 18:57:54.513 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2022-08-13 18:57:54.514 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling initialised at 86400 seconds - start in 1500 milliseconds.
==> /var/log/openhab/events.log <==
2022-08-13 18:57:54.484 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' received command ON
2022-08-13 18:57:54.493 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' predicted to become ON
2022-08-13 18:57:54.496 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' changed from OFF to ON
==> /var/log/openhab/openhab.log <==
2022-08-13 18:57:56.015 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling...
2022-08-13 18:57:56.015 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling deferred until initialisation complete
2022-08-13 18:57:56.321 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Command received zwave:device:cd2ff9fc7d:node4:lock_door --> OFF [OnOffType]
2022-08-13 18:57:56.321 [DEBUG] [mmandclass.ZWaveDoorLockCommandClass] - NODE 4: Creating new message for application command DOORLOCK_SET, value 0
2022-08-13 18:57:56.322 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY required on COMMAND_CLASS_DOOR_LOCK
2022-08-13 18:57:56.323 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Command Class COMMAND_CLASS_DOOR_LOCK is required to be secured
2022-08-13 18:57:56.324 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Bump transaction 305 priority from Get to Immediate
2022-08-13 18:57:56.325 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Adding to device queue
2022-08-13 18:57:56.326 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Transaction already in queue - removed original
2022-08-13 18:57:56.326 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Added 305 to queue - size 2
2022-08-13 18:57:56.327 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2022-08-13 18:57:56.328 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling initialised at 86400 seconds - start in 1500 milliseconds.
2022-08-13 18:57:56.944 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 4: TID 300: Timeout at state WAIT_DATA. 3 retries remaining.
2022-08-13 18:57:56.945 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 300: Transaction CANCELLED
2022-08-13 18:57:56.945 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2022-08-13 18:57:56.946 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: notifyTransactionResponse TID:300 CANCELLED
2022-08-13 18:57:56.947 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2022-08-13 18:57:56.947 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 300: Transaction event listener: DONE: CANCELLED -> WAIT_DATA
2022-08-13 18:57:56.949 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 4: Node Init response (1) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@62f46b5b
2022-08-13 18:57:56.949 [DEBUG] [mmandclass.ZWaveSecurityCommandClass] - NODE 4: isNonceAvailable = null
2022-08-13 18:57:56.949 [DEBUG] [andclass.impl.CommandClassSecurityV1] - Creating command message SECURITY_NONCE_GET version 1
2022-08-13 18:57:56.949 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 4: No data from device, but it was ACK'd. Possibly not supported? (Try 1)
2022-08-13 18:57:56.950 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 04 02 98 40 25 27 39 
2022-08-13 18:57:56.951 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 4: Sending REQUEST Message = 01 09 00 13 04 02 98 40 25 27 39 
2022-08-13 18:57:56.951 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2022-08-13 18:57:56.952 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 306: [WAIT_RESPONSE] priority=High, requiresResponse=true, callback: 39
2022-08-13 18:57:56.952 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2022-08-13 18:57:56.953 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2022-08-13 18:57:56.954 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2022-08-13 18:57:56.954 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 306: [WAIT_RESPONSE] priority=High, requiresResponse=true, callback: 39
2022-08-13 18:57:56.954 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2022-08-13 18:57:56.955 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-08-13 18:57:56.955 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2022-08-13 18:57:56.959 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
2022-08-13 18:57:56.960 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2022-08-13 18:57:56.961 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2022-08-13 18:57:56.961 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 306: [WAIT_RESPONSE] priority=High, requiresResponse=true, callback: 39
2022-08-13 18:57:56.962 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2022-08-13 18:57:56.962 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 306: [WAIT_RESPONSE] priority=High, requiresResponse=true, callback: 39
2022-08-13 18:57:56.962 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2022-08-13 18:57:56.963 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 4: sentData successfully placed on stack.
2022-08-13 18:57:56.963 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 306: Advanced to WAIT_REQUEST
2022-08-13 18:57:56.963 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: TID 306: Transaction not completed
2022-08-13 18:57:56.964 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-08-13 18:57:56.964 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
==> /var/log/openhab/events.log <==
2022-08-13 18:57:56.308 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' received command OFF
2022-08-13 18:57:56.309 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' predicted to become OFF
2022-08-13 18:57:56.312 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' changed from ON to OFF
==> /var/log/openhab/openhab.log <==
2022-08-13 18:57:57.828 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling...
2022-08-13 18:57:57.829 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling deferred until initialisation complete
2022-08-13 18:57:58.190 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 27 00 00 7C B0 
2022-08-13 18:57:58.191 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Request[0], dest=0, callback=39, payload=27 00 00 7C 
2022-08-13 18:57:58.192 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Request[0], dest=0, callback=39, payload=27 00 00 7C 
2022-08-13 18:57:58.192 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 306: [WAIT_REQUEST] priority=High, requiresResponse=true, callback: 39
2022-08-13 18:57:58.193 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2022-08-13 18:57:58.193 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 306: [WAIT_REQUEST] priority=High, requiresResponse=true, callback: 39
2022-08-13 18:57:58.193 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 306: (Callback 39)
2022-08-13 18:57:58.194 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2022-08-13 18:57:58.194 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 306: callback 39
2022-08-13 18:57:58.195 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Request[0], dest=0, callback=39, payload=27 00 00 7C 
2022-08-13 18:57:58.195 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 4: SendData Request. CallBack ID = 39, Status = Transmission complete and ACK received(0)
2022-08-13 18:57:58.196 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 306: Advanced to WAIT_DATA
2022-08-13 18:57:58.196 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: TID 306: Transaction not completed
2022-08-13 18:57:58.196 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-08-13 18:57:58.197 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2022-08-13 18:57:58.205 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 04 0A 98 80 A5 3C 22 E3 09 CC 83 B3 50 
2022-08-13 18:57:58.206 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 0A 98 80 A5 3C 22 E3 09 CC 83 B3 
2022-08-13 18:57:58.207 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 0A 98 80 A5 3C 22 E3 09 CC 83 B3 
2022-08-13 18:57:58.208 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2022-08-13 18:57:58.208 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Application Command Request (ALIVE:DYNAMIC_VALUES)
2022-08-13 18:57:58.209 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Incoming command class COMMAND_CLASS_SECURITY, endpoint 0
2022-08-13 18:57:58.209 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY check internal
2022-08-13 18:57:58.209 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 4: Received COMMAND_CLASS_SECURITY V1 SECURITY_NONCE_REPORT
2022-08-13 18:57:58.210 [DEBUG] [mmandclass.ZWaveSecurityCommandClass] - NODE 4: NONCE Received start...
2022-08-13 18:57:58.210 [DEBUG] [mmandclass.ZWaveSecurityCommandClass] - NODE 4: NONCE Received start null
2022-08-13 18:57:58.211 [DEBUG] [mmandclass.ZWaveSecurityCommandClass] - NODE 4: NONCE Received ZWaveNonce [nonceBytes=(A5 3C 22 E3 09 CC 83 B3 ), timer=146591, valid=true]
2022-08-13 18:57:58.211 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Commands processed 1.
2022-08-13 18:57:58.211 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@18e5c2e6.
2022-08-13 18:57:58.212 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@18e5c2e6.
2022-08-13 18:57:58.212 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: notifyTransactionResponse TID:306 DONE
2022-08-13 18:57:58.213 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2022-08-13 18:57:58.215 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1
2022-08-13 18:57:58.215 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-08-13 18:57:58.216 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-08-13 18:57:58.216 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2022-08-13 18:57:58.216 [DEBUG] [andclass.impl.CommandClassSecurityV1] - Creating command message SECURITY_MESSAGE_ENCAPSULATION version 1
2022-08-13 18:57:58.218 [DEBUG] [mmandclass.ZWaveSecurityCommandClass] - NODE 4: SECURITY_TXD 62 01 FF 
2022-08-13 18:57:58.220 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 1E 00 13 04 17 98 81 78 09 61 F5 59 51 E8 66 31 C8 8E C7 A5 

Here are the thing properties: I think it says it is secure

    zwave_class_basic  BASIC_TYPE_ROUTING_SLAVE
    zwave_class_generic GENERIC_TYPE_ENTRY_CONTROL
    zwave_frequent   true
    zwave_neighbours   1
    modelId  Kwikset 620
    zwave_listening false
    zwave_plus_devicetype  NODE_TYPE_ZWAVEPLUS_NODE
    zwave_version  7.20
    manufacturerId  0090
    manufacturerRef  0811:23A8
    dbReference  1513
    zwave_deviceid 9128
    zwave_nodeid 4
    defaultAssociations  1
    vendor Black & Decker
    zwave_routing true
    zwave_plus_roletype  ROLE_TYPE_SLAVE_SLEEPING_LISTENING
    zwave_beaming  true
    zwave_secure true
    zwave_class_specific SPECIFIC_TYPE_DOOR_LOCK
    zwave_devicetype 2065
    zwave_manufacturer  144

All help is appreciated…
Eddie

Having two binding processes cannot be good and you need to eliminate that variable. At this point I would delete the 3.4 from the addons, then use openhabian-config to update to the 3.4 milestone 1. That will have a zwave binding with the lock. IMO it is better to update to the milestones (after a few days) than wait for releases, despite the warnings. If something goes astray you can find the problem in the recent posts. If you wait 6 months for the release, the problems that happened in earlier months are harder to find.

You probably need to run the Debug longer, it seems like it was cut off. Also there is a zwave debug viewer here. It makes it easier to understand, at least at a high level. This is what I got from yours (events files are not really needed).

I was able to upgrade to 3.4.0 milestone. It still showed 2 zwave bundles. I kept the one with the date I was looking for and uninstalled the other.
I can see no change to the behavior of the lock except that I don’t seem to be able to set lock codes anymore.
I don’t see anything bad going on in the zwave viewer. I am having trouble making the file small enough to include in a message.
I don’t have any other zwave devices. Would it tell me anything if I got a zwave motion detector to try. I eventually want to add some anyway.
Eddie

I won!!! I re-read all the instructions several times. The lock just says to refer to the home automation systems for instructions. OpenHab instructions are naturally very generic. The KS instructions say that if you are unsuccessful to do a factory reset and reinstall and it may take several attempts. That is what I had been doing all along. Nothing new. On my third attempt this morning it worked. Go figure.
The solution I think was a combination of getting a working zwave binding, upgrading to the same OH version as the binding and repeatedly installing it until it worked.
Thanks for all the help. I learned a lot. On to the zigbee controller.
Eddie

1 Like