I'm about positive the lock is reset to factory defaults. I went through the steps, and the lock opened and closed on it's own as described in the reset instructions. Also, a code I had programmed no longer works.
To I've tried including the lock by clicking the Add Device button, then "Z-Wave", then Start Z-Wave Inclusion. I also tried searching by brand and using a similar Kwickset lock. Then after starting the inclusion process I press the "A" button on the lock one time. All it does is beep once followed by a 10 second or so pause, then 3 beeps.
I have the hub right next to the lock as you can see in the photo. Not sure what I'm doing wrong. Any suggestions would be appreciated.
Make sure you can successfully exclude the lock using Hubitat before attempting to include it. It is possible that a factory reset doesn't cause this particular lock to leave it's current controller, in which case, inclusion would not work.
I've tried several times to exclude and include the lock to no avail. I have instructions from the manual on how to accomplish this, and also from AI (Microsoft Co-Pilot) shown below. It just doesn't work for some reason.
To add a Kwikset 888 lock to a Hubitat hub, follow these steps:
Factory Reset the Lock (if needed):
Remove the battery pack.
Press and hold the Program button while reinserting the battery pack.
Keep holding for 30 seconds until the lock beeps and the status LED flashes red.
Press the Program button once more. When the LED flashes green and you hear a beep, the lock has been reset.
Perform the Door Handing Process:
Press and hold the Lock button while installing the battery pack.
Hold the button until the latch bolt starts moving on its own.
If the latch bolt does not retract and extend on its own, remove the battery pack and wait 15 seconds, then try again.
Join the Z-Wave Network:
Hold the interior assembly within 12 inches of your Hubitat hub.
On the Hubitat Web Interface, go to Z-Wave and select Start Z-Wave Inclusion.
Press Button A on the lock once to include it.
Keep the controller and lock stationary for 60 seconds during the inclusion process.
If inclusion fails, go to Z-Wave Exclusion and press Button A once to exclude the lock, then repeat the inclusion process.
Ensure Secure Pairing:
If the lock does not pair securely, exclude it and try again.
Bring the hub within inches of the lock during pairing.
Having a Z-Wave repeater nearby (like a Leviton switch or Aeotec repeater) can improve connectivity.
I just powered the hub back on so I can get this information tomorrow. In the meantime, can you tell me if Hubistat is a "security enabled" Z-Wave controller?
FWIW, I have five Kwikset z-wave locks that I'm using with Hubitat. These are newer locks, so they are paired with S2 security; however, Hubitat also supports pairing using the older S0 security.
I do have two T6 thermostats paired, along with a smart light switch. I was looking at the Kwikset 888 trooubleshooting docs (attached). I am reasonably certain that the lock has been excluded from the former Safe Haven network. The reset went as described. I checked the Safe Haven log and there has been no activity for the lock in two days.
Make sure that some anti-theft feature has not been turned on. That will prevent the lock from pairing with another controller. See this post for details:
So I did an AI query. The only new thing it referenced was a "flag* that systems such as vivent and safe haven could set as part of an anti theft feature. If so set, the lock would need to be excluded from the original system. A factory reset is not enough. With all your driver writing experience, have you heard of such a flag?
Did you click refresh stats, wait then refresh the page first? The RTT are all blank.
Probably wont matter though, you only have 3 devices and no dead/ghost nodes so there should not be anything blocking you from pairing a new device.
I would focus on getting the lock to EXCLUDE from HE first. You should be able to run the exclude process and get "unknown device excluded" on the hub side when it works. If that wont work then there is close to 0 chance of getting an include to work.
