Macro won't transmit codes automatically, only manually

[mark k]

I just bought AHP with Chime and sensor and
created a macro (A4) to turn on chime
(A1).  Simple, right? The macro works
(transmits A1 On code per activity log and
rings chime A1) when I manually mouse click
the "run macro" button in AHP.  However,
when a sensor (A4) triggers the macro to
run, the "run macro" button does flash, but
NO On code is transmitted (per activity
log)  Why??
If the macro transmits On code when
manually triggered, why doesn't it transmit
On code when sensor triggers it?
Any help will be appreciated.
Mark K.

[ajleduc]

Sure would like to know if anyone has figured this one out.
I was working fine and now I have the exact same problem.

Macro works fine if you click on it with the mouse.
When sensor triggers flashes like it were running but nothing happens.

This exact same macro worked last week.

I have tried to remove any changes made since last week.
Also tried many combinations of commands inside the macro to see if something else was going on.

Any Ideas?

[Puck]

ajleduc: Make sure your macros are downloaded to the CM15A; and if your macros have conditions, pressing it with the mouse will bypass the condition and the macro will run all the time.

[ajleduc]

I made sure I downloaded and removed all conditions.
Still no difference.

More info...
I have run this hundreds of times now. 
Sometimes it kind of works.

There are 2 commands in it.
1) turn on camera.
2) turn on phantom switch.

Phantom switch starts another macro to control recording

The macro always flashes when triggered.
There are times when
   Nothing happens
   The camera turns on but no switch
   The camera turns on, switch turns on and recording macro flashes but does not run.
   
What gets me is this all worked perfectly last week.   
I am thinking that reinstalling everything is somewhere in my future

[Puck]

There are 2 commands in it.
1) turn on camera.
2) turn on phantom switch.

Try a Zero-Second delay before the phantom switch:

1) turn on camera.
2) delay (zero seconds)
3) turn on phantom switch.

[ajleduc]

I tried the 0 second delay. 
That didn't seem to help either.

But,
I think I may have found it.
I moved the address from N1 to F1 it appears to work now?
I tried P1, N1 they didn't work F1 seems to work.

I am going to load up my test house and start playing around to see what other addresses work/don't work.

Thanks for the help.
And
Happy New Year!

[Puck]

Thanks for sharing that ajleduc.

What version of AHP and what OS are you running?

I have Version 3.204 and run Win2K. In order for my macros to trigger a phantom switch, I have to place the delay before it in the calling macro.

Happy New Year to you (and ALL) too.

[ajleduc]

I am running version 3.206 windows XP.

I have read a number of posts where placing a 1 second delay in the macro helps.
I didn't realize you could set it to 0.

Anyway I tried both 0 and 1 second neither worked.

I just checked again and its still working OK on F1.

[Dan Lawrence]

If you have AHP version 3.206 you also have On Alert.  That version comes only when you install On Alert.

[ajleduc]

After a bunch more testing F1 started failing just like all the rest.
I finally resorted to reinstalling everything.
Basically deleted everything and started over.

Things appear to be working as they should for now.

[Tuicemen]

ajleduc:
If you start to experiance the same problems try just creating a new AHX file and configure your setup in it some times AHX files get corrupt with installing updates\plug-ins
Always keep a back up of this file!
You may also have an appliance that is sending noise onto the power lines, this will cause all kinds of strange behaviour!