[Release] Reliable Locks

aaiyar · May 2, 2019, 10:39pm

@jwetzel1492
I will. I uninstalled Reliable Locks earlier today because I couldn't get it to work. I will reinstall it over the weekend and post logs.

Thanks!

jwetzel1492 · May 3, 2019, 3:56pm

also if you can turn on the debug logging in the app settings before you run the test, that will make more informative logs.

jwetzel1492 · May 3, 2019, 3:59pm

UPDATE: The auto-refresh period is now configurable for each reliable lock instance. The only file you have to update is:

github.com

joelwetzel/Hubitat-Reliable-Locks/blob/master/ReliableLocksInstance.groovy

/**
 *  Reliable Locks Instance
 *
 *  Copyright 2019 Joel Wetzel
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 */

import groovy.json.*
	
definition(
	parent: "joelwetzel:Reliable Locks",

This file has been truncated. show original

aaiyar · May 3, 2019, 9:19pm

@jwetzel1492

So, when I reinstalled it, it works perfectly when controlled via Hubitat. I'm at work, so I can't tell you whether it updates when the lock is controlled manually. But I will later tonight.

Anyway, here are the logs for my BE469 (called Front Door BE469):

aaiyar · May 4, 2019, 1:28am

@jwetzel1492

Manual unlock/lock are also fine. Here are the logs:

Katraz · May 4, 2019, 6:31pm

When I import this driver I get

No signature of method: Script1.definition() is applicable for argument types: (java.util.LinkedHashMap) values: [[name:Reliable Locks, namespace:joelwetzel, author:Joel Wetzel, ...]]

what am I doing wrong? I am pulling this directly from the git groovy file

vjv · May 4, 2019, 6:53pm

Welcome to HE.

this is an app, probably you are trying to install the app in the driver code of HE. you can try to use the import button and pasting the raw address of the code from github.

Katraz · May 4, 2019, 7:24pm

Ahhh silly me - thank you

Katraz · May 4, 2019, 7:29pm

I got past trying to load it as a driver (silly me) but when I follow the instructions to wrap my lock I get

Error 404

Child app not found for namespace: joelwetzel and name: Reliable Locks Instance

The Page requested could not be found

Guess it's not my day to move from ST to HE

spalexander68 · May 4, 2019, 7:31pm

There are two apps you must install and one driver.

ReliableLocks.groovy and ReliableLocksInstance.groovy as Apps

ReliableLockVirtualDriver.groovy as the driver device.

Then add User App Reliable Locks and voila!

Katraz · May 4, 2019, 7:35pm

Thank you - worked like a champ!

lelynch · October 17, 2019, 2:57am

@jwetzel1492 I've been using this app since you first put it out and it has really helped a lot. I have two Yale locks. One Zigbee and one Z-Wave that both are about 70-80% reliable on responding the first time to a lock or unlock command even though both meshes are pretty strong. I am wondering if it would be possible to add an option to retry the lock/unlock command if it were unsuccessful the first time? A second try in these instances on either is almost 100% successful. I can modify parts of code sometimes when I need to but I'm not a programmer and I know nothing of Groovy. Thanks!

jwetzel1492 · October 17, 2019, 3:22pm

Yes, that's a great idea. I have something similar in related app I made: Lockdown. I can make it an option in this one too. Might take me a week or so to get to it.

lelynch · October 18, 2019, 1:30am

Thank you! I'll look forward to the update when you get time.

basic261 · October 23, 2019, 10:47pm

@jwetzel1492

What does this section do? What is the recommended setting? Also in the Wrapped lock section do you choose the physical lock, the virtual lock or both?

aaiyar · October 23, 2019, 10:59pm

As far as I can tell, it is the wait time (in seconds) before it refreshes the physical lock. I've used the default 6 seconds for several months now.

The physical lock.

basic261 · October 23, 2019, 11:12pm

@aaiyar that's what I kind of thought but then got a little confused on the option to Auto refresh every 30 minutes

aaiyar · October 23, 2019, 11:31pm

The 6 second refresh is done right after sending a command (lock/unlock) to the physical lock.

The 30 minute refresh is a periodic synchronization - in case the physical lock was manually operated, but it took a while for that change to be registered with the controller (Hubitat).

Navat604 · October 23, 2019, 11:31pm

I think the 6 seconds is to refresh the lock 6 seconds after you use reliable lock to lock/unlock your door. The 30 mins is a regular refresh every 30 mins.

basic261 · October 23, 2019, 11:50pm

@aaiyar @Navat604
so let me ask this. If I have some rules set up to lock unlock the door should I use the physical device in the rule or the virtual device in the rule?