John G: You do need an outside trigger to
start macro execution. You can't just
expect the macro to execute just because
you are testing for a time inside of a time
range. Whether you trigger it from a timer
or from a remote is immaterial, you require
this trigger - something has to tell the
controller what macro to execute. Time
conditions are designed to check to see if
the macro was triggered within the time
range specified - NOT to be executed when
ever the time is between the time range
specified. If that was the case then your
macro would be executing every second
within your time range (ie: from 8:00 to
8:05 (300 seconds= 300 executions) rather
than once if you set off a motion sensor).
Based upon your earlier post It appears
that you are mistaken about how macros are
executed. If you only want a macro to
execute during a certain time frame then
you have to use conditional time range to
allow the macro to execute. The macro may
initially execute outside this time range
(up until the conditions are checked) and
then stop - but there still has to be an
outside trigger. Macros in AHP are event
driven - they will not execute on thier
own - timers, remote controls, motion
sensors, 2-way devices can all cause a
macro to execute. Your conditional tests
dictate whether the commands contained
within the macro will be executed or not.
