Program Next Run in 2029!

[daxiang28]

I attached a screenshot of my Summary page from my Admin Console. I was wondering why my programs were not running today and I noticed that the ones scheduled for this evening were all scheduled to run in 2029! The last time they were run successfully was yesterday. A glance at the logs showed no errors. I recently upgraded to 3.3.3. Any thoughts?

 

 

Steve

[apostolakisl]

I would try a reboot.

[daxiang28]

I would try a reboot.

 

Yup, that worked. Thanks!

 

Steve

[db2ace2]

I have a similar issue but instead of the Next scheduled Runtime in 2029 its the Last Run Time and Last Finished Time in 2029

 

I will try a reboot but I was curious whats up with the 2029 Year?

 

Thanks

[Michel Kohanim]

Hi Guys,

 

That's not normal. Can you please let me know what's your firmware version?

 

With kind regards,

MIchel

[db2ace2]

I am running V3.3.10.

 

The Current Date and Time was all correct and at one point when I sorted by Last Run Date it had a 2013 Year sorted ahed of the 2029 year so it made no sense at all to me. The Reboot did clear it up. Its just curious as to why it picks the 2029 year?

[Michel Kohanim]

Hello db2ace2,

 

Indeed quite strange. Can you please copy to clipboard your program for which you had this issue and paste here?

 

With kind regards,

Michel

[db2ace2]

This happened for about 20-30 out of about 3-4 Hundred Programs executed in the ISY screens. I cant remember them all and should have captured a list but I will next time. I have had this happen more than once but not regularly so its intermittent, but this is at least one set of programs I remember as being involved in the 2029 year issue. I will try to describe these programs. Sorry for the lengthy discussion, but I kind of like these programs and use them a lot without fail. These Programs are designed to allow me to use an X10 Palmpad and let me push a single Palmpad Button Multiple times in succession within 6 seconds with each push performing a different task. In other words instead of using three or four buttons to control multiple bedroom lights I can use just one (A1) button multiple times (1 second apart) in a row with each push performing a different task. This really works great, and I use it every morning and night with great success.

There are actually 8 programs to make this happen and all 8 had the 2029 date as the last run, however I will only show the four "ON" Button Programs here since the "OFF" Button programs just do the same thing in reverse.

You will see variables in the program for My Alarm System which basically only allow this Multi Button sequence to work when the Alarm in not processing an ALERT or an ALARM status since doing so could interfere with the alarm process. The only issue I can see is that each time the button is pushed the X10RF is repeating its Button 1 command but it doesn't seem to hurt other than generating traffic and since its light is already on it stays on or off.

 

Program 1 On - Detects that one of three different Palmpad On Buttons were pushed and sets a Variable to initiate Program 2 on. It also initiates a WAIT condition for 6 seconds. While it does not turn any lights on from withing the program, the X10RF is actually set to turn some Night Lights on in the bedroom so that happens at the same time program 1 on is executing and beginning the process.

 

If

(

Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.1' is switched On

Or Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.1' is switched Fast On

Or Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.2' is switched On

Or Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.2' is switched Fast On

Or Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.3' is switched On

Or Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.3' is switched Fast On

)

And $MultiX10_Bedroom is 0

And (

$Al_PrcVar_Phase_All_0Monitor_1AlertInProg_2AlarmInProg_3Reset_4Disabled is 0

Or $Al_PrcVar_Phase_All_0Monitor_1AlertInProg_2AlarmInProg_3Reset_4Disabled is 4

)

 

Then

$MultiX10_Bedroom = 1

 

Else

Wait 6 seconds

$MultiX10_Bedroom = 0

 

 

Program 2 On - Only executes once Program 1 has set its variable and it detects a second push of the Palmpad Button. within the 6 second wait of Program 1 On. When the second Push is detected it then turns a scene on that has Bedroom and Bathroom Lamps and Vanity lights on.

 

If

(

Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.1' is switched Fast On

Or Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.1' is switched On

Or Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.2' is switched Fast On

Or Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.2' is switched On

Or Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.3' is switched Fast On

Or Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.3' is switched On

)

And $MultiX10_Bedroom is 1

 

Then

Set Scene 'X10-EZX10RF / X10RF Multi Bedroom Scene' Fast On

Set Scene 'X10-EZX10RF / X10RF-A01 Mbdrm-Mbath Mood Sw' Fast On

$MultiX10_Bedroom = 2

 

Else

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

 

 

Program 3 On - Only executes once Program 2 has set its variable and it detects a third push of the Palmpad Button. within the 6 second wait of Program 1 On. When the third Push is detected it then turns a switch that turns on the Bedrom Ceiling Lights so basically each push is progressively turning on more lights in the Bedroom and Bath areas.

 

Only executes once Program 1 has set its variable and it detects a second push of the Palmpad Button. within the 6 second wait of Program 1 On. When the second Push is detected it then turns a scene on that has Bedroom and Bathroom Lamps and Vanity lights on.

 

 

Program 4 On - Only executes once Program 3 has set its variable and it detects a fourth push of the Palmpad Button. within the 6 second wait of Program 1 On. When the fourth Push is detected it then turns a scene on that turns on most of the lights in the whole house. The Fourth On program is rarely used, however in the OFF button Programs I used it every night to turn all lights in the whole house that need to be off when retiring to bed. It also runs a couple of programs that contain schedules to turn Scentsy Candles off or on at scheduled times.

 

If

(

Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.1' is switched Fast On

Or Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.1' is switched On

Or Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.2' is switched Fast On

Or Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.2' is switched On

Or Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.3' is switched Fast On

Or Control 'X10-EZX10RF / X10 Devices / EZX10RF 1B.02.C0.3' is switched On

)

And $MultiX10_Bedroom is 3

 

Then

Set Scene 'X10-EZX10RF / X10RF Multi AllOnOff Scene' On

Run Program 'P-Scentsy-Off' (If)

Run Program 'P-Scentsy-On' (If)

$MultiX10_Bedroom = 0

 

Else

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

 

 

 

 

Once six seconds or the fourth button has been pressed, Program 1 then executes it else which changes the variable back to 0 which would then start the process over again.

 

 

Again I use the OFF set of programs which do the reverse of this ON process every night to turn the bedroom lights off and ultimately on the fourth button press to basically turn all lights that need to be off off.

 

I see nothing that should cause the 2029 Date issue in the Last Run Date, but I have seen this several times not only for these programs but others as well. I really haven't been able to pin down a cause at this time but it just seemed coincidental that someone else had posted about a 2029 date.

[Michel Kohanim]

Hello db2ace2,

 

THANKS SO VERY MUCH. This is excellent input and feedback and pretty much more than I expected. Your contribution will certainly help us figure out where those dates are coming from.

 

At a high level, none of the conditions seem to be time based, so that might be a clue.

 

Thanks again SO very much and with kind regards,

Michel

[db2ace2]

Just an Update on the 2029 Date Issue. This normally never happens, and My ISY normally runs without many Glitches at all, but I did a PLM Restore today, and Lo and Behold about 30 Entries cam up with 2029 as the Year for the Last Run and Last Finished Times. These dates are somehow happening when the PLM gets restored, but they do not happen every time it gets restored. Just FYI!

 

Thanks

Charles

[arw01]

Just curious, what is the maximum epoch date the isy can handle with it's offset it uses?

 

Is the epoch an unsigned int for absolutely sure in the code? If an epoch made it negative what would your routines think the year was?

[Michel Kohanim]

Hi db2ace2,

 

Can you please copy/paste the condition of one of the programs for which you had 2029?

 

Hi Alan,

 

Good questions. We use an unsigned int for time. Time cannot get negative ... there seems to be something related to programs that causes these issue. The fact that now we have at least one way to reproduce (restore PLM) is a welcome sign.

 

With kind regards,

Michel

[db2ace2]

Again, it doesnt happen every time I restore the PLM (Which hopefully is not very often!), but that did seem to trigger it. Interestingly the programs Involved do not use scheduling functions or After Lastrun, or any Date/Time related functions. The Dates that showed 2029 were the Dates updated automatically by the ISY such as Last Run Date, and Last Finish Date. I could attach Program code, but again I dont see the point since these were not doing any Date/Time scheduling. They were simple Check Variable or Status, and Set Device On/Off. etc.

 

Hope this helps!

 

Thanks

Charles

[Michel Kohanim]

Hi Charles,

 

Thanks so very much for the update.

 

With kind regards,

Michel

[db2ace2]

Another incident of Time related Issues. In the attached File you will see a screenshot of my Variables screen with the Time clearly showing as 10/02/2013 01:28:23 PM. I have not rebooted or done any time changes prior to this and yet the last Update time on the variables clearly shows a Last Change Date over an hour into the future. I would think this might be related to Daylight Savings differences except that the time is more than 1 hour off.

 

Any Thoughts?

 

I see similar issues to this quite often.

 

I am at 4.05 Version Level.

 

Thanks

Charles Seiler

[db2ace2]

Never Mind. I was looking at the wrong ISY and I see the date is 10/01 not 10/02. My Mistake!