Is there a certain order that programs run when the isy is restarted? I was trying to come up with the logic last night after the upgrade and I could not figure it out. Some of my lights were not in the correct state when the isy was done running programs.

 

I will say this, the programs that ran were consistent to the state of my Keypadlinc buttons before the restart. The statuses for the Kepadlinc buttons still showed blank in the Main page, and as usual toggling the buttons fixed that. Is that going to be changed in the future, where it shows the status based on the state before restart?

The ISY queries all devices at startup, during this time no programs run. When the query is finished, the 'Run At Startup' programs run, followed by any programs that were triggered/scheduled to run.

 

There was a change in 2.6.4 such that "Run At Reboot" is now "Run At Startup", and, more importantly it does a Run (If) now, instead of a Run Then.

 

In the program summary, you can look at the last run time and Status to determine which programs ran when, and which path they took (Then path for Status=True, Else path for Status=False).

Chris,

 

Just to verify that I have this right, the new "Run At Startup" in 2.6.4 runs a Run (If) now, but if there is a program to be run at start up that has no If condition to evaluate, then would the Then statement be run automatically? Is this correct?

 

Thanks.

Dave, you are correct. Whether at startup or any other time, if a program with no condition is run using Run (If), the Then clause is executed.

Mr. Jahn,

Thank you for your reply, but I was asking specifically what order the programs themselves run. At an 11:00 PM reboot, any program that should have run sometime that day, ran and sent the appropriate commands out to the modules. They all show the same time as have run because they run so fast. Does the "Sunrise" program run before the "Sunset Program", etc.?

 

Is that new catch up on schedules grace period supposed to only run programs that were scheduled within 15 minutes (or set duration) of a restart? If so, it did not work and all my programs ran.

 

Thanks!

Mr. Jahn,

No!!

 

Thank you for your reply, but I was asking specifically what order the programs themselves run. At an 11:00 PM reboot, any program that should have run sometime that day, ran and sent the appropriate commands out to the modules. They all show the same time as have run because they run so fast. Does the "Sunrise" program run before the "Sunset Program", etc.?

 

I see what you are getting at ... there is no predefined order for running programs running at startup.

 

Is that new catch up on schedules grace period supposed to only run programs that were scheduled within 15 minutes (or set duration) of a restart? If so, it did not work and all my programs ran.

 

In the configuration screen you can specify if you want schedules to catchup:

 

-- If selected then all programs are caught up from the beginning of the day.

 

-- If it is not selected then they are run based on the grace period specified.

 

The grace period is also used for upcoming schedules as well and is only used for 'Time is' entries.

Ok then, Chris.

 

Should there be a defined order, say either one we can set, or somehow made to run in the order of the times they are referencing? ie. a program that is set to run at 10:00 AM will run before a program that is set to run at 11:00 AM. Can that be put in the next drop? I think it would be very beneficial.

 

Thanks!

Ok then, Chris.

 

Should there be a defined order, say either one we can set, or somehow made to run in the order of the times they are referencing? ie. a program that is set to run at 10:00 AM will run before a program that is set to run at 11:00 AM. Can that be put in the next drop? I think it would be very beneficial.

 

Thanks!

 

I can see the need for a defined order, unfortunately its not an easy fix. I'm not sure if it will make it into this release.