Schlage Lock wtih ZWave JS Conundrum

Configuration Z-Wave
1

Okay I’m totally baffled. I’ve been using my Schlage BE469ZP with the legacy HA Z-Wave integration for years, in conjunction with PTDalen’s lock components. I just got a HA Blue and decided this would be a good opportunity to migrate to ZWave-JS and start using Lock Manager. I got everything installed fine and can control the locking and unlocking without any issues but when I try to setup Lock Manager I run into issues. It would seem I am missing some important entities, namely sensor.be469zp_connect_smart_deadbolt_user_code. I checked to see if maybe it was disabled by default but simply is not there. The lock is paired in secure mode. I am at a loss and hoping someone might have some idea. Attached is the screenshot of the available entities.

Any assistance would be greatly appreciated.

zwavejs-lock
zwavejs-lock1543×906 155 KB

2

All ZWaveJS usercodes for Schlage locks come through as events on zwave_js_event and not on sensors. I’ve never used Lock Manager, but it sounds like it needs to be re-worked to be usable with ZWaveJS.

2 Likes
3

Did you get anywhere with this?

I too am using a BE469ZP and used the user codes unlock to trigger a variety of automations.

I’m seeing the manual unlock happen, but not anything being written to MQTT so as I can create a sensor from (or just leverage in another way).

4

As mentioned above you need to look for the zwave_js_events and you can change your automation triggers to that. There are posts about it somewhere… I can share my automations when I get home.

1 Like
5

thanks, i’m not using the WS i’m using the ZwaveJS2MQTT instead. So not sure if that complicates things. appreciate the help and offer of the automations too!

6

I would check the things mentioned here also… see if you have zwave_js_event and “listen” to it while unlocking the lock…

7

thanks - this looks like its using the integration rather than the Z2MJSMQTT docker though.
My device is showing as Interview stage ‘Complete’.
I’ve enabled events, but there is a bucket load of JSON that comes through under the general topic (rather than specific to the device). If this is the new way of handling this, it seems this has added a LOT more complexity.
I used to subscribe to a topic zwave/front_lock/113/260 and would just get a number (which was the user code that unlocked the device).

I may be mis-understanding this of course