Schedule Changes

[hart2hart]

I knew this was an issue but I've never taken time to think it out. Can I get your thoughts?

I've got HVAC programs that run primarily by time of day to set temps.  Following is an example for Master Suite sleeping temps.  Last night about 10:00, I discovered the eISY was "hung" so pulled power and it restarted -- looked good on restart.  However, I noticed my setpoint temps for Master Suite were not properly set when I was getting ready for bed a little later.

The program to set sleeping temps runs at 9:00 so it is ready when I turn in.  What do you put in programs in case eISY was hung like my case or maybe if a power failure occurred while it was supposed to run?  I learned after I wrote these that the time function is only used to schedule running (if) start time and the end time.  A state variable could be included in if it was within that time frame is my first thought (no sure what it would be other than something that ticked a variable on/off and forced all stuff like this to evaluate the If every 10, 15, or 30? minutes) but I'm sure one of you has a superior method to accomplish this so it's good in event of an issue at start time.

 

HVAC:Master Temp For Night

If
        From     9:00:00PM
        To       6:29:59AM (next day)
    And $HVAC_MasterSuite_Override_Programming is $Not_Overridden_I
 
Then
        $Thermostat_Master_Temp_Setting  = $Thermostat_Master_Night_Temps_I
 
Else
   - No Actions - (To add one, press 'Action')
 

Edited Monday at 02:34 PM by hart2hart

[Guy Lavoie]

In the System configuration options, there is a checkbox that allows you to "Catch up schedules on restart", which you might want to try.

[hart2hart]

34 minutes ago, Guy Lavoie said:

In the System configuration options, there is a checkbox that allows you to "Catch up schedules on restart", which you might want to try.

Thanks. Ages ago there was advice that it created issues of its own.  Do you think that has all been resolved or maybe it was just the logic got out of sync so no real "fix" was coming.

Edited Monday at 03:54 PM by hart2hart

[Guy Lavoie]

1 minute ago, hart2hart said:

Ages ago there was advice that it created issues of its own.  Do you think that has all been resolved?

No idea about any issues. I haven't used this myself. I just thought I'd mention it because I remember seeing this option

[Geddy]

@hart2hart is the program enabled to "run at startup"? In the summary tab it should show if it is or not. I would turn that on before the catch up schedule option. I'm like you have read about that possibly causing other issues. This way an individual program is running at startup.

I think others have said that could also be an issue if you have a lot of programs running at startup and they have built a startup program to trigger all the other programs they want to run at startup, but with a short wait (a few seconds?) between each run. 

 

[hart2hart]

Thanks @Geddy .  I had forgot that Run at Startup would evaluate that it was within the timeframe and not just at the From and To times.

[Techman]

F.Y.I. If you have a program scheduled to run at startup and if the IF clause is blank, the THEN clause will execute.