upstatemike
Senior Member
One of my biggest worries when starting my conversion to Insteon was the need to keep X-10 functionality during the transition. I was sure this would be a problem because I had well over 100 X-10 modules installed and most of them were 1-way (PLC or "low suck") devices. It seemed only logical that the 2-way Insteon devices would attenuate the X-10 signals in the house and that at some point during the conversion X-10 would just stop working at all.
Now that I am about 115 devices into the transistion I am happy to report that this is not a major problem at all. In fact I have had only a couple of locations where the X-10 signal was affected at all! Because my Stargate does not do Insteon yet I have had to program any light controlled via motion detector or that that is on a timed schedule, with an X-10 address. Only one has failed to work immediately and this was reolved with a boosterlinc.
The most dramatic surprise came last weekend when I replaced some modules in my home office. A lot of things come together under my desk and I had 5 piggy-backed v1 modules under there to control various lamps and stuff. The cluster of 2 lamp and 3 appliance modules is fed by a short extension cord that plugs into an outlet that is shared by a UPS for my monitor.
I replaced the 5 v1 PLC (1-way) modules with 5 Insteon 2-way modules. Then to add insult to injury I ran another extension cord out of the feed-through outlet on the last module and ran it to the top of my desk where I plugged in a controlinc. (another 2-way device) I also plugged a powerlinc into that cord so I could test out PowerHome.
Buried in the cluster of 5 modules is 1 lamplinc that needs an X-10 address so Stargate can turn on a small lamp in the evening. With the UPS right there, X-10 was right on the edge even using the old PLC devices. I figured replacing 5, 1-way devices with 7, 2-ways would absolutely kill the marginal X-10 signal.
Long story short, the lamp works great with X-10. 100% reliability! Needless to say I have stopped worrying too much about any serious impact to X-10 from my Insteon installation.
Now that I am about 115 devices into the transistion I am happy to report that this is not a major problem at all. In fact I have had only a couple of locations where the X-10 signal was affected at all! Because my Stargate does not do Insteon yet I have had to program any light controlled via motion detector or that that is on a timed schedule, with an X-10 address. Only one has failed to work immediately and this was reolved with a boosterlinc.
The most dramatic surprise came last weekend when I replaced some modules in my home office. A lot of things come together under my desk and I had 5 piggy-backed v1 modules under there to control various lamps and stuff. The cluster of 2 lamp and 3 appliance modules is fed by a short extension cord that plugs into an outlet that is shared by a UPS for my monitor.
I replaced the 5 v1 PLC (1-way) modules with 5 Insteon 2-way modules. Then to add insult to injury I ran another extension cord out of the feed-through outlet on the last module and ran it to the top of my desk where I plugged in a controlinc. (another 2-way device) I also plugged a powerlinc into that cord so I could test out PowerHome.
Buried in the cluster of 5 modules is 1 lamplinc that needs an X-10 address so Stargate can turn on a small lamp in the evening. With the UPS right there, X-10 was right on the edge even using the old PLC devices. I figured replacing 5, 1-way devices with 7, 2-ways would absolutely kill the marginal X-10 signal.
Long story short, the lamp works great with X-10. 100% reliability! Needless to say I have stopped worrying too much about any serious impact to X-10 from my Insteon installation.