"AND" Rule Works One Way but Not the Other?

[video321]

I am creating some semi-dynamic rules for alarm notification and noticed something that didn't make sense to me.
What I am doing is creating a single email for each door location and then grouping windows and glass breaks since there aren't enough spots. So this is what I did:

this did NOT work:

WHENEVER (Area 1) arm state becomes armed
AND Front Door is not secure
THEN turn output xx on for xx seconds

WHENEVER output xx is turned off
AND the burglar alarm in (Area 1) is active
THEN send email message


then I switched the first part around and it DID work:

WHENEVER front door becomes not secure
AND (Area 1) arm state = armed
THEN turn output xx on for xx seconds


So, two things....why does it work one way and not the other and is there a better way to accomplish my goal?

 

[apostolakisl]

The first line is the "trigger". Any additional conditions (and's) must also be true for the "then" to execute, but the "and's" don't trigger the program.

So, in the first rule, the program triggered when the system was armed. If the front door was secure, the program ended.

In the second program, the program triggers when the front door becomes un-secure, and if the alarm is armed, it goes on to the "then".

 

[video321]

Thanks, Lou.
I knew it was something simple, but couldn't wrap my head around it. That makes perfect sense.