New Problem -- Cannot Control SOme Devices
Bookmark this page:
 Yahoo!
 Google
 Windows Live
 del.icio.us
 digg
 Netscape
|
|
||||||||||||||||
|
Posted by Johnnie on July 5, 2007, 8:46 pm
Please log in for more thread options controller. Normally, this would indicate a problem bridging the 2 sides of a 220V line but I had no trouble for over 4 years and this just started. I also have the home security system (which handles the wireless controllers) and several wired controllers and none of them have any problems getting to all the devices! Any troubleshooting suggestions? | ||||||||||||||||
|
Posted by Charles Sullivan on July 5, 2007, 10:41 pm
Please log in for more thread options If you can't control _anything_ with your AH controller, it may have died. But if it's just certain devices, think about any electronic equipment you may recently have acquired (TV, DVD player, Cell phone charger, etc.) which has a switchmode power supply. Many of these devices will introduce noise on the powerline or have heavy capacitive filtering ("signal sucker") which will attenuate the X10 signals. To test, unplug suspected devices from the wall - merely turning them off isn't sufficient. If you identify an offending device, get an X10 noise filter and plug it in between the device and the wall socket. | ||||||||||||||||
|
Posted by Jeff Volp on July 5, 2007, 11:47 pm
Please log in for more thread options The fact that you comment about bridging leads me to believe you might not
have some sort of coupler already installed. While many get by without a coupler - we did for many years - the signal strength on the second phase is probably marginal. It doesn't take much loading to reduce it to the point that reliability suffers. So, if you don't have at least a passive coupler, certainly add one. And then considering filtering any potential problem loads. I wrote some tutorials that may help: http://jeffvolp.home.att.net/x10_info/x10_troubleshooting.htm Jeff > All of a sudden, I can not control several devices from my Active Home
> controller. Normally, this would indicate a problem bridging the 2 sides > of a > 220V line but I had no trouble for over 4 years and this just started. I > also > have the home security system (which handles the wireless controllers) and > several wired controllers and none of them have any problems getting to > all > the devices! > > Any troubleshooting suggestions? | ||||||||||||||||
|
Posted by BruceR on July 6, 2007, 3:57 am
Please log in for more thread options Jeff is being modest. Just buy his XTB II and all your X10 troubles will
be over (unless your ActiveHome died). It's the hottest X10 compatible product to come out in 20 years. Jeff Volp wrote: > The fact that you comment about bridging leads me to believe you
> might not have some sort of coupler already installed. While many > get by without a coupler - we did for many years - the signal > strength on the second phase is probably marginal. It doesn't take > much loading to reduce it to the point that reliability suffers. So, > if you don't have at least a passive coupler, certainly add one. And > then considering filtering any potential problem loads. I wrote some > tutorials that may help: > http://jeffvolp.home.att.net/x10_info/x10_troubleshooting.htm > > Jeff > >> All of a sudden, I can not control several devices from my Active
>> Home controller. Normally, this would indicate a problem bridging >> the 2 sides of a >> 220V line but I had no trouble for over 4 years and this just >> started. I also >> have the home security system (which handles the wireless >> controllers) and several wired controllers and none of them have any >> problems getting to all >> the devices! >> >> Any troubleshooting suggestions? | ||||||||||||||||
> controller. Normally, this would indicate a problem bridging the 2 sides of a
> 220V line but I had no trouble for over 4 years and this just started. I also
> have the home security system (which handles the wireless controllers) and
> several wired controllers and none of them have any problems getting to all
> the devices!
>
> Any troubleshooting suggestions?