X10 Code preset in Insteon switch

[JohnG]

After days of program modifications and testing, I just figured out what was causing apparently inconsistent behavior in a garage motion-activated program using an X10 motion sensor. I'm throwing this out in the hopes of helping someone else to avoid the time that I spent trying to figure this out.

 

The reason that this was so difficult is that when you're learning ISY programming, you're trying to figure out if you have done something wrong with your logic first.

 

The cause of the problem was that an Insteon switch was throwing out an X10 code that just so happened to be the same code that I had setup on the garage motion sensor. This switch came from SmartHome with this X10 code set. So, when this switch happened to be on when my 'All - Off' program was run, it would send the same X10 code that I'm expecting from the garage motion-sensor, and after all the lights would go off, lights would go on that were supposed to be triggered by the garage motion-sensor.

 

I was about ready to pull my hair out after going through iteration after iteration, separating the programs, reviewing the logic, and hearing my family's complaints about it not working properly and the repeated testing (lights going on and off).

 

It was just good luck that I finally caught the link between the Front Porch light switch and the wacky behavior. The reason that this happened to be inconsistent, was that I had put the Front Porch light on a motion sensor as well. So it wasn't always on. I changed the X10 code on the garage motion sensor, and the problem went away.

 

Bottom line is that it seems that doing a factory reset on Insteon switches might be a good thing to do when you're installing the switches. This will clear any preset X10 codes from the switch. Apparently, SmartHome doesn't always reset switches after testing, before shipping.

[Algorithm]

John, sorry you found out the hard way--glad you still have some hair left!

 

Seriously, this has been an ongoing problem with SmartHome, and has had many posts on their forum. You are absolutely correct that doing a factory reset should be the first step for any new switch/module install.

 

I have no idea whether any of my switches/modules had any residual X-10 code in them, because after reading about these issues on the SmartHome forum, I made it a practice to factory reset every device before installing it--even the in-wall ones, for which I have a temporary setup on my desk to wire them up for just that purpose.

 

Good report, John. I hope this thread will save someone else from going through what you did! Thanks for posting it.

[Illusion]

Just installed some new SL, KPL, and RelayLincs and I can confirm that SH is shipping out devices with links to other devices, not sure about the X-10 because when I found those errant links I factory reset all the new devices and started over.

 

ALWAYS factory reset the device on initial install. Save yourself some misery!

[upstatemike]

One continuing frustration I have is that you should be able to do a factory reset remotely. Since an Insteon device address is hard coded it should always be reachable from a controller even after a hard reset. I don't know why Smarthome did not provide a way to force a factory reset remotely. That way you could do all your troubleshooting from the PC screen.

[Algorithm]

UpstateMike,

 

That is a good idea; I concur entirely.

 

In addition to Factory Reset, it would also be helpful if INSTEON devices could be remotely rebooted, as when new local settings are written to the device.