looking for some input if anyone has run into this issues with any of there migrations, i opened a ticket with support and got the generic link to the wiki... which i've tried in my orignal migrations and still not having any success, hoping that someone here might be able to share there experiences if they were similar

Issue Summary: I recently migrated from an eisy v1 (which was stable for years) to a new eisy v2. Since the migration and backup restore, I have been unable to achieve stable two-way communication, despite testing three different PLM units and moving the controller to multiple physical locations.

Detailed Timeline:

• Initial Migration: Upon the first restore to the eisy v2, the original PLM (2413S with the serial-to-USB adapter) was not recognized at all. Despite multiple reboots and full factory resets of the PLM (holding the set button until the beep stopped), the eisy v2 would not acknowledge the hardware.

• New Hardware (2413U): I purchased a brand-new USB PLM (2413U). The eisy v2 discovered this unit immediately. I performed a Restore Modem, and while the system appeared to function initially, I began experiencing "one-way" communication issues.

• Linking Failures: Multiple existing switches stopped reporting status updates to the interface. Furthermore, when attempting to add a new KeypadLinc, I consistently received the error: "Cannot determine device link table address".

• Isolation Testing: I attempted to "Restore Device" on several switches; however, the communication was too unstable to complete the writes. I physically moved the eisy v2 and PLM to a different part of the house to rule out local interference, but the "Reason 9" timeouts and status update failures persisted.

• Regression Test: I attempted to revert to the original PLM and even a third, brand-new-in-box 2413S unit. The eisy v2 continues to fail in recognizing the older serial units and maintains unstable communication with the USB unit.

Request: Because this mesh was 100% stable on the eisy v1 and the issues persist across multiple PLMs on the v2, I suspect a hardware defect in the eisy v2's USB bus or a corruption in the migrated link database.

So you're saying that the same original PLM and serial adapter that worked fine with the original eisy isn't seen by the new one? And works fine when put back on the original? That does look like some kind of unusual problem with USB communications. On the v2 unit, you connected the power to the designated USB C power port (next to a hdmi port), right? Have you tried the power supply of your original eisy on it too?

hen migrating from my eisy v1 to the v2, I initially performed a factory reset on my original PLM. However, after multiple reboots and troubleshooting steps, the eisy v2 would not recognize the original module. I then connected a brand-new USB PLM (2413U), which the v2 detected immediately.

I proceeded to restore my v1 backup onto the eisy v2 and ran a PLM Restore. While everything initially seemed to work, I noticed after a few days that several switches were failing to sync status back to the eisy. Commands and scenes triggered from the interface work fine, but it has become a "one-way" communication issue.

Watching the Level 3 Event Viewer diagnostics while manually toggling a switch shows no activity, and the eisy status does not update. I have already tried factory resetting several switches and running the Restore Device command within the eisy, but the issue persists.

If you factory reset the PLM even before doing the migration, then you already had need to do some kind of PLM restore. Ideally you want to simply backup on the original eisy and restore on the new one, and keep the PLM intact. But that doesn't explain why the PLM isn't being recognized.

Did you check that Insteon was enabled in the Configure screen? It would be now if the USB PLM is recognized.

Right now I'd try to figure out why it's not working right with the new USB PLM. As a new, blank system. Just trying to add a new switch or module.

I actually tried that first moving the PLM without a factory reset but the new eisy v2 consistently reported 'PLM not connected'. I tried multiple reboots and different USB ports, but since nothing worked, I assumed a PLM factory reset was the best path forward.

I’m now at the point where I’ve tried three different PLMs, performed hard resets on the switches, and ran the restore commands inside the Admin Console, yet the issues persist. I’m almost ready to just screenshot all my device settings, factory wipe the eisy v2 and the PLM, and manually rebuild the entire network from scratch.

It sounds like a massive pain for 40–50 devices (with another 15 still to add), but I'm running out of ways to diagnose this. I previously migrated from the ISY-994 to the first eisy version without any issues by just swapping the controller, but that same scenario clearly isn't working this time around. now my next question is do i go back to my orignal PLM with the ethernet to USB adapter since i have 2... or do i swap right to the new USB model, not sure there's an advantage over the new USB one besides it being newer...

Under the Configuration tab make sure the "Insteon Support" box is checked