I have these kwikset locks and a brand new c-8 pro. The link says 914 and the paperwork inside says 620. 46 zooz switches and the first lock paired with no issues. Second one started to pair and then froze up. Now I think I have what's referred to as a ghost. I have reset the lock at least 10x. I've rebooted the hub, left it unplugged, batteries out of the lock, excluded over and over, spammed refresh, etc. The hub is hardwired and within a foot of the lock. I''m not 100% sure if it's the orignal power block because I don't remember what it looks like, BUT i set this up when my house was completely empty and it's the only option I had at the time and don't know why I would have changed it. I'll attach a picture.
Edit: finally got it to start inclusion again last night after resetting and restoring. It timed out again and I now have 2 ghosts and the entire zwave network is unresponsive for controls. I am getting updates when manually turning switches on and off. "Z-wave network responded with Busy message" is any time I try to control something via the hub.
Seems like you may need to do this before you go any further. If its going into that busy state right after booting up, something is spamming the mesh. Do you still have the batteries in the lock(s)?
First factory reset the lock, you can also exclude but after that I would factory reset it.
Pull lock batteries.
Add device to SmartStart using the mobile app. Do not change the security settings.
Shut down hub and unplug for 30 seconds, boot back up.
Open logs in a new tab.
Power up the lock.
You should see a log message about SmartStart join started, and then 30-60 seconds later it should start the pairing process (lots of logs).
If it does not start pairing on its own, manually put the device into inclusion mode. You should not need to start inclusion on the hub when using SmartStart.
I put the security code in both times it tried to include.
I have factory reset the lock at least 10x. I've left the batteries out for hours at a time while shutting down the hub and unplugging. I can't tell you how many times I've hit refresh hoping to see that remove option.
I've read that and I ordered a zwave stick last night but it won't be here for another day or two.
I tried using SmartStart and let it sit for 24 hours and it never left this state.
I was just trying to make the point of how many times I've tried all these steps. We just moved in so I was messing with it between unpacking, work, life, etc.
Good call. Controls through hubitat work like that. Last niight I had the batteries out and clicked refresh probably 20x while doing other things. Refreshed it several times this morning before work. 2-3x once I got home. Never got the optiion to remove.
I guess I just have to wait on the zwave stick at this point ?
Well, I thought I had a temporarily functional system. I only tried the room I was in and it worked. Tried my living room and it's the same as before.
The top on/off attempts are via the hub trying to turn the bathroom lights off that were just manually turned on. The Ones at 7:59 were a diff room that are currently off, but were showing on in the app.
And now the room I'm in that worked a few minutes after the shutdown no longer works. I'm assuming this is because I clicked refresh ONCE on the lock
Probably, stop touching it.
No amount of clicking that refresh is going to make it work or able to remove.
If you want some light reading look up how FLiRS Z-wave devices work and then you will understand why messing with the lock node so much is causing such a problem.
zooz zwave stick came in today. after a lot of attempts I finallyu got both ghosts (same lock) removed. Added the lock on first attempt with no issues. Will this zwave stick cause issues on the hub as a ghost? It never paired as device. Just shows up in details.
No not really but you can also exclude it, Put hub into exclusion mode, In PC Controller click Select Learn Mode then NWE. It should exclude pretty quick.
