Print

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

[roger1818]

With the current software you can set timers
for individual modules and macros but you
can't set up a timer for one of the all
on/off commands (room, house code or all
modules).  This can be done with the a
macro, but why create a macro for a command
that already exists?

It would also be nice if you could make a
macro "Quiet" so that if the ActiveHome
interface generates the command locally or
it receives it via RF, it wouldn't send the
command on the power line but instead start
processing the macro imediately.  This would
make the macro react faster by almost a
second.  This should be an option you can
turn on or off though as there are instances
where you might want to send the marco
command on the powerline.

[donald mcmow]

The reason for transmitting your commands
(RF/PLC/MACRO) is that you may have other
modules on that address that need to
respond to that command. And on top of that
it would require more memory to remember
what commands are to be transmitted and
which are to be ignored - not an efficent
use of memory. Or do you want your computer
hooked up to the CM15 ALL of the time (on
and running AHP).

[roger1818]

I agree that some users might want to
transmit the command (you will notice I
said that in my original message).  I don't
see how using one additional bit per macro
(I am sure there must be a spare bit in the
macro header) is an inefficient use of
memory.  Even if they had to alocate an
extra byte the theoretical maximum number
of macros is 512 which would be 0.5kB in
the worst case (not too likely though).

If this is too expensive, a global option
could be available to indicate if you want
to transmit the macro command.  This would
only use one bit total.

To answer your outher question, no I don't
want to have my computer running ActiveHome
Pro all the time.