NIGHT vs. NIGHT DELAY Programming

[sjht]

I'm using NIGHT DELAY when we have a family member out late at night and want to arm the system, but allowing a delay when the family member returns and opens an entry/exit zone. Now, I was writing some automation code to handle things a bit differently if this happens (lighting, etc.). Was suprised that NIGHT DELAY will also run any automation that is for just NIGHT (normal, non-delay). Is this by design? Going to do some checking, but does it run the code for both ARM and end of exit delay? I can work around this, but thought I would check with this group. Thanks. SJ

 

[Desert_AIP]

As a state or condition for automation, NIGHT and NIGHT DELAY are the same thing, as are DAY and DAY INSTANT.
Only the entry delay is affected.

In general terms there are 5 unique armed states.

 

[sjht]

Thanks. Interesting that when I set the alarm for NIGHT it does not execute the NIGHT DELAY code, but when I set NIGHT DELAY it does both. SJ

 

[Desert_AIP]

NIGHT DELAY = NIGHT
But
NIGHT != NIGHT DELAY

 

[sjht]

 

[cornutt]

You can put a condition on your NIGHT code blocks -- AND IF NOT NIGHT DELAY -- if you don't want them to run when you arm NIGHT DELAY.

 

[sjht]

Thanks. That is a good idea. SJ