Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[jrubenstein]

My CM15A seemed to change to Daylight Savings Time today.  Did this happen to anybody else?  Or am I in the twilight zone?
 
I have accepted the fact that unless I connect my CM15A to my PC during the (old & new) Daylight Savings Time change weekends, it will incorrectly use the (presumably hard-coded) old DST changeover dates and not the new ones.  But I still leave it disconnected most of the year, except for those four special weekends.  But ... this morning (Sunday December 16th) I woke up and noticed that all of my timers are firing exactly one hour early.  Exactly what would happen if it had switched to Daylight Savings Time.  I'll just go ahead and hook it up to my PC now and set the clock, and I assume that will fix it.  But what's up with December 16th?

Anybody else see this happen today? 

[Dan Lawrence]

You are in the Twilight Zone!!!!!

Is your PC also in the Twilight Zone?  When the CM15A is plugged into the USB port, the CM15 takes it's time from Windows.  If the PC has hopped an hour early, either the PC clock is wrong or the motherboard battery is bad.

[jrubenstein]

This entire episode happened with the CM15A completely independent and not connected to the PC.  The last time I connected it was during the real DST changeover period back in November, and it did indeed get the correct instructions via the PC/Windows connection at that time.  (I know you wonder why I don't leave it connected all the time, but there are a number of reasons.)

It is pretty strange.  I have no idea why it would decide to jump ahead exactly one hour on December 16th.  It is a Sunday ... just like it would be if it were a real DST changeover date.  But ... obviously it's not supposed to do it today.

I was just wondering if anybody else had it happen too.

And ... The date on my computer is - and always has been - correct.

Jeff

[murphy]

My lights came on an hour early this morning also.  It's another bug in the CM15A firmware.  The same problem was reported last year by me and many others and they chose to ignore it just like they ignored the other DST problems.  If you have the CM15A connected to a running computer it won't happen.  If you run the CM15A standalone (i.e. not connected to a computer), it will happen every year.

[jrubenstein]

Great!  I am not alone. 

I guess I missed it last year.  I understand it will do it in accordance with the "old" DST changeover dates.  (And not the new dates.)  But does anybody have any idea why it does it on December 16th?

[Dan Lawrence]

No idea.

The old DST dates are hard coded in the CM15A's firmware, so the only way to get the DST dates correct is to hook the CM15A to the PC before the DST begin and end dates and let Windows do the change before you unhook it.   If the CM15A's regular place it's plugged into is near the PC, keep it hooked 24/7, you will  have less problems with things like DST dates.

My CM15A is connected 24/7 365 days of the year, including Leap Years (which 2008 is). 

[Walt2]

My CM15A seemed to change to Daylight Savings Time today.  Did this happen to anybody else?  Or am I in the twilight zone?

It happen to me too.   

I didn't really notice it until I was awaken an hour early this morning.   

I don't remember a second "fall season" DST change last year.   

This sucks.   

[Walt2]

The old DST dates are hard coded in the CM15A's firmware, so the only way to get the DST dates correct is to hook the CM15A to the PC before the DST begin and end dates and let Windows do the change before you unhook it. 
 

While I agree, my CM15A hasn't been connected up to my PC for several weeks.  So, it is clearly the CM15A which suddenly decided on its own, that it needed to change time by one hour on 12/16.

An "easter egg" left by Mike C?   

[jrubenstein]

I'm glad to hear that I'm not the only one seeing this same fascinating problem.    At least I don't have to wonder if my CM15A got damaged, or corrupted, or something.  It isn't convenient for me to leave it connected to my PC all the time, as the location where it works best (due to distances to the receivers down in the barn more than 250 feet away) is not near my desktop computer.  I've been running it as a standalone unit for years, only connecting to the PC when necessary for updating the program.  And it worked great until the DST date change last year.

I tend to be sympathetic with programmers, as I was one in a previous life.  So I understand it can take some time to fix a bug and allocate appropriate time for testing to be sure you didn't create new ones.  But I have to believe the support people have now had plenty of time to get this fixed.  Yet I have not seen a single software update since the DST change last fall.  Very disappointing.  Perhaps it's not fixable through an update to the ActivehomePro software, and requires a firmware (hardware) upgrade in the CM15A.  I sure wish somebody from X10 would address this issue and let us know.

Jeff

[Walt2]

You are in the Twilight Zone!!!!!

Now, why didn't this 1 hour set-back happen to EVERYONE on 12/16?   

[Dan Lawrence]

Easy.

It only happened to those who don't have their CM15 conected to the PC 24/7/365(6).

[wcbenje]

Well, a year later and I find that this year, DST may have started on December 14, as it did on Dec 16, 2007.  Has there been a fix to this problem yet???

Chris

[Tuicemen]

wcbenje
AHP version 3.236 is suppost to fix this!
If your not running that version Update to it!

[wcbenje]

Cool, let me get home and update.  I guess I won't be able to see if it really is fixed,though, for another 364 days. 

[murphy]

wcbenje
AHP version 3.236 is suppost to fix this!
If your not running that version Update to it!

So why wasn't this update put on the automatic update queue?  I am running 3.228 and a forced update says that I have the latest software.