I am finally getting around to moving off my ISY994 to my EISY that has been sitting on my desk since May of 25. i was amble to get all of the programs, schedules, devices, Alexa integration moved. I only have 3 Z-Wave devices so I will reset all of that manually. I have a 2413S PLM with what appears to be a date code of 4716. The PLM powers up and has a solid green light and will beep on button press so it seems alive. It was working just fine before I touched it but now seems unresponsive. It doesn't show up in PLM status on my old ISY or new EISY. I have tried using the USB/Serial cable that ordered with the EISY but nothing seems to be working. What is the best way to attach to it from a mac or PC to double check before giving up on it. I have ordered a new USB PLM but am really not liking my house being "DEAD".

If you want to use the2413S serial PLM on an EISY you need the UDI USB to serial cable they sell. The EISY does not do serial communications to the PLM.

If you try a USB to Serial port adapter. It will not work. The serial signals are not correct for a standard adapter.

Edited Thursday at 06:42 PM5 days by Brian H

A couple of things

• The date code is 2016, I think that was in the bad capacitor days, and having said that a long time ago in PLM years

• My experience with some older Insteon devices is that they will work untouched but then lose it when trying to reconfigure them

• Another thing is when I first set up my eisy, the eisy needed to be restarted a time or 2 before showing PLM connected. That's important because the PLM connected only comes on eisy restart, not unplug replug. You can try that

4 hours ago, Brian H said:

If you want to use the2413S serial PLM on an EISY you need the UDI USB to serial cable they sell. The EISY does not do serial communications to the PLM.

Hey Brian, as mentioned above I have that serial cable. " I have tried using the USB/Serial cable that ordered with the EISY but nothing seems to be working."

4 hours ago, paulbates said:

A couple of things

• The date code is 2016, I think that was in the bad capacitor days, and having said that a long time ago in PLM years

• My experience with some older Insteon devices is that they will work untouched but then lose it when trying to reconfigure them

• Another thing is when I first set up my eisy, the eisy needed to be restarted a time or 2 before showing PLM connected. That's important because the PLM connected only comes on eisy restart, not unplug replug. You can try that

Hey Paul, how would a bad cap manifest? I can get it to chirp at me if I press the button so from a very simple perspective it seems to have at lease minimal function.

I am at 5 reboots now and still no luck. i was hoping to be able to attach from serial port on my machine to be able to manually poke at it to see if it responded to anything. i tried putty at 9600 8n1 no flow control

It manifests in weird behavior. A sign is if unplugging and replugging the PLM helps temporarily, but eventually starts having problems.

Looking at the links count is a place to start.

Wrong serial settings. 19,200 8 Bit No Parity 1stop bit.

Bad caps frequently. Caused things like 0 or few links in it. Restoring it so the link count is more normal but then eventually is again 0 or very low link count. Runs for a short while after a power cycle.

Are you running windows and a serial port? There are a few programs to access it but are more for folks that can use the low level commands to see what it is doing.

28 minutes ago, Brian H said:

Wrong serial settings. 19,200 8 Bit No Parity 1stop bit.

Bad caps frequently. Caused things like 0 or few links in it. Restoring it so the link count is more normal but then eventually is again 0 or very low link count. Runs for a short while after a power cycle.

Are you running windows and a serial port? There are a few programs to access it but are more for folks that can use the low level commands to see what it is doing.

I am a sysadmin by past trade. lots of consoles and ssh sessions. looks like this thing is kaput. has serial session open with puTTY while pluggin git in and nothing. no response, nada. :-( USB version will hopefully be here on Sunday per USPS.

When following the PLM replacement procedure, you'll want to pick a backup from before these problems happened if possible and restore it before connecting and performing a 'Restore Modem' from iox. The records in the current PLM have likely been polluted, and there's a chance that's what goes back to the new PLM.

It can be fixed normally, but better not to start off on the wrong foot

The link is from an older unit, but the basics are the same other than the backup restore suggested here

One thing I forgot. The PLM both 2413S and 2413U. Use a HEX message for receiving and sending data.

Get Version should get a reply back with the PLMs information. 02 60 Cartridge return. Should send back 02 60, the PLM's data and end in an 06 ACK.

The serial 2413S also had serial port interface chip problems occasionally. Rev 2.3 changed the chip for one with better ESD protection. V2.4 and above. Have a new serial port daughter board that also has a protective on the serial in and out signals from the PLM.

Thanks Paul and Brian.

ok new 2413U in place and everything came back up on the insteon side. now to fight with the 3 schlage locks and zwave. I am not running anything overly complete. is there a way to independently migrate the zwave stuff? I have been poking around and it does not look like it un less i am missing something.

I got this figured out. Thanks again Brian and Paul!!

Well crap. poor assumption made that all was well. Scenes from EISY (and hence Alexa) work just fine but apparently my inter device links are gone.

• The scenes all show right in terms of controller/responder in the EISY and when the scene is operated from the EISY all of the devices operate.

• When a device that is operated in the scene none of the other devices control the scene.

Looking at my device links tables on both the primary (electrically attached to lights) and secondary (remote controlling devices) i see the opposing device and the EISY device IDs.

Link table from Living Room Primary (electrically attached to lights) address: 56 3C EA 1

Thoughts?

PLM Links Table.v6.0.4__Mon 2026.02.16 10.51.52.xml Living Room Pri 56 3C EA 1 Device Links Table.v6.0.4__Mon 2026.02.16 10.47.31.xml Living Room Sec 56 28 49 1 Device Links Table.v6.0.4__Mon 2026.02.16 10.48.46.xml

Edited Monday at 06:53 PM1 day by Ethan
added link tables

Have you tried a "restore device" on the affected devices? Start with two devices that should be communicating between them (eg: a switch that should turn on another one, like a 3 way). Right click on the device in admin console and then choose "restore device". Then tdo the same on the second device, and test if the link(s) between them are back.

4 minutes ago, Guy Lavoie said:

Have you tried a "restore device" on the affected devices? Start with two devices that should be communicating between them (eg: a switch that should turn on another one, like a 3 way). Right click on the device in admin console and then choose "restore device". Then tdo the same on the second device, and test if the link(s) between them are back.

that worked for the set that i tested. will File -> Restore Devices fix all of them or do i need to do individuals to fix them all?

You could try an all devices restore. I hadn't really thought about that option.

1 hour ago, Guy Lavoie said:

You could try an all devices restore. I hadn't really thought about that option.

All device restore complete and everything is back in business!!! YAY!!!

We love happy endings!

If you have any battery powered devices like motion sensors, open/close contact sensors, etc, those need to be put in linking mode manually and then restored. Just to be sure nothing gets overlooked.