RE: Dusk/Dawn - before and after

[Jon Whiten]

Not good for day 1, but for the pre-dusk (or pre dawn) why not create a
determinator that suspends for 23 hours 30 minutes. Not as accurate as
"dusk - 30 mins" but would it be close enough?


Regards

Jon Whiten
<a href="http://www.whiten.co.uk";>http://www.whiten.co.uk</a>
-----Original Message-----
From: John B [mailto:<a
href="/group/ukha_xpl/post?postID=jH-LdKeQEbGacYfZVE6wXMH2X6HKPs5-o1wXyP3RPMzy9CEbKBmnzDAVHAke6_qlnkMcCCAqGqNUG3u60zy1YX2prShiIf4I">home-automation@j...</a>]
Sent: Wednesday, April 28, 2004 5:31 PM
To: <a
href="/group/ukha_xpl/post?postID=e1RLsRsD4LcJRalauJHU2123bVasAtREmHGRjRbqjgX5huVFitQun1r6d0aMk5XvJc2tq_qRxyBA0CZZ9KnVMQ">ukha_xpl@xxxxxxx</a>
Subject: RE: [ukha_xpl] Dusk/Dawn - before and after

> > > In Homeseer I've 3 events based around a "dusk
time" - an event
> > > that is dusk-30mins, an event at dusk and a further event at
> > > dusk+30mins.
> >
> > We'd need to add an option to trigger pre/post dusk/dawn
messages.
> >
> > Makes sense, never thought of that before!

The post-dusk messages can be done at present:

Detect the dusk trigger and set an event to occur 30 minutes later.

You can do this either using VBScript, or by creating a determinator that
suspends itself for 30 minutes when it's triggered.

The pre-dusk events can't currently be replicated without changes to the
dawn/dusk code.


<SNIP>