@toggledbits I don't care what that @therealdb says about you 
I never doubted you for a second.
Got home from doggo playtime and walked thru the MBR and it didn't even dawn on me until 10' later that the lights had gone on with the OLD rule, not the workarounds.
Ran to the front door (ok, slow walked...) and opened the door and 90 seconds later the porch lights dropped back to "ambiance" level from "don't fall on your face" level.
Well done, sir! Stick the proverbial fork in this one.
@therealdb I saw the rules I saw having the issues go by along with many others. Most of my noted impacted rules are after hours so we'll see what happens this evening. Your response is encouraging!
@toggledbits this did not do the trick but I grabbed logs (didn't even have a chance to review them, sorry) and put them in the 26016 folder.
The rules in question:
rule-grpvl9oypg
rule-lnict0lq
Real world names:
Porch lights: brighten for guests
MBR Lamp ON/OFF (via Motion and ESP)
Note: I apparently did not complete the download from MSR of reactor.log so I reran the tests and pulled it again (hence why it is newer than the included reactor.log1.
It's been a day... week...
I copy-pasted the ruleID... restarted MSR. I know this worked previously, I had older rule-specific logs in my logs directory that I've since deleted and in fairness to me, I'd just commented out the prior entry from logging.yaml and reused it lol
What obvious thing am I missing here?
@toggledbits Is this not correct?
"Rule#rule-lnict0lq":
level: 5
streams:
- type: file # filename is derived from rule ID
keep: 2
level: 999
"Rule#rule-grpvl9oypg":
level: 5
streams:
- type: file # filename is derived from rule ID
keep: 2
level: 999
recycle: true# recycle: true
(It is in line...)
@toggledbits logging enabled for both rules.
The deep rules are simply presence rules. When I isolate each group into it's own rule and change nothing else, they work fine.
@toggledbits That's why I uploaded the full reactor.log to your Dropbox.
These are two different rules. Here they are in full:
Porch lights (logs provided last night)
Bedroom lamp (no logs yet)
I'll try to grab logs on the second one today and put in the same Dropbox folder.
I have some rules that have multiple Groups as the Set Reaction based on different scenarios. In one instance, it's a bedroom light that has three possible "outcomes": morning, evening, and rainstormers. If I break out the ruleset into three unique rulesets each works fine.
Here's another instance that I caught tonight: porch lights that are supposed to react differently - but this time it's the Reset Reaction that's being ignored:
Here are the log entries directly tied to this but I will upload the entire log to you @toggledbits
[latest-26120]2026-05-02T01:17:35.641Z <Rule:INFO> Porch lights: brighten for guests (rule-grpvl9oypg in Outdoor Lighting, Nightly) evaluated; rule state transition from SET to 'RESET'
[latest-26120]2026-05-02T01:17:35.644Z <Engine:INFO> Enqueueing "Porch lights: brighten for guests<RESET>" (rule-grpvl9oypg:R)
[latest-26120]2026-05-02T01:17:35.655Z <Engine:NOTICE> Starting reaction Porch lights: brighten for guests<RESET> (rule-grpvl9oypg:R)
[latest-26120]2026-05-02T01:17:35.655Z <Engine:INFO> Porch lights: brighten for guests<RESET> all actions completed.
The Set Reaction for the bedroom light looks like this:
I've not had a chance to re-enable that ruleset and grab logs from it yet.
@toggledbits I still have the ruleset, just disabled. Easy enough to disable the temporary ones and re-enable this one and try to trigger it. (I had a smart moment!)
I'll try to find a few minutes to grab logs. I gave a quick look and saw nothing screaming.
@toggledbits how does this pertain to rulesets that have Groups in Set Reaction for different "scenarios", if you will.
Example:
I'm asking because this ruleset stopped working with 26116 and I'm so strapped on personal time atm that I just broke it out into three sep rulesets and each works correctly.
I have used the functionality of moving Reactions from the Global Reactions list to the Rulesets lists. I was editing some Reactions this morning and noticed the following:
Selecting a Reaction and copying "to current rule set" results in the Reaction appearing in the current rule set as expected.
However, upon editing and saving the Reaction disappears from the Rule Set list and moves to the Global Reaction list. One must manually move it back to the Rule Set list.
Running the latest version, 26011.
@retireditguy here's my xmas which is tricky because it moves year-to-year based on starting the day after Thanksgiving:
And here's my Thanksgiving which is tricky because it moves year-to-year, being based on the "fourth Thursday of November":
And here's a more "traditional" one for a set date:
@tamorgen just spitballing here but could you add a delay = 5 and then a second step in your Set Reaction that does a "changes from pending > disarmed"? Shrink down the delay time if the "pending" period is shorter.
Again - just a first thought.
@CatmanV2 in my (recent) experience, as soon as a ruleset or reaction attempts to run that's missing something it will alert and then mark it in the list of rulesets/reactions.
Then you go thru and correct it.
@Pabla AH, see, I pull my lx data in from the weather station array in my backyard. Hyper-local data. Covers the entire house, no matter the room.
@Crille this is a credible use case - I call it "Rainstormers" in my rules and it turns on a select couple of lights (not everything like Evening time) throughout the house.
@Pabla I put a Condition on my rule:
This prevents the flapping you're seeing. Essentially this says "ok, it's <=35lx - please wait :90 to ensure it persists."
I use it for my temperatures and light levels in my Shared Rules ("It's too dark", It's too cold", etc.) In some cases the hold time is 300 seconds.
@CatmanV2 my bad - I should have called you out for not following posting etiquette. I just recognized a scenario similar to one I run.
Here's an example of what I do for my garage overhead light:
Expanding the yellow outlined three dotted box....
Then my SET/RESET are
All told, what happens is "If the laundry room door out to the garage is opened, and the garage door is closed during the day OR it's night time/really dark outside turn on the light and leave it on for :90 after the laundry room door closes then turn it back off".
Doing it the way you're doing it, it's gonna turn off after that 180 second delay no matter what happens.
Doing it the way I'm doing it, if the laundry room door is left open... or is reopened... the light stays on. :90 is enough time to close that door and get oneself and doggo into the Jeep if leaving. If returning, :90 isn't too long to have the light on after one goes into the house.
This is where @toggledbits says "wow, that's over-complicated --- try this instead" because he usually does and is usually right LOL. (I tend to overthink/overcomplicate my automations....)
@CatmanV2 Off the top of my head, you'd want to set the Follow to 180 (three minutes).
I'd create an OR Group that contains both doors. Set the above at the Group level... in my mind that means " of either/any/both" doors, the last one closed starts the three minute timer. If any are reopened before it runs out, it restarts upon re-closure.
