Can someone explain for me how to use Reset reaction in MSR without disturbing other rules.
-
@crille yes i understand but you cant have constraints for Reset Reactions. Only for Reactions.
I’m not friend with MSR at them moment but I know it’s just something I understand wrong... Gaaah drives me nuts!
@matteburk Yes, the Constraints would block the Reaction in Rule 1 to run, thus will Reset Reaction in Rule 1 not run.
-
@toggledbits I think it's becoming apparent that users might interpret Constraints in one of two diametrically opposite meanings. Some might think for example that a TRUE constraint condition will prevent the rule from continuing to run. Others, more correctly in my opinion, will understand that a constraint condition must be TRUE in order for the rule to run.
I wonder if there could not be some clarifying language in the user interface? -
I'll refer to the documentation, and you can tell me if it's clear enough or still needs work: https://reactor.toggledbits.com/docs/Rulesets/
Also, it would be good to have the full rules posted in this thread. The descriptions of what the rules look like just leave too much room for interpretation. Let's see what's actually being done.
-
I'll refer to the documentation, and you can tell me if it's clear enough or still needs work: https://reactor.toggledbits.com/docs/Rulesets/
Also, it would be good to have the full rules posted in this thread. The descriptions of what the rules look like just leave too much room for interpretation. Let's see what's actually being done.
-
@matteburk I think you need to put AND in top level for the triggers for Rule 1.
-
@matteburk I think you need to put AND in top level for the triggers for Rule 1.
-
OK, that's a start, I guess, although they are barely readable. Maybe we'll need to go back to some kind of Logic Summary-like thing.
Now, what are these supposed to do, and what is the problem you are having with them?
-
@matteburk I would still put condition "natt"/"dag" and "kväll" in Constraints as it's not a trigger, rather a condition and would prevent Reaction/Reset Reaction to run.
Edit: Clarification for future readers. Forcing the Constraints condition to go FALSE prevents the SET/Reset Reaction to run.
-
@matteburk I would still put condition "natt"/"dag" and "kväll" in Constraints as it's not a trigger, rather a condition and would prevent Reaction/Reset Reaction to run.
Edit: Clarification for future readers. Forcing the Constraints condition to go FALSE prevents the SET/Reset Reaction to run.
@crille said in Can someone explain for me how to use Reset reaction in MSR without disturbing other rules.:
rather a condition and would prevent Reaction/Reset Reaction to run.
No, that's not how Constraints work. Constraints do not prevent Reset reactions.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@crille said in Can someone explain for me how to use Reset reaction in MSR without disturbing other rules.:
rather a condition and would prevent Reaction/Reset Reaction to run.
No, that's not how Constraints work. Constraints do not prevent Reset reactions.
-
Rule 1 is 1 motion sensor I Master bedroom and 2 motion sensors in bathroom that if any is true (delayed reset 120s)and Natt mode is true master bedroom light and bathroom light is turn on. Reset reaction turn off
Rule 2 If any of the 2 motion sensors in bathroom is true(delayed reset 600s) and dag or kväll mode is true bathroom light is turned on . Reset reaction turn off -
@toggledbits No, but it will prevent the Reaction to run, thus the Reset Reaction?
@crille said in Can someone explain for me how to use Reset reaction in MSR without disturbing other rules.:
o, but it will prevent the Reaction to run, thus the Reset Reaction?
THAT is true, so we need to be careful how we phrase it, because your other statement is incorrect and misleading, and would give other readers the wrong idea. But you are correct in the last: if the SET reaction does not run, neither can the RESET, because RESET will only follow SET (once the basic state of the rules has been established).
-
Rule 1 is 1 motion sensor I Master bedroom and 2 motion sensors in bathroom that if any is true (delayed reset 120s)and Natt mode is true master bedroom light and bathroom light is turn on. Reset reaction turn off
Rule 2 If any of the 2 motion sensors in bathroom is true(delayed reset 600s) and dag or kväll mode is true bathroom light is turned on . Reset reaction turn off@matteburk And the problem?
-
@matteburk I would still put condition "natt"/"dag" and "kväll" in Constraints as it's not a trigger, rather a condition and would prevent Reaction/Reset Reaction to run.
Edit: Clarification for future readers. Forcing the Constraints condition to go FALSE prevents the SET/Reset Reaction to run.
-
I have a strong suspicion that both of your rules are running simultaneously because they are reacting to very (overly?) similar conditions. That is, when the light is increasing from Off to 100%, it passes 20% and may thereby trigger Rule 1.
You could include a Restriction on that Condition such that the dimming level "Must be sustained for at least 4 seconds" or so. -
I have a strong suspicion that both of your rules are running simultaneously because they are reacting to very (overly?) similar conditions. That is, when the light is increasing from Off to 100%, it passes 20% and may thereby trigger Rule 1.
You could include a Restriction on that Condition such that the dimming level "Must be sustained for at least 4 seconds" or so.@librasun said in Can someone explain for me how to use Reset reaction in MSR without disturbing other rules.:
when the light is increasing from Off to 100%, it passes 20% and may thereby trigger Rule 1
Yeah, but Rule 1 doesn't say that. Rule one seems to be triggered exclusively by the motion sensors, and as posted (screen shot) potentially by a change in mode if a motion sensor is active at the same time (moving the mode check to Constraints solves this).
I would not expect the RESET reaction to run in this case, but I'm also not watching the state of these rules. This might a case where putting both of these rules into the Scope and watching their state interact with each other would be educational. If anything is triggering rule 1, that would be obvious there (also looking just in the status view for the rule at a changing timestamp). But I don't see why the reset would run for rule 1, and I'm off to do some code review and see if I can back into reason...
