I had my first phase coupler back in the days of X10, later replaced that one with the Insteon phase coupler. Still have one or two Insteon Access Points plugged in. Yup, that old. Also had a bunch of Insteon FilterLinc's and X10 FilterLinc Pros. Use to have extensive saltwater reef systems with lots of large pumps and halide lighting so lots of filters. Still have some of the X10 Pro filters still in use but several of the Insteon FilterLinc's died.

(2) 2477D Dual Band SwitchLinc Dimmer v.41

(2) 2472D Dual Band OutletLinc Dimmer v.40

(1) 2456D3 LampLinc v.33

Event file after trying to restore the 2472D Jans Lamp 1A 86 62 1 again, still not responding. Did get a switch and outlet to respond to EISY that previously wasn't responding. Still having issues with the mini remote for the living room that controls the switches and outlets that are having issues.

Progress

ISY-Events-Log.v6.0.4__Sun 2026.05.24 06.56.04 PM.txt

I still have a pair of Access Points in use.

You may want to check the date on them. Rev 2.0 and newer are built on the base 2413 PLM board and have the same failed capacitors we see in the 2413S PLM. I had to rebuild a pair myself. The 4 tap/communications builtin test, May give you some added data.

13 hours ago, DIYguy said:

several of the Insteon FilterLinc's died.

If haven't opened them up, there's a fuse in there. They could have been used over their spec'd rating, possibly inrush current turning them on

4 hours ago, Brian H said:

I still have a pair of Access Points in use.

You may want to check the date on them. Rev 2.0 and newer are built on the base 2413 PLM board and have the same failed capacitors we see in the 2413S PLM. I had to rebuild a pair myself. The 4 tap/communications builtin test, May give you some added data.

I brought about 6 back to life with capacitor replacement. I’ve still got many switches and dimmers installed from 16 years ago that are single band so accees points keep device communications at high reliability.

I bought several dual band replacements during a smarthome 40 or 50% off sale before they closed. I install them as devices go bad but I’m guessing 70-85% are still original.

Edited May 25May 25 by hart2hart

On 5/24/2026 at 11:33 AM, DIYguy said:

@oberkc Network Gateway, EISY, Insteon Hub, security system, NAS, Internet gateway, etc are on battery backup and surge protection. All nodes not working are in wall switches and outlets.

Dedicated outlet installed next to EISY has been in place for years. Have somewhere around 30+ nodes communicating but six device nodes that are not. Restore Device performed multiple times on each failed device, tried factory reset and add back, still didn't work All this is after the PLM failed and was replaced. I've restored the PLM MULTIPLE times. Most nodes work, some don't.

Is your dedicated Outlook on a separate circuit? I understand that the PLM is not on the surge suppressor, but the mere presence of surge suppressors and UPS can make it hard for insteon devices to communicate of whether the insteon devices are powered by the UPS or surge Suppressors.

@DIYguy , your event viewer file does not appear to be on "Level 3". It does not show the details of the communication to the device.

It also does not show any errors (appears to have completed normally).

It wrote ONLY the responder link to the PLM (1 link). You should have at least 2 links

• responer to the PLM

• controller to the PLM (so the device can inform the PLM of changes).

Have a look at the "ISY link table" for this device (please post). If there is only 1 link the ISY link table is corrupt.

8 hours ago, paulbates said:

If haven't opened them up, there's a fuse in there. They could have been used over their spec'd rating, possibly inrush current turning them on

There was for a short tine a five amp version. After examining both version. Only thing I found was a different fuse and a higher price for the 10Amp model. 10Amp, fast blow, 5mmX20mm axial leads, ceramic body. There was a post here a long time ago. Where a member found bad solder joints on the heavy coil leads and re soldering them to the PC board made them operational again.

Edited May 25May 25 by Brian H

@IndyMike Had to look up how to do a level 3 Event log. Think I got it. One of the devices that I can't get to communicate is the Jans Lamp I tried including before. Did another restore for that module (node) and ran the Event Viewer log. What the log has to say is above my normal grade.

ISY-Events-Log.v6.0.4__Mon 2026.05.25 05.53.14 PM.txt

You event viewer is a little odd. You have good communication with the device, but you experienced errors communicating with the plm.

Could you please try switching communicatio from "automatic" to "device reported" mode. That should force the ISY to use I2 communication

In Link Management-Advanced Options I changed from Automatic to Device Reported.
Tried to turn on device, adjust on to 100% and write file. Did another Restore Device and then save the Event Log.
Latest attached.

ISY-Events-Log.v6.0.4__Mon 2026.05.25 06.29.38 PM.txt

It looks like that completed correctly. Unfortunately, the ISY only wrote 1 link again. It looks like the isy image for this unit may be corrupt. You can view by right clicking on the device tree and selecting /advanced/show is table. If this only shows 1-2 links you'll need to delete and re- add the device

I think we've achieved the point of delete and attempt to add back. I did get a couple devices to respond to EISY commands but there are several remaining such as Jan's lamp (lamp on end table where she reads) that just do not respond. Shows status but no response.
See attached screen shot.

25 minutes ago, DIYguy said:

I think we've achieved the point of delete and attempt to add back. I did get a couple devices to respond to EISY commands but there are several remaining such as Jan's lamp (lamp on end table where she reads) that just do not respond. Shows status but no response.
See attached screen shot.

To be clear, your device is responding rather well. It's the ISY that is wriwriting incorrect information due to a corrupted file. Nothing wrong with the device itself.

In the end the result it the same - delete device/re-add.

Deleted the model in EISY. Did the factory reset. Turned circuit off at load center, had wife on phone, held the set button while telling wife to turn power back on and continued to hold set button LONG time, no beep.
Unplugged PLM for 20 seconds, plugged back in. Did a reboot of the EISY from the Configuration screen. Tried to add Insteon device in link management using auto and it didn't find the device. Tried again manually adding address while linking and it worked. Device is back and responding.

ISY-Events-Log.v6.0.4__Tue 2026.05.26 10.57.56 AM.txt

@DIYguy , your event viewer shows 2 links being successfully written. If this was your initial link after "deleting/resetting/re-adding", that's appropriate.

Hopefully that gets you past the recent speed bumps.

@IndyMike I want to thank you for your help. After the delete and re-add modules were communicating properly with EISY and didn't have to replace any modules. Was able to successfully re-link with other controllers and add back to programs. Alexa is even cooperating.

In a related topic, mentioned at start of post that numerous electronics went bad at the same time. May have been a surge after a local power outage and surge when power came back but don't know for sure, may have been coincidence. One of the devices was my Honeywell Tuxedo Touch keypad. Have that one in the hallway next to the bedroom. Finally got that back online but lost all programming and firmware out of date. Been working on that one along with the Insteon. Good news, Tuxedo has latest firmware and all programing is reentered.