I just attempted to switch PLMs.  I went from a 2413S to a 2413U.  I am using EISY and everything is up-to-date. Although the administrative console recognized my Insteon devices, it would not communicate with them until I individually relinked them. Unfortunately, I have a few micro switches which are very labor-intensive to access in order to be able to relink them. From previous posts, it appears that in making this transition the Insteon devices should be automatically reconnected. Are there any special steps to take to be able to accomplish that?

Did you use replace PLM?

Edited February 8Feb 8 by hart2hart

Battery powered Insteon devices don't relink automatically. You have to put them in linking mode and restore them one by one.

4 minutes ago, hart2hart said:

Did you use replace PLM?

No, I didn't use replace PLM. Where will I find that. Does it Show up under tools | diagnostics with a new modem is attached? Right now, I can't find it anywhere. Or is that "restore PLM"?

Edited February 8Feb 8 by Ed Sybesma

16 minutes ago, Ed Sybesma said:

No, I didn't use replace PLM. Where will I find that. Does it Show up under tools | diagnostics with a new modem is attached? Right now, I can't find it anywhere. Or is that "restore PLM"?

Yes it’s called Restore PLM in the admin console and there are steps as I recall to power off eISY, replace the actual PLM and then to run Restore PLM. It then goes through each device and replaces the PLM address in all your devices including battery operated but have to wake them up to process the changes.

However if you’ve done part of it manually, you may want to open a ticket and consult UD to get advice on next steps.

Edited February 8Feb 8 by hart2hart

Here's the instructions for replacing the PLM

Replace PLM Procedure (EISY or POLISY).pdf

Edited February 8Feb 8 by Techman

Even after resetting my new PLM to factory settings and starting over, the Restore PLM command and the Replace Modem PLM instructions did not do the trick for me, but I did find a very convenient workaround: Querying the modules triggered the green 1011 “waiting for updates to be written” flag and then using the “Write updates to device” option got my devices linked.  But thanks to hart2hart and Techman for their input which might have saved me that extra effort if I had started with it the first time.

I had a similar problem. Either my old serial PLM or the serial-RJ45 adapter died during the recent geomagnetic storm. I followed that procedure to the letter. Twice. Here it is not in PDF format for reference:

PLM Replacement (from PDF on ISY forum)

================

Replace Modem (PLM)

This operation is most useful when you need to replace a defective PLM and the EISY/POLISY is rebooted with a new PLM. When the communication links were established via the Link Management Menu, the PLM and INSTEON devices adds each device addresses it is linked to, in its own link table.

The EISY/POLISY also reads and stores the PLM’s address at boot up. The EISY/POLISY stores all the configurations settings in the device tree. If you are replacing a PLM the EISY/POLISY will have the old PLM address link stored in it.

Warning: Never replace your PLM while the EISY/POLISY is running because it will assume it is still connected with the old PLM. The EISY/POLISY will appear to work, but it will be writing the address of the old PLM into the device links, thus you will not see devices updates etc. If this menu option is selected, the EISY/POLISY goes through all INSTEON devices looking for old and new PLM address links. If an old PLM address link is found, it replaces them with the address of the new PLM and adds the corresponding device link to the new PLM.

To replace a PLM:

- Unplug EISY/POLISY from the power outlet

- Unplug the PLM from EISY/POLISY and power outlet

- Connect the PLM to the EISY/POLISY (connection will vary depending on the type of PLM)

- Plug the new PLM into a power outlet

- Plug EISY/POLISY into a power outlet

- Go to Admin Console and wait for system initialization to complete

-Click on the Battery icon at the top. This will prevent EISY/POLISY from trying to update programming on your RF devices which are probably in sleep

mode

- Click on the Restore Modem (PLM) menu option

- In case EISY/POLISY cannot communicate (or decides not to if it’s an RF device during the process, you will have a series of nodes with green 1011 icons in the device tree. For each one of those nodes:

- If an RF device, ensure that the device is in Programming mode (awake)

- Right mouse click | Write pending updates ...

If the above procedure fails on many of your devices, it's highly recommended that you follow the instructions for Restore Devices.

===============

I am having to restore more than half of my devices, one by one. Sigh.

BTW, my new USB PLM is recent, Revision 2.7, 2023. And in IoX I am finding that some of my devices that worked fine with my old PM and have a big red ! after replacing the PM fail a manual Restore Device. However, they seem to work with a Write Updates to Device.

My procedure is to go through all of the devices in red letters at the top left of IoX (Network > ISY) and trying to turn them on and off. If that works, fine. If not I Write Updates to Device.

I started by turning the device on in IoX, manually going to that light was on, and then going back to IoX. I quickly realized that if turning on and off didn't trigger an "UNABLE TO WRITE TO DEVICE" and a big red ! to the left of the device, I could go on to the next device and "Write Updates to Device."

35 minutes ago, KConover said:

My procedure is to go through all of the devices in red letters at the top left of IoX (Network > ISY) and trying to turn them on and off. If that works, fine. If not I Write Updates to Device.

Interestingly, for me, with a 2024 PLM (same revision I think), switching on and off did not work on any of the devices, but clicking on query worked for all of them to generate a 1011 icon to allow write updates to device and connect.

Thanks for the tip, Ed! I was able to "Query:" a couple of devices that IoX couldn't reach and then "Write Updates to Device" and it worked!

However for others, it didn't work; the query didn't result in a "1011" icon, and "Write to Device" and "Restore Device" didn't restore the connection with IoX (though the devices still work fine with local control and local links).

I did find that for at least one of my wall switch dimmers, I had to long-press the tiny clear button at the bottom to go into linking mode before "Write Updates to Device" would work, but then the red ! went away and I could turn on and off via IoX.

However, for several devices that were accessible to my old PLM, "Query" didn't result in a "1011" icon at the left.

I found that one of the lamp modules that worked fine with the old PLM wouldn't respond to the "Write Updates to Device" or "Restore Device" so I long-pressed the linking button and then tried "Write Updates to Device" which failed, and then "Restore Device" which also failed. I checked its programming with the four-button wall switch that controls it, and that works fine.

But many other devices are refusing to speak with IoX or vice versa, no matter which of the above I have tried.

So I am at a loss for understanding why IoX cannot access it through the new USB PLM.