X10 Community Forum

🖥️ActiveHome Pro => ActiveHome Pro General => Help & Troubleshooting => Topic started by: daveva on December 13, 2009, 09:35:55 PM

Title: Lights came on early
Post by: daveva on December 13, 2009, 09:35:55 PM

I have my Christmas lights programed to turn on Dec 1st to Jan 2nd at 6:00 PM and tonight they turned on at 5:00. Any suggestions on why?   

Title: Re: Lights came on early
Post by: Dan Lawrence on December 13, 2009, 10:02:39 PM

I presume you are using Active Home Pro and the CM15A. What version of AHP?

Title: Re: Lights came on early
Post by: daveva on December 13, 2009, 10:15:28 PM

 3.228

Title: Re: Lights came on early
Post by: murphy on December 14, 2009, 02:34:35 PM

It happens every year on the second Sunday in December if you are running the unit disconnected from the computer.  I have a note in my yearly calendar to be ready for it.  Reconnecting to the computer will fix it.

Title: Re: Lights came on early
Post by: daveva on December 14, 2009, 04:08:14 PM

Thanks

Title: Re: Lights came on early
Post by: mitch5225 on December 14, 2009, 05:45:57 PM

I was just coming to look for an answer to the same issue! Thanks for the advice.

Does anyone know WHY this happens?
I sure as heck would never have figured it out on my own.

Regards,
Michelle

Title: Re: Lights came on early
Post by: twood on December 14, 2009, 11:36:54 PM

Quote

It happens every year on the second Sunday in December if you are running the unit disconnected from the computer.  I have a note in my yearly calendar to be ready for it.  Reconnecting to the computer will fix it.

Thanks, Murphy--you got a Helpful from me!  Is the problem fixed by simply connecting to the computer, or downloading all timers and macros?

Title: Re: Lights came on early
Post by: Dan Lawrence on December 15, 2009, 08:28:18 PM

If you don't have the CM15A connected to the PC 24/7, you get to play the reconnect game four times every year.  The old DST dates are hard coded in the CM15A and the new (current) DST dates are not, so four times a season you get to hook the CM15 to the PC on the new date, then unhook it until the old DST date, then reconnect it again.  You get to play that game twice a year.

Why a problem on the second Sunday in December?  No DST change then.

Title: Re: Lights came on early
Post by: murphy on December 16, 2009, 03:16:37 PM

Quote from: twood on December 14, 2009, 11:36:54 PM

Quote

It happens every year on the second Sunday in December if you are running the unit disconnected from the computer.  I have a note in my yearly calendar to be ready for it.  Reconnecting to the computer will fix it.

Thanks, Murphy--you got a Helpful from me!  Is the problem fixed by simply connecting to the computer, or downloading all timers and macros?

You just have to connect to the computer so the CM15A gets it's date updated.  Downloading is not required.

Title: Re: Lights came on early
Post by: murphy on December 16, 2009, 03:18:45 PM

Quote from: Dan Lawrence on December 15, 2009, 08:28:18 PM

If you don't have the CM15A connected to the PC 24/7, you get to play the reconnect game four times every year.  The old DST dates are hard coded in the CM15A and the new (current) DST dates are not, so four times a season you get to hook the CM15 to the PC on the new date, then unhook it until the old DST date, then reconnect it again.  You get to play that game twice a year.

Why a problem on the second Sunday in December?  No DST change then.

I have no idea.  I reported it over two years ago but my report was ignored.

Title: Re: Lights came on early
Post by: Dan Lawrence on December 16, 2009, 07:18:09 PM

I would not be surprised to hear the folks who have odd shifts on the second Sunday in December have some strange holiday decoration not controlled by a module that is the cause.   Power line noise drives X10 crazy.