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