[Solved] Rulesets with multiple groups in Set Reaction not working post-26116
-
Enable logging at level 5 just for that rule. Anything else is going to generate too much information/distraction.
Edit: I'm not finding any issues yet in focused testing on this. I obvious don't know what the dependent rules do in your conditions (what conditions they have), but basic functional tests of groups with true and false constraints are working fine for me.
Since you have delays in your groups (or can easily add them), that's one way to slow things down so you can watch the "Running Reactions" status widget, which also may give us a clue why it's not working the way you expect.
@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...)
-
Looks OK. Check your IDs if you are not getting logs. The files will be named
Logger#Rule#<ruleid>.log. -
Looks OK. Check your IDs if you are not getting logs. The files will be named
Logger#Rule#<ruleid>.log.
I copy-pasted the ruleID... restarted MSR. I know this worked previously, I had older rule-specific logs in my
logsdirectory 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?
-
At this point I would need to see the entire config file. You could also run it through yamllint.com to make sure it's all OK (and remember, no tabs -- always spaces for indenting -- that's a common trap with some editors that "help" you during copy/paste).
Build 26127 has a change that may be responsible for the misbehavior, as well as additional logging in case that's not the problem. Please upgrade to that when able and see how it behaves.
-
At this point I would need to see the entire config file. You could also run it through yamllint.com to make sure it's all OK (and remember, no tabs -- always spaces for indenting -- that's a common trap with some editors that "help" you during copy/paste).
Build 26127 has a change that may be responsible for the misbehavior, as well as additional logging in case that's not the problem. Please upgrade to that when able and see how it behaves.
@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-lnict0lqReal 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.logso I reran the tests and pulled it again (hence why it is newer than the includedreactor.log1.It's been a day... week...
-
I dropped you a DM. Whatever folder you are uploading to has expired and I no longer have access to it.
That may be moot at this point, since info from @therealdb is likely leading to the same conclusion. I have a fix build coming soon that I'm at least 50% sure will address your problem as well as his.
-
it fixed a couple for me, so definitely working! thanks!
PS: is it safe to delete the json files in the folder?
--
On a mission to automate everything. -
it fixed a couple for me, so definitely working! thanks!
PS: is it safe to delete the json files in the folder?
@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!
-
it fixed a couple for me, so definitely working! thanks!
PS: is it safe to delete the json files in the folder?
@therealdb said in Rulesets with multiple groups in Set Reaction not working post-26116:
PS: is it safe to delete the json files in the folder?
Which folder?
-
@toggledbits the one with the rules.
--
On a mission to automate everything. -
@toggledbits the one with the rules.
@therealdb Yes!
-
@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 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.
-
That's great to hear! Sorry for the disruption! Onward!
