When turning the thumbturn if you don’t hear the confirmation beep then the module doesn’t register that it’s unlocked, meaning it won’t appear in HA.
For me it’s been like that since I brought it (5yrs)
1 Like
Thank you. I’m guessing that would be the same for any platform, not just HA (eg Hubitat etc)
Yes, I just did a test to confirm. Thumb turn generates a status update and generated the following entries in the logbook.
Front Door Lock fired Notification CC 'notification' event 'Access Control': 'Manual unlock operation'
07:50:34 - 3 minutes ago
Front Door Lock Last seen changed to 17 April 2024 at 07:50
07:50:34 - 3 minutes ago
Front Door Lock: The current status of the door was opened
07:50:33 - 3 minutes ago
Front Door Lock was unlocked
07:50:33 - 3 minutes ago
Front Door Lock Current lock mode changed to Unsecured
07:50:33 - 3 minutes ago
Front Door Lock Last seen changed to 17 April 2024 at 07:50
07:50:33 - 3 minutes ago
1 Like
@siwilson thank you for confirming. I wonder why my lock doesnt show the same in the log, lol I have probably set it up incorrectly - when I paired the lock and stick I just ticked everything (legacy and s2?) to pair. Any suggestions on guides how to set this all up?
Mine was legacy and also it was included in direct range of the controller.
Just in case anyone comes across this in the future, I found the issue with no update status for manual unlock to HA - the internal thumb turn was not being fully turned during unlock until the thumb turn wont turn anymore. This applies to both zwave and wifi/bluetooth modules
2 Likes
Disclaimer: I don’t have the bridge. I hate them, have no bridges in my home.
I was struggling with direct zwave control, because the lock needs to be factory reset (and key fobs/cards are lost) to pair zwave, and it also needs to be reset to pair bluetooth (with the new module) to manage fobs. If I pair zwave and then install bluetooth module, the app will not connect. So what I did:
- disassemble and reset the lock as per manual. Install zwave module. Pair with home assistant.
- remove zwave module, disassemble lock again, factory reset.
- install bluetooth module, pair with Yale Home app, manage my key fobs/cards.
- remove the module and reinstall zwave again. HA control works without resetting the lock.
- following key fob management can be done by swapping modules. To swap: remove battery, replace module, insert battery. Blue light rapidly blinks a few times followed by a solid white light and a melody (I guess this indicates successful start).
While playing with it, after trying different combinations, my lock dropped in to a weird state: when powered on, internal blue LED was blinking, stopped after pressing the button. Also, outside LED was rapidly blinking blue, and would not stop no matter what I did, and which module is installed. This continued for days. But I was able to factory-reset it once again and the above combination has worked.
I still have a problem that app says pairing my fob was unsuccessful, but I cancel out and see the key in list, and my fob works.
My overall experience with this lock is that it’s extremely buggy. I often hear motor spinning up some time after the lock was operated. I sometimes hear it playing melodies hours after interaction. I found it to be unlocked a few times when I’m sure I have locked it. Also, when locking and unlocking it sometimes plays wrong melodies, eg. dedicated for app unlock. It’s either they are all like that, or my unit has a failing flash memory. I have recently updated it to latest firmware.
Anyway, hope this saves a week of frustration to someone. Or to future me.
I have decided to stay with the Z-wave module, using Z-wave JS. You can update the auto relock function in the configure section of the lock. I ordered the free Yale connect module, just in case I change my mind. I am having an issue with it going to sleep and not waking up for automations. I thought it might be the module which is a few years old, but it isn’t as a new module did the same. My Yale keyless lock with a Z-wave module doesn’t do this, but it is closer to the controller. All my Z-wave devices are battery powered, so there is no mesh. To help I have plugged a z-wave adapter into an electric socket, hopefully it will help.
So here are my adventures with my lock…
I had already ordered the module and hub, with a view to keep using the zwave module but just upgrade it like others on here and then swap them out.
Disaster struck though. I broke the stupid pins swapping out the modules (they really are a bad design), so neither module worked!
As if by fate, it was Prime Day and I ordered a new L2 on Amazon pay in 5.
Fitted it today - they are identical externally in all ways - I spend a bit of time making larger holes in the door, as for 4 years it has sometimes spun as I knew it wasn’t quite square, but didn’t want to go through the hassle of taking it off to fix,
Internally, I was happy to see that where the module goes it is now a proper socket, so you cant bend the pins!
Anyway, set it up with the wifi module & hub as new (well it was lol) and then added all my key fobs. All working good.
I then thought why not give the zwave module a go and removed the batteries and swapped it out and then powered it up.
Reinterviewed the node and no other config in HA needed - it is as if I had the L1 
All my entities are the same and all my automations work
I have put the module and the hub away in case i want to add any more fobs.
Hope this helps someone.
mb
2 Likes
Thank you for sharing this is really helpful if anyone moves over to the L2
1 Like
I will add that I realised I hadn’t added my fobs that are stuck on our phones, so swapped the zwave module for the bluetooth and added the fobs. Swapped them back again and no dramas.
Took literally 2 mins all in all. Do a battery pull though before.
mb
1 Like