Jump to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Upgrading from ISY to EISY and a new PLM too

Featured Replies

I basically am upgrading my system hardware from a working set up currently using a 2412S PLM and an ISY.

Essentially swapping the above out with a new EISY and a new 2413U USB.

I’ve read the wiki and many forum posts, but they are a little confusing. In the wiki for restoring the PLM it says I need to connect my new PLM to the old PLM? I don’t think I have the cable to do that, so is that completely necessary? Any other short description tips on how to go about this upgrade?

Sidenote. I did an admin console restore from a saved backup file and that seemed to work as I see all Devices. And now I am restoring the PLM, which might be working because I hear my house full of Insteon devices beeping in sequence. Perhaps they are all reconnecting to the new PLM as expected?

Sounds right.

The upgrade would now be updating all your modules to update their links to the PLM, so they can "call home" to the new device id. The PLM itself will have all the module addresses it needs to know about also written to it.

1 hour ago, windrockwater said:

In the wiki for restoring the PLM it says I need to connect my new PLM to the old PLM? I don’t think I have the cable to do that, so is that completely necessary?

I don't believe I have ever seen that in the wiki.

You need to plug the new plm in to eisy and at the right time, restore the plm.

Follow these instructions:

Migrating

On the Eisy / Polisy you are migrating to

Do the appropriate preparation step (see above)

Make sure Eisy / Polisy is up to date

Go to Admin Console configuration page and select update packages

If you don't have a current backup, make a backup of your Eisy / Polisy (Admin Console | File | Backup ISY)

If you are using Insteon, plug in the PLM

If you are not migrating your Z-Wave network

Use (Admin Console | File | Restore IoX) to restore either your Eisy / Polisy backup or your ISY-994 backup

If you are migrating your Z-Wave network

If you aren't already using it, plug in your ZMatter Z-Wave dongle and unplug any other Z-Wave dongle you may have been using.

(Polisy only) If you have a ZMatter Z-Wave board then power down Polisy, add it, then power on again.

Reboot Eisy / Polisy

Use (Admin Console | File | Restore IoX) to restore your "migration" backup

If you are migrating from Eisy / Polisy use the migration backup (e.g. "ISY-BackupWithZWaveMigration.v5.5.4__Sat 2023.01.21 09.07.44 AM")

If you are migrating from ISY-994 use your ISY-994 backup

When IoX restarts, it automatically does the following:

Writes you Z-Wave network into the ZMatter Z-Wave controller

Interviews every Z-Wave device in the Z-Wave nework, creating/updating nodes, programs and scenes.

This process can take anywhere from a few seconds to a few minutes for each device depending on the complexity of the device.

The best way to monitor the progress is to open the Admin Console Event Viewer to level 3

For those who want lots of low-level details, you can also use this from the command line: tail -f /var/isy/FILES/LOG/ZWAY.LOG

If you don't actually change your Z-Wave network by adding/removing Z-Wave devices after migration, you can back out the migration by connecting whatever Z-Wave dongle you were using before migration and restoring the backup you made prior to migration.

If you are using Insteon

Go to the Admin Console configuration tab and make sure INSTEON Support is enabled (default username/pwd = admin/admin)

If you are using a new PLM, Restore the PLM

Reconfigure any software utilizing to point to this Eisy / Polisy, restart the other software, if necessary.

If you have ISY Portal on your 994

Follow these instructions to migrate your account, license, and Alexa/Google Home settings

This will also migrate all node server licenses from your Polisy to Eisy / Polisy

If you are using Polyglot / Node Servers

See Migrating Node Servers to PG3x

If you migrated your Z-Wave Network then make a backup of it (Z-Wave | Backup)

Make a backup of your newly configured IoX.

I do not think a restore will work. Maybe you are thinking of the Replace function.

You have to rewrite all the links in you modules. For the 2413U's six digit so they respond to the commands from the new PLM.

42 minutes ago, Brian H said:

I do not think a restore will work. Maybe you are thinking of the Replace function.

You have to rewrite all the links in you modules. For the 2413U's six digit so they respond to the commands from the new PLM.

It has been a long time since I did it, but what I posted above is from the wiki on migration.

This is done during the migration, so maybe when using the migration backup that is taken in to account when restoring the migration backup?

The migration procedure indicates:

"If you are using a new PLM, Restore the PLM."

  • Author

I think i have it working. Here is what i did:

-Made a backup in the admin console.

-Unplugged both the ISY and the old PLM

-Plugged new EISY into network. Admin console saw it. Did the 'upgrade packages" thing.

-Restored from the saved file. Then i saw all my devices in the console.

-Plugged in the new PLM and then clicked Restore PLM in the admin console.

-All my insteon devices beeped as they relinked to the new PLM i guess.

All seems to be working although i lost Alexa spoken commands. Not that big a deal. The admin console locked up a few times, so i rebooted and restarted a few times.

39 minutes ago, windrockwater said:

I think i have it working. Here is what i did:

-Made a backup in the admin console.

-Unplugged both the ISY and the old PLM

-Plugged new EISY into network. Admin console saw it. Did the 'upgrade packages" thing.

-Restored from the saved file. Then i saw all my devices in the console.

-Plugged in the new PLM and then clicked Restore PLM in the admin console.

-All my insteon devices beeped as they relinked to the new PLM i guess.

All seems to be working although i lost Alexa spoken commands. Not that big a deal. The admin console locked up a few times, so i rebooted and restarted a few times.

That is the procedure posted above, but I was only posting the answer to your question about the plm.

Go back to the wiki and follow the rest of the migration procedure.

Going from memory, you need to go through all your programs and network resources if you have any. You may need to reserve each one.

You also need to migrate pg3 and possibly some action in the portal. Follow the instructions in the wiki and you should be good to go.

Create an account or sign in to comment

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.