I am on 5.0.15 and I have a 2876D3 icon dimmer which is defective and needs replaced.  My question is can the failed  device cause other devices in the same program to not be triggered on?. The devices that are not being turned on are all called in the same program. The attached photo shows the defective device highlighted in red and the devices that are not being turned on in yellow. The air gap is pulled on the icon dimmer that is defective. Should I try removing the defective device from the program?  Could this be a bug? Never experienced this type of issue before.

Edited April 12, 20196 yr by keribi

37 minutes ago, keribi said:

I am on 5.0.15 and I have a 2876D3 icon dimmer which is defective and needs replaced.  My question is can the failed  device cause other devices in the same program to not be triggered on?. The devices that are not being turned on are all called in the same program. The attached photo shows the defective device highlighted in red and the devices that are not being turned on in yellow. The air gap is pulled on the icon dimmer that is defective. Should I try removing the defective device from the program?  Could this be a bug? Never experienced this type of issue before.

Yes. I have had this same problem. Insteon likes to retry a few times when no response is received. The PLM should be able to accept this trouble and work around it but it doesn't seem to in my case.

This seems like it may be a problem between the PLM and ISY missing some handshaking and overflowing a cache.
 

You can insert a Wait 5 seconds line after the bad unit command line, or move that program line  to the bottom of the program and retest.

Thanks!   Will try just that.

Did exactly what you said and all is working.  Now to replace the failed device and add it to my box of other failed insteon devices.

Thanks for the help