DennisC

Yes, I am. My Polisy is shown in the finder, but I have to clear the not found message twice before I can access the admin console. In addition, my backup repeatedly fails.

I tried the fix this morning and it is not working. I have informed support.

Glad you are up and running. I also use Elk outputs any time I come across something ant fully supported on the ISY side. I think you will find the Elk node server well worth the investment. There is great support and actively being developed.

I communicated with support yesterday about this issue. There was supposed to be a behind the scene fix for this issue last night. I haven't attempted to do this yet this morning, but what needs to be done is the following: 1. Clear Java cache - check all 3 boxes to delete files and applications. 2. Download a new start.jnlp from UD - the link is in the wiki. 3. Run start.jnlp and the IoX Finder should be added to your desktop.

You can also set up Favorite tile of the Command type and for the action have it run the "then" portion of the program. Create a second one to run "else". This way with push of the button you run the section of a program you want. You can then add a custom name and have the tile change color when running.

Yes, but how often do you do this? As @Geddyexplained above, when there are repeat notifications, the provider picks up on it and starts throttling the delivery time.

I do this for most of my tiles in Favorites. Huh? Why? Here is what I do: Once I decide the colors I want to use, I enter the hex code in a note app on my phone. I go to my Favorites click on edit icon, enter the formula and then copy and paste the hex color code. If I am doing a lot, I even spend a minute in the note app and enter the custom naming I want. That way I can copy and paste that info also. Once I get going I can knock out a lot of them. @Javispelled out how to do this for you. I do it for my wife's phone and my tablet, it is very eisy and works well. I also used to use Mobilinc, but I dropped them when they refused to add support for node servers because it was a "beta" feature. I find UD Mobile eisy to use, fast to respond, and I can customize it how I want.

As we already indicated, that's an issue with Verizon. The only fix has been explained by myself and @Geddy.

No, Notifications with Pushover will not require UD Mobile. However, while there is a trail period, there is a charge for Notification node server. Using UD Mobile with the free Notification node server has no cost.

There is not going to be a fix for something that is normal and expected behavior. If eisy is discoverable on your network either as a local host or IP address, it will show up in the Launcher.

I also have Verizon and moved away from using default notifications because of delays. This was back on my ISY. I moved to using the Notification node server and Pushover. Very fast delivery of all notifications and many options you can set. I also use the native notifications built in to UD Mobile. That uses a free Notification node server arrangement, so you could try that for no charge. If you like it and want some extra features, you can move up and buy the Notification node server. Many have experienced delays through Verizon, you are not unique.

Follow my advice above and run upgrade packages again. There was a patch issued that fixes sluggish systems but does not update version number. Let's make sure it's not the problem.

Have you considered moving to UD portal and UD Mobile? You would much less problems. UD Mobile is actively being supported and we get excellent support from the developer. It is also quick and very customizable.

The status of your shade shows 50%, what was the shade position before setting it to 50%? We will need more information to try to help you. You should do some testing to determine actual shade position, node settings and what happens at various positions. Observe the event viewer set to level 3 while testing. Also, check the logs for information.

What version firmware are you running? If not on v5.6.4 with the patch that was released about a week ago to fix sluggishness, try updating followed by a reboot.

After clearing your Java cache, download start.jnlp from UD to access your ISY. It will install ISY Launcher to your desktop, which is the prefered what to access the admin console. If the Launcher fails to find your ISY, you can click on add and enter your LAN IP address. Installing the Admin Console Icon on Your Desktop It's always best to use the Admin Console application which is browser independent. To do this: Clear your java cache Use the ISY Launcher to launch the Admin Console. This should put an icon on your desktop once you run the downloaded start.jnlp file. Click on the discovered 994, Polisy, or eisy and you will see this menu Admin Console (LAN) This menu item downloads the Admin Console directly from Polisy Admin Console (Cloud) This menu item downloads the Admin Console from our cloud servers Regardless of how you get to the Admin Console (Cloud vs. LAN), the results are the same: Admin Console is brought up and connected directly to your Polisy. Admin Console allows you to add/remove/change Z-Wave/INSTEON devices, make programs, and make configuration changes. The best source for what you can do with the Admin Console is our ISY Cookbook .

Try one more thing and if that doesn't work, open a support ticket with UD. Try 6 presses of the multi function button and wait for the unit to shutdown. After it does, remove power, wait a minute and power it back up. Give it sufficient time to completely restart and then try upgrade packages by either 1 press of multi function button or the button in admin console. Afterwards you will need to reboot again.

Try rebooting and then try the backup.

I run a Polisy at one location and an eisy at the other. Yes, I would do as you are suggesting and use eisy at the larger site. If you read the migration instructions it covers upgrading a Polisy to eisy.

I am wondering if an update was interrupted before finishing. Try updating with the multi function button (think it is 1 press). Wait at least 20-30 minutes and follow that up with the 6 button press and pulling the power suggested by @Geddy.

Try rebooting and then try again.

@Geddywas spot on with his advice. Document your programs before you start, including disabled programs. Be sure to follow the migration instructions completely. Make sure you are on the latest firmware for each system before you migrate and remember, there is a minimum firmware you must be on to migrate an ISY. You don't state what you are currently running. Makes no difference if you convert to the Elk node server before or after moving to eisy. However, there will be some manual intervention required once you migrate to eisy. So if you change over to the node server before migrating, you will need to complete manual work twice. Most importantly, read and follow the instructions and ask questions if you don't understand something before doing that step.

Since you are on v3.2.1 for PG3x, you haven't run upgrade packages since last week when a patch was issued to correct systems bogging down and being slow to respond. Suggest you upgrade packages and after all is done, reboot. PG3x should update to v3.2.2. If you can't log in to upgrade, try from UD Mobile if you have it. If not, try power cycling and then updating. I think this might correct your issues.

You always needed to back up Zwave separately, even with the ISY. This needed to be done before taking a "migration" backup. You need to start over following all of the directions in the link I sent earlier, starting here (I highlighted some important info): Preparing for Migration from ISY-994 On your ISY-994 Make sure the ISY-994 is upgraded to 5.3.4, If you are migrating your Z-Wave network You must be using a 500 Series Board in the ISY-994 Make a backup of your Z-Wave network (Admin Console | Z-Wave | Backup) Make a backup of your ISY-994 (Admin Console | File | Backup ISY) Power down your ISY-994 (very important). ISY-994 needs to be powered off because when you migrate, both your ISY-994 and Eisy / Polisy will think they are controlling the Z-Wave network. If you are not migrating your Z-Wave network Make a backup of your ISY-994 (Admin Console | File | Backup ISY) 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 ISY) 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 ISY) 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. Post Migration If you migrated your Z-Wave Network If you have any Z-Wave nodes with a type of (Placeholder) it means the device has not been migrated yet. In most cases they are battery powered devices that were not awake during migration To migrate one of these devices, wake it up (see user manual for the device) and then do the following right+click on a placeholder node for the device, select Z-Wave | Synchronize | Update with Interview When it completes do the same for the next device

Did you back up Zwave and then make a migration back up in according to the following instructions: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration