Print

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

[Joe W]

I have Active Home V1.4 (B2.0.70), which I believe is the latest version. It doesn't recognize that the beginning and ending dates for DST have changed even though I entered the new beginning and ending dates in the Geographic Location box before DST began this year. I had problems when DST began this year and now Active Home thinks DST ended last Sunday (10/28). I'm in the Pacific Time Zone, so I have San Francisco selected as the city, and the DST box is checked. I have 4/01/2007 as the beginning date and 11/04/07 as the ending date for DST but Active Home ignores those dates and is using the old ones. Is there a way to solve my problem?

[steven r]

There has been an on going discussion on this issue for the last year. Basically it boils down to if you leave your CM15A connected 24/7 to your computer it will update ok. Otherwise you'll need to connect it 4 times a year for time corrections.

You might want to search the forum and read the on going discussions for more information.

[-Bill- (of wgjohns.com)]

There has been an on going discussion on this issue for the last year. Basically it boils down to if you leave your CM15A connected 24/7 to your computer it will update ok. Otherwise you'll need to connect it 4 times a year for time corrections.

You might want to search the forum and read the on going discussions for more information.

PSSST... He's using Active Home and the CM11A.     

[steven r]

PSSST... He's using Active Home and the CM11A.

Hey no fair reading between the lines. 
Joe W: My comments were based on the assumption you were using the CM15A with AHP.

[Dan Lawrence]

It's been a long time since I used Active Home and the CM11A, but it was long before Congress messed up the Daylight Savings Time dates, so I would suspect the CM11 will either not be affected or if the old dates were hard coded in the firmware, they can't be.

[Joe W]

The Geographical Location window allows you to enter the start and stop dates for DST, but doing that doesn't seem to have any effect so the dates must be hard coded. I've decided to solve my problem by changing my time zone from Pacific Time to Mountain time for the days that DST was extended by Congress. That causes everything I programmed X-10 modules to do to happen an hour earlier, which will be the correct time. When DST ends I'll change  my time zone back to Pacific.