#Yale Assure Lock 2 YRD450-ZW2 joins but has no controls?
1 messages · Page 1 of 1 (latest)
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.
It's not added using security which might be the issue?
did you pair it using a code?
It's not prompting for a code just adding when I search for it. I'm not sure the green module the ZW2 supports S2?
https://products.z-wavealliance.org/z-wave-product/yale-assure-2-lock-sl-key-free-touchscreen-deadbolt/
Can you share the Z-Wave logs of you trying to join it?
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?
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.
This the right place for the version?
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.
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.
I think a log of the inclusion would determine if that's the case. https://github.com/zwave-js/zwave-js/discussions/8205#discussioncomment-14563838
If so, then your options are 1) wait for HA to update to a newer Z-Wave JS (or build your own), or b) switch to Z-Wave JS UI (https://community.home-assistant.io/t/switching-z-wave-js-addons-with-minimal-downtime-z-wave-js-official-to-z-wave-js-ui-community/409904
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!
Seems like quite a bit of noise in that log. If I can tweak something to help clear it up just let me know. Sorry for the delya.
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.
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?
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. 🙂
I think you should be able to select S0 as the joining strategy, or is that only Z-Wave JS UI?
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.
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?
The goto right now for that is keymaster
Thanks! Greatly appreciate all your help with this.
So this worked... Using 'advanced security options'?
I'm struggling and so sad.
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.