I've read a whole bunch of similar posts, but none are helping me solve my problem.
I'm running a Hubitat C8 Pro, version 2.4.3.123. I had some VERY similar problems trying to install a Schlage BE469ZP -- I decided to ditch it and now I'm trying to install a Kwikset 620.
I've tried installing it from the "Devices" page with a process like this:
Hub physically next to the lock
Put hub in z-wave inclusion mode
Click the "A" button on the Kwikset lock. Steady red LED light comes on
Answer "with security" at the next prompt
Input 5 digit PIN
Hubitat web interface starts a new 99 second countdown. A few seconds later it finds the lock and says to wait for bootstrapping. Red LED on the lock goes OFF at this point
The countdown timer goes to zero
A z-wave entry has been created in "Z-Wave Details" with S2_AccessControl security, but there is no device created
I've also done SmartStart by scanning the QR code. This uses Z-Wave LR (which isn't really what I want, but if it works I'm fine with it). After it runs, I also get a new entry in "Z-Wave Details" but no devices.
Before starting the install, I'm generally removing the ghost node, powering down the Hubitat hub, unplugging it. I then perform a factory reset on the lock, power up the hub, and start the "Add Device" process. I've done this probably a dozen times or more.
I don't think I've got any ghost nodes. I'll follow up with some screenshots of my "Z-Wave Details" page.
In the first post you seem to have done everything I would suggest as I had many problems joining these locks in the early days.
I do see you have many ghosts in your ZW mesh.
Anything without route, blank info, or Pending needs to be addressed first.
You may have to repair or remove try to add those back.
Those are... not ghosts? Well, maybe they are -- not sure how you define that. I can't communicate with them because I had to move my hub into the garage near my lock. So they are only temporarily unreachable. There are also a few battery powered devices that don't respond to pings, but the devices work otherwise (when my hub is in its normal location).
I suppose there are a couple of other devices that I use seasonally (switches for Xmas lights). Should I be removing those and re-adding them when I need them again?
Seasonal devices like Xmas, which I used to leave paired but unplugged in the deco box, were a bad idea as they ruin the mesh.
I now leave them plugged in all year long so the mesh is happy.
You need to satisfy the Pending and remove or remedy the blank routes as the mesh will be unhappy with a dead end road.
Okay, thanks for the tip. I'll try putting my hub back in place, and resolve all the blank routes. I'll probably pull the lock off the door and move it near the hub instead of moving the hub.
Okay, I addressed anything that looks like a dead node. I think everything's pretty clean. But... still no device is getting created... I poured through the logs and as near as I can tell the keys are getting exchanged, then Hubitat does this interview with the Kwikset lock... then it just kind of gives up.
I tried this 4 times with SmartStart. Once with a factory reset while it was still on the door. Then I factory reset it, removed it from the door and placed it right next to the hub. The last two times I just did a zwave exclude, because in order to properly reset it you've got to have it on the door.
At some point during this ordeal I did create a virtual lock device. I changed the Device Network ID to match the node ID in Z-Wave Details. That actually allows me to automate the locking/unlocking. But I could not use the lock code manager at all. And I was nervous that I wasn't really communicating securely hacking it this way. Or maybe that's fine?
I actually have three different z-wave smart locks right now, a Schlage BE469, a Schlage BE469ZP, and a Kwikset 620. All of them create an entry in "Z-Wave Details", but none of them create a Hubitat device. It doesn't matter how I include them -- with the manual z-wave inclusion process or with SmartStart. The Kwikset exhibits the same behavior with both LR and standard mesh. (The Schlage devices don't support LR.)
I'm kind of wondering how hard it is to do a local backup, factory reset the Hubitat C8 Pro, and the restore my automations. Is that something that can even be done? Like, I'm willing to re-pair all of my z-wave devices, but I don't want to re-write all of my automations. I'm curious to know if this problem would still happen on a factory reset Hubitat...
Are you using ZWaveJS or Z/IP gateway (Legacy). Of you’re on ZWaveJS, switch to Legacy. Then shutdown the hub, do a power cycle, and try pairing your locks.
I've been going back and forth between JS and Legacy throughout. But I couldn't confirm that I did a power cycle after switching. So I just did that now to confirm. Not much improvement.
I made two attempts -- first with SmartStart to get the lock paired in LR mode, then manually by going through Z-Wave inclusion, pushing buttons on the lock, and entering the security PIN.
The only difference is that in Legacy mode the z-wave entry shows that security is "None", while in JS mode it shows "S2_AccessControl". In neither case does a Hubitat device get created.
At this point I'm skeptical that all three locks are defective. My first attempts to pair locks on this hub go back about a year. I've since purchased two more zwave locks (all slightly different models). I don't really understand the Hubitat internals but I'm worried that there may be something "invisible" in the user interface that is corrupting my z-wave chip, or my Hubitat database. (I've also done a "rebuild database on reboot".)
That's why I was asking about doing a full factory reset. I'm curious if I would still have a problem if I tried pairing the locks on a fresh C-8 Pro. At this point it might be worth it to just buy another hub to see.
I have 5 of the Kwikset 620 deadbolts paired to my C-8 Pro. All paired using SmartStart. All paired in mesh mode, and all paired using z/ip gateway. And they’ve all been fine with ZWaveJS since January.
This may not help, but I just replaced a Kwikset 620 that was failing, and I had a lot of trouble getting the new 620 to pair. I could not get it to pair with SmartStart and I could not get it to pair using the Device>Add webpage when I specified I was adding a Lock>Kwikset>620. However, to my utter relief and amazement, it paired when I didn't filter for a that specific device. I note it and my other two 620's are paired as "generic locks". I don't know if this is related to the discussion but I thought I would mention it.
@aaiyar Thanks, it was reports like yours that convinced me to go with the Kwikset 620 in the first place!
@john.ke5c I've been kind of wondering if the process of choosing the device type, brand and model of lock does anything at all, since this lock just uses the Generic Z-Wave Lock driver. I've definitely tried it both ways, but most recently I've been clicking through and selecting the device type, brand and model each time. If I make any more attempts I'll just skip this!
After I posted, I found my original notes from March 28 (link below). At that time I was able to pair using Lock>kwikset 620 but I sure could not yesterday. Something has changed either with Hubitat or Kwikset software/firmware. I suspect Hubitat since the Kwikset is probably close to locked in stone. I agree, odd that you can select the lock but it just uses generic lock profile. March post
It does not. Choosing a specific device in the list just gives you the instructions how to to perform the pairing.
Many of us old timers just skip right to the Z-wave or Zigbee button instead of using the prompts, that is all we used to have before UI improvements.
The only thing I could see how it could make a difference is if a device has both a Zigbee and a Z-wave version, and you somehow chose the wrong version and didn't notice that the buttons you press for pairing had the wrong protocol listed.
So I just deployed the "nuclear option" on my C8 Pro hub -- I reset the Z-Wave radio. This successfully wiped all of my Z-Wave devices.
However, it did not solve my problem, unfortunately. With no Z-Wave devices whatsoever, none of my locks will completely pair. (They stop before adding the device.)
