Older Kwikset S0-only locks fail inclusion on C8 Pro

Hey all,

I recently (tried to) move all my Kwikset smart locks from my C8 to my C8 Pro. All the newer (S2-capable) locks worked seamlessly. However, the two older Kwikset locks (which were working before) just won't complete the inclusion process. These older locks only support S0. Is this an/the issue?

I found a few older posts (here) that seem to indicate there's some fragility between the C8 Pro and S0 devices--anyone got anything helpful to either point me in a different direction or give up?

Thx!

Links to any specific discussions would be helpful, but no, there shouldn't be any general problems with all S0 on the hub. On any model of hub, it is preferable to avoid S0 where possible since it is chattier than either S2 or no security, but in cases like your locks, it's the only option since it's all they support and you need security.

FWIW, I have two S0 locks I've included to a C-8 Pro without problem. This was on legacy Z-Wave, but they were moved to (re-interviewed automatically but not re-included) Z-Wave JS without problem, too. Which Z-Wave stack are you using? That could affect things, too.

1 Like

Still using the Z/IP stack. I switched to JS a week or two back but things went pear shaped so I reverted... for now.

Agreed on S2 but, as I said, I've had these locks foreverrrrrr and don't enjoy fixing what ain't broken (that's arguable from a security standpoint but you no doubt follow my point). The other 3 locks are working fine.

have you tried to factory reset those kwikset locks before inclusion?

Both of my z-wave locks only support S0. They work on the C8-Pro.

Thx. I did, multiple times (batteries out, hold programming button, batteries back in and hold for 30 secs or so, wait for beep, and release and push programming button again to confirm). I even joined the C8 Pro to my WiFi, shut it down for 2 mins or so, hooked it up to a portable UPS, and took it next to the lock (any closer and I'd have grandchildren). Started with an exclusion (the hub failed to recognize the event) so proceeded with an inclusion which also obviously failed... repeatedly. Once the inclusion fails, the hub's Z-Wave is dead--as in can't control anything--and requires a typical cold-boot to restore normalcy. :man_shrugging:

You migrated to the new platform? Did the problem locks migrate too? If those devices are still in the data base, they should be deleted after they are swapped for a virtual device so your rules Don't break. Perhaps reboot with a DB rebuild too. Then see if they will include.

Thx for the input!

After the JS switch, I switched back and restored an earlier cloud backup for good measure. All devices reverted to original/working behavior.

I'd already created and 5 virt equivs and migrated the rules swapping the devices in flight so that part was handled.

I don't recall when I performed the DB rebuild but it was recently. No harm in trying again. I'll give that a shot. :+1:

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.