I am trying to add my Kwikset 620 deadbolt to my HA. I currently have about 5 zwave lights connected to my home assistant and the lock is about 30 feed from the nearest switch.
I am trying to add the lock, but z-wave JS cannot find it via add device. I’ve been pressing the z-wave connect button the lock per the directions.
Are there any suggestions/thoughts where to start?
Thanks
-Dan
Kwikset locks all use the whisper protocol when they are being added to the z-wave network. You need to have the lock a lot closer to a router node than 30 feet to get it added into the network. Once it’s added to the network it will operate and can respond at decent distance from the next nearest router node.
I have Kwiksets at several different locations that I’ve got HA at and anytime I’m building out a new site I get the deadbolt all put into the door and properly “handed” and then I’ll get it as close as I can to one of my routers (or generally the system running HA) and add it. That may mean needing to take it back off the door :-/ and wire it all up near my control system.
That worked, I was able to connect to the device. However, when I try to unlock/lock the device nothing happens. Any suggestions?
Device ID: 13
Device Status: Alive
Device Ready: Yes
Highest Security: None
Z-Wave Plus: Version 2
You need to make sure that the device has been fully interviewed before anything properly.
I do know that with one lock that I’ve got at the edge of the network I have a lot of issues trying to program or trigger state changes on it. I’m working on getting another zwave router in between that and the controller to fix the problem.
What you might try to do is bring the device close by again (if you’ve already put it back where it needs to be). While it’s close to whatever router you used to get it included, validate that it can unlock / lock while it’s nearby. If you’re planning on using Keymaster now would also be the best time to make sure it gets configured so you can get some codes into the lock.
Thanks again for the help. I made sure that the lock was fully interviewed and it is sitting on the floor right under my other Zwave switch. I’ve added the lock to the Home Screen, but when I click lock/unlock nothing happens.
I’ve added kwiksets before, and it always just seemed to work.
You can’t control a lock if it’s included w/o security, which is what this says. When you include you should get a warning if secure inclusion fails. Did you see such a warning? When that happens, you have no choice but to exclude and re-include.
I reconfigured the lock, it now has security. It still does not lock/unlock.
Device ID: 13
Device Status: Alive
Device Ready: Yes
Highest Security: S0 Legacy
Z-Wave Plus: Version 2
Somethings still not quite right if you have a Z-Wave Plus V2 lock and it is not including with S2 security. Regardless, it will still function with S0 Legacy, communication will just be less efficient. This could be a problem if you later have range issues.
You’ll probably need to post some driver Debug logs when attempting to operate the lock.
My other Zwave (zooz light switches) work fine, but I am getting this error
Configuration invalid
CHECK CONFIGURATION
Integration error: zwave - Integration ‘zwave’ not found.
Here is the line from my configuration.yaml file
zwave:
usb_path: /dev/ttyUSB0
Here is information my logs
2022-04-27T01:29:29.034Z CNTRLR [Node 013] Timed out while waiting for a response from the node (ZW0201)
2022-04-27T01:29:46.494Z CNTRLR [Node 013] Timed out while waiting for a response from the node (ZW0201)
Verbose
Subscribed to Z-Wave JS Log Messages…
Log Level changed to: Verbose
2022-04-27T01:31:36.444Z DRIVER » [Node 013] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 54
└─[LockCCSet]
locked: false
2022-04-27T01:31:36.451Z DRIVER « [RES] [SendData]
was sent: true
2022-04-27T01:31:37.709Z DRIVER « [REQ] [SendData]
callback id: 54
transmit status: OK
2022-04-27T01:31:37.740Z DRIVER » [Node 013] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 55
└─[LockCCSet]
locked: false
2022-04-27T01:31:37.749Z DRIVER « [RES] [SendData]
was sent: true
2022-04-27T01:31:37.761Z DRIVER « [REQ] [SendData]
callback id: 55
transmit status: OK
2022-04-27T01:31:42.805Z DRIVER » [Node 013] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 56
└─[LockCCGet]
2022-04-27T01:31:42.813Z DRIVER « [RES] [SendData]
was sent: true
2022-04-27T01:31:44.024Z DRIVER « [REQ] [SendData]
callback id: 56
transmit status: OK
2022-04-27T01:31:46.273Z CNTRLR [Node 013] Timed out while waiting for a response from the node (ZW0201)
Here is the information from the logs. It looks like everything should be working, but the lock doesn’t actually lock/unlock.
I believe the issue has something to do with: Timed out while waiting for a response from the node (ZW0201)
Subscribed to Z-Wave JS Log Messages…
2022-04-30T13:58:26.447Z DRIVER » [Node 013] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 127
└─[LockCCSet]
locked: false
2022-04-30T13:58:26.456Z DRIVER « [RES] [SendData]
was sent: true
2022-04-30T13:58:27.796Z DRIVER « [REQ] [SendData]
callback id: 127
transmit status: OK
2022-04-30T13:58:28.206Z DRIVER » [Node 013] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 128
└─[LockCCSet]
locked: false
2022-04-30T13:58:28.216Z DRIVER « [RES] [SendData]
was sent: true
2022-04-30T13:58:28.260Z DRIVER « [REQ] [SendData]
callback id: 128
transmit status: OK
2022-04-30T13:58:33.290Z DRIVER » [Node 013] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 129
└─[LockCCGet]
2022-04-30T13:58:33.297Z DRIVER « [RES] [SendData]
was sent: true
2022-04-30T13:58:34.912Z DRIVER « [REQ] [SendData]
callback id: 129
transmit status: OK
2022-04-30T13:58:37.565Z CNTRLR [Node 013] Timed out while waiting for a response from the node (ZW0201)
Where you able to resolve this? Im getting the same issue. Connected it with the security and now i cant unlock/lock with the HA.
Where’s your logs?
Thanks for following up. I was able to resolve this by removing it from the network and door and bring it right next to the hub to sync it. After syncing it, i then put it back in the door and it worked great.
For anyone who finds this later, if you add a Kwikset 620 by pressing the button you will get lower security than if you use the QR code. I ended up scanning the QR with my phone camera which allowed me to copy the really long number from it. I then pasted that in via the add via QR code method. That resulted in “Highest security: S2 Access Control Z-Wave Plus: Version 2”
I have to disagree that you will get lower security if you do that. I added mine by way of the button, no issues and it’s on the higher security setup as well.
If the controller and the lock both support it, they should train on the higher security configuration.
Weird. I used the button and got low security. I removed it, readded the other way, got high security. Nothing else changed.
I got one of these recently and it’s been incredibly picky. I upgraded my Zwave stick to an 800 series long range from Zooz. It was added with no problem after that upgrade and it worked great for about a week.
I then had to swap out the NVMe from the Proxmox box running HA with an SSD so I could free up room in a new Proxmox box to install a 4 NIC card. All my VMs came back up and all my devices work great, except the 620. It re-interviews fine, and healing it is successful, but it’s showing up as unavailable.
I’m going to factory reset it and add it again, but it really is the most finicky Z-Wave device on my network.
edit: I actually only had to remove it and add it again using Smart Start (QR Code) and it’s working correctly again
I’m using the button method, and cant get the damn thing to add with security.
I Have an aeotech gen 5 USB stick, so I don’t have the ability to add via QR code.
"The device was added insecurely
There was an error during secure inclusion. You can try again by excluding the device and adding it again."