Elk / Insteon lights turning on......again

[Spanky]

We have an Insteon setup working in our lab.

Do not use the "ALL LIGHTS OFF" in rules.
There is no equivalent command for Insteon except for issuing a
Group command. If the M1 sends the M1XSP an "ALL LIGHTS OFF,
HOUSECODE A", the M1XSP is actually sending a command to control
Insteon device number 1.

 

[mustangcoupe]

not related to number of devices I only have 5 and they turn on......

 

[aehusted]

any update on this issue?
I just enrolled 12 devices to the XSP using powerhome utility and made 3 rules. One light (that was not controlled by any rules) kept coming on by itself.
If anyone has an update to this situation, I would like to hear it.
Thanks!

 

[GraysonPeddie]

One question that may not have been asked is "does your Insteon devices have X10 addresses set?"

Maybe you may have overlooked the Insteon devices that have an X10 address set for them. If you erase all the links from M1XSP and reset the devices back to the original factory, maybe this will help clear up the problem.

I know you have a strong assurance that it is the polling issue with the M1XSP, but I think it helps to do a process of elimination by resetting all the Insteon devices.

I hope this helps!

Regards,
-Grayson Peddie

 

[mimitche]

My phantom light on problems have not reoccurred a single time since I disabled polling; it's been at least a month now. As an added bonus 'on for duration' rules also work now; with polling on they would never turn off.

 

[aehusted]

Thanks for the tip. I did not set any X10 addresses, but this is something else to try. So far the only phantom light I have is a SwitchLinc. I have not seen this behavior from a ToggleLinc, LampLinc, or ApplianceLinc. I don't know if this really means anything, but it is more food for thought.

One question that may not have been asked is "does your Insteon devices have X10 addresses set?"

 

[GraysonPeddie]

As far as I know from SmartHome forum (www.techmall.com), SmartLabs forgot to reset the SwitchLinc to clear the X10 address, so if I were you, I'd reset the SwitchLinc(s) and maybe this will help cure the problem.

 

[aehusted]

Does a "factory reset" erase the X10 address or do I have to do the X10 removal separately? I did the factory reset as described in the manual and I am still getting the same problem.

As far as I know from SmartHome forum (www.techmall.com), SmartLabs forgot to reset the SwitchLinc to clear the X10 address, so if I were you, I'd reset the SwitchLinc(s) and maybe this will help cure the problem.

 

[aehusted]

I did a factory reset on the troubled switchlinc and erased the X10 address as described in the instructions. I verified that my XSP controlling insteon has the jumpers set to the default 111 0011, so the polling should be off.
This problem only started happening since I installed an additional XSP to connect the W800RF. These two are on the same leg and the W800 is terminated.
Any ideas what might have caused my one switch to start going buggy?

 

[aehusted]

I think the light sensor in one of the Hawkeyes I had laying around was triggering it. I did not realize that the X10 codes from the W800 will trigger the lights of that code from the M1G. <_<

This problem only started happening since I installed an additional XSP to connect the W800RF. These two are on the same leg and the W800 is terminated.

 

[gatchel]

If the Elk hears an X-10 signal it may repeat it to the corresponding Insteon light. I have seen this on my setup and Elk confirmed it on their forums.

The manual says to not overlap x-10 and other lighting devices even though they are different technologies.