Auto Relock of Kwikset 912 That was Manually Unlocked

#1

1) Give a description of the problem
Won’t send lock command to a Kwikset 912 that was manually unlocked

2) What is the expected behavior?
Sending the lock command regardless of if SmartThings reports locked or unlocked

3) What is happening/not happening?
Lock will re-lock if unlocked via code or via SmartThings app. It will not re-lock if I have manually unlocked it.

**4) Post a Green Snapshot of the piston![image|45x37]

download
download.png1178×531 86.2 KB

Hi All,

New to Webcore. I’m trying to figure out a way to send an auto-lock signal to my garage entry (from garage to house). I have everything working EXCEPT that the lock is a Kwikset 912 and if you manually unlock it Smartthings does not realize it is unlocked. Because of this it seems that Webcore won’t send a lock command. I know it can be done because another SmartApp I have installed will do it.

Anyway, is there a way to get Webcore to ignore the lock status and send a lock command regardless of the lock state?

Thanks.

#2

Two things you’ll want to do on this one:

  1. When editing your piston, click on settings at the top, then disable command optimization. With command optimization enabled, webCoRE will not send redundant commands (tell lights that are on to turn on, or locks that are already locked to lock).

  2. Change your condition on contact sensor 3 to “is closed”.

It’d work the way it’s written if there wasn’t a wait command in the body of your piston. But your wait 5 minute command sets a wake-up timer for your piston 5 minutes in the future. When that timer expires, your piston executes again from the top. Since your contact sensor 3 changed 5 minutes ago, it will evaluate as False for “changes to closed”. When your statement evaluates false, your piston will cancel any pending tasks it has going… including anything written after your “wait 5 minutes” command.

#3

Thanks. I turned off optimization but did not make the other change and it is functioning correctly now.

I appreciate the tip.

#4

It really shouldn’t. I’d double check the logs and make sure it’s doing what you want it to.

Anyway, if it acts up in the future you’ll know what to change.

#5

It is definitely working as it should. I’ll keep an eye on it though.