Hi - Dug through the forum posts and did not find my issue.

1. I have an EISY with a device that cycles the power 1/week on Sunday at 12:05 AM - off, and 12:10 - on (currently - can be scheduled).

2. I have a program that turns lights on at Sundown - 20 minutes

3. The program was set to run at startup, so it ran at at 12:12 AM,, then set the next run time at Monday at 8:05 PM. This SKIPPED the Sunday 8:5-ish run and my lights didn't turn on.

4. 

Call me puzzled.

Thoughts from the experts?

Edited 6 hours ago6 hr by JimTurner
typo

@JimTurner would you mind posting a copy of the program that you thought would run? Please select the program, right click on it and select the last menu item "COPY to Clipboard". Then paste the program in your reply. Do NOT post screen shots. This will make it easy for people offering help to edit/comment directly in the program.

Do you have 2 programs with the same name? Why does the top line of your image above not have any time associated with it?

The "turn on" is actually 2 programs: the second is run with no conditions but executed from the "Run Then" in the first (which is scheduled). I used a "Repeat 3 times" in the second as some of my devices didn't respond correctly / consistently. That solved it. (may be overkill, but it worked).

There are no other folder conditions. The governing triggers are the generator switch and the sunset time - 20 minutes. It's the first program that shows the messed up times in the screen snippet above (new snippet attached showing complete line...). I would have expected that the next run should have been Sunset on SUNDAY not Sunset on MONDAY...

---

First Program (controlling):

NighttimeLightsOnAtSunset - [ID 0054][Parent 0026]

If

$GeneratorInUse is 0

And Time is Sunset - 20 minutes

Then

Run Program 'NighttimeLightsOn' (Then Path)

Else

- No Actions - (To add one, press 'Action')

---

Second Program (does the work):

NighttimeLightsOn - [ID 0053][Parent 0026]

If

- No Conditions - (To add one, press 'Schedule' or 'Condition')

Then

Repeat 3 times

Set 'ButterflyLamp' On

Wait 2 seconds

Set 'Dining Room Chandelier' On 35%

Wait 2 seconds

Set 'Front Porch' On

Wait 2 seconds

Set 'Front Porch Plug Top' On

Wait 2 seconds

Set 'Front Up Lights' On

Wait 2 seconds

Set 'Garage Outside Lights' On

Wait 2 seconds

Set 'Kitchen Und Cab Fridge' On

Wait 2 seconds

Set 'Kitchen Und Cab Stove' On

Wait 2 seconds

Set 'Living Room Floor Lamp' On 50%

Wait 2 seconds

Set 'Media Room inner wall' On 50%

Wait 2 seconds

Set 'Media Room outer wall' On 50%

Wait 2 seconds

Set 'Shop Front Lights' On

Wait 2 seconds

Set 'Shop Side Lights' On

Wait 2 seconds

Set 'Virtual Device Controller / GoodNightControl' On

Else

- No Actions - (To add one, press 'Action')

Uploading Attachment...

Edited Monday at 04:04 PM3 days by JimTurner

UPDATE: it seems that an "Run at Startup" selection messes with the next scheduled run.

Example: I have outside lights that are supposed to come on at sunset.

Here is the sequence:

Saturday -

Last Run Time is Saturday 8:06PM, Next Scheduled Run is Sunday @ 8:05 PM <-- THIS IS CORRECT

Sunday - System auto power cycles @ 12:05 AM which now reports the next line:

Last Run Time is Sunday @ 12:06 AM, Next Scheduled Run is Monday @ 8:04 PM <-- THIS IS INCORRECT

I would NOT expect running a program between scheduled times would affect the schedule...

I turned off the "Run at Startup" and tested again. The schedules now report correctly.

It's possible that power cycling your controller close to midnight is affecting the schedule. Try setting the power cycle at 12:30 am.

You can also try changing the last two lines in the configuration