[SOLVED] Question regarding "in" vs "contains" vs contents of the string
-
inmatches the listed (comma-separated) words exactly.partlycloudyshould not matchcloudyby itself. My testing bears this out. You are not showing the actual condition state, which would be preferable here (i.e. open the Rule's detail view in the Rules list). If you've been editing the rule, you may need to reset it to flush old state. -
inmatches the listed (comma-separated) words exactly.partlycloudyshould not matchcloudyby itself. My testing bears this out. You are not showing the actual condition state, which would be preferable here (i.e. open the Rule's detail view in the Rules list). If you've been editing the rule, you may need to reset it to flush old state.@toggledbits I just did a restart of Reactor and it's acting as expected (described by you).
In MSR's defense, I have been doing a LOT of rule optimization over the weekend. I can be quite the hack over the months and years some of these rules have been around lol
Closing this as likely a cache issue.
-
Reactor tries to be conservative about state when you edit a rule. That's to avoid whipping devices around every time you hit "Save". If you've been editing a rule and it stops behaving consistent with its intent, try the Reset Rule button first... it will wipe the entire state of the rule and force a full re-evaluation. Faster and less dramatic than restarting Reactor entirely.
-
Reactor tries to be conservative about state when you edit a rule. That's to avoid whipping devices around every time you hit "Save". If you've been editing a rule and it stops behaving consistent with its intent, try the Reset Rule button first... it will wipe the entire state of the rule and force a full re-evaluation. Faster and less dramatic than restarting Reactor entirely.
@toggledbits TIL... thank you!












