X10 Community Forum
🖥️ActiveHome Pro => ActiveHome Pro General => Topic started by: ryan on August 10, 2005, 10:47:50 PM
-
This is a new problem it seems for me. I
have an On Macro and Off Macro assigned
to "J". If I press the macro buttons
within the software, everything is great.
However, if I press the On macro by remote,
both the On and Off macro's are triggered -
both bottons in the software blink.
The Off Macro works fine with the remote
without affecting the ON.
Please help. I am having company this
weekend and this killing me.
-
I had same problems. I believe it is a no
cost, undocumented feature of AHP.
-
When you press the On macro trigger on the
remote, do both sets of macro events actually
run, or is it just the buttons on screen
flashing?
-
They both run half-way it seems. The on
and off macros are sending signals to the
same lights - just opposite signals. So it
is kind of hard to tell what it is actually
doing. It certainly is not working the On
Macro to completion.
Thank you for the response thus far!
-
I am experiencing the same problem.
I have a light switch, an ON macro, and an
OFF macro, all on K4. The ON/OFF macros
contain nothing but the light switch. The
macros are triggered by signals from a
TM751, which in turn picks up the light
on/off signal from a wireless remote.
Attempting to turn the light on results in
the light coming on for one second, and then
it switches off! This happens when using the
remote, clicking the AHP switch icon, and
the AHP ON macro.
I replaced the off command in the OFF macro
with a dim 50% command, and the light dimmed
instead of going off.
I've cleared the CM15A memory, restarted my
PC, reloaded the macros, deleted and re-
built the macros, and the result is the same.
I running Windows XP SP1, and I have a
diagnostic CM15A.
Bob
-
X10 Pro,
Have you been able to reproduce this
problem?
Is there a workaround until a fix is
available?
Thanks,
Bob
-
X-10: A clue to a more annoying problem?
I usually see double blinking (but not
always) when the "On" macro is initiated.
An "Off" command seems to only blink the
off macro.
Most macros are carried out correctly, but
I have found one "on-off" set to eventually
STOP ALL TIMERS AND MACROS(a common problem
that the hardware has often been blamed
for.)
Could the macro's usage over time be
causing the eventual system crash many of
us experience? Just a thought...
-
I have had the same problem and never was I
ever able to make the macro work.. The CM15A
is junk and x10 knows it. No response from
repeated emails asking for help. Have you
lost your timers yet when the power fails,
watch what will happen to new batteries.
Buy a smarthome timer instead.
-
Same thing here.. just installed it all and
adjacent ON and OFF trigger macros both run
at the same time... repeated playing with the
macros seems to cause the CM15 to freak out
and finally stop responding entirely to any
commands including simple on and off commands....
Does any one have a solution?
Wayne
-
Perhaps the question should be: Does X10
have a solution?
-
OK... after a call to customer support it
appears that it is the RF Palm Pad that is
causing the problem. ( I don't understand
why but they claim that it generates an OFF
command first and then generates the ON
command when an ON button is pressed) The
problem does NOT happen with the hard wired
remotes on the same house and unit codes,
only the Palm Pads cause the problem.
I also had random lights coming on and going
off, and at one point had one light cycling
on and off by itself. I let it run for an
hour before pulling the CM15. And, when the
CM15 was plugged in it would get all
confused with commands coming from the Palm
Pads interrupting regular on and off
commands that had nothing to do with Macros.
I called X10 and requested a return
authorization. I am back to using my CM11
which has been flawless for the last four
years.
In my opinion, the CM15 is not ready for
market.
-
Sounds like a signal collision. When you
send an on/off signal with the palmpad, it
signals housecode/unitcode,
housecode/command, then repeats. The TM751
happily relays these signals to the
powerline no matter what other devices are
trying to transmit at the same time. If the
AHP interface is transmitting at the same
time as the TM751 is, you most likely end up
with a corrupted signal on the powerline.
Does it work correctly if the first step in
your macro is to wait for a couple of
seconds?
Tom
-
Tom:
I didn't try a wait as the first step of the
macro. But why would the same macro work
when I use the hard wired remote on the same
house /unit code, and not when it was
triggered via the RF Palmpad?
Also, a simple on command from the Palm Pad,
one that had no associated macro in the
CM15, would cause that light to go on , and
then a couple of seconds later it would turn
off? If I disconnect the CM15 and connect
one of the older Transceiver only units that
same simple on command works as it should.
And finally, why do all of the same macros
work on the CM11 with the RF Palm Pad but
when I use the CM15 I get the Macro On and
OFF symptom mentioned in this forum?
-
Can someone verify the earlier X10 customer
support statement?
"they claim that it generates an OFF command
first and then generates the ON command when
an ON button is pressed"
When I look at the activity monitor, it only
shows the ON command. Incidentally, when I
press the OFF key, the activity monitor
displays the OFF command, but it doesn’t
trigger the OFF macro!
Bob
-
Wayne-
Wireless remotes take longer to transmit
signals than the plug-in units, and the
CM15a starts running macros more quickly
than the CM11a. The resulting signal
collisions can do strange things.
If you remove the macro and the Palmpad
still behaves this way, I'd guess you have
another wireless receiver in the mix.
Either disable that housecode in AHP or
unplug the other wireless receiver to avoid
the signal collision.
Tom
-
Tom:
Thanks for your time and help on this... I
did use one of my old tranceivers as the
CM15 range was not as good as I was getting
with the seperate transmitter and the CM11
combination. However, I did have the RF
reception diabled on the CM15 so that there
was only one RF receiver inthe system. In
anycase, I decided to go back to using the
CM11 as it has not given me any problems for
the last four years... I just have to keep
my programming really tight!
-
The funny thing is, you never really disable
RF reception on the CM15a, you just disable
RF to AC line transmission. Consequently,
you get this:
/TM751 -> Powerline
RF signal-> and
\CM15a -> Run Macro -> Powerline
The result: 2 powerline transmitters are
sending at the same time.
To really oversimplify things, x10 codes are
a timed series of 0s and 1s. If one
transmitter is sending 1001 and another
overlaps with 0110, it comes down the
powerline as 1111. If the corrupt signal
works out as a valid code, you might well
trigger another device or cause the CM15a to
run an entirely different macro...
The CM11a escapes the problem because it
isn't as fast to respond as the new unit is.
That's why I suggested the delay at the
start of your macro, to "emulate" the delay
on the CM11a.
In any case, I can understand you just
wanting to go back to the CM11a. Mine was a
workhorse. Too bad it can't be upgraded to
support conditional macros (without
dedicating an always-on computer, or building
a dedicated "controller-controller", that is)!
Tom
-
Looks like the message board software
reformatted. Let me try that again:
> /TM751 -> Powerline
>RF signal-> and
> \CM15a -> Run Macro -> Powerline
-
Tom:
Brilliant! Thanks for the insight... Now it
makes more sense and I hope that this thread
will help any others who have been
experiencing the same problems...
Wayne
-
What a great thread. It got me to realize
that AHP can monitor different codes and it
got me to unplug the other RF modules I have.
I very please except that now I need one more
condition option that AHP won't let me have.
The problem is that a macro will trigger with
Code On but it won't work unless I also use a
condition saying that if a certain module is
on. This is preventing me from use the two
condition of "after dusk" and "before dawn."
Any suggests?
-
Ok, I found what I was looking for in the
"The time is between" option. In there you
can say between dusk and dawn.
Good news for what I'm trying to do.
-
Well, it worked once as I expected. :(
-
i am having the same prob with my PRO
unit... macros freeking out i will push one
on switch in the software and many
different macros ( ie b2,b3,b4) will all
start flashing., on's and off,s i have
been a big supporter of the previous ahc
but the PRO is a POS..! it runs * or is
supposed to run ) my 500 gal aquarium
setup, and all my outside lights on my
house... my wife hates it...help us!!!