Lights not turning off

I have a basic rule with this logic
When Time of Day is 8:00 PM ...
Dim LR Ceiling Lights Dimmer, Stair Dimmer to 40
Dim Kitchen Island Lights, DR Track Lights Dimmer to 10
Dim Deck Lights to 25
Wait until Motion Sensor 1 (Kitchen) motion stops and stays inactive for 15 minutes, then ...
Turn off Kitchen Sink Lights, Kitchen Work Lights Switch

The issue is that the last line never happens. Even after an hour with no motion in the kitchen area. What am I doing wrong? Is there a better way to do this? I've tried set it up as a separate rule but that doesn't seem to work either. The motion sensor is Third Reality, the switches are GE.

Based on the details provided, the rule should work as expected, however, if it's not, we would need additional details to further assist. Please check out the following document for ideas on how to troubleshoot misbehaving apps and the level of details you might want to provide so others can help:

1 Like

Thanks, I'll check that out.

Is the motion sensor ALWAYS active at 8:00 PM? I am thinking a motion sensor has to be active in order for it to "stop and stay inactive". So, if it is not active when triggered, the wait for never happens? :man_shrugging:

1 Like

Generally yes, but that's a good point. I'll check the logs that I'm learning to use and understand.

Thanks.

So I've got the lights working the way I want them to. Both comments were very helpful. I've learned how useful the logs can be as well as the event histories. I discovered two things that seem to be affecting my app. One, the motion sensors field included a ceiling fan that runs 24x7. The log indicated that motion was never inactive long enough to trigger the lights. So I moved the sensor. Second, the app that turns on the lights was using restricted hours. Those hours overlapped with the timing of the app that dims and turns the lights off. Once I edited the hours to stop the overlap everything has been working fine.

Thanks for the help.

1 Like

So true, most of of the issues that come up can be figured out via logs/event history. The recently added ability to filter the logs view by devices and/or apps really makes them easy to use.

I feel you. In my case, the % of my problems that turn out to be ones I caused is an embarrassment of riches. See my mea culpa post here. :wink:

2 Likes

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.