2.1.7.121
Also recreated another copy of the reliable lock instance for this one lock and it gives me the error. Pretty sure it is not related to 2.1.7 as I just upgraded to it and reliable locks was not working for me before.
Been running the Reliable Locks app since it was created.. Never had an issue with it so far. Works great for me. I have two Yale locks, one is Z-Wave (non plus) and the other is Zigbee.
Well I deleted all the devices and the app. then I created the app and one of my Zigbee locks and now it works again.
So if anyone gets this same error message do that and see if it fixes it.
Just wanted to say thanks for this, works like a charm thus far.
Cheers
Anson
2 Likes
@jwetzel1492 Can this app be made to help locks that will not lock/unlock correctly? In addition to requesting updated status, could it also resend the command to lock/unlock?
Use case;
I have locks that do not listen to commands all the time. I have created a rule that monitors lock status/mode and resend the lock/unlock as needed until the lock changes. But it has to check constantly. See this thread for details.
My thought is if reliable lock could do it, then it would only have to run checks on the lock that is not responding and only during the time it was asked to change, and the change really happened. If Reliable Locks could do both status, and command updates that might help a lot of people that have lock issues with HE.
I am not a coder and have no idea how you guys make this stuff work, so sorry if this is a stupid questions. Thanks for the current app, and consideration.
Hi @TechMedX, yes it will re-send lock/unlock commands several times. It doesn't keep sending it long-term, but it will do a couple retries.
I tired the app a few weeks and it didn't help lock the door. I could see refresh request in the log, but never saw it resend the commands. Is that something that needs to be set? Could there be an option to adjust when to resend commands, and when/if it stops trying?
Sorry to be a bother. Just trying to find someway to use these locks in HE without going back to ST hub.
Oh, you are right. That is a feature I put in my other lock app: Lockdown. I could add it to this one.
2 Likes
Downloading!!! 
God I hope this fixes my locks! If it does tell me where to donate!!!
What would be the difference between Lockdown and Reliable Locks be if you add this feature? Why choose one over the other?
Seems like Lockdown is more to stagger the events using a virtual switch. I guess that is nice, and I could see myself using it, but in my case I would also need "Un-lockdown". For now all I really need is....
Truly "Reliable Locks" - (I never thought there would be anything I missed about ST. This is it!)
@jwetzel1492 I would be endlessly grateful if you could add this feature to resend lock AND unlock commands every 10 seconds until it locked/unlocked! If you do please let me know when to update and I will happily be a test dummy!
2 Likes
Any thoughts on when you might have a chance to add it? I am hoping to not have to put these locks back on ST, but planning a trip and need them to be reliable while we are gone.
Thanks for the consideration and your time.
1 Like
Good news! I've posted an update to GitHub. You only need to update the ReliableLocksInstance.groovy file for the child app.
There's an option: "Retry lock/unlock commands if the lock doesn't respond the first time?" I found that I had put comments in to explain what this SHOULD do, but I hadn't actually implemented it before I got distracted by something else. It is implemented now.
It will retry up to 3 times. (Though you can easily change that in the code. Look for the number 3 on line 180.)
(Sidenote: I would not rely purely on smart locks for security in a house. What I mean is that if I were leaving on a trip, I would not drive away with the house unlocked and then lock it on my phone. I would make sure things were locked before I left. However, I'm guessing maybe you're using it to let people in and out of your house while you're gone?)
3 Likes
Yes, but moreover, people have access. People are saposta lock doors. People are people 
Thank for very much!
I know, right? If I didn't have these got-dang people in my house, my automations would be so much easier! 
1 Like
A big thank you from me as well for this update.
2 Likes
I just wanted you to let you know this has made ALL the difference with my locks. I have not had to request a second "Lock/Unlock" since installing the update. 
I will be recommending this to anyone I see that has any 
issues
It makes me wonder if other hubs implement a similar process by default which makes them better than HE with locks. Either way mine are truly Reliable Locks now thanks to your update. 
3 Likes
I don’t know about all hubs, but ST definitely does not do this. I had to come up with a similar solution for ST before I migrated to Hubitat.
3 Likes
The update has made a big improvement for my locks as well. This is an excellent app that I will definitely recommend.
1 Like
