Triggers cannot be AND because that would require that both triggers happen simultaneously and that is virtually impossible. It's a common misunderstanding that many of us, incl. myself, have made. Instead, your trigger is that either door changes.
Then, in Actions, you have to use a conditional that if Door A OR Door B is open, then lights go on 100%
If Door A AND Door B are closed, then light goes on at 5%.
Appreciate your reply.
If I understand correct this basically means that I may have to make multiple rules to operate a single device/variable.
For instance I have a variable "DAY" which I want to set if any of my door contacts is opened (but only after 6:00AM) OR if motion is detected in the bathroom (but only if outside illumination >500) OR if illumination gets above 500 (but only if AWAY).
I then need 3 rules to set the variable DAY:
rule1 = trigger: (any) door contact -> open => set variable DAY:= true IF condition= time>6:00AM
rule2 = trigger: motion in bathroom => set variable DAY:= true IF condition= illumination>500
rule3= trigger: illumination>500 => set variable DAY:= true IF condition= mode=away
Is my understanding correct that the use of these 3 rules is the best/only method via the rule machine?
Three rules might be the best option but not the only. You could have each of the events as triggers and then use off statements and the %device% variable determines which device triggered the rule and then apply additional conditions to that.
However it take processing power to calculate all of those if statements.
I don’t have the link handy but there is a video on what they have called the KISS method.
What your missing is a little history. What you are describing is called a restriction. Some apps have restrictions, see for example Simple Automation Rules. You can have a restriction that says something like "Only if mode is X or Y". Rule Machine used to have this type of restriction.
What isn't perhaps obvious about restrictions in general is that they are really hidden conditional actions that run for every activation of that rule. Every time it is triggered, it has to check to see if its restricted or not. There is no magic here, some piece of code has to do the test about is there an applicable mode restriction. So, every rule carried that overhead by allowing restrictions.
A change was made with Rule-4.0 to remove restrictions, and to instead make them explicit instead of hidden. The test can be the same, but only a rule that needs the test pays for it. For example, one can do this Simple Conditional to get 'Only if mode is Day':
IF(NOT Mode is Day) Exit rule
You don't need to create multiple rules to do what you asked about above.
Trigger: door opens (any selected)
IF(--the complex conditional you showed--) THEN
Set Day: true
Set Day: false
Thanks for your replies and the KISS
It seems that I need let go of some learned (probably: bad) habits from WebCore under ST. I actually just installed WebCore under HE -grabbing back to a known environment- but apparently I need to give the rule machine another try now its possibilities/principles got more clear to me.