Homeowner Forum / Home Automation / February 2007

Dawn/Dusk is indeed affected by DST. In fact that's the ole point of
DST... to move dusk an hour later. Now, if dawn/dusk is based on a photo
sensor then DST makes no difference but the calculated dawn/dusk will
have the lights coming on an hour before sunset until it catches up.
Simple solution if no patch is available is to simply turn DST off and
manually change your timezone to the one immediatly west of you i.e.
Central to Mountain (GMT -6 to GMT -7).

According to the ActiveHome Help file - Geographic Location (Configuration
Menu)...

"...if you live in the USA and in a State which observes Daylight Savings
Time, you should check the Daylight Savings Time box. If you live in a state
which does NOT observe D.S.T., you would not check this box. When you check
D.S.T., ActiveHome will automatically advance its clock on the first Sunday
in April and the last Sunday in October. When you select D.S.T., the
previously grayed-out start and stop dates for D.S.T. become active. These
boxes show the dates when you would normally put the clocks forward and back
(in the USA). If you live in a country which observes D.S.T. but puts the
clocks forward and back on a different date from the USA, you can simply
type in the appropriate dates into the boxes provided."

You need to uncheck the box and manually adjust the dates each year.

http://davehouston.net
http://tech.groups.yahoo.com/group/roZetta/
roZetta-subscribe@yahoogroups.com

Thanks to all who have considered and replied. But as I think about it
more, because all my simple setup cares about is executing macros when
dawn/dusk occurs, the output shown on a wall clock seems irrelevant.
Indeed, our agreement to observe DST does not change the time when
dawn/dusk really occurs (in a celestial sense). It only changes how we
agree to map our clocks' readout in relation to dawn/dusk.

Looking carefully for the first time, this is shown in the data on the
Statistics dialog. When DST is NOT checked, the times shown for
dawn/dusk change for every list entry in a fairly smooth and regular
progression/regression. However, when DST is checked, a large (1 hour)
discontinuity in this pattern is introduced at the points where DST
starts and ends. This just handles the difference between the DST state
when the macros are downloaded and the DST state when the CM11A's
interface clock is set.

If I lived in a state like Arizona (I live in Washington state) which
does not observe DST, I would always be on "standard" time and dawn/dusk
triggered macros would still run fine. So it seems to me that if I simply:

(a) uncheck the DST box,
(b) download my marcos into the CM11A,
(c) ensure that the time on the CM11A is set during a period when my
computer is NOT on DST, and
(d) disconnect the CM11A from my computer (which it is unless I am
changing something)

I should be just fine. The CM11A's internal clock will be on "standard"
time and the macro triggers will always be relative to "standard" time
(according to the Statistics dialog). Since everything in my simple
setup happens only relative to dawn/dusk times, everything should be
consistent.