I was wondering if the shift to DST went well for the rest of you. Some of you will remember my earlier post in which I presented an argument as to why I thought a firmware update was in order:
http://www.x10community.com/forums/index.php?topic=11694.0Thank you to all of you who responded to my previous post. It seems that the majority of you looked at the Dusk/Dawn table and assumed that would tell us when the INTERFACE would change its internal clock. WRONG! The Dusk/Dawn table simply displays the calculated Dusk/Dawn times ADJUSTED FOR TIME IN YOUR REGION!!! That's why the Dusk/Dawn table changed after the Windows DST update. Simply put, the Dusk/Dawn table is regionalized based on your PC operating system settings.
However, that was not the crux of my argument. My point was that up until now, the interface changed its internal clock according to DST rules. I never had to keep my PC plugged into it and I never had to update the time manually. My interface is located in my attic where I get awesome RF reception all over the house and yard. I have to take a laptop up to the attic now to change time in accordance with the new DST rules. Not just twice a year, but 4 times a year.
So, long story short. I have Windows XP Professional. It has been patched with the Microsoft DST update since February 25th, 2007. The last update to the timers in the interface was March 3rd, 2007. Today I watched in complete dismay as ALL my macros, timers, and events were late. When I took the laptop up to the attic and connected to the interface, I noticed the interface time was off by an hour per my reasoning. A few seconds later I saw it update itself to match the time on my PC. Aha! Caught you! The interface still updates its internal clock according to old DST rules. I usually love it when I'm right. In this case, I was really hoping I was wrong.
I can't wait for April when the interface puts its internal clock forward an hour, thinking DST has begun.