Time change issues (end DST)

[Illusion]

Daylight Saving Time?

 

Woke up this morning to an email from my system that happens when the system boots up typically. It showed a system start up time of 1am. And I do not have a status of any device that was not queried at startup.

Also, my sunrise and sunset times are off my an hour. I have considered rebooting, but also kinda want to wait to see if it fixes itself tomorrow. 

[wrj0]

Sunrise & sunset off by an hour here as well; system time is OK and the system did not reboot at DST change.  eisy v5.8.4

[hart2hart]

I have a program that uses time nodeserver to detect time change and then forces a reboot. Works great!

[Illusion]

4 minutes ago, hart2hart said:

I have a program that uses time nodeserver to detect time change and then forces a reboot. Works great!

That is kinda interesting. Can you post said program? 

[hart2hart]

Here you go:

 

DayLight Saving Time:Check For Change

If
        'Date Time and Celestial Info / Calendar' DST is not '$Daylight_Saving_Time_Current Boolean'
 
Then
        Wait 5 minutes 
        Send Notification to 'Me' content 'Daylight Saving Time Change'
        $Daylight_Saving_Time_Current Init To 'Date Time and Celestial Info / Calendar' DST 
        $Daylight_Saving_Time_Current  = 'Date Time and Celestial Info / Calendar' DST 
        System: Restart IoX
 
Else
   - No Actions - (To add one, press 'Action')

[WFP]

I use a LAT/LONG custom location versus eastern time.

My Sunset and Sunrise are also off by an hour, system time is correct.

Reboot did not correct.

EISY/5.8.4

 

/Bill

Edited November 3 by WFP

[bwdavis7]

Same here...custom location...worked before time change, now Sunset Sunrise off by an hour, system time is correct.

Reboot/upgrade/reboot ..reboot...reboot...reboot...reboot...  DID NOT WORK!

[Illusion]

I am NOT at a custom location. 

[Brian H]

My older ISY994i changed as expected today.

[BobT]

Same here...my eisy reports correct DST time, but sunrise/sunset are reporting 1 hour earlier than actual.

Reboot did not help.

[milodorr]

Same for me.  eisy (v5.8.4 firmware) thinks PST sunrise/sunset is 5:15a/3:57p, which is a bit more than an hour early here in the SF Bay area.

[hart2hart]

My guess is it calculates the sunrise and sunset times at midnight but did not apply new time to the calculations correctly after the change. As others have said, it will probably be right just after midnight.


I feel like that this was reported last change and it was confirmed that it’s the displayed sunrise and sunset that are wrong but the actual comparison times used in programs is correct. Did I dream this or does someone else recall the same? I located post where it was discussed.

https://forum.universal-devices.com/topic/43242-sunrise-off-1-hour-this-morning/


I use lux value from weatherflow to turn on and off lights based on night and day so wouldn’t notice if it were wrong with eISY.

[BobT]

UPDATE:   Even though UD Administrative Console says Sunset is 4:07pm (see image), the program I have set to run at sunset DID indeed run at 5:07pm, very close to actual sunset (see the other image).

[milodorr]

In my case, the program I have to turn on my evening lighting, which is set to run at sunset minus 30 minutes, definitely ran an hour early.  I was on my couch watching a football game when the lights came on at 3:30.  I then fired up the AC to try to understand why.

[Illusion]

Sunrise/Sunset times are correct today. No manual intervention to system. It just fixed itself.

[wrj0]

One day after the DST change, my eisy console now displays the correct Sunrise and Sunset; no reboot was performed.  Also, notifications using ${sys.sunrise24} and ${sys.sunset24} are also correct today; they too were off by an hour yesterday.

[WFP]

Corrected today for me as well.

/Bill

[Ross]

@hart2hart "My guess is it calculates the sunrise and sunset times at midnight" - perhaps the EISY should perform the calculations at 3:01am so that it's after both the fall-back and spring-forward time changes.

Also, I'm interested in your nodeserver  'Date Time and Celestial Info / Calendar' (mostly for the Celestial Info).  I don't see it in the nodeserver store.

Thanks,

Ross

[hart2hart]

@hart2hart "My guess is it calculates the sunrise and sunset times at midnight" - perhaps the EISY should perform the calculations at 3:01am so that it's after both the fall-back and spring-forward time changes.
Also, I'm interested in your nodeserver  'Date Time and Celestial Info / Calendar' (mostly for the Celestial Info).  I don't see it in the nodeserver store.
Thanks,
Ross

I believe it’s called TimeData. There is also one called Sun. I may have renamed it to include celestial in the name.

[Techman]

After the end of Daylight savings tme none of my sunset or timed programs ran Sunday night. The time was correctly displayed in my eisy. I did a cold boot and will see what happens tonight.

[oberkc]

We get these problems every spring and fall, it seems like.  It has always fixed itself for me and I just learn to accept this and not to get too excited when thing are not quite right the first day.

[Techman]

1 hour ago, oberkc said:

We get these problems every spring and fall, it seems like.  It has always fixed itself for me and I just learn to accept this and not to get too excited when thing are not quite right the first day.

It didn't happen to me during the previous time change. Guess it's a little glitch in the current firmware. 

[dbuss]

3 hours ago, Techman said:

After the end of Daylight savings tme none of my sunset or timed programs ran Sunday night. The time was correctly displayed in my eisy. I did a cold boot and will see what happens tonight.

I had the same issues. A reboot resolved my issues. This is the first time I've experienced any issues with the time changes.

[Brian H]

The DST issues where also reported on the Insteon Forums.

So the ISY products where not the only controller with possible issues.

[Techman]

1 hour ago, Brian H said:

The DST issues where also reported on the Insteon Forums.

So the ISY products where not the only controller with possible issues.

Glad to know we're not alone