I just purchased the Yale Assure 2 zwave module lock YRD450 to replace my Schlage Lock BE469ZP. My reason for moving away from the Schlage was to find something that actually worked well with Hubitat, beyond locking and unlocking (which worked fine). Specifically the ability to control users via Lock Code Manager or even under the device settings - neither will work. Well, the YRD450 is absolutely no better so far, in fact it is worse. I cannot control anything from LCM and cannot add users via the Yale app since I have told it to manage via external hub…. Note, it uses the “Generic Z-Wave lock” driver. I looked for a new drive for this specific model but I did not find one. Anyone have any tips and tricks that I am missing to make it work in Hubitat or I guess back to Schlage (because I sure do not see many other Zwave locks out there that work much better). Thanks in advance.
I have 2 Schlage locks and a Yale Assure SL YRD256, all working fine here with Lock Code manager.
I am also using the Generic Z-wave Lock for the Yale.
Did your Yale pair with S0 or do you have newer ZW3 module with S2?
Here is what I have, all working with LCM no problems.
I have the same reaction as @jtp10181 -- with two Yale locks, both work well with LCM. However, I haven't used LCM much. I set it up, tested and then have left it more or less idle. I mention that because I remember there was a need to reset the factory code slots on the Lock, THEN let LCM manage it... but it's been so long, I don't remember if the Yale needed that. Their "admin" code slot is #256, which is beyond the 255 slots that can be reset.
Yeah there was some initial pain with more than one of my locks, especially just getting everything to sync up since it was a TON of z-wave traffic reading in every single code slot. Once it was all synced up though I was able to add 4 users no problem, and then I added one more guest code later to the Yale only which also worked fine.
If amazon is to be believed this time, I should have a YRD450 arriving today (it's already "late"). I can report back if I was successful on this model. I have a YRD256 connected and working with LCM, and only "issue" I have with that device is the Z-Wave table lists it as a repeater for some reason. Being battery powered, I wouldn't think this should be the case. Nothing is routing through it and it responds quickly to lock/unlock commands, etc. Seems to be reporting correct state, etc., so I'm not messing with it any more.
What is your app state for LCM? Mine appears False for all activities but not sure if I am reading this correctly.
Those are just state variables used by the app to (I assume) keep track of what it is doing at the moment. Mine looks about the same but I have a userMap with the users and codes in it.
Maybe it would be good to first look at the info on the device page
I have lock code encryption disabled, as I am not really sure of the point of it. Seems like it just makes things complicated.
You could also enable debugging on the device page. Then try to manually add a new code from the device page and check the logs. This is the first step to making sure everything is working correctly.
I received the YRD450 yesterday with the legacy Z-Wave module (S0 only). I was able to pair it, but could not control it, see status, etc., so never even got to the point of trying to add codes from LCM. Tried removing and re-adding, only to end up with ghosts which took a while to remove. Not quite sure what's going on there, but it's likely going back unless I can figure it out quickly. It's too expensive for it to be this finicky. I'm actually surprised that the "older" model I got last week came with a newer Z-Wave module than this one.
Thanks Applejosh. Yeah, looks like it may not be ready for primetime. I returned mine and going back to the Schlage for a while until I can figure out another device.
I just purchased a Yale Assure Lock 2 YRD450-ZW3-619. I have my Hubitat C8 about 50 feet away from the lock and paired it the first time after 7 attempts. I then had too hard reset it and tried about 20 times to pair it again and it would not. I then took my Hubitat and put a 50 foot Ethernet cable on it to get it within 5 feet of the lock and then it connected/paired VERY reliably about 3 times in a row. After pairing it I took it back to its 50 foot position and locked, unlocked, and set a key code without problems. I then installed:
and when I ran it I got around 3 to 5 dB for the LWR RSSI. Compared to all the other device I have this has the lowest strength. I was wondering if others had dB levels higher than this or is that typical for this device. I reported this to Yale Technical Support but they said the only way they would replace the z-wave ZW3 module is if it did not work at all. I bought this from Amazon 4 days ago so I can return it and get another one but I thought I would check in with the community first. Thanks
How many ghost nodes did you create with all those pairing attempts?
Do you have any repeaters between the lock and hub? If not, you need to add some.
My YRD256 with ZW2 module is about 15ft from the hub and has 51 dB
Are we sure LCM isn't what is causing the grief. I have a Ring Keypad and the Yale Assue Lock 2. The lock has been great but managijg it with LCM has been my pain point. I don't think it is the fault of the lock.
I use LCM on the ZW2 module and have zero issues with it.
The model of the lock I dont think is that relevant, its either the ZW2 or ZW3 modules talking to the hub.
I do know people have had issues with the ZW3, possibly why Yale has been reluctant to start selling them mainstream. I want to switch my lock over to it for the S2 security but they were hard to find standalone to purchase, have not looked recently though.
May end up just upgrading to an Assure 2 eventually, to take advantage of the door sensor and auto unlock features.
It is common for locks to pair using very low power as a measure to limit the range to minimize the process being monitored.
Usually only older locks.
I have a Yale Assure SL (YRD256), Alfred DB1, and two Schalge BE469ZP and they were all paired in place 20-30ft from the hub with no problems.
I ran Settings->Z-Wave Details and got the following:
I do not see ghosts and presently I see no repeaters. I have tried Repair for the entire mesh and also the specific Repair for the Yale Assure and a repeating node did not appear. I came back hours later and it showed for the first time a routing of 01->0x0011->0x001a. That went away hours later and I got a direct link again. Prior to running the Z-Wave Details I put my ZoozZac38 in between the Hub and the Lock... It never has contributed as a repeater yet. I then moved the Hub from 50 feet away from the lock to 40 feet and both locations where line of sight. When I moved it 10 fee closer I then got a dB = 15 instead of 3. Prior to moving it closer I tried locking and unlocking with the Hub and it was not reliable. After the move I did 10 lock/unlock's and it was 100%. I thought Z-Wave had the capability of dictating a repeater so I can force the ZoozAac38 to be in between but it looks like you cannot do that right?
The following is from running Hubitat Z-Wave Mesh Details app:
Moving the Hub 10 feet closer made a huge difference in communication reliability and I think the lock is a keeper.
Every single node with a "Discover" button is a ghost node. They are not tied to a device entry on the hub, and probably a failed pairing.
The routes on the details page do not update instantly. There is a lot going on behind the scenes in the zwave mesh. If you have a solid repeater between the lock and hub and the direct connection fails it will go into route discover and probably flip to the best repeater. This could take hours to see the change in the route on info on the hub. In the meantime if it fails on the repeater at all it will discover again and possibly flip back to direct. Locks tend to have a lot of route changes just due to the way the FLIRS system is setup.
You can use a secondary controller to manually set a priority route but the device can still select another route. I have tried it out before, complicated to do and did not get much for results.
Interesting comment... it corresponds to my experience. Stretching out 50 feet of Ethernet cable is getting old! But after I am done experimenting with the lock I should not have to pair it again. I would imagine every time I replace the batteries I will have to do a pair.
Nothing else behaves like that. Don't understand why a Lock would traverse a battery change any different than a Door/Window sensor or a Motion sensor, or a Leak sensor.
I have two Yale locks and both have had a battery change in their time. I've never had to do anything ZWave related to them as a result. I tested them of course, but that's not any different in my process than for a Recessed Door sensor, for example.
I appreciate the feedback... it looks like I made a bad guess. I am already down to 88% after 5 days or so (But, of course, I am in play mode). I guess I will find out soon.
