Macros doing things not in the Macro

[bill slusser]

I am a VERY long time x10 user. Upgraded to
Active home pro and now, (imported AH file)
several of the more complicated macros will
turn something on that is not in the macro
or not turn something on that is. The item
will always turn on or off manually or from
the AHP interface. Hmmm. One of the more
problamatic macros, re-created from
scratch. It still does the same thing. I
have put delays between the steps, one of
the items that it turns on (it is fairly
consistent) is not in ANY macros.

[jim lytle]

I'm experiencing the same symptoms as
Bill.  My macros are faily straightforward,
but I consistantly get phantom commands
when they execute.  The phantom commands
are consistant, always the same.

I've experienced this from day one (two
upgrades ago).  I'm using Windows XP and
I've upgraded to 3.178.

I'm a long time user of the CM11A and this
upgrade has truely great potential, but I
share the view of many in this forum that
it wasn't quite ready for prime time when
it was released.

I'll hang on though for another upgrade or
two.  I have two more weeks before my 30
day return offer runs out.  

[roger1818]

This is a known bug.  Commands that follow
a dim command seem to create phantom
commands.  Try not dimming any modules in
macros that are causing you problems.  This
should temporarily fix the problem until
X10 fixes the bug.

X10 Pro:  Any update on the status of this
bug fix?

[X10 Pro]

Bill Slusser & Jim Lytle: Can you send the
.AHX files with the macros that show this
problem?

[jim lytle]

Thanks for the response Roger H, but I
don't have any dimming commands in this
macro.

I have sent the file to you X10 Pro, as
requested.  

[jim lytle]

Thanks for the response Roger H, but I
don't have any dimming commands in this
macro.

I have sent the file to you X10 Pro, as
requested.  

[jim lytle]

Thanks for the response Roger H, but I
don't have any dimming commands in this
macro.

I've sent the file to you X-10 Pro, as
requested.  

[X10 Pro]

We found a bug related to macros that start
with delays that was causing this. It will be
fixed in the next update.