Another Elk changed behavior

[MWareman]

Can you tell I'm getting my Elk going again??

 

Anyway - another changed behavior..

 

If

        Elk Zone 'Door To Garage' is Violated

    And From     8:00:00AM

        To      10:00:00PM (same day)

 

Then

        Set Elk Speak Word 'Door'

        Set Elk Speak Word 'Two'

        Set Elk Speak Word 'Garage'

        Set Elk Speak Word 'Open'

 

Else

        Set Elk Speak Word 'Door'

        Set Elk Speak Word 'Two'

        Set Elk Speak Word 'Garage'

        Set Elk Speak Word 'Closed'

 

 

Two things about this...  Back at 4.0.something, this would cause the Elk to speak 'Open' or 'closed' when the zone on the door violated or returned to normal - but only between 8am and 10pm (so leaving for work early in the morning does not wake up the house!).

 

However, on 4.2.8 - it speaks outside of the hours. Annoying.

It also spontaneously speaks at 10pm and also at 8am. Also annoying.

 

Right now - I've moved the time to a folder condition. Hopefully - that works. Why wouldn't this?  I believe it used to.

 

Michael.

 

 

 

 

[LeeG]

The time range gates whether the If is True or False when the garage is violated.  The Else will be executed when the garage is violated outside the time range.

 

The time range triggers the Program at the From time and the To time.  The From time trigger is True but is also dependent on the violated state in this case.  The To time triggers the Program with a False state regardless of violated state.

 

The From (True)/To (False) time triggers have not changed. 

[apostolakisl]

The behavior you see in this program is as it should be.  It would have always behaved like you are describing.  You must have changed something for it to behaved different in the past.

 

There are 3 triggers.  

 

1) Change in the status of the door

2) 8am

3) 10pm

 

If any of those 3 things happens, the program triggers.  Since you have voice anouncements in both the "then" and " else" clause, you will always get speech with any of the 3 things.  Outside of 8 to 10, you will always execute the else, inside of those hours it depends on the status of the door.  At 10pm you always get the else, and at 8 am it could go either way depending on the door status.

 

As you surmised, putting the program in a folder with the time constraints instead of putting the time in the program will fix it.

[MWareman]

Thanks for that. Brain kicked in again. Thanks for the reminder all! I was tearing my hair out! Something must have changed in the system being in storage for 6 months behind me just disabling my ISY programs. Oh well.