Most of our motion lighting has a 60 second delay. On some mode changes when the behavior of the lights change to something else, Hubitat will wait until the inactivity timer reaches the 60 second mark before the new behavior takes hold as it shows as "Already activated".
Is there a setting that allows the new rules of the new mode to be adopted immediately without waiting for any existing inactivity timers to lapse?
I've migrated most of my motion lighting / lighting rules into the new Room Lighting app.
This is happening in multiple rooms, however for this example I'll provide the kitchen. I couldn't find an easy way to keep the kitchen lights on solid for my "Evening" mode, so I've created two entries in Room lighting. One that covers motion lighting for Day / Night and another that covers the solid non-motion lighting for Evening.
If the rules look odd, it's because we run coloured lighting on weekends throughout the entire house. We also have night lighting setup for "follow-me" night lighting.
Just to add, a good example of this would be if a cat is wandering around in a room with motion detectors and that specific mode lacks any logic to enable the lights. The mode changes, and because the motion detectors are still active the room will wait for the 60 second cooldown that started before the mode change before the lighting in the room will activate.
It leads to us asking "Why aren't these lights working in here?" - and the answer is to stay out of the room for 60 seconds for the cooldown to lapse. Once we do that, everything works properly.
I'm not certain that I'm following what you mean by "60 second countdown". Are you talking about the motion sensors resetting to inactive so they can report a new active event? If so, there's nothing you can do about that other than, as you say, "stay out of the room for 60 seconds for the cooldown to lapse", or have some other way to activate those lights.
I have this problem at times in my house, because Lutron motion sensors have the 60 second reset time. One example of how it can bite is if I manually turn off the lights in our bathroom with a wall switch as I leave the room, and my wife comes along 10 seconds later, motion is not going to turn those lights on because there will not be a new motion active event. Worse, there won't be another new event as long as she is in there in range of the sensor. Consequently, I've learned to be cognizant of where she is before I turn the lights off that way, or just leave them on and let the automation turn them off after motion has truly gone inactive.
If this post doesn't fully answer your question, the next thing for you to do is to show a screenshot of the app logs for when you experience this issue.
Are you talking about the motion sensors resetting to inactive so they can report a new active event? If so, there's nothing you can do about that other than, as you say, "stay out of the room for 60 seconds for the cooldown to lapse", or have some other way to activate those lights.
That's it! It was a long shot at best, but I figured I'd try
There may be a way to get around this problem. A Rule Machine rule that is triggered by the mode change could check if motion is active, and if so, turn on the lights.
