Geddy

There is a migration process (UD links to it in their email release). Although you can also review the UD Wiki for the eisy user guide that has the migration process included. https://wiki.universal-devices.com/Eisy:User_Guide In typical migrations from ISY994 to eisy most Insteon is simply moved to the new device. Everything should look and act exactly the same. There are some issues that have been posted about here (probably a while back now), but I think the process is fairly straight forward and seems to work (the posts here about it not working might be rare cases because most won't come to the forums to post "it worked as described"). And the option of what to upgrade to is simple...only the eisy is available from UD at this time. The Polisy is no longer available. That's why this topic is asking about upgrading from the Polisy to eisy.

From recollection when the eisy was released there is marginal differences on the surface level as far as IoX and Plugins are considered. I think all the underlying programming that UD handles is the same (or at least very close to identical). The reason for the eisy introduction when it was released was lack of ability to source the hardware for the Polisy (one of those issues that can be blamed on covid and the supply chain issues that followed). As stated above if you've got a working Polisy at this time just keep it updated. UD pledged to support the Polisy for several years after the eisy was released. That timeframe I do not recall for certain, but think it was several years. We are a couple of years since the eisy was released so expect the Polisy to continue to be supported for a few more years as long as UD can keep the code for the two devices similar. I moved from Polisy to eisy when the eisy was released. I do not experience any difference in my use. I have a mid-size Insteon install (~70 nodes +/-), 6 z-wave devices, 4 zigbee devices, and maybe 5 plugins. I don't get crazy with programming or variables. Since the underlying IoX code is identical there's no "speed" difference. I'm sure the device processing power might be different/better, but at the end of things IoX computes the change and sends signals out via the PLM so there's not any speed difference, at least probably not that a we could tell in the real world use (as @larryllix points out).

When you log in this way use your portal credentials. Needs the port like @slimypizza suggests. If you're downloading the admin.jnlp from the device itself then you've got the IP right. Are you not using the IoX Launcher? That's start.jnlp and is available from the UD website (clicking "My ISY" on the top right) or linked in the Wiki.

@KenUD2 if you cannot connect locally, but the portal says the eisy is connected then it's still something locally blocking local network traffic. Are you running different vlans? Do you have a firewall device or different SSID that is blocking cross communication? But you're able to get something working after a reboot? If you cannot connect with IoX Launcher what computer system are you using (Windows 10/11, MacOS, other)? Can you connect with IoX Launcher after you power cycle the device? It might be best to open a support ticket with UD and see if there's something happening in the logs. Go here to open a support ticket: https://www.universal-devices.com/my-tickets Please post back with answers to the above questions as well as if you get help via the ticket what happens to resolve the issue so we can learn and it might help if others have a similar issue down the road.

Did you create at least one notification with UD Mobile? According to the post by @Javi in the thread at least as of last year UD Mobile would create a template and increase the number if there was already one created. It's possible something has changed as both systems developed over the last year. Might also need to run a sync on UD Mobile (while Admin Console was CLOSED) then re-launch admin console.

@KenUD2 this sounds like a possible internal network issue blocking communications. Have you setup UD Mobile with local access and can you still control devices while local with UD Mobile this way? Have you checked the Portal to see if the eisy is connected (https://my.isy.io/)? This might be something you need to open a support ticket (https://www.universal-devices.com/my-tickets) with UD to get the logs checked. There was a portal maintenance scheduled about a month ago. Did it happen then and since? Have you performed a full power cycle of the eisy? Lastly, what firmware are you currently running (please give actual version number)? Please be sure you're up to the most recent release (5.9.1) - be sure if you're not current to read the release announcement to be sure you don't run into issues. Don't blindly click the upgrade process without reading and preparing for the update.

@matapan the link that @Techman posted includes some information about having to enable the .jnlp to run (and if you've got -8 means you must have a lot of start.jnlp downloads (at least from a Windows user any -# or (#) means you have multiple copies of the same file. Delete all old "start.jnlp" or "start-#.jnlp" files. Also, the part about Apple not letting it run because it's from an unknown developer is covered in the wiki: https://wiki.universal-devices.com/Main_Page#Unidentified_Developer_Blocked Seems that Apple is fighting the Java world more than Windows is sometimes.

@slimypizza glad things are returning to normal. I wonder if you might have had a surge from some of the storms we had push through ATL recently. Not sure what side of town you're on, but we did have some recently that carried a lot of lightening. So random, but glad that resetting them and restoring them in the eisy seems to be bringing things back to normal. @Guy Lavoie agreed - this is one for the memory bank for future troubleshooting and hopeful tips for good outcome.

@matapan what version of macOS are you running? More than likely it’s a macOS issue with the certificate and not something you need to do with/for the ISY994. If you’re on an older version of macOS there are some possible support stems in the wiki you should try. Otherwise, there have been others that have posted help for getting IoX Launcher and admin console working on macOS. Maybe try a Google Site Search to find those posts. Be sure you review this recent post about getting things to load:

I've never attempted such a restore process. Might be time for a support ticket with UDI to see if there is any troubleshooting they can see. Very strange that the switches work with other controllers since they all go through the eisy/PLM to operate the switch. When a physical switch doesn't operate when manually controlled it usually means the switch is bad or wiring to the switch is bad. If you were to remove the eisy all switches should still at least function when manually operated. I would test a few switches by factory resetting them, removing them from the wall and setting up a local test loop to see if they do function correctly on their own. Agreed that it would be unlikely so many switches fail at once, but further unusual that if they were controlled by the PLM/eisy then you have them exposed to Echo via the UD Portal and HA via the ISY integration that those 3rd party controllers are operating the switch when they basically pass code back through the eisy to PLM to switch. If you've setup some direct connections to HomeAssistant then that makes sense why the eisy isn't controlling them, but no sense why they wouldn't operate manually.

Is the old PC still available? Does it still connect? Why can you not just continue to use that PC?

@pooderbill first DO NOT UPDATE YOUR ISY! At least don’t randomly update to 5.x firmware. Your system is very old. I do not think IoX launcher will work for that old firmware version. You are better off downloading the admin.jnlp from the device itself. I forget the exact link, but reading the wiki should get you the URL to try. https://wiki.universal-devices.com/Main_Page The link should be something like http://ip.of.isy/web/admin.jnlp (but just going by memory and it’s been a while since I tried it so double check on the wiki. To answer your question, yes, Java’s.exe should be what you need to run the .jnlp file. Make sure you don’t have any 3rd party firewall or antivirus apps running. The reason not to upgrade is there is a huge change from 4.x to 5.x. If you’re happy with how your system is running then you do not need to jump up to the last version for it. There is a big change and lots of issues if you’re not prepared to update. The most I would suggest is to update to the last 4.x version (I think 4.9), but DO NOT update to 5.x until you’ve don’t A LOT of reading on the forums (not sure if really old posts are still available, but try a good search for issues updating from 4 to 5.

@cksedg what lights do you have on the front of the ISY994? Refer to the wiki for issues: https://wiki.universal-devices.com/Main_Page#Front_Panel_LEDs/Lights You might also want to unplug the device, remove the micro SD card and use a soft eraser on the connections and reseat the card in the device. It’s possible the SD card needs adjustment in the device or has become corrupt. Last thing would be to remove the .state files mentioned here: https://wiki.universal-devices.com/Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored Are you running any 3rd party antivirus or firewall apps? Turn them all off after trying the above. What version of Windows are you running? On the network settings be sure your home network is set to private (and not public) type.

@pjjameso have you relaunched admin console since making the changes? I’m not sure what you mean by adding in portal but not seen in NS (assume you mean plugin?). The flow of information is from Plugin to Admin Console to ISY Portal.

@pjjameso this happens to me often. No telling what exactly happens since I run admin console a lot (troubleshooting other posts) so I know it’s not only when Java updates. It just gets flushed somehow now and then. I assume since the .state files are in a temp folder they get overwritten or “updated” back to default and I just have to reset the size. A PITA for sure, but not too difficult to reset. Hopefully the web interface is available soon….and not mice type! (And hopefully better colors, as the font/background colors on admin console leave a lot to be desired too!)