Print

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

[tom h.]

The macros only send commands that are
different than the current status of the
device. I.e., if it thinks a lamp is already
on, it skips sending that command, even if
in fact it is off.

I have set up my macros to always do the
opposite first, than what I request. (To
turn 3 lights on, I turn them off first,
then turn them on.) This ensures that the
appropriate command is sent, regardless of
the current status. This works, but takes
way too long!

Can you include an option to always send the
command, regardless of its current status?
FYI, I can see (or not see) the commands in
the Activty Monitor.

[X10 Pro]

Tom H: Do you see this behavior when clicking
the "Run Macro" button in the software, or
when triggering with a remote control? Or is
it both?

[tom h.]

FYI, I do not have Smart Macros;
I do not have 2-way modules.
I have redone my Macros as follows:
M8-On turns on lamps M1, M5, M7.
M8-Off turns off lamps M1, M5, M7.
I have removed all duplicate, opposite and
delay commands. I selected Store in
Interface for both, then Download Timers and
Macros.

It seems to always issue the full 3-lamp
command when triggered from a wired mini
remote control. If the "Run Macro" button is
pressed from the PC, it only issues the
command if it thinks that lamp needs
changing. If I turn on M1 from the PC, then
running Macro M8-On only turns on M5 and M7
(because M1 was already on.)

If I Run Macro M8-On again, it does nothing
(because M1, M5, M7 are already on.)

If I change M1, M5 or M7 locally, nothing in
the PC is updated, so future Macro M8-On or
M8-Off runs from the PC are incomplete.

I don't know, maybe I don't understand the
command structure well enough. I just know
that not all lamps are on or off as desired.

[X10 Pro]

Tom H: I thought that's what was happening.
The "Run Macro" button runs the macro from
the AHP software, not the macro stored in the
interface. The interface always runs the
exact commands stored. When AHP runs the
macro, it tries to be smarter about it and
does as you describe. I'll see if we can add
a preference to disable that.

[tom h.]

Yes, adding an option to send all commands
regardless of current status would be great.

After further testing, I found if I trigger
Macro M8-On from the wired remote, lamps M1
and M7 come on, but not M5. I can always
control M5 locally, pressing M5 on the
remote or pressing M5 in AHP. The opposite
is true when I trigger Macro M8-Off from the
wired remote, it won't turn off M5. The
Activty Monitor only shows M8 was received,
not the separate Macro M8-On commands, so I
don't know if all Macro commads were sent.

Thoughts?

[tom h.]

I reset the CM15A using the unplug, remove
batteries, wait and replug scenario,
then "Clear Interface Memory,"
then "Download Timers and Macros." The
aforementioned macros mentioned below now
work correctly using the wired mini remote
or RF remote. The option to send all
commands from the PC regardless of current
status would still be good.

Does the CM15A only work with RF commands if
they have a macro? Do I need to set up an On
and Off macro for each device that I want RF
control? The RR501 RF Transceiver controls
units directly from RF commands without the
need for macros.

[tom h.]

O.K., I didn't know there is a Transceived
House Code setting under Tools -> Hardware
Configuration. All is well now. Thanks
everyone!