Despite some complaints about the product we replaced an older smart lock that kept cracking with the YRD450-F-ZW3 because most of the more highly rated smart locks were either WiFi only (potentially worse battery, less secure, and more interference) or very aesthetically unpleasing (for us).
Hilariously we haven’t really experienced any of the more commonly complained about issues, but have starting having this one issue that I can’t quite find described elsewhere so I was curious if anyone else that stumbles on this has had the same experience and possible insight.
- The door will be locked
- The door is unlocked manually. The bolt is able to be retracted about 3/4 of the way but youre stopped from turning the bolt further unless you really force it and feel yourself fighting the gears/servo. Its enough to open the door at least
- The Yale App shows a manual unlock event and acts like everything is fine; however, in HA the lock still shows as “Locked” and the “Lock Jammed” sensor changes to “Problem”
- You can then trigger an unlock in HA and the lock will actually “unlock” again, this time pulling the bolt 100% of the way in, after which the jammed status clears and lock state is then once again synchronized between the Yale app and HA. The yale app records this as a “smart module unlock event”, leading to showing 2 unlocks in a row. I think you can also “fix” the issue happens if you manually force the bolt in all the way by hand but of course that probably isnt good for it
We’ve tried redoing the handing calibration with no success, and of course Yale support is usless as since their software doesn’t say “jammed” itself and this involves “3rd party software” (like dude, you sold a device with a ZWave module of course it will involve 3rd party software) they act like it’s not really their problem, even though there are vague signs in their app like the door unlocking twice in a row which of course shouldn’t be possible. I think it’s just that their team that made the module did a better job in exposing error state than their app developers.
I think whats going on is that theres a calibration issue of some sort where its not letting you manually unlock the lock all the way. The internal hardware just sees the bolt being opened at all as a manual unlock event and logs that but the additional hardware in the module is smart enough to see that the bolt was turned and then left part way open and reports that as a jam, while the app doesn’t expose that info.
Essentially, I believe that if there was a way to have the bolt always able to be retracted all the way when unlocking manually, the jam state would never occur. When the fix support wanted us to try presumably doesn’t work, I’ll probably just focus on that aspect when I call back. I think in the end the module firing the jam alert is just a downstream effect of the true issue, which is that you should be able to retract the bolt all the way when unlocking manually (without resistance), but we cannot for some reason.
For now I have an automation that will trigger an unlock 20 seconds after a jam state is detected so the lock is still useable, it’s just stupid.