To start off I should say this lock has never worked correctly. It was a refurb which I returned and the replacement behaved exactly the same. It was only $100 and I was able to get keycodes to work so I kept it.
Was kind of hoping the move to zwave JS might make it spring to life but instead those two entries that were showing in HA are now not available…
The device page shows, well it actually hides the only entity.
sensor.touchpad_electronic_deadbolt_node_status - entity is unavailable
Device info
SmartCode 888
by Kwikset
Firmware: 4.76
If anyone has a pro tip or two for me I’m willing to test or try anything. I even got myself a second zwave stick so I could do testing and firmware updates.
I would guess the lock is not included properly or missing necessary security keys to control it. When you moved it to zwavejs, did you exclude and reinclude? If not, did you pull the security key from open zwave to put into zwavejs?
I have two kwikset locks and they are fussy to setup, but work well once properly paired.
Another option is the lock is just not in the zwavejs database, and you would need a custom configuration,
which is a bit advanced to setup.
I’d start with an exclude then re-include first. The lock likely uses older s0 security. To exchange the security keys, these locks use “whisper pairing” and must be directly next to the zstick for initial pairing. Take the lock off the door to the stick or bring the stick/device to it. Once paired, it will work fine in its final location- you’ll want to heal the Node after though to update the routing table when it’s in its final installed spot.
The link from AllHailJ is to the DB no? If so, all good there.
I have redone the whole zwave setup here a few times and tried the lock right next to the zstick when pairing trick. The best I ever got was doing some tricks with the old zwave integration which gave me some entities - battery and lock. Battery always reported 100% and the lock didn’t respond.
At the time that was my only lock so I put it on the back door and used it for code entry only. Since I got my front door lock, not the same kind but zwave and it works a treat I was hoping to figure out the back door too.
Will check that guide and retry pairing this weekend but I did try few times before demoting it to the back door lock and had followed similar guides advice.
Anyone have a kwikset 888 that can chime in with their firmware version and maybe the entities you got in home assistant?
I have a Kwikset 888 running ZwaveJS. Mine added perfectly the very first time, from a distance of about 80 ft away from my Nortek GoControl zwave/zigbee dongle. Same firmware version as you, too.
I would try excluding the lock and re-adding it like the others mentioned. It sounds like you set it up correctly using secure inclusion otherwise you wouldn’t be able to lock/unlock it at all. My next best guess is that maybe there was a hiccup in the inclusion process or it got hung up and never actually added all of the entities like it should have. It sounds like you know what you are doing, but you are welcome to read this over as you set yours up again: https://smarthomepursuits.com/add-kwikset-888-to-home-assistant/
I did try this afternoon when I had the chance and it was looking good. Got a couple entities - one being the lock - following the advice from the smarthomepursuits link from djbrooks I left it for a good 20 minutes then rebooted.
Unfortunately that didn’t add a bunch of new entities like I was hoping it would. I no longer see firmware version either.
If anyone else arrives hear I had the same problem. I have the Kiwkset 910 lock, Aeon Labs Gen5 Z-wave stick, and Zwave-JS. I tried multiple times unplugging the stick and pairing at close range and every time no matter what combination it would pair instantly but with zero functionality. I ended up leaving the stick plugged in and adding a node from the home assistant zwavejs screen, and it paired quickly and did all the negotiations, and now it works like a champ.
