Programs report "next run" are off by an hour+

[paulbates]

I'm guessing its dst related, but I'm writing new programs on a new eisy so can't be 100% sure

I'm writing programs that look at time. At this point I'm not worried about the one running the next day vs today. The problem is the "next runs" are all times that look correct for before DST took effect.. an hour after the sun has set.

The eisy reports the correct DST at the top, but next run is ~1 1/4 hour behind. Am I doing something wrong? The "Lights on at Dusk" program was working as written before the time change

Take a look:
(Sorry about the eye strain on the last one, it can be "zoomed in on"

[Techman]

I think the problem is that you have several conditions in your "Dusk Sensed" program so the next run time is not a hard number.

Try deleting the first two conditions leaving only the Sunset condition and see if the next run time is then correct.

Edited November 7, 2023 by Techman

[paulbates]

Thanks @Techman. I created a new program with only the schedule condition to trigger at dusk minus 30 minutes and no other conditions. Its first "next scheduled runtime" is tomorrow, thursday at 5:53pm, and dusk today day is 5:17, so it will be a few minutes before that.

Wondering if you or someone could create a test program like above with the only condition being if time = sunset - 30 minutes, save it and then look at next scheduled runtime. If it doesn't happen on other systems then I'll know it's something specific to me and I'll submit a ticket.

Thanks in advance if a couple of people are willing to try that

Edited November 8, 2023 by paulbates

[IndyMike]

Hey @paulbates,

Let me start by saying that I have the ISY994.  I have two programs that run nightly at sunset, and 30 minutes past sunset.  When I looked at the program summary tab, both programs were set to run @EXACTLY sunset and 30 minute past.  My sunset is at 5:36:10 (I'm a little West of you).

Since my programs are slightly different from your Time = Sunset, I decided to add a test case.  That's when things got weird.

After saving my test program, ALL of my sunset programs showed a "Next Scheduled Run" time that was 4 minutes, 4 seconds early.  I expected 5:36:10 PM (sunset) for my sunset programs, but got 5:32:06.  I expected 6:06:10 PM for my night program (sunset + 30 min), but got 6:02:06 PM.

All that I can think of is that the next run is "predicted" when you save the program.  It is then "refined" after the program executes (or perhaps at the end of the day).  Definitely not the result I was expecting and in line with what you are seeing.

 

Original Sunset Program: Fires @5:36:10

Outside Sunset - [ID 0015][Parent 0002]

If
        From    Sunset 
        For      1 minute 
 
Then
        Set 'Outdoor / SC Outside Sunset' On
 
Else
   - No Actions - (To add one, press 'Action')
 

Original Night Program: Fires at 6:06:10

Outside Night - [ID 0016][Parent 0002]

If
        From    Sunset  + 30 minutes
        To      Sunrise +  5 minutes (next day)
 
Then
        Set 'Outdoor / SC Ouside Night' On
 
Else
        Set 'Outdoor / SC Ouside Night' Off
 

 

New Test Program: Fires at 5:32:06

Outside Sunset1 - [ID 0011][Parent 0002]

If
        Time is Sunset 
 
Then
   - No Actions - (To add one, press 'Action')
 
Else
   - No Actions - (To add one, press 'Action')
 

 

 

[paulbates]

Thanks @IndyMike. Could be something that's been there all along and didn't notice or forgot. I'll update it and let it run and see what happens.

[Geddy]

7 hours ago, paulbates said:

Wondering if you or someone could create a test program like above with the only condition being if time = sunset - 30 minutes, save it and then look at next scheduled runtime.

Just made a program like this on my eisy. 

 

Test-PaulBates 

If
        Time is Sunset  - 30 minutes
 
Then
        Set 'Backdoor' On
 
Else
   - No Actions - (To add one, press 'Action')

 

isy-5.7.0_5
Name           : isy
Version        : 5.7.0_5

 

I even closed admin console and re-launched to be sure display wasn't frozen and it still shows as expected to run 5:07:08 with sunset at 5:37:08. 

 

[IndyMike]

Wow, after reading @Geddy's post I logged into the admin console to re-checked my Scheduled execution times (no changes).  They are back to being correct down to the tenth of a second. 

Wild and wondrous - I guess that's why they call it software.

 

[paulbates]

@IndyMike and @Geddy Thanks for responding

The same happened to me Mike... a while after discussing it here, I made some mods, another program I left alone, and they all went to where they should be for Next Scheduled Run!(?).

Included in this was no longer having it wait a day to start a new program with a schedule.

Calling this one closed, thanks again