Print

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

[WinS]

For some time I have experienced random "on"
problems, where an appliance module would
come on for no reason.  Sometimes the lamp
would light and sometimes just the status in
AHP would change to "on".  After much
analysis and hair pulling I have duplicated
the problem at will.  Perhaps the info will
be helpful to others with similar experiences.

I found that the module that errantly turns
on always has it's timer set, and is
triggered by a macro which is supposed to
trigger a different module (and does).  But
only that same module always has the problem
and the problem always involves the RF
triggering of the unrelated macro (by a
remote control or a motion sensor).  If I
build an identical module, set it's timer,
and turn off the timer on the original
problem module...the new module then comes
"on" to the unrelated macro.  The most
recently built module with timer set is
always the target of the phantom signal. To
fix the problem, I created a "dummy" module
with timer, and set the HC to one not
transceived by the cm15a.  Now the false
signal goes into oblivion and no more false
"ons" occur, except for the status indicator
of the "dummy" module.

I know, there seem to be a lot of conditions,
but when you have motion sensors triggering
macros, this happens quite often.  What I
don't know is whether it is related to the
cm15a (why is it always the last module built
with a timer?), or just some weird fault in
my environment.

I would appreciate knowing I'm not the only
one with this specific problem.

[rob]

Umm, I'm lost ;-)  Can you post a simpler
step-by-step configuration?

[WinS]

Additional and probably critical information
regarding this odd problem: It appears that
when an RF source signal, such as a remote
control or motion sensor, is within range of
both the cm15a and an RF repeater, the
duplicate signal to the cm15a causes the
phantom "on".  Yes, this may be a case of
overlooking the obvious, but I never thought
a duplicate signal (which registers in the
activity log) would create a problem.  All of
the criteria listed earlier still applies.

When I isolate the RF repeater (a large metal
pot with cover works well), no duplicate
signal is received and no phantom "on" occurs.

A response from X10 would be appreciated to
the following:

1. Why would a duplicate signal become a
problem for the cm15a under certain conditions?
2. Because a remote control is portable by
intent, how can you not be within range of
both units at times?

[WinS]

Rob
Re: I'm lost.

Quite understandable - I've had that lost
feeling for some time.  My setup is nothing
unusual - a few macros pointing to modules
and a few modules, some with timers.  This is
really peculiar and difficult to follow, but
is obviously related to the RF repeater
adding a second signal to the cm15a. The
phantom "on" signal only affects a module
which is set up to come on with a timer.  It
seems that the last module to have it's timer
set up is the target for the phantom signal.
I have no idea why.  That's why I set up a
"dummy" module and set it's timer - now it
gets all the phantom "on" signals and the
rest of the system works.

I sent activity logs to X10 illustrating the
problem, and a log of normal operation when
the RF repeater is disabled.  I'm hopeful
they can come up with something.

Thanks for your interest.

[danno]

I believe I have the same sort of a
problem.  Macro M11 triggered by a Hawkeye
motion detector turns A9 on and then off
after a delay but B5 gets turned off also
after the delay.  B5 does not appear
anywhere in the M11 macro, only A9 does.
It's been driving me crazy trying to figure
out why this is happening.  Not sure how or
why your method gets around the problem and
I'm not sure I understand how I would
implement it in my case.

[X10 Pro]

We're looking at the data Win S sent us, and
hopefully should have some more understanding
of the problem soon.

[kc]

The phantoms are still out there.
AHP had been running fairly well till I
added a new macro. Using a timer triggered
RF macro (M4 on) to turn on a lamp module
(A16) that was not working on the powerline.
Another timer triggered RF Macro (M4 off)
dims A16 25% delay of 5 min then turn off
A16.
The M4 on macro worked fine. The light came
on at its appointed time.
The M4 off did not dim A16. It turns on
another module A5, and 5 min later turns off
A16.
Checked the macros for errors, cleared
memory and reloaded file. Next day the same
thing happened.
Loaded an empty file into the CM15A, cleared
memory and reloaded the data file again.
This time it seemed to work. I'll see what
happens tonight.  

[jerry r]

I too am having similar problems when running
macros triggered by eagle eye rf sensor.
I am NOT using the rf repeater yet (on order
though). What happens to me is the macros
don't always run and other devices get turned
on too.

Using 3.174 and the additional macro plug in.

Could any of this be noise on the lines, also
on order is the x10 meters to check signal
and ac quality.

[WinS]

I stumbled onto something interesting
regarding this phantom problem I have been
having.  Today I built a new macro (M10 on)to
turn on the Xmas lights on 12/25 only at 0700
and another (M10 off) to turn them off at
2200. When I use RF (from a remote or motion
sensor) to trigger another macro (M11 on) to
turn on a test lamp, it works but  the Xmas
lights also turn on (phantom). This happens
every time unless I add a 5 sec delay to the
M10 on and off macros. With the delay in
place no phantom appears anywhere in my
system from any macro using RF from a remote
control.  If I delete the 5 sec delay the
phantom reappears...so I leave it in.

Maybe others could use this info to test
their particular phantoms. I'm still thinking
that my phantom is related to the RF repeater
in my system and the last timer/macro built.
The repeated commands should not cause a
problem, and is indicating a weakness in the
HW/SW.