JoeA Posted November 3, 2014 Posted November 3, 2014 On Sunday, the first morning after the end of daylight saving time, the following program ran at 8am. No problem before or after Sunday. I must be missing something simple. Any idea why it ran at 8am? If Time is 7:00:00AM Then Run Program 'MBR-SW Open' (If) Else - No Actions - (To add one, press 'Action') Config options daylight saving time is checked. sync every 24 hours with pool.ntp.org thanks
stusviews Posted November 3, 2014 Posted November 3, 2014 Configuration, Clock. Is Daylight Saving selected? Is NTP enabled? Is the an NTP Server entry?
larryllix Posted November 3, 2014 Posted November 3, 2014 Does your sync with NTP happen every 24 hours? At midnite? DST changes at 2:00 AM and may not be updated until the next night sync.
Techman Posted November 3, 2014 Posted November 3, 2014 Also the default setting on the ISY is to synchronize with the time server every 24 hours.
MWareman Posted November 3, 2014 Posted November 3, 2014 Time servers send the time in UTC. Conversion to summer/daylight saving hours (and the switch) should be handled by the OS itself. I seem to recall issues last change as well with a prior firmware, though I have not checked my ISY with the current beta yet.
Michel Kohanim Posted November 3, 2014 Posted November 3, 2014 Hi Techman, What's your ISY's firmware. This might be an old bug. With kind regards, Michel
Techman Posted November 3, 2014 Posted November 3, 2014 Hi Techman, What's your ISY's firmware. This might be an old bug. With kind regards, Michel Hi Michel I'm running 4.2.17. All is working fine on this end, did you mean to respond to JoeA?
JoeA Posted November 4, 2014 Author Posted November 4, 2014 Hi Techman, What's your ISY's firmware. This might be an old bug. With kind regards, Michel Hi Michel, I'm the original poster, not Techman From the About box: Firmware - 4.0.5 UI - 4.1.1 Not a big problem for me so don't spend time on it. Just wondering if I'm missing something simple. If it happens again, I will do some better problem isolation. thank you Joe
Michel Kohanim Posted November 5, 2014 Posted November 5, 2014 Hi Joe, Apologies. That's really odd. Would you please take a look at your logs and see if the time actually changed (fell back) on Sunday? With kind regards, Michel
JoeA Posted November 6, 2014 Author Posted November 6, 2014 Hi Michel, I looked at the log & attached a JPG of a part of it with many Excel rows deleted/hidden for clarity. I found some things worth pointing out. First, the ISY time was correctly adjusted for the end of DST as far as I can infer. I have some lights that ISY turns off at sunrise. The log shows those programs executed correctly. On Saturday Excel rows 14-17 show sunrise was at 7:57AM and on Sunday rows 167-170 show sunrise was 6:58AM. That is good. Second, I have a startup program that runs a pump for 2 minutes every half hour forever. Rows 164-165 show the pump cycling off at 1:56AM and going into a 28 minute WAIT. After that, there are no more log entries from that program so it appears it somehow stopped execution. I assume the ISY executed some end of DST code at 2AM. Coincidence? Third, the program I posted in the first post uses the network module at 7AM to raise 12 shades (I removed some of the NETWORK commands in the THEN clause to make it short for discussion purposes). The shades didn't go up but the nature of the log seems to not show program executions that are triggered by calendar conditions and only execute NETWORK commands. So I can't prove the program ran or not. Fourth, I rebooted the ISY just before 8AM Sunday and everything has been good since. Based on my experience, I expect it will remain that way until perhaps when DST restarts. I appreciate your interest but don't spend much time on this. Version 5 sounds much more interesting! If there is no obvious issue or resolution, is there a way to programmatically reboot ISY? That would probably be a simple workaround for me to run twice a year after DST logic runs and see if my little problem goes away. thank you
Michel Kohanim Posted November 7, 2014 Posted November 7, 2014 Hello JoeA, Thanks so very much for the details. Yes, you can definitely reboot ISY using our WSDK. This said, please let us go through your logs and fix this issue. It has to be fixed anyway. Thanks again and with kind regards, Michel
Recommended Posts