[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: Older Active Home (v 1.3) / DST Question

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).

 David White wrote:
> Knowing that the dates for DST are changing in the US, I have been
> trying to figure out if I need to do anything (or can do anything) in
> my old Active Home setup.
> I have a simple setup and only run macros from the CM11A module which
> is not connected to my PC. My macros only run in relation to
> Dawn/Dusk. I don't have any that are driven by specific times.
> Do I need to change anything? It would seem that dawn/dusk does not
> care about DST and such. So I would guess not. However, I did have
> the DST checkbox checked when I downloaded macros into the CM11A. I
> have no idea how the CM11A works so maybe I do have to make some
> changes.
> It seems that the UI of Active Home will permit me to manually enter
> dates for begin/end of DST. The values shown today do not correspond
> to those shown in my Windows setup (which has already been updated to
> reflect the change in DST) so I presume that Active Home does NOT get
> its info from Windows - or at least not directly. I'd rather not have
> to manually change this year in and out. So if any changes are
> needed, if this can be avoided, that would be great!
> Thanks for you input/help.

alt.home.automation Main Index | alt.home.automation Thread Index | alt.home.automation Home | Archives Home