I have a C-7, running v2.4.4.135 . I am using a Motion Sensor from Third Reality, model 3RMS16BZ, and using the "Generic Motion Sensor (no temp)" driver from Hubitat. Log files and copy of the rule are included.
I have a basic Motion Lighting Rule setup for my office so that when I enter the office, it turns on two lights (Office and Office Hutch). I have set up the rule to use a 180 minute delay before I want the lights turned off, even if no motion is detected. The Motion Sensor is aimed at the doorway to my office.
The lights are triggered by the Rule (as can be seen in the log), but the 180 minute delay appears to be ignored (even though it appears in the log). 1 minute after the lights come on, they get turned off, as you can see in the log. I only have that one "don't turn off light" condition in the rule (I read somewhere that multiple conditions cause all to be ignored, so I removed the other ones). I also have tried the "Don't turn off if on", the time of day exclusion, and the mode exclusions. No matter which I choose, one minute after the lights come on, they get turned off.
I saw a suggestion of adding a 2nd Motion Sensor aimed at me while I'm at the desk, but I also could be at a guest chair. I don't want to have to add more motion sensor(s) unless I have to.
I didn't see an example of this situation in the forum posts, so I'm hoping someone may have some ideas about how to solve this?
From a quick look at the app, I'm not sure it's equipped to handle delays over an hour. Have you tried a delay of 59 minutes or less to see if that works as you expect?
I’ll try a delay if 58 minutes and report back my results.
If that does work, that will help.
Doesn’t explain why either the “time of day” or “don’t turn off light if on” constraints don’t work, but I’ll be happy it I only have to wave my hand up in the air once an hour!
Your logs do not show the ML app turning off the lights - the "Turning off lights" log line. That was the basis of my question. Are there any other apps that could be controlling the lights? Here are logs that show the ML app turning off the lights.
You could just use a Simple Automation rule if you only want the lights turned on. If I remember correctly, you can choose a specific time to turn them off if desired. This might fit your needs, and SA rules have less overhead, meaning that they fire quicker than ML rules. Or you could add a mmwave sensor to your office. Then you won’t have to move for it to know you are there.
Thanks for all the input, I sincerely appreciate it.
I tried a delay of 58 and 59 minutes, same behavior. I tried many variations of Motion Lighting parameters and never got it to work.
I can't find any other apps manipulating the "Office Light" device.
However, I did disable the existing Office Motion app, and set up a Simple Automation Rule, and that worked fine. It detects me entering my office and leaves the light on all the time, which is my desired behavior. I turn the lights off when I exit the office, so all is good.
I would really like to understand why the Motion Lighting solutions didn't work. I thought maybe I had an old version of that app/code, but it appears I don't.
So all is good, except I don't like unsolved mystery's. It looks like I will have to accept this one.
Again, thanks for all the help and thinking that was applied to this.
Normally 'Dim:Office Light to 95' would turn the light on and dim it to 95. It appears that you also have the same light checked for switches as well effectively giving it two on commands (though I have been known to talk complete so could be wrong!)
so could be wrong!)
