Ok, so I'm still struggling with setting up my rule for my door locks... Schlage be469... I want the door to auto lock after 30 seconds whenever the door is opened by a code, or manually unlocked from inside, whether the door opens or not.
I was running a trigger rule on the door contact sensor, but switched over to conditional rule instead due to manual unlock but the door never opening would never trigger the contact.
Here's my rule... as you can see it's all set to true currently since I manually unlocked the door but never opened it. Based on the true action, the lock should wait 30 seconds, and then lock again. But that action never takes place.
Define a triggered rule. The trigger would be if the door is unlocked either by code or physical. If so, and the door is closed, then lock the door after a 30 second delay. Wouldn't want to re-lock if the door was open.
The only think I would add to @spalexander68's rule is a cancel on truth change. That way if the door is opened again within the 30 seconds, it's not trying to relock it while it's open.
If the door is opened manually from inside, does it report back to HE that that has happened? If not, then you're won't be able to trigger of the lock unlocking alone. Instead, you could modify the triggered rule to also trigger off the door being closed. That way, if you unlock the door from the inside and open the door, then close it, it would automatically lock after 30 seconds. In general, I think that would be a much better trigger anyway.
My lock actually does respond to commands (schlage be469), I have two of them about 3 feet apart and both are within 10 feet of my hub. I will be adding the Aeotec repeater in several locations throughout my home to help stabalize my zwave and zwave plus mesh as it can only help. With that being said, the rule that spalexander68 posted does work. However I'm not sure i understand how to setup a cancel on truth change for a triggered rule? I don't see anything in the rule that states cancel on truth change as it does in the lighting rules. Could you provide an example?
I had also setup my auto lock to trigger off the contact sensor, but I ran into an issue where my kids would unlock one door and then unlock the 2nd door and never open and close the door they originally unlocked but rather went out through the 2nd door. Because the trigger of the contact sensor never changed, the door never re-locked and the house was unlocked all day long while I was away. I've changed it to trigger off both for safe measure.
I was going to drum him up a rule with a cancel on truth change. However, I cannot find that option nor does it pop up after entering the 30 seconds delay. What am I missing? I am wondering if contact or lock capabilities not have that as an option?
You can't add that to a triggered rule...my apologies. You can only do that with a simple rule. So, that is what you would want to do...have you conditions be lock unlocked and door closed and only list actions for true with delay 30 seconds w/cancel and lock the lock.
This will only give you 30 seconds to lock the door after you unlock it though. Wouldn't you want more time than that?
Having went through all of this, at first blush, his original rule should have locked his door in 30 seconds. Don't know why it did not. Hence why I asked him if his lock was responding to commands.
The rule is evaluated whenever an event affects its condition. For example, if the door closed as in your condition, that rule would be evaluated. Or in your example, if the door was unlocked, your rule would have been evaluated.
and it was, which is why I was questioning my rule. The logs clearly show the door was unlocked (which was manually done by me), and the rule changed to true, and delayed by 30 seconds... then it went true... but it never locked the door. The triggered rule as you posted works and locks after 30 seconds whether it's manually unlocked or unlocked by a code.
I don't understand why your first post's rule didn't work. It looks like it should have to me. Had you tried taking the delay out and seeing if it works out of curiosity?
Like I said earlier, your rule should have worked as you had it originally in my opinion.
One thing I noticed is that you have Front Door and Reliable Front Door devices in your Rule and Conditions. I am assuming they are the same device and the "real" lock is wrapped in the Reliable Locks app. In your True action, you only have Front Door device. I don't use Reliable Locks, so I don't know if something between the two is causing it not to work.
They are the same devices. I have them both listed as a fail safe if the state of one changes but doesn't report back the state to the other, then the rule would trigger. I've seen where the lock itself changes but the reliable lock has not and vice a versa for some reason.
Ok, so I paused my triggered rule...and recreated the following:
I went to the door, unlocked the lock. I got my pushover that the lock unlocked, and then after about 10 seconds I got a 2nd pushover that the lock was locked. But in fact the lock did NOT lock. Its still unlocked.
