#Yale Assure Lock YRD226 w/ Zwave No Longer Reporting Lock Capabilities and Can't Lock or Unlock

1 messages · Page 1 of 1 (latest)

rustic crystal
#

I've been successfully using my Yale Assure Door lock (model YRD226) for over a year with their 500 series (green) zwave plus smart module. Within the last month or so I have been unable to remotely lock or unlock it, and all lock related entities are now showing as 'Unavailable'. I use the Home Assistant ZWA2 controller (upgraded somewhat recently but the lock worked post upgrade). I have another Yale lock, albeit a different model that is working and reporting just fine, so the issue appears to be limited to this model and presumably some HA and/or Zwave update.

Troubleshooting:

HA is on latest - 2025.12.5 - and zwave controller firmware as well as the zwave JS addon are all up-to-date

Per the Yale model instructions I've tried excluding and including the lock multiple times via Zwave with HA to no avail. In all instances the lock shows up in HA with an unknown manufacturer & model and just with a ping entity and very basic zwave related diagnostic entities, but 0 entities related to it being a lock or any of the entities it had previously. When I trigger a device reinterview it does correctly identify the manufacturer and model, but the same entities remain. I subsequently did a full factory reset of the lock and the same behavior occurs.

I went so far to buy another same Yale lock model with zwave module and it too exhibits this same behavior right out of the box...

At this point I'm not sure what to do and/or where & how to file this as a proper issue or bug on GitHub to hopefully get resolved. I did grab a diagnostic report of the new lock following setup and reinterview in the hopes of revealing what issue(s) may be at play here...

Can anyone help point me in the right direction for reporting this?

lapis ibex
#

If you are using the core add-on, and the lock only supports S0 security, you must be sure to select the advanced inclusion option and choose "Legacy security"

rustic crystal
#

You sir or madam were SPOT ON! ... WOW didn't realize that was a thing and as soon as you said S0 I vaguely remember seeing that in the original config of the lock before I originally excluded. You have saved me a lot of headache 😅 thank you thank you!!!

lapis ibex
#

It's a driver bug in the version the add-on is using, it's quite out of date and fixed now

#

Normally the regular inclusion process would work w/o issue

rustic crystal
#

Good to know, thanks again 🙂

livid moat
lapis ibex
#

The symptom would be if it's included w/o security

livid moat
#

I can’t remember. I added that over a year ago. I’m just now noticing symptoms

#

I’ll try removing it and follow the legacy option and see what happens

lapis ibex
#

Shouldn't be applicable then

#

The device page shows what security level it has

livid moat
#

It’s on legacy. Hmm wonder what the issue is then