#Yale Assure Lock 2 YRD450-ZW2 joins but has no controls?

1 messages · Page 1 of 1 (latest)

sour gazelle
#

I think I'm missing something but can't seem to get this lock to play with HA properly. I include it succesfully but it has no controls. I've factory defaulted the lock and tried inclusion a few times. I've also tried reinterview. I also rebooted HA.

#

Yale Asure Lock 2 YRD450-ZW2 joins but has no controls?

#

Yale Assure Lock 2 YRD450-ZW2 joins but has no controls?

#

https://github.com/zwave-js/zwave-js/discussions/5391
I did find this other thread with folks using them. I do have the older ZW2 module but from what they are saying it still worked just with less features. I plan to look for the ZW3 module but would love to get this running in the mean time.

GitHub

This discussion is just to share some information and my current experience with a Yale Assure 2 lock and a Yale Z-Wave 700 series Smart Module (which are not available from Yale yet, but can be pu...

quartz thicket
#

It's not added using security which might be the issue?

#

did you pair it using a code?

sour gazelle
latent mantle
#

Can you share the Z-Wave logs of you trying to join it?

sour gazelle
#

Do I just grab the Diagnostic file for the device or watch the zwave log in the integration and try to include it? Do I need a specific log level if doing the integration log?

frail sand
#

Which version of Z-Wave JS are you using? The core add-on still has a bug related to including security devices that has been fixed in newer releases.

sour gazelle
#

This the right place for the version?

frail sand
#

Yeah, that version doesn't have the (potential) fix. Not sure if that's the root cause but it fits.

#

For S0 devices specifically

#

The one you linked to in the ZWA DB does not support S2.

sour gazelle
#

Ya and I think S0 is all this module supports. One of the reasons I'd like to get the new ZW3 module. But Ideally if I can get these working until. Just trying to get away from SmartThings at the moment.

frail sand
sour gazelle
#

I'll work on getting the inclusion log in just a bit. I have the house half broken at the moment moving over other devices. Thanks for all your help!

sour gazelle
frail sand
#

Seems you have zigbee debugging on, that's all the noise

#

The zwave debug logs are at the end, so it captures everything. I'm guessing the recent bugfix addresses the problem, but I can't say 100%. It looks like the interview just stops prematurely probably due to losing the device class information.

sour gazelle
#

Weird in the zigbee integration it shows debugging off. Should I check somewhere else to turn that off? Just so I'm not slamming logs?

Ok good deal. Glad it was in there. So at this point unless I jump through some of those hoops you mentioned earlier it's ride it out until the HA core Z-Wave JS gets updated?

I'm kinda ignorant to the difference between those 2 Z-Wave JSs. One is more official? But the same folks are working on both?

sour gazelle
#

Ah ok thanks. I'll see how quickly I can locate one of the newer ZW3 modules and if not I'll check out the swap. Appreciate all your help, time, and patience with this. 🙂

latent mantle
#

I think you should be able to select S0 as the joining strategy, or is that only Z-Wave JS UI?

sour gazelle
#

I thought I tried with the top one but I can try the Legacy Secure and see if that acts any different? Might not get to it until tonight after work though.

sour gazelle
#

I'll be dipped. That did it. "Regular" inclusion didn't work and neither did "Secure if possible". The "Legacy Secure" did the trick.

I'll still look to replace the module to all the security stuff over to S2 but this is great.

To manage user codes I need another integration/add on right? This won't do it natively?

latent mantle
#

The goto right now for that is keymaster

sour gazelle
#

Thanks! Greatly appreciate all your help with this.

uncut vapor
#

I'm struggling and so sad.

sour gazelle
#

Ya. Select advanced while joining and select the Legacy Secure choice. I had to click it fast and then next. If I waited too long the box unchecked itself. Not sure if it's just a GUI bug or it was actually turning it right back off.