Print

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

[Danny Rego]

I would LOVE to see the ability for you to
trigger a macro from within another macro.

Also (along the same line), I would love to
have an ALIAS feature where you can have
X10 Code A1 control the same appliance/lamp
as M12...including dimmer commands.

While I'm at it...why not have the
DIM/BRIGHT commands be useable by macros?

[steven r]

It can. I've built a conditional macros
that are called from within other macros. I
don't know if you have to have conditionals
to make it work.

[Danny Rego]

You must, because I don't see that ability
anywhere?!  I can't drag a macro into a
macro...bah!!!  Don't tell me I have to
waste my $$$ on that module.  (the price
makes me mad)

[steven r]

For each macro you wish to call, you will
need to make a dummy module.

e.g. If you want to call macro M1, make a
dummy module M1. Drag the dummy module M1
in where you you want to call your macro
M1. I believe a delay is helpful before or
after the call.

I have a macro that shuts off my lights and
appliance modules. It then calls a
conditional macro to turn the front porch
light back on if it is between dusk and
midnight.

[Danny Rego]

Well...that's bloody stupid, and there
should be a nicer interface for doing this
stuff.

We shouldn't have to HACK good/usefully
functionality in there.  X10 should add it
in properly.

Thanks for the info though.  I will try it
soon.

[steven r]

I don't think it was a planed / supported
feature to be able to have macros within
macros.

Be careful not to create and endless macro
loop by calling a macro that calls the
original macro. Unless one of the macros is
a conditional macro, you would need to stop
the loop yourself.

[steven r]

"planed" should be "planned" and
"and" should be "an" in the previous
message.

[Danny Rego]

That's why I thought I'd bring it up here.
It's a very useful feature to have, and
they should add it to the software
OFFICIALLY.  (instead of us having to do
this hack-around)

Thanks again for the info though!

[h j flynn]

There was a post sometime ago from X10
support about this, they stated the
currently they did not support MACRO's
Calling MACROs. It just happens to be
working, until someone reports a looping
problem, They may decide to plug the hole.  

[Danny Rego]

I can't get the macro from a macro hack
working at all.  I am becoming very unhappy
with my CM15A.  I have two different
remotes, running on seperate house codes,
and I want to share two rather lengthy
macros between them....that's all.  It is
really stupi that I have to make two
copies, just to do that.

I know about the trick where you setup a
SWITCH module with the same code as your
macro...but it as much as the windows
interface shows everything happening,
nothing actually gets switched in the house.

Buying this X10 product was a big mistake.
I can't trust it to run any sort of macro
reliably.

[Danny Rego]

Can anyone help me with my problem???  I am
going crazy here!!!  I am getting  so mad
with AHP it isn't even funny.  Please
follow what I'm writing and point  out
anything I may be doing wrong.

- I set up a BIG FANCY "ON" macro for code
M1.
- I set up a BIG FANCY "OFF" macro, also
for code M1.
- I add a simple switch module that also
uses code M1.

I click the switch module on/off in the
windows app, and the proper macro
runs...all is well (so far)

- I create another SIMPLE "ON" macro for
code A1, that contains one module the
switch (M1) I created above, and tells it
to switch on.
- I create another SIMPLE "OFF" macro for
code A1, that contains one module the
switch (M1) I created above, and tells it
to switch off.

From the windows interface again, I click
the A1 macro on/off, and voila....my BIG
FANCY M1 MACROS execute.    Now the
kicker...I setup a palmpad unit to  send
the A1 ON/OFF signal.  I press A1  on....I
see the windows interface light up  like a
christmas tree, where everything  appears
to have worked, however, NOTHING  HAS
ACTUALLY TURNED ON OR OFF!!!

What the hell am I doing wrong here???  I
just want to setup two palmpads that are on
seperate house codes to execute the same
complex macro.

HELP!!!

[David Mark]

>>I add a simple switch module that also

No.  Just click the macros to test them.

>>I  just want to setup two palmpads that
are on  seperate house codes to execute the
same  complex macro.

You are making it too hard on yourself.

Start with one PalmPad.  Set up the macro
and test it by clicking it.  If the lights
do not go on or off, see if all of your
macros are suspended.  If so, stop and
start AHP.  That always restarts the
malfunctioning macros here.

So now that you have one macro working,
test it with the PalmPad.  Add the second
macro with the other house code.  Add the
same lights and appliances, etc. just like
the first macro.  It is unfortunate that
the edit menu in AHP has no commands for
editing (eg cut, copy, paste, select all,
etc.)  Odd indeed.

Anyway, forget any ideas about nesting
macros.  This controller has horrible
problems with just the basics.

[Danny Rego]

All I want to know is, what's the
difference triggering by clicking the
palmpad, or clicking "run macro" in the
windows app?!  They both APPEAR (in the
windows app) to trigger everything fine,
but the one from the palmpad doesn't
actually work.  (it just looks like it
does?!)

[David Mark]

The software sucks!  Are you new around
here?

[kc]

I got the nested macro thing to work, but
it hasn't done any recursion.  I have
conditions set (time between x & y).  How
did the recursion get activated?  Did you
have to start with a simple macro, then
call a conditional one? Can the macro still
be recursive (provided conditions for this
rumor of looping to infinity) if it's not
downloaded, so that it can be tested?