burbankadam

So there is nothing further that needs to be done? I just wanted to make sure that successful device communication wasn't necessary to properly remove the device from the ISY / PLM since communication is no longer possible due to the failure. Thanks Adam

I just had one of my insteon devices completely fail. The ISY-99 can no longer see it and none of the LEDs illuminate. I removed the device from the ISY-99 using the Remove command and it appeared to delete successfully. I then viewed the PLM link table and noticed that the address of the removed device still shows up a few times. Is this expected? Is there any other way to completely remove a dead device from the ISY-99? Thanks Adam

I recently upgraded from 3.2.6 to 3.3.2 as I was having issues with the two I/O Lincs that I recently purchased. As was true for other users, I was unable to save settings using the admin console. Once I upgraded to 3.3.2, I was able to save settings and everything appeared to be working normally. Then I discovered that every time I switched on the relay of the I/O Linc, the sensor status would also be reported as on. When I turn off the relay, the sensor status is reported as off. At the same time, if the relay is not controlled, the sensor status will respond normally to the sensor input. I have observed this behavior regardless of what options I have set on the I/O Linc and there is no option for the sensor status to follow the relay status anyway (only vice versa). A review of the event viewer shows that every time a command is sent to the I/O Linc to turn the relay on or off, a message shows up that says "Duplicate or ACK for a different device". Not sure if this is related but I thought it was worth mentioning. I have two different I/O Lincs and both have this problem. I tried restoring both devices and I also performed factory resets on both and neither resolved the issue. I then downgraded back to 3.2.6 and the problem went away, except I am back to the original problem of not being able to save the settings. Lastly, I tried upgrading up to 3.3.1 instead of 3.3.2 to see if both versions have the issue and they do. 3.3.1 allowed me to save settings but caused the "Duplication or ACK for a different device" message and the sensor status follows the relay status. I also noticed that when the relay status is changed and the sensor status follows, a single device query will return the sensor status to the correct state. Anyone else have an I/O Linc they can test?