Global Moderators group | Smart Home

toggledbits

Reactor buld 26137

Rules: fix an error where a Variable Value condition in a constraint may not be reevaluated correctly when the variable changes.
Rules UI: if a Rule State condition uses the changes operator with terminal values, make sure those are shown on the detail card.
Rule Editor: when a new local variable/expression is added to the rule currently being edited, make sure all expression selectors in any Variable Value conditions shown are updated so that the new variable can be selected immediately (a bug was causing some to be missed).
HassController: Bless HA to 2026.5.2

therealdb

@gwp1 I never had any doubt about @toggledbits

toggledbits

That's great to hear! Sorry for the disruption! Onward!

toggledbits

@therealdb Yes!

therealdb

@toggledbits the one with the rules.

toggledbits

@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?

therealdb

it fixed a couple for me, so definitely working! thanks!

PS: is it safe to delete the json files in the folder?

toggledbits

Reactor build 26130

Reactions and Reactions UI: fix a long-standing issue where imported/cloned Group and While actions were not given unique IDs by the UI. Until 26116, this bug lurked in the shadows because IDs on actions in Reactions didn't matter at all, so the duplication went unnoticed and was actually harmless. But changes in 26116 to improve predicate response and display made these IDs important for Rule-based Reactions. IDs tend to change when Rule-based Reactions are edited, but long-standing objects that aren't often touched could be left with duplicate IDs embedded. In 26116, this duplication would cause inconsistent and incorrect evaluation of group/while predicates (because two different predicates sharing the same ID would share the same status/result). This build fixes the situation in two ways. First, existing Rules are fixed by deep-scanning when loaded (i.e. at startup), and any conditions or actions having duplicate IDs are given new, unique IDs. Second, fixes have been made to the Reaction Editor to prevent duplication of IDs when an action is cloned or a Reaction is imported. The former fix should ensure that your existing rules are corrected with no further intervention on your part. The latter fix addresses the original editing (copy and import) bugs that gave rise to the problem in the first place. Note that IDs are only required to be unique within the context of a Rule or Reaction; they do not need to be globally unique. If you are the type of person who likes to "deep dive" your storage data and you happen to find duplicate IDs in different Rules/Reactions, that's OK; it's only a problem if an ID is used in duplicate within a single Rule or Reaction. If you get an alert in the Status page that rules were modified by the new startup scan, please delete the alert and restart Reactor. The alert should not return (i.e. the rule is fixed). If the alert returns across more than two restarts, let me know in the Smarthome Community.
HassController: Bless HA to 2026.5.1

toggledbits

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.

Global Moderators

Posts

Reactor buld 26137

Reactor build 26130

Member List