[CONFIRMED FIXED] Add "Jammed" or "Unknown" state for Yale Assure2 Zwave

[a.mcdear]

Almost all door locks seem to report when a lock jam is detected, yet Hubitat doesn't seem to officially support any lock states besides Locked and Unlocked. Could we please add a state for Jammed lock to Hubitat for those of us with locks that support reporting this?

Yale Assure Lock 2 Z-wave using Generic ZWave Lock driver

EDIT
As the thread has been automagically locked for some stupid reason, I was unable to add an update to the thread with a new post. Trying to see if it will still let me update the top thread and title to reflect that the issue has been fixed with the changes to the driver and the most recent firmware update which once again reports when the lock has jammed.

[ogiewon]

Hubitat does already support an “Unknown” state for locks. It is up to the driver to support it.

[a.mcdear]

Huh, I'm using Hubitat's built in generic ZWave driver and it just reports some code from the lock with a note that says "what is the lock state?" or something of the like in logs but does not change the lock to "Unknown" when lock jams.

[ogiewon]

I’d recommend reaching out to @bcopeland and @mike.maxwell from Hubitat, as they handle changes to the built-in device drivers.

[mike.maxwell]

Yeah, I can change that

[a.mcdear]

Awesome, I'll send you a private message (I saw something about my particular lock and the Generic ZWave Lock driver on the recent beta release notes)

[mike.maxwell]

@a.mcdear

I saw something about my particular lock and the Generic ZWave Lock driver on the recent beta release notes

that was for a different issue

[a.mcdear]

@mike.maxwell
Interesting development. I took this screenshot several months ago where it showed the message I got when the door jammed. Just last week, my Yale Assure Lock 2 received an OTA firmware update when I opened the Yale app on my phone. Today when I intentionally jammed the lock to show you the log output, it seems to no longer report this in my logs. Maybe it's no longer able to report a lock jam?? Geez I hope not. Oh, I'm on 2.3.6.146 Anyway, here's the log from a few months back:

[mike.maxwell]

different lock models and firmware can produce different codes, in any event the next build will parse 0xB as unknown.

[a.mcdear]

@mike.maxwell

different lock models and firmware can produce different codes, in any event the next build will parse 0xB as unknown.

Thanks. This is specifically a Yale Assure Lock 2 (YRD420 model with keypad and Zwave)

[a.mcdear]

Well, it really looks like the last Yale firmware update for this lock seems to have actually removed the lock jam code reporting via Z-Wave. It definitely no longer shows anything in logs for the lock jam condition anymore, and it seems to just revert the lock to "Unlocked" instead. This is a huge bummer!

@mike.maxwell Thanks for your attempts to help fix the issue. I am going to contact Yale to figure out why they removed this and see if there's any chance to add it back in.