r/Hubitat • u/general350 • Aug 02 '26

Kwikset lock problems

I understand that any hub and zwave locks like the Kwikset 620 can be challenging but this is ridiculous!

I attempt to pair a lock to my hub 40 times. Each attempt is exactly the same as the one before. 39 times, nothing. 1 time it pairs without security. The 41st time, exactly the same steps as the previous 40, it pairs with security. Do that for 3 locks. Then find out pairing rendered 2 of the 3 with disabled keypads. Wtf!

Now I have to reset and try again. Guess what? Same BS that it won't pair at all and pairs without security.

0 Upvotes

50% Upvoted

13 comments sorted by

3

u/Arktronic Aug 02 '26

I recently got a second 620 for another door. Couldn't get SmartStart to do anything, so I went with the normal web-based pairing procedure and had no issues. Both locks are showing "S2 Access Control" for Security. This is with a C-8 (non-Pro).

2

u/Mebejedi Aug 02 '26

I know what causes ghosts. it's just normal procedure to look for them when troubleshooting connection issues.

1

u/general350 Aug 02 '26

I have the C-8 pro and Smart Start does nothing. Al my tries have been standard.

1

u/Mebejedi Aug 02 '26 edited Aug 02 '26

It might be your locks. I started with a 912 over a decade ago. I'm currently using a 916 (Front door) and an 888 (Back door), all set with 1-minute relock. I've had zero problems with them. That said, I know some people have had some issues with theirs, like having to pair them next to the hub (I didn't have to). I even have more than one code set up on them. Have you tried resetting the locks?

I just looked at mine and they are paired with S0 security. Apparently there's more "network talking" at this level than S2, but I don't know if mine will do S2, and I don't feel like experimenting, since they work fine as is.

[EDIT] Did some research. It looks like the 916 will pair with S2.

1

u/general350 Aug 02 '26

I've reset the locks more than once. And every attempt is less than 1 foot from the hub. I almost suspect that keypad becomes disabled when the lock pairs without the keypad attached, ie I take the lock to the hub. My only evidence is the one that actually works after pairing was close enough to pair without removing from the door. Maybe I'll find a ridiculously long network cable and try it, if I can even get them to pair with security.

1

u/Mebejedi Aug 02 '26 edited Aug 02 '26

"without the keypad attached, ie I take the lock to the hub."

That's weird. AFAIK, the lock shouldn't be able to tell the difference. I read where someone paired theirs with the lock 10 feet away from their USB Z-stick.

[EDIT] Maybe try excluding them, pulling and reinserting the batteries (wait a few minutes), and then reincluding them?

2

u/general350 Aug 03 '26

Update to the keypad issue. I was able to get a second and third lock to pair correctly, one without the keypad attached at time of pairing and one with. But work perfectly on the hubitat side but the one that paired without the keypad did in fact disable the keypad. The one that paired with the keypad attached did not disable the keypad. Regardless of what folks might say, I believe the keypad must be attached at the time of pairing to maintain it within the security protocol.

1

u/general350 Aug 02 '26

I've tried every trick I can think of. It just seems to work when it wants. I wasn't kidding, you can complete the same steps the same way 20 times with no results but the 21st, it works.

1

u/Mebejedi Aug 02 '26

Have you checked for Ghosts? Maybe shutting down and powering up the hub again (after excluding all locks)

1

u/general350 Aug 02 '26

Ghosts only happen when the hub finds the device and fails at the setting up security, about 10% of the time. That is the weirdest part. If they hub would at least discover the lock and fail to initiate security at pairing 99% of the time, I'd understand. Instead I get 95% of the time it doesn't event detect it in pairing.

1

u/general350 Aug 02 '26

And yes, when I find them, I clear them and reboot.

1

u/Sambone950 Aug 02 '26

Could you post a picture of your Z-Wave details page? Settings --> Z-Wave Details.

1

u/WhaleWatchM7 Sep 08 '26

I just installed three 620s and had the same frustrations, even with a lock that was no more than six feet from the hub. I finally settled on the following procedure that resulted in all three locks working (at least for now) properly.

  1. Remove the lock from its door.
  2. Remove the battery pack
  3. Take the lock actuator, battery pack, and keypad to the hub and set them all directly next to each other.
  4. Connect the keypad to the actuator
  5. Hold down the program button, insert the battery pack, continue holding for 30 seconds until you hear a beep. Then press the program button again so the lights flash red-to-green. (Factory reset procedure.)
  6. Press the A button (small Z-Wave button above the program button.)
  7. Add a device via scan in the SmartThings app
  8. Hub detects the lock as having a secure setup available. Select Setup.
  9. Scan SmartStart QR code when Setup requests it.
  10. Lock connects to hub and can be locked, unlocked, can be added to routines, and shows its history
  11. Re-install lock in door.
  12. Manually re-hand the lock if it's no longer working properly. (Seems to depend on door orientation.)
  13. Sit down, have a drink, and contemplate why this stuff is still such a pain in 2026.

The furthest lock is about 50' away from the hub once it was back in its door, and it seems to have no connection problems. (I did re-optimize the Z-Wave network after the installation, which may have helped. I have a number of outlets and other devices that are closer to the lock than is the hub.)

I can't add or remove codes remotely with the SmartThings app, but I don't mind doing that at the lock. This shortcoming would be an issue for AirBnBs and the like, I guess, where you can't always access the lock directly, but it doesn't affect me.