Print

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

[j.r.]

When "on" or "dim" command is sent to lamp
module on timer or macro,  Lamp  turns on as
it should but within a sec or two turns off
and then back "on" again and stay "on".  I
have an older X-10 timer controller and when
on command is sent lamp stays on for good,
no on/off before stays on problems.  Any
ideas on what is going on with this new
controller?  Thanks in advance.

[X10 Pro]

What kind of lamp are you controlling with
this module?

[j.r.]

It is just a regular 60 Watt bulb End Table
lamp, with a X-10 lamp module (two
locations).

[X10 Pro]

Are you using a 60-Watt compact fluorescent
bulb, or just a regular incandescent?

[noshali]

I faced the same problem today. The light
turns on for a second and switches off.
Press the button on the remote and the same
thing. Using a socket rocket and a standard
60 watt bulb in a lamp. The lamp was
working fine yesterday.
Today all my timers went on exactly 1 hour
earlier than the time on the timers.

This product has such potential but
everyday there is a new thing.

Please advise if you are facing the same
issues. I'd rather that you face the same
issues and are working on them.

[j.r.]

Noted today using the "Activity Monitor"
that there is a difference between timer
commands and manual commands lines:  When
in timer mode Activity command line
reads "Macro".  And  when in manual mode it
reads "Transmit".  Could this be something
to look into or is it normal?  And yes, it
is a 60 Watt incandescent.

[X10 Pro]

Timed events that are stored in the interface
show up as "Macro" in the Activity Monitor.
Tha's OK, and doesn't indicate a problem.

Here's something to look for: when you
trigger a macro or timer to control that lamp
do you see an Off command following the On in
the Activity Monitor?

[j.r.]

After more troubleshooting, I noticed the
following: The two rooms in question have
an "Eagle Eye" sensor in them.
The Activity Monitor reads as follow:
* Receive RF A16 OFF
* Receive    A16
* Receive    AOFF
* Macro      A5(Lamp)
* Macro      A5 Bright 100%(Lamp)
When I recreate the same commands manually
the following happens:
*Receive   A5(Lamp)
*Receive   AOn(Lamp)
*Receive   RF A16 OFF
*Receive   A16
*Receive   AOff
(No on/off problems) Notice that the
command sequence is reversed, and the off
command is in the wrong Unit Address on
both scenarios.
When I remove the sensor from the room, the
following  happens:
*Macro A5(Lamp)
*Macro A5 Bright 100%(Lamp)
Apparently there is some kind of
interaction between the Sensor and the
Controller.  Wonder why the Rf command is
ahead of the real command.  Please advise.

[j.r.]

?

[Mike C]

Question for x10
"Timed events that are stored in the
interface  show up as "Macro" in the
Activity Monitor.  Tha's OK, and doesn't
indicate a problem."

Is this on the list of things to fix? I have
reported this in the past but have had no
indication as to whether it will be fixed.
Should timer triggered events not show up as
timer and macro triggered events show up as
macro?

[X10 Pro]

MikeC: That is something we will fix. We
should display the correct type for the events.

J.R.: Can you send me (ahpsupport@x10.com)
the AHP file you're using, so I can try to
reproduce the problem here?

[billy-soft]

J.R.

What is the purpose of the MS?  If you have
the MS addressed @ A15 for motion then
light/dark sensor will be reported on A16.
Light=Off, Dark=on, (so it can turn a light
on when it gets dark)

What doew you macro that turns on A5 use as
a trigger? A15 or A16?
It looks to me your using A16 the light/dark
sensor of the MS to trigger your macro.

I beleive that's why you see the sequences
that you do.

Hope that may help!

[roger1818]

This reminds me of a problem I had years
ago where the light in my hallway would
periodically turn off and then back on a
few minutes later.  It turned out that my
motion sensor would catch my neighbor
walking by and turn on the outside light on
C4.  The light sensor would then be
triggered and turn off the light in the
hall on C5.  A few minutes later the motion
sensor would turn off the outside light,
which then made the hall light turn back on
again.  I thought I had configured my
motion sensor to have both the motion and
light sensors on the same unit code but I
guess I hadn’t.  It was a pain to try and
fix, so I just left it that way until the
batteries died.  In the spring I will put
it on a different house code and use a
macro to turn the lights on and off.

[j.r.]

Any luck with the file I sent?