DennisC

Try rebooting eisy first. Also, be sure to synchronize UD Mobile, then try adding the favorite back.

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.

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."

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.

Since at least the release of v6.0, the recommended method for accessing pg3x is from eisy.local. In fact, using any other method involving port 3000 potentially impacts some plugins. Using the local port causes some plugins, including Elk, to disconnect and than reconnect. This is also the case if you access pg3x from UD Mobile using a local connection. It is something UD is working to correct. As for login credentials, UD is moving to single sign on concept. Currently, for the Launcher & eisy.local you use your portal credentials. Using ssh, remains the original a**** credentials. Connecting locally, by directly downloading the admin console is still your local credentials. Hope that helps.

Try entering easy.local in Chrome browser and see if the new UI loads. If you get to the login screen, use your ID portal login credentials. If that works, you can also access pg3x from the menu. If it doesn't, open a support ticket with UD to get things straightened out.

Now that I am at a computer, here is the link to the wiki instructions: https://wiki.universal-devices.com/UD_Mobile#Backup_and_Restore

Before switching phones, make sure your phone is backed up so all of your programs will load on your new phone. Specifically for UD Mobile, do and app backup, which will take a snapshot of your app settings and favorites. After your new phone is up and running, you can import the app backup. Be sure to save the app export backup in a location you can load on your new phone when the time comes to restore it. There are detailed instructions in the wiki for exporting and importing the backup.

While you wait for UD to get back to you, try a new power supply.

It looks more like a PLM issue to me. Is your PLM connected, how many links are shown?

That's the version that corrected the issue for me.

I'm not sure you are in the right location. While you can check plugins within UD Mobile, it might be best to use eisy ui. From the menu, select Pluging, Dashboard. That will open the dashboard for all plugins. Check slot 1.

When was the last time you ran upgrade packages? I have another post that talks about this issue and around beginning of December, and update to udx corrected the problem. I suggest upgrading packages, reboot when instructed, and after everything is up and running, an UD Mobile sync. Before syncing UD Mobile make sure you are on latest version.

UD support is aware of both of these issues. I reported them this morning and was told they are looking in to #1 and #2 is a known issue.

@dbwarner5 Would you be able to check something for me? Sign in to eisy.local and go to menu Plugins Dashboard. Is Elk Plugin connected? Next go to Elk nodes tab and see if the nodes are populated with values.