I thought all Conditions would go under Constraints.
A trigger is a trigger.
I’ve just added this one.
The trigger is 40 mins before sunset and it has various Constraints (Conditions) that should all be met before the Reaction (Action) is run to turn on the lamps.
Triggers cause action. Constraints prevent the action, if necessary. So in MSR, trigger → constraint → action. If there are no constraints, the SET reaction happens any time the trigger conditions are met (i.e. state goes from false to true for that group). The RESET reaction happens when the trigger conditions are not met (state goes from true to false). The reactions only run when the state changes, so a persistent true or false does not cause action.
Example with constraints: motions sensor in trigger that turns on a light. You only want that to happen between sunset and sunrise, so you add the “Sunset/Sunrise” condition as a constraint. While you are learning to use MSR, I recommend you not use constraints.
the trigger at 7.30 and the trigger curtain closed both have to be true for the reaction to fire, unless you set the “or” for the group. So if at 7.30 the curtain is open the group remains false and the curtain will not open.
This is not the forum for MSR discussions, gents. I’m about to lock this thread. Take it where it belongs, please (see the Community button in the left nav of the bug tracker if you don’t know).