@toggledbits Damn you lol I'd just updated Brave a couple hours ago, then sat back lying in wait.
I just now went to test it and it worked normally, I was logged out with the login screen visible. I thought "huh - musta been a Brave issue, well it's fixed now" - and then I saw both this post and the version change.
Thank you, sir, as always!
@toggledbits I will the next time it times out. It's annoying but not debilitating so I deprioritized troubleshooting for other things. Dealing with a lot of work-related browser issues and this finally added to the pile 
Noticing since 170 that the lock screen doesn't switch to the logon prompt but, rather, stays on the active UI until such time as you go to click something within it. Then it jumps to the login screen.
Brave browser
Brave 1.92.139 (Official Build) (arm64)
Chromium: 150.0.7871.114
@toggledbits I'll say it aloud: I've never noticed that button LOL
@toggledbits I checked, rechecked, RErechecked and couldn't find any issue with that YAML.
That being said, I completely removed the extra rule logging I had added and restarted. Brought down the new image and everything is fine.
So... my question NOW is: why did it run fine until this build? That logging has been there for several weeks.
@toggledbits Repulled, same thing happened: unreachable.
2026-05-31T19:33:04.533976919Z at wrapModuleLoad (node:internal/modules/cjs/loader:255:19)
2026-05-31T19:33:04.533978974Z at Module.require (node:internal/modules/cjs/loader:1600:12)
2026-05-31T19:33:04.533980967Z at require (node:internal/modules/helpers:153:16)
2026-05-31T19:33:04.533983008Z
2026-05-31T19:33:04.533984917Z Node.js v24.16.0
2026-05-31T19:33:56.035775922Z Reactor latest-26150-7b86db04 app 26150 configuration from /var/reactor/config
2026-05-31T19:33:56.053129729Z NODE_PATH /opt/reactor:/opt/reactor/node_modules
2026-05-31T19:33:56.054371749Z Failed to parse /var/reactor/config/logging.yaml YAMLException: bad indentation of a mapping entry in "/var/reactor/config/logging.yaml" (56:34)
2026-05-31T19:33:56.054391711Z
2026-05-31T19:33:56.054396228Z 53 | - type: file # filename is derived from rule ID
2026-05-31T19:33:56.054399741Z 54 | keep: 2
2026-05-31T19:33:56.054402822Z 55 | level: 999
2026-05-31T19:33:56.054405736Z 56 | recycle: true# recycle: true
2026-05-31T19:33:56.054408789Z ---------------------------------------^
2026-05-31T19:33:56.054456413Z At about line 55; near
2026-05-31T19:33:56.054461049Z > level: 5
2026-05-31T19:33:56.054464372Z > streams:
2026-05-31T19:33:56.054509289Z > - type: file # filename is derived from rule ID
2026-05-31T19:33:56.054513314Z > keep: 2
2026-05-31T19:33:56.054515586Z > level: 999
2026-05-31T19:33:56.054517599Z > recycle: true# recycle: true
2026-05-31T19:33:56.054478049Z Use https://yamlvalidator.com/ and correct all indicated errors.
2026-05-31T19:33:56.054522741Z failed to read configuration file /var/reactor/config/logging.yaml; attemping last-known-good
2026-05-31T19:33:56.054619109Z unable to load configuration data for logging
2026-05-31T19:33:56.056778406Z /opt/reactor/server/lib/Logger.js:429
2026-05-31T19:33:56.056793267Z const _0x98a8e2 = a22_0xf250f4, _0x36af7e = log_config['getConfig'](_0x98a8e2(0x14d), _0x98a8e2(0xfd), {});
2026-05-31T19:33:56.056795940Z ^
2026-05-31T19:33:56.056798247Z
2026-05-31T19:33:56.056800114Z TypeError: Cannot read properties of undefined (reading 'getConfig')
2026-05-31T19:33:56.056801991Z at Logger.getLogger (/opt/reactor/server/lib/Logger.js:429:63)
2026-05-31T19:33:56.056803906Z at Logger.getDefaultLogger (/opt/reactor/server/lib/Logger.js:460:40)
2026-05-31T19:33:56.056805752Z at Object.<anonymous> (/opt/reactor/server/lib/Logger.js:761:619)
2026-05-31T19:33:56.056807789Z at Module._compile (node:internal/modules/cjs/loader:1854:14)
2026-05-31T19:33:56.056809659Z at Object..js (node:internal/modules/cjs/loader:1985:10)
2026-05-31T19:33:56.056811482Z at Module.load (node:internal/modules/cjs/loader:1577:32)
2026-05-31T19:33:56.056813567Z at Module._load (node:internal/modules/cjs/loader:1379:12)
2026-05-31T19:33:56.056815388Z at wrapModuleLoad (node:internal/modules/cjs/loader:255:19)
2026-05-31T19:33:56.056817221Z at Module.require (node:internal/modules/cjs/loader:1600:12)
2026-05-31T19:33:56.056819018Z at require (node:internal/modules/helpers:153:16)
2026-05-31T19:33:56.056820871Z
2026-05-31T19:33:56.056822616Z Node.js v24.16.0
This is what the container logs show.
@toggledbits if I have time here I'll try to pull the image again and capture logging.
Following up here, did a backup restore of my Portainer VM from 05/29 (most recent) and MSR is back on 26143.
@toggledbits I pulled the image (well, Watchtower did) and within minutes the whole system went offline.
The log looks like it ends with 26143.
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mkahsmgf/26qq82mw-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lqyfljfi/22f8on0t-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lsb61rw8/24oenqi2-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/rule-lrh58he0:S-1c00gfib-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1c00dylr-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1nam9w5u-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miuh2qqi/22ls4lql-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1vj8sdfc-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1qanz01x-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/24lq19p6-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mk0o8iox/23oy468y-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miscg2h3/rule-miscg2h3:S-22gmbq1c-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrfjke/238p0old-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-m7ccsso5/re-m7ccsso5-1r0myjxa-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/19nl9wq2-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3xk9t-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3vv5m-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/re-ln7j2nqp-22mx9lzd-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/22mx87c8-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-licneppy/1mzwe7ht-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ml3194ih/25jqt1j4-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrg7kf/227hshak-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13ua1p95-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13uagam7-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x4cbv-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x2fyl-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-lscjrws1/238p5c22-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lbwr0jvq/1xkczf03-cons
[latest-26143]2026-05-31T15:23:44.547Z <Structure:NOTICE> Structure Structure#1 stopped
[latest-26143]2026-05-31T15:23:44.547Z <app:NOTICE> Closing APIs...
[latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: closing...
[latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: disconnecting from "192.168.1.23#82" (1001 service closing)
[latest-26143]2026-05-31T15:23:44.548Z <httpapi:NOTICE> HTTP API closing...
[latest-26143]2026-05-31T15:23:44.549Z <wsapi:NOTICE> wsapi: server closed
[latest-26143]2026-05-31T15:23:44.549Z <httpapi:INFO> HTTP server closed.
[latest-26143]2026-05-31T15:23:44.549Z <app:NOTICE> Stopping timers...
[latest-26143]2026-05-31T15:23:44.551Z <app:null> Shutdown complete, process ID 1
[latest-26143]2026-05-31T15:23:44.551Z <app:null> Closing logs...
[latest-26143]2026-05-31T15:23:44.551Z <default:null> Closing log
I can SSH to the VM. Alas, I do not have the previous image for 26143 as I'm a little too quick sometimes on housekeeping.
@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.
