This morning I woke up and found our dressing room lights still on, so I thought i'd check the log to see what was going on.
From what I can gather is: I have a simple automation app rule running that turns on the dressing room light when motion is detected only is Mode = Awake or Evening and deactivate after 2 minutes of motion becoming inactive. Now at 5:11am in 'awake' mode the motion was triggered and set off the lights to turn on. Now at 5:13, but mode changed to from 'Awake' to 'Morning' and after that mode change the motion became inactive and didn't turn the lights off after 2 minutes.
It seems that it subsequently didn't trigger the lights to go off, I can only assume this should have done or the mode change disabled the automation
dev:9972020-06-26 05:13:07.751 am infoDressing Room Motion is inactive
app:7602020-06-26 05:13:00.345 am infoMode change to Morning
app:7062020-06-26 05:13:00.218 am infoMode set to Morning from Awake
dev:9942020-06-26 05:12:18.735 am infoDressing Room Light 2 was turned on
dev:9932020-06-26 05:12:18.717 am infoDressing Room Light 1 was turned on
dev:9952020-06-26 05:12:18.587 am infoDressing Room Light 3 was turned on
dev:10372020-06-26 05:12:18.379 am infoDressing Room switch was turned on
app:9422020-06-26 05:12:18.295 am infoDressing Room Turn On
dev:9972020-06-26 05:12:18.241 am infoDressing Room Motion is active
Restrictions means the automation won't turn on or off the light if you aren't in that mode. You will need another automation that turns off the light when mode leaves awake and evening.
I've also had this happen but with time rather than modes using rule machine. My kids toilet light is activated with motion and stays on for 4 minutes but if it was on as the times for the rule passed it wouldn't turn off. I've changed to the motion lighting app and it seems to be better.
I wonder if that is why I've never experienced it before as normally I would have done this in motion lighting, I moved some to simple automation as it was quicker.
Haha, I'd like to say it's fancy, but essentially we had a box room upstairs and our main bedroom isn't that big, so instead of cram furniture in there we just have the bed and some bedside tables and we got some fitted wardrobes and cabinets in the box room for our clothes.
It's not that simple. Motion Lighting fully separates the logic for on and off, and by doing so it can effectively deal with the issue of still turning lights off when they are restricted from turning on. This can be accomplished in Simple Automation Rule also -- by using two rules, one for on and one for off.
If it isn't obvious, the problem would become that Simple Automation Rules wouldn't be simple anymore. Adding options for things like separate restrictions for on and off quickly becomes a complex stew, a slippery slope of feature creep. Meanwhile, there is absolutely nothing wrong with having two rules, one of on and one for off. The only reason someone wouldn't want that is the complaint that their list of Apps gets to be longer, that there are more installed apps. So what? The idea is not to have the shortest possible list of installed apps, but the most effective home automation implementation. Rules are free. Use as many as you need to accomplish the desired outcome.
take out the "turn off" from this rule and create a separate rule to turn off when the motion stops. this way regardless of the mode it will turn off the light when the motion stops, but this rule will only turn it on when you're in the specific mode
