Print

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

[ericd]

Has anyone run into any issue with the timers
being off by 1 hour.  Seems as thought there
is an issue with daylight savings time
calculation.  Everything has been fine for
over  a month but then I updated the
interface 2 days ago and now everything is
off by an hour and my laptop time is correct.
Any thoughts???

[Scott T]

I noticed the sames issue last night. Lights
clicked off a 9:00pm instead of 10:00p.
Plug the cm15a back into the laptop check
clock and programming.  Spent a hour check
all macros and timer, but came up with
nothing.  I'm running 3.198.

[murphy]

Version 3.198. I had the same problem Sunday
morning and evening with timers.  They all
fired 1 hour early.  The dusk triggered macro
fired at the correct time.  This leads me to
believe that the unit did indeed think that
daylight time had returned.  I had been
running since my last download in September
with no problems.  I made a couple of changes
to timers that I had been putting off and
redownloaded between 10 and 10:30 PM Sunday
night.  The 11:00 PM and 11:30 PM timers
fired at the correct time.  My next timer is
at 6 PM so I won't know until then if it will
continue to work.

[PK]

Same scenario here.. not a clock drift
problem.  Timed events ran as expected last
Friday, but as of Saturday AM were exactly
1 hour early.  3.198 in use also (after
months of good timekeeping and correct DST
behavior with 3.183).  Is the AHP update
causing this?

[joe]

Me too, my 10 pm timer fired off at 9 pm.
Here we go again!

[david_l]

Yea, I noticed it this morning.  Lights came
on at 4:30 am instead of 5:30.  Lifted my
head of the pillow and did a bleary
eyed "what the *%!&".

Haven't had it hooked up since the time
change.

Well, since I was up an hour early...
Hooked it back up, updated to the latest
(3.198 or 3.199?), cleared the interface
memory, & redownload.

We will see what happens (anyone want to
call tech support?).

[me too]

Same thing happened here in New Orleans,
central time. I havent updated or changed
anything for weeks.  Then last night the
lights went out one hour earlier.

[me too]

And, I can't blame FEMA or Katrina.

[murphy]

My 6 PM timer fired on time so re-downloading
the program appears to have fixed the problem.
I just hope it stays fixed.

[donald mcmow]

If your !@#$%$%^&* government wouldn't mess
around with daylight savings time then we
wouldn't have this problem now would we.

[Mike C]

I had the same problem, would someone from
x10 like to comment on how so many of us
all had the same issue?

[M Nemeth]

That is so weird! Mine did exactly the same
thing on Sunday, and I had to pull the
batteries (hard reset) and then re-program
it. I'm still running 3.187, and the CM15A
had not been disturbed in any way for the
last several weeks. What, was it a cosmic
space-time warp or something that affected
all AHP owners, no matter where they lived?
(cue music from Twilight Zone here)

[Scott T]

I love then end of the means.  It's path to
get there that continuous to frustrate me.
I love the concept of the CM15A, but I don't
know how much more I can take.  “Robust
first, features second” Maybe one device
can’t do it all!

[dengland]

Same problem here too.  About 2 weeks early
to be a leap second problem.  My old CM11A
used to lose it's mind every so often.  I
assumed it happened CM15A too.

[Mike C]

I do not believe all our units lost their
minds at the same time.  There must be a
programming issue that caused this to
happen.  Over 4 months ago I took both my
units apart and added decoupling
capacitors.  Since then I have had stable
operation.  Before I did this I would be
lucky to get a month of stable operation
from either unit.  I left one unit hooked
to a PC and one unit disconnected.  The
disconnected unit was set to ring a chime
every day at 8:00 AM and for the last 4
months triggered the chime everyday at the
correct time.  It now triggers the chime at
7:00 AM every day. The Unit connected to my
PC has not had any issues but I believe
this is because it gets its time updated
from the PC every time the program is
started. I connected the PC to the
disconnected unit and updated the time
tonight.  I expect that this will fix the
clock issue.  I wonder why x10 has not had
any comment on this issue. I am sure they
read this forum.