So I have set up a rule to lock doors when away based on presence un RM 4.0. It looks to be logging correctly, however, the lock isn't actually locking. Yes, I can lock the lock from dashboard or devices. Any thoughts?
Does it work if you create it as a RM3 rule?
No. I had it as a 3.0 rule and it could never get it to work. I paused that rule and wrote a new one when RM 4.0 came out. I did finally get modes to change pretty reliably (at least when I move the geofence location in the app it updates properly). Here is the 3.0 rule
also interesting to note, with RM 3.0 is the status changed from False to true when I removed the presences, but the lock didn't actually , well, lock .
See what happens when you hit Run Actions on the rule page.
Nothing Happens. I had tried that with the 4.0 rule, but not the 3.0. Just tried in the 3.0 rule log attached.
Do me a favor, and just do the 4.0 rule, and isolate the logs to just the rule. Hit Run Actions.
Ok. Just on a hunch I went and cycled the lock with the key a few times. That seems to have kick-started it. But now If it's unlocked, whether we are both at home or not it will lock. I guess its the safer option, now I'm kind of curious whats pushing it. Logs first, then the 4.0 rule next.
1 Like
A couple of suggestions: (1) Update to the latest release. (2) Open the device page for the lock, and see if it works from that page. (3) Delete that rule and recreate it. There is no reason that the rule should not work, and I can verify that Rule 4.0 does lock locks. Most likely case is that there is an issue with the lock. Is this a Z-Wave or a Zigbee lock?
1 Like
Since you asked about "away" and in 2 other posts you are working on getting that set correctly, I would recommend not doing something else based on Presence but instead tying this into your away mode.
2 Likes
(1) I'm currently running Hubitat Elevation® Platform Version 2.1.2.117, I don't show an update available. (2) Yes, I am able to operate it both ways from the device page. (3) I deleted the old RM 4.0 rule and recreated it. I found another rule that seems to have been causing it re-lock almost immediately. I paused that, and I THINK I have it figured out. Rule and logs attached.
That was actually my next thought, to convert this to a mode driven rule. But I also want to make sure I'm going down the right path with this one.
To clarify, I had originally started working on the presence based rule when i couldn't get the Away mode working right. With yours and @bravenel's help I was able to rewrite and clean up about 5 rules and retire about 5 more last night. So far everything seems to be working as intended. As long as I can remember what I did, I should be in a good position to add future devices and rules when the time comes. I have to say I like RM 4.0 much better. I have been able to get my mind wrapped around it a lot easier.
