Svede Posted January 27, 2016 Share Posted January 27, 2016 Not sure if anyone has experienced this but here goes.... I have successfully installed 4 Insteon bulbs (2672-222) and 2 insteon dual outlets - all programmed and running perfectly. The other day I added a 5th insteon bulb and set up a program... when it came time to turn on - the bulb turned on, when it came time to turn off... no response. I thought it was a programming error but after logging into the counsel, I still could not turn off the offending bulb. There was a comm error thrown at this point. Long story longer... after some trouble shooting, I noticed that the comm error would generate and the bulb would be unresponsive only when the ceiling fan / light in that room was on... How can turning on a fan in a room disrupt the insteon bulb? Everything else on this line works regardless of the state of the ceiling fan. Link to comment Share on other sites More sharing options...
stusviews Posted January 27, 2016 Share Posted January 27, 2016 Any motor can generate noise. Can you control the bulb from the Admin Console (instead of the program)? Can you control the bulb from a scene (instead of the program)? What is the result if you swap the bulb with one of the others? Link to comment Share on other sites More sharing options...
Svede Posted January 27, 2016 Author Share Posted January 27, 2016 The bulb is in a table lamp in the master bedroom... this bulb will respond to the program and On/off commands from the console when the ceiling fan/light (in the master bedroom) is off. When the ceiling fan and or ceiling fan light is on - the insteon bulb does not respond to anything and throws a communication error. Link to comment Share on other sites More sharing options...
stusviews Posted January 27, 2016 Share Posted January 27, 2016 So, just the fan light causes the problem. What type of bulb(s) are in the fan light? Did you try swapping the table lamp bulb? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.