Two identical Kwikset 912 ZWave locks. One Highest Security: S0 Legacy Other NONE

I have been struggling for some time to resolve this issue. I have two identical locks with ZWave modules. One of them is added to Zwave network with Highest Security: S0 Legacy making it fully operational.
The other is added without security (Highest Security: None) making it useless.
I have tried many approaches: Include/exclude, create new HASS site and starting from scratch, etc.
I suspect the setting is recorded in my AEOTEC Z-STICK Z-WAVE USB STICK GEN5 and no matter what I do in HASS, I cannot change it.
Any way to force the device to be viewed as Highest Security: S0 in HASS?

Thank you.

You will need to exclude it first. Then include it securely.

To force s0 inclusion, under the add device screen in the zwavejs integration configure screen, you can click “advanced inclusion”, then select “legacy secure”


The lock will also need to be next to the controller. They generally use “whisper” pairing to initially share the security keys. You shoud then be able to move it to its final location and it should work if you have a good mesh/signal.

Also see this guide for tips. As you have discovered, s0 security is required to control this lock.

Thanks for the tips. Unfortunately, I have attempted to include the lock several times using legacy secure, but it always ends up as insecure. It is probably the closest zwave device to the Aeon stick, so I don’t believe that could be the issue. A Zwave JS update just hit my host a few days ago. I am going to exclude/include again to see if the update solves the problem.

How close? I’ve read people have literally needed to duct tape the lock to the hub/zstick for pairing.

Across the room might seem close, but likely not close enough to exchange the required security keys for s0 inclusion.

Also, be sure to perform the exclusion (remove device) first, even if it didn’t show connected. This will clear the network settings from the lock.

I doubt this will make a difference. My locks have paired fine since I switched to zwavejs2mqtt in May, and that was many versions ago.