New user and first post, which may help others some day.
TLDR: Apparently Z-Wave devices must be securely enrolled to expose lock control entities. Thus, when pairing a non-Z-Wave-Plus device, select legacy security when enrolling.
I have finally transitioned all my Vera-controlled locks to HA 2025.11.2. Moving the Z-Wave+ lock devices (Schlage BE469ZP) was simple; the ‘legacy’ Z-Wave locks were another story.
I finally stumbled across an old youtube video which demonstrated how to add these which caused me to select additional mechanisms on the searching dialog box, and then Legacy Security.
Hope this helps and saves someone from spending as much time as I did to finally get my Schlage FE599 locks added to HA :).
FYI normally this is not required, the default inclusion strategy is sufficient. The core Z-Wave JS add-on currently is still on a buggy version of Z-Wave JS. The Z-Wave JS UI add-on is using a fixed version.
To reiterate, I was using the core Z-Wave JS version, and found that the default inclusion for a non-Z-Wave Plus lock would not fall back to legacy security unless I explicitly requested it during the auto enroll process.
I attempted to enable the JS UI version over multiple days, and could not get it configured properly to work. So I backed off to the non-UI version. Maybe I’ll give it a try again.
Yeah, that’s the bug in driver v15.15.0, which has been fixed for awhile now, the core add-on just hasn’t updated. Z-Wave JS UI is currently on v15.17.1.
If you want to switch (which isn’t necessary, just depends on your needs), try: