You might find some useful tips in one of X-10's FAQs...
http://www.x10.com/support/x10trou.htm#on
Inductive spikes from fluorescents and brown-outs are among the causes.
Bruce: Most Smarthome switches and modules (even the low end ones) send
off commands or preset dim commands indicating the current level whenever
there is a change of state. This has been the case for 3-4 years now.
> The X10 Pro line does not generate a signal under any condition - they
> are receive only devices. Higher end switches from Leviton and Smarthome
[quoted text clipped - 63 lines]
>>>>
>>>> Thanks.
BruceR - 12 May 2008 02:07 GMT
> You might find some useful tips in one of X-10's FAQs...
>
[quoted text clipped - 7 lines]
> whenever there is a change of state. This has been the case for 3-4
> years now.
Right, I didn't mean to exclude remote operation but the OP was
specifically asking about manual operation. The only Smarthome
manufactured switches that are currently in their catalog are their
Insteon switches which are also X10 compatible.
dlh - 12 May 2008 11:38 GMT
> Right, I didn't mean to exclude remote operation but the OP was
> specifically asking about manual operation. The only Smarthome
> manufactured switches that are currently in their catalog are their
> Insteon switches which are also X10 compatible.
In X10 mode, they report changes even with manual operation or with
things like bulb failure.
Thanks for all the responses.
I had another XPS-3 that has been working perfectly on another circuit.
So I took your advice and swapped the two switches. I find that the
problem does NOT follow the switch. So there does seem to be an issue
with the circuit in question.
Thinking that there may be stray commands passing, I have been running
version 1.42 of ActiveHome (which seems to fix other strangeness I have
been seeing when running version 1.32 on Windows XP) and watching its
communications log. I am not seeing any unexpected commands being received.
So perhaps it is noise as you suggest. But if, as you say, the noise
should not generate on/off commands, how could it be impacting the
XPS-3? I bought these switches precisely because they are supposed to
handle fluorescents. Can I tell if the fluorescents are the cause simply
by removing the tubes? Or will there still be noise from the ballasts?
Is there anything I can do about the noise save removing the shop lights?
Thanks.
> The X10 Pro line does not generate a signal under any condition - they
> are receive only devices. Higher end switches from Leviton and Smarthome
[quoted text clipped - 64 lines]
>>>>
>>>> Thanks.
BruceR - 13 May 2008 06:32 GMT
Try running each fixture alone to see if you can isolate the problem to
one or the other (more likely the flourescent). If that's the problem
you can use an in-line filter at the fixture to remove the noise. If the
fixture is really old changing the ballast may help although it's
usually cheaper to buy a whole new fixture than a ballast.
> Thanks for all the responses.
>
[quoted text clipped - 87 lines]
>>>>>
>>>>> Thanks.
dlh - 13 May 2008 12:58 GMT
The switch mode power supplies used in CFLs frequently output continuous
noise in the band used by X10. This tends to block X10 operation -
frequently allowing you to turn them on but preventing you from turning
them off. Filters between switch and fluorescent can address this.
Such noise does not generate phantom commands. (There are a few monkeys
typing away furiously and randomly at their keyboards who dispute this.)
Monitoring the line with an X10 interface (e.g. CM11A) can detect valid
commands but will not detect random noise. I have monitored using methods
that will show noise and detected nothing at the time such phantom events
occur. My events were caused by spikes when a particular fluorescent was
operated - replacing the LM14A with an Insteon/X10 module cured it.
Older fluorescents with magnetic ballasts can generate spikes on the
powerline when turned On or Off. The spikes can cause some X10 switches
and modules to turn on or off. Some switches can be modified to address
this. See...
http://groups.google.com/group/comp.home.automation/msg/62d41d8a36fef5ea
The trickle current of the local control feature can cause lamps
(especially fluorescents) to turn back on shortly after they are turned
off. Local control can be disabled but the specifics vary from one model
to another.
> Thanks for all the responses.
>
[quoted text clipped - 87 lines]
>>>>>
>>>>> Thanks.