Z-Wave Yale Lock issue, missing AlarmLevel and AlarmType

Hello,

With the release of 2021.4, I decided to bite the bullet and migrated from the depreciated Z-Wave addon to Z-Wave JS. The new Z-Wave appears to be a lot faster! Great work in modernizing the platform!

However, I have an issue with my Yale lock:
NexTouch Wireless Push Button with Z-Wave
NTB610

At first the AlarmLevel and AlarmType sensor entities were missing. I eventually figured out they were simply “disabled”. I was able to enable them from the Integration setup, however their state is always “unknown”. It never gets updated, even after multiple reboots.

Entities:
sensor.nextouch_wireless_push_button_with_z_wave_alarmlevel
sensor.nextouch_wireless_push_button_with_z_wave_alarmtype

I also tried with zwavejs2mqtt (7.1.1), same result.

From the zwavejs2mqtt dashboard:

[8-113-0-alarmType] Alarm Type
undefined

[8-113-0-alarmLevel] Alarm Level
undefined

[8-114-0-manufacturerId] Manufacturer ID
297

[8-114-0-productType] Product type
32769

[8-114-0-productId] Product ID
2816

Is it possible to add the alarmlevel and alarmtype again since many nodered automations rely on them?

Or should I rework them to use the zwave_js_notification events (Is that where the future is headed?)

At this point, the zwave_js_notification appear to be incomplete: I get events for User Lock, User Code Added, User Code Deleted, but I don’t get them for other events like Keypad lockout.

Thanks!

Did you ever find a solution to this? I’m running into the same problem

I have this same problem but found this blueprint below which does everything I wanted by using zwave_js_notification in an automation.

I just ran into this problem. My zwave (deprecated) lock was working fine until today, including the alarmlevel and alarmtype entities. I migrated to zwave JS and lost them both. The lock could be locked and unlocked, but I no longer had jam warnings or notifications about who unlocked it. So I removed zwave JS and went back to zwave depreacted, and both those entities are still missing!

Has there been any update on getting AlarmLevel and AlarmType entites working for the Yale locks? Mine both show “null” no matter what the status is?

I just tried to swap over to zwave js today and I’m finding this (among a painful number of other things) as a problem myself. Enabled the “sensor” but it stays “unknown”.

To me these are absolutely critical as I had things set up to message everyone if a lock jams (so it doesn’t get left unlocked just forever trying to re-lock) as well as other things like triggering “coming home” events when an authorized code unlocks the door from outside.

Kind of defeats the point of a smart lock if you ask me.

1 Like

Yep…I feel your pain, I’m in the same boat…I’m a little shocked that this hasn’t been addressed by now. Surely there are others that have the same issues?

Looking at this template it seems to still miss a lot of possible states…

For example, some “alarming” things that I would want to have trigger alerts for something suspicious going on or malfunction:
-Motor jammed
-Deleted code
-Factory reset
-Unlocked by master-PIN (nobody should be using the master PIN)
-Master PIN changed
-Added new code
-RF module power loss-restored
-Keypad Escutcheon Removed
-Too many failed attempts
-Other unknown tamper alarm
-Low battery (reported by the lock, not by %)
-Critical battery (reported by the lock, not by %)
-Not enough power to operate

All of these have published alarm type/level combinations documented by Yale, but who knows how or if there’s a way to access that data now…and the values aren’t passed up to be sure we are getting it directly.

When I briefly thought I had the zwavejs working, I couldn’t get it to trigger events on several of these - it did show for lock/unlock but yanking/reinstalling the RF module, removing the front keypad, jamming the motor did not generate events to try and capture.

I had to revert from backups to get my stuff working again, ran out of time messing with it.

Just wondering if there is any update? What I find strange is that these disabled sensors at least showed up for me yesterday but somehow my zwavejs/keymaster configuration got corrupted so I decided to start fresh with a new HA install and to factory reset the lock. Ever since I brought the lock back into zwavejs those sensors don’t even show up anymore.

Before:

Now: