Hi, just wondering if anyone could help me with this, I have a Yale Yrd226 lock, with a z wave module installed into it, I’ve been running home assistant for a good 2 months now, though my Yale lock is always defaults back to unlocked, as soon as it locks either from an automation of from GUI, it will go back to unlocked, I’ve got no idea what the problem could be here, I’m currently running z wave js to mqtt, though even on just the standard z wave js it had the same problem, any help would be great.
Just to add, the physical lock isn’t unlocking, only the GUI will show it unlocked while the lock itself will remain unchanged
Thanks
An update, I was running the zooz series 7 z wave controller on the old firmware, thinking that the old firmware may have been the issue I updated it,
the lock is now currently performing as expected when manually opening and closing, though when done from call service lock.lock or lock.unlock it will lock, the gui will show the lock turn green for a split second then back to unlocked
Again this is just the gui showing this, the lock isn’t actually unlocking
Any help please
When you paired the lock, did you do it using secure mode with a security key? It sounds like the lock was paired in legacy mode, but I’m just taking a stab in the dark.
Not sure if you are using the Z-Wave JS to MQTT addon…but either way, you need to make sure you have a Z-wave Security Key registered and are using S0 secure pairing, otherwise the lock isn’t going to respond properly. Depending on your Z-Wave mesh, it might take a couple times to pair the lock in secure mode. Those Yale locks can be a little finicky, however, once they are paired, it’s been my experience they are pretty rock solid.
Network keys are used to connect securely to compatible devices. The network keys consist of 32 hexadecimal characters, for example, 2232666D100F795E5BB17F0A1BB7A146 (do not use this one, pick a random one). Without network keys security enabled devices cannot be added securely and will not function correctly. You must provide these network keys in the configuration part of the Z-Wave JS Server.
For new installations, unique default keys will be auto-generated for you by the Z-Wave JS add-on. You can also generate those network keys in the Settings section of Zwavejs2Mqtt.
If migrating from the zwave integration, your network key from those integration should be entered as the S0 network key. Those integrations did not support S2 security, so you will not yet have S2 network keys to configure.
Make sure that you keep a backup of these keys in a safe place. You will need to enter the same keys to be able to access securely paired devices.
Hi, thanks for your help so far, and yes I’m using zwavejd2mqtt, the keys were all set up when I first set up home assistant a couple months ago, the s2 unauthenticated, s2 authenticated, s2 access control, and s0 legacy are all there.
The locks security is currently s0 legacy
Do you have a couple good Z-Wave devices around the lock to create a good mesh?
Have you tried moving the Hub closer to the lock to see if it responds better?
I haven’t tried moving the hub yet, it’s pretty close about 10 metres and both are in view of each other, I checked the mesh for the lock yesterday it’s only 1 jump from lock then straight to hub
Looking at your photo you have a yrd226 lock like mine, but my one has paired as a yrd 426, not sure if that might be the issue or not
So a bit of an update on this, I originally had the model with the key and ended up buying the keyless model, everything is working as normal now, no issue at all, so I’m thinking it may be that it was a firmware issue on the Yale side of things, though from the pictures above both of us had the same firmware, so it may have just been the lock itself.
The only other thing now is that it is not pairing in s2 security, which isn’t a major issue for me right now, but I may buy another z wave module in a few weeks to see if that will do it.
Good to hear you are making progress. I’m not sure about the YRD 226. Mine are all YRD 256 models, but none of mine have the ability to pair in S2, just the secured legacy mode. Nonetheless, they work just fine.
Ok that’s good to hear, mine are also the YRD 256 paired in legacy, though I called a smart home supplier near me that said they do pair in s2.
Although it’s not really an issue I’ve just read that s2 is a lot less clunky then s0, the module isn’t that expensive so I wouldn’t mind buying it to just try it out
Thanks for your help also
