Print

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

[mk]

Hi,
I apologize if this question has already
been posted, I could not find it in the
list.  I just got ActiveHome Pro and set it
up today.  I created a few simple macros to
turn on a couple of lights, some fades,
just to get started.  When I run the macros
from my PC they work fine.  If I hit the
corresponding trigger button on a remote,
the macro flashes on the screen in
ActiveHome as if it were running, but
nothing happens.  If I let my mouse hover
over the icon that shows the log, it
confirms that the signal was sent.  I've
tried changing the triggers to different
codes, unplugging the unit from the
USB/wall and back in.  Is there a step that
I'm missing or is there a problem with my
hardware/software?  Thanks!

[anonymous]

MK, make sure that the CM15A is set to
transceive the houscodes for the devices
and triggers that you are using.  Check
the 'Tools > Hardware Configuration'.  You
might have to set them to 'specific' and
check the appropriate boxes in
the 'transceived house codes' section of
the configuration screen.

[hs]

I am also just installed the application and
I am having a similar problem. I have the
transceiver house code on auto, although I
am only using housecode A (which is checked).

When I have a created macro configured
to 'Run on PC',  and the trigger is
received, the macro flashes as if it were
running, but then it does not output
commands to the modules.

If I manually run the macro by clicking it,
it works correctly.

If I 'Store the macro on interface', it
works correctly.

Can anyone please advise?

Thank you.

[hs]

I read another users comment where he stated
that the macro must be saved or it will not
work. Tested. Still does not work. It seems
that running from the 'PC' has a bug of some
sort.

[hs]

After reading more comments from other
users, it seems pretty obvious that other
users are experiencing the same problem.

I am using version 3.183 so I cannot comment
on previous versions.

Here is a post from another thread:

"Unlike most people so far, I have found
this  version to be worse than previous
ones.  This  is not the first time this has
happened.    I have motion sensoprs that
trigger simple  macros e.g. turn on a light,
turn off a light  after receiveing an off
signal from the  motion sensor.    The
actiivty monitor for the senosr shows  that
the signals are being received but the
specified action is just not happening.
This  was a smaller problem with the last
version  and seems to be worse now.
Signals are being received by the unit and
then nothing happens so it is a software
problem not a signal reception issue.    I
have not seen any improvement since 3.179
and many things have gotten worse."

[joe s.]

Here's a couple things to try if you
haven't already - try the cold/hard
reboot/reload described by tuicemen in the
thread: "Monitored House Code".  A number
of people believe the CM15a doesn't clean-
out code very well.

And during the reload, switch from "auto"
to "specific" on tranceived
housecodes...and manually check "A" (if
that's the housecode you're transceiving).

[X10 Pro]

Triggering a macro that runs from the PC and
triggering a macro stored in the interface
are very different. In the first case, AHP
processes the trigger and sends the commands
contained in the macro out through the CM15A
one at a time, according to the schedule in
the macro. When a macro is stored in the
interface, the trigger tells the CM15A to
look up the macro data, which is then
processed and executed inside the CM15A.

For a macro stored in the interface to be
triggered, the trigger (A1 On, for example)
must be on one of the Transceived House
Codes. So, if a stored macro isn't executing
when you use a remote control, that's the
first thing to check.

I'll have to check on the execution of a
macro stored in the PC in this version.

HS: How are you triggering the macros that
aren't working? What commands do they contain?

[martin]

I have my Transceived House Codes set to
automatic and it only shows F since I’m
using two TM751 for house code A and E as
part of my AHP configuration (because of the
poor RF range on my CM15A, about 12 feet).
All my macros on A and E are triggering just
fine from remote controls / motion sensors.

[hs]

x10Pro,

I am running the following Macro:

Trigger Conditions A1 On and
It's After Dawn
End Trigger Conditions
WAIT for 5 seconds
Turn New AM486 OFF

AM486's code is also A1.

So basically this is just a little test
macro I wrote to test triggers and sending
of data. If A1 is turned on, and it is after
dawn, then wait 5 seconds and turn A1 off.

I have an X-10 keypad/timer plugged in the
wall to trigger the macro.

As I mentioned, when the macro is stored on
the interface, it works correctly.

If I manually click the macro with the mouse
(assuming A1 was on when it was clicked), it
works correctly.

When the macro is run from the PC, and I hit
the button on the other keypad, I see that
the Macro is triggered, but the A1 Off
command is never sent.

I am guessing that you should be able to
find this problem quickly since we know the
macro is firing, but it is not sending the
command after the 5 second wait.

I did clear the interface memory to make
sure I was not doing something wrong.

Please let me know if I can be of further
help.

[X10 Pro]

HS: You're right this problem should be
pretty easy to track down. It's not a problem
with the interface, but with how AHP is
processing incoming trigger for a PC macro.