I was having the same issue. I had my 914 on my Ring Alarm and properly removed it from that network. I then tried to add it to my HomeAssistant network and it kept partially working but was missing all of the configuration items and did not have lock/unlock available. My final solution, which worked, was to do the following:
Remove the battery and disconnect the inside part of the unit from the keypad (the little cable connector). I left the keypad unit on the door.
Factory reset the unit by holding down the program button (the one in the middle, not A or B buttons) while the battery is still removed, putting the battery back in while still holding down the program button and continuing to hold down the program button for 30 seconds. The unit will beep and the green light in the middle will come on; then you know you can release the program button. This wipes everything including codes and zwave info. (After this, I went ahead and removed the battery, hit the program button once (it will make a squelchy noise), and put the battery back in to be thorough).
Place the unit right next to the zwave controller, initiate an “add device” in the zwave controller web interface, and then press the “A” button on the unit 4 times.
The unit should be added very quickly. You can then remove the battery and reinstall to the door; including reconnecting that little cable connector to the keypad on the outside of the door.
When I had my lock on the door, which is only about 10ft from the controller hardware, adding the lock to zwave would start and show that it had received the protocol info but it would sit there for a very long time and never complete. The device would show up in the devices list as a node named after the node number.
However, when I held it very close to the controller, adding the device took about 5 seconds and was done with all of the right stuff.
My impression is, if the lock still has codes, it may refuse to be included (I know mine still had it’s codes because I tried one of them even after the lock was properly removed from the zwave network and it still unlocked). By the way, I did try bringing the lock very close the the controller without factory resetting it and got the same failed result.
I hope this helps someone else that comes across this thread.
I had a Kwikset that was paired with the Vivint panel in the house I had purchased. The Vivint panel had enabled the Anti Theft feature of the lock and it would not pair with my Home Automation software of the time. If Anti Theft is enabled, the only way to disable it is to disable the feature and exclude the device with the original panel, a factory reset won’t help.
Fortunately I had kept the Vivent panel and was able to get the Master Code from an Internet search because the previous homeowner left no information about it.
I currently have this same vivint installed with no word on it. its been unplugged and the anti theft isnt triggered still. Do you still have the master unlock code that would be helpful and maybe free the vivint door sensors back also
Hi all - I hope this helps some of you out there with the Kwikset / Weiser SmartCode 10 Door Lock and Z-Wave inclusion with Home Assistant. My touchscreen deadbolt was working fine for years with HA, but when it was removed/re-added I found it did not expose the same functionality. It seems Z-Wave JS favours unencrypted pairing for some reason (Even though you specify it!) AND does not seem to properly interview the device. Successful unencrypted inclusion DOES NOT expose any of the unlock/lock entities you want when pairing with HA). You need to ensure that the device is pairing with S0 Legacy encryption or higher! (as shown in the successfully paired device info below):
Steps I used to successfully pair using Z-Wave JS UI (forcing S0_Legacy encryption inclusion):
Unpair the lock from the existing controller and perform a factory reset. (If necessary). Note: Try and use USB extension cables to get the device as close as possible to the door lock if having pairing issues. One simple press of the ‘A’ button should be fine for pairing with the Z-Wave model of this lock.
Start/Open Z-Wave JS UI Addon in Home Assistant (not Z-wave JS - stop Z-Wave JS if necessary!) and put it into inclusion mode to pair the device.
Ensure to Pair using S0_Legacy - unencrypted will not expose UNLOCK/LOCK features after interview!
Quickly press the ‘A’ button (left) on the front door lock once.
Wait for the device to pair. Afterwards, refresh all CC values, node values, and re-interview the node if necessary.
Stop Z-Wave JS UI after about 5 minutes (waiting until values/interviews are completed), and then start Z-Wave JS back again. Verify that the highest security protocol is S0_Legacy or higher & allow for for ~3-5 minutes for values to refresh!
Amazing - I certainly hope so! Perhaps a recent regression. I’ve confirmed it has still not been corrected in the most recent Z-wave HA addons though: this issue still exists and was confirmed yesterday using the latest ADDON versions of Z-Wave JS (addon 0.27.0) and Z-Wave JS UI Addon (5.3.1)… I believe they may be slightly behind though from what it looks like so hopefully an update will come soon.
But I’m not sure I read your original message correctly. No-security inclusion will never work for a lock. Were you purposefully including w/o security? Or are you referring to the “default” strategy which choose security automatically (and which is what was not working for some devices).
I actually tried both. I was selecting both the “default” strategy (Which chooses security automatically), and then tried manually selecting S0_Legacy (which is acknowledged it was being used in the UI, but still did not pair using S0).
FYI - I just upgraded my controller to the new ZWA-2 and this issue still exists within Z-Wave JS 15.15… it seems like 15.15.1 still hasn’t been released on the HA side yet?
