Disable program

[Vortec4800]

From what I can tell, if you disable a program but call it from another program, it will still run - the program just won't run by itself unless its specifically called. Is this correct? Is there anything else to note about the enable/disable bit?

 

Also, I had some problems with a sunrise to sunset program. Basically I want something to happen if the program is called sometime between sunrise and sunset. I disabled the program (so it would only run when called, not everytime sunset happens or anything like that) and set the schedule to be from sunset to sunrise next day. This worked before midnight, but not after because then its same day, not next. I've been using an or statement that reads from sunset to 11:59 or 12:00 to sunrise same day which seems to work, but its a pain. What's the correct way to do this? And what's the usefulness of the next day function if it doesn't seem to work?

[IndyMike]

Vortec,

 

I believe your statement below is correct - As of Version 2.6.4:

 

If program1 is disabled, program2 can still execute program1 with a "run program1 (then path)" call. This will force the "then" statement (similar for the else path).

 

If program2 uses the "run program1 (IF Path)" all of the conditions in program1 must be met to execute the "Then" path. If they are not, the "Else" path will be executed.

 

One caveat to the above - If Program1 resides in a conditional folder (and it's condition is false), you will not be able to execute it from program2.

 

From what I can tell, if you disable a program but call it from another program, it will still run - the program just won't run by itself unless its specifically called. Is this correct? Is there anything else to note about the enable/disable bit?

 

While there have been some complaints regarding the "Sunset to Sunrise" time condition, most of these were misinterpretations of how the conditional ran on first execution. I'm not sure if your description fits into that category. As you noted, there are workarounds for this condition, but that shouldn't be necessary. While there have been changes to the "Schedule catchup" in version 2.6.4 (it's now configurable), I'm not aware of any problems with the function.

 

Could I impose upon you to post your program? You can copy a program by right-clicking on the program name in the left hand "program tree". Select "copy to clipboard" and then past into your forum post.

 

Thanks,

IM

 

Also, I had some problems with a sunrise to sunset program. Basically I want something to happen if the program is called sometime between sunrise and sunset. I disabled the program (so it would only run when called, not everytime sunset happens or anything like that) and set the schedule to be from sunset to sunrise next day. This worked before midnight, but not after because then its same day, not next. I've been using an or statement that reads from sunset to 11:59 or 12:00 to sunrise same day which seems to work, but its a pain. What's the correct way to do this? And what's the usefulness of the next day function if it doesn't seem to work?

[Chris Jahn]

While there have been some complaints regarding the "Sunset to Sunrise" time condition, most of these were misinterpretations of how the conditional ran on first execution.

 

This has been fixed in 2.6.5, such that the first execution is no longer delayed.

 

For example, if you have program X with a schedule going from Sunset to Sunrise, and you save program X at 3:00AM, the schedule is true immediately.

 

In other words, you no longer have to wait until sunset later that day for the schedule to kick in.

[Vortec4800]

While there have been some complaints regarding the "Sunset to Sunrise" time condition, most of these were misinterpretations of how the conditional ran on first execution.

 

This has been fixed in 2.6.5, such that the first execution is no longer delayed.

 

For example, if you have program X with a schedule going from Sunset to Sunrise, and you save program X at 3:00AM, the schedule is true immediately.

 

In other words, you no longer have to wait until sunset later that day for the schedule to kick in.

 

Oh that's great, so I can use sunset to sunrise and I'd set it to next day and that would work properly? And after midnight it would still be true?

[Chris Jahn]

Oh that's great, so I can use sunset to sunrise and I'd set it to next day and that would work properly? And after midnight it would still be true?

 

Yes.

 

Just to clarify ... it already works that way. The only problem that 2.6.5 fixes is when the schedule actually kicks in.

 

Prior to the fix in 2.6.5, if you saved the program at say 1:00AM Monday, the schedule wouldn't kick-in until sunset on Monday, but after that the schedule worked properly (across midnight or more days etc).

[IndyMike]

Vortec,

 

My apologies for not being clear earlier. To my understanding, there is not a problem with the Sunset to Sunrise condition after the first day.

 

Referring to the time condition below - the program summary tab should show "True" for the entire time span from sunrise to sunset. Please let us know if this isn't the case (if you see a false for times after midnight).

 

IF
From Sunset
to Sunrise (next day)

Then 

 

Following up on Chris's post, the problem comes in on first execution if you modify and save the program after midnight. In that instance, the ISY will wait for the next "sunset" to enable the program. In other words, if you save your program after midnight it will not become "true" until after sunset the next day. After this 1st iteration it should "initialize" and behave as you would expect (Chris - I trust you will correct me if my understanding is wrong).

 

If you are seeing something different please get back with us and, if at all possible, post your code.

 

Thanks,

IM

[Vortec4800]

I'll set up a program and let it go and see what happens. I set it up one night and tested it but didn't really let it do its thing, just saw that once I set the clock past midnight it said false. I'll try it out.

[Vortec4800]

I just realized I'm using v2.6.4 (which was a good upgrade from the 1.0 that came on it) but that explains why I'm still having the problem with the schedule like that. I won't have Internet here for a couple more weeks so I'll have to upgrade it then and bask in the bugfix glory.