I was notified up an update. I update. The console closes and I open it. But surprise! "The Admin console is not compatible with the installed version of the IoX Firmware".

Not all of us live and breath Eisy. We just use it. Now I'm out searching these forums on how to update the console.

Please help those of us that are not power users. Updates should not be painful in 2026.

How the heck do I update the console? The program says not compatible, then I click OK and it closes. So now I can't open the console. UGH!

I thought I saw a message many months ago that this was going to be simplified.

Edited Saturday at 02:44 AM5 days by nowandthen

To update the admin console, in IoX finder, choose "Admin Console (cloud)", this will update your admin console version.

10 hours ago, Guy Lavoie said:

To update the admin console, in IoX finder, choose "Admin Console (cloud)", this will update your admin console version.

That never appears in my IoX Finder. Any links I had to update or load the latest IoX are defunct now, again. This happens every upgrade so I feel his pain.

I have not been able to find or install the proper IoX avatar/link since the last upgrade now. The older one I am using will not install on the windows 11 task bar on the Desk top screen.

Edited Saturday at 12:57 PM5 days by larryllix

Just learn to avoid the finder unless you are remote.

Do this instead, after every update.

-enter this in your browser: http://<your Eisy IP>:8080/admin.jnlp

-a file titled admin.jnlp will download.

-move it to your desktop or other easily access location

-click on it. this will take you DIRECTLY to your Eisy w/o using the finder

-enter your local username / password.

This direct link will work until the next time you update and then just do it again. Easy, simple and quick.

On 2/21/2026 at 10:18 AM, dbwarner5 said:

Just learn to avoid the finder unless you are remote.

Do this instead, after every update.

-enter this in your browser: http://<your Eisy IP>:8080/admin.jnlp

-a file titled admin.jnlp will download.

-move it to your desktop or other easily access location

-click on it. this will take you DIRECTLY to your Eisy w/o using the finder

-enter your local username / password.

This direct link will work until the next time you update and then just do it again. Easy, simple and quick.

Thanks. That got me this but when run anyway, got me the windows 11 taskbar compatible launch link.

Where the v6.0.0 came from, is beyond me..

However, now my ISY Portal credentials do not function to get me IoX access. The old admin/password doesn't work with this either and locks me out.

Geeesh....this keeps getting worse.

I guess I am sticking to the java launch icon (start.jnlp) . So tired of fighting with this every update. Every saved link, so far, has disappeared or stopped functioning. The latest install link technique never works the next update.

Edited Monday at 01:27 PM3 days by larryllix

Clear your java cache. https://www.java.com/en/download/help/plugin_cache.html.

If you just type java in the windows search box you'll see the java admin as an option. Delete all temporary files and applets.

Then download the following.

https://isy.universal-devices.com/start.jnlp

It will put the iox launcher icon on your desktop and it will always get the right version. Even multiple versions if you have multiple isy's.

44 minutes ago, larryllix said:

Thanks. That got me this but when run anyway, got me the windows 11 taskbar compatible launch link.

Where the v6.0.0 came from, is beyond me..

However, now my ISY Portal credentials do not function to get me IoX access. The old admin/password doesn't work with this either and locks me out.

Geeesh....this keeps getting worse.

I guess I am sticking to the java launch icon (start.jnlp) . So tired of fighting with this every update. Every saved link, so far, has disappeared or stopped functioning. The latest install link technique never works the next update.

when connection locally, you do not use your portal credentials.. you use your local username/ paswd

1 hour ago, dbwarner5 said:

when connection locally, you do not use your portal credentials.. you use your local username/ paswd

When you load IoX launcher on your desktop, it will find ISY automatically but it will only automatically give you the portal login. If you want to add the local option, click "add" and then type in the url. ie, http://xxx.xxx.xxx.xxx:8080 or you can use the https://xxx.xxx.xxx.xxx:8443 if you want an encrypted connection (I don't see the point when inside your lan). If you have your ISY across a vpn or on a different vlan, or you have auto-discovery blocked by your router, then you will need to manually enter the ip no matter what.

Whether you use the local credentials or portal credentials, it doesn't matter, both work the same. And the login prompt will tell you which to use in case you lose track of what you clicked on.

EDIT: This is where you want to delete all the java saved applets and configurations. This is very important. When you relaunch the start.jnlp you will get the iox launcher that autodiscovers the firmware and works across multiple firmwares of ISY. Generally, I have found that it will also not need to be cleared again upon further updates to ISY. But if it starts giving you issues, then just repeat this process.

Edited Monday at 04:17 PM3 days by apostolakisl

@apostolakisl All great and correct information.

However, the easiest method though when local is to skip the finder completely.,

http://<your Eisy IP>:8080/admin.jnlp

and click on the link that gets downloaded. Use local NOT portal credentials when prompted by the EIsy and you are immediately connected. No waiting, no manual loads, just a simple and immediate connection.

42 minutes ago, dbwarner5 said:

@apostolakisl All great and correct information.

However, the easiest method though when local is to skip the finder completely.,

http://<your Eisy IP>:8080/admin.jnlp

and click on the link that gets downloaded. Use local NOT portal credentials when prompted by the EIsy and you are immediately connected. No waiting, no manual loads, just a simple and immediate connection.

I believe that loads a firmware specific IoX launcher. At least it used to, perhaps that has changed. I have had issues with that in the past still getting messed up by cached Java stuff when firmwares change. Again, I haven't messed with this in a long time since I just keep using IoX launcher that I downloaded a long time ago that keeps working on multiple and updated versions of ISY firmware without needing any update to the launcher. The main issue I run into is after updating the actual Java app, not updating ISY. I also manage multiple ISY's at different locations over VPN's so I manually put in the IP addresses. Though you could also go to the ISY portal and copy the portal URL for your ISY and do it over the open internet.

In short, either way works. I would suggest that he completely clear Java cache and applets to be sure that everything is starting off fresh.

7 hours ago, apostolakisl said:

Clear your java cache. https://www.java.com/en/download/help/plugin_cache.html.

If you just type java in the windows search box you'll see the java admin as an option. Delete all temporary files and applets.

Then download the following.

https://isy.universal-devices.com/start.jnlp

It will put the iox launcher icon on your desktop and it will always get the right version. Even multiple versions if you have multiple isy's.

The java cache must be one of the problems here. Where else would it get v6.0.0 to report?

However, the credentials input box states, to use my portal credentials and my local credentials haven't worked for a month or two now shortly after the new credential login technique started.

As the OP stated in his concern, the technique keeps changing and the method of recovery works for a short while each time and other times not at all. The Iox Finder was tooted to self adapt to various versions and this would not be required anymore. My take is that the technique attempted must not have worked out..

Every time my IoX Finder tops working I post in the forum and get a different technique to recover. That seems to be the only way currently.

Thanks all.

On 2/21/2026 at 10:18 AM, dbwarner5 said:

Just learn to avoid the finder unless you are remote.

Do this instead, after every update.

-enter this in your browser: http://<your Eisy IP>:8080/admin.jnlp

-a file titled admin.jnlp will download.

-move it to your desktop or other easily access location

-click on it. this will take you DIRECTLY to your Eisy w/o using the finder

-enter your local username / password.

This direct link will work until the next time you update and then just do it again. Easy, simple and quick.

Brilliant. Thank you for this!!!

On 2/23/2026 at 1:51 PM, larryllix said:

The java cache must be one of the problems here. Where else would it get v6.0.0 to report?

However, the credentials input box states, to use my portal credentials and my local credentials haven't worked for a month or two now shortly after the new credential login technique started.

As the OP stated in his concern, the technique keeps changing and the method of recovery works for a short while each time and other times not at all. The Iox Finder was tooted to self adapt to various versions and this would not be required anymore. My take is that the technique attempted must not have worked out..

Every time my IoX Finder tops working I post in the forum and get a different technique to recover. That seems to be the only way currently.

Thanks all.

Must not have been using finder. The start.jnlp link must be used, not admin.jnlp. The finder can access multiple isy's on different firmware at the same time. For a while I had a 994i and Polisy at the same time with way different firmware. Clearing the cache is still an issue after updating java, not after updating isy. For local credentials you must manually add. Http://xxx.xxx.xxx.xxx:8080. If you let it automatically find your isy it will go through portal credentials. It really would be fine if it weren't for java updates. Seems like every windows update triggers a java update.

The credentials that are required are a function of what port you are attempting to access, not what method you are using to access the box. Here is a summary:

Access methods available with any version of IoX:

Interface protocol port Credentials Invocation

--------------- -------- ---- ----------- ---------------------------------

AC http 8080 local start.jnlp -> http://BOX_IP_ADDRESS:8080

AC https 8443 local start.jnlp ->https://BOX_IP_ADDRESS:8443

Additional access methods available when IoX >= 6.0.0 :

Interface protocol port Credentials Invocation

--------------- -------- ---- ----------- ---------------------------------

EISYUI http 80 ISY_Portal http://BOX_IP_ADDRESS

EISYUI https 443 ISY_Portal https://BOX_IP_ADDRESS

AC http 80 ISY_Portal start.jnlp ->http://BOX_IP_ADDRESS

AC https 443 ISY_Portal start.jnlp ->https://BOX_IP_ADDRESS

On 2/25/2026 at 8:11 AM, Athlon said:

Brilliant. Thank you for this!!!

I know.

And I dont understand why more people dont know of this method or use it. IT IS FAR SUPERIOR than dealing with the finder.

On 2/25/2026 at 2:11 PM, apostolakisl said:

Must not have been using finder. The start.jnlp link must be used, not admin.jnlp. The finder can access multiple isy's on different firmware at the same time. For a while I had a 994i and Polisy at the same time with way different firmware. Clearing the cache is still an issue after updating java, not after updating isy. For local credentials you must manually add. Http://xxx.xxx.xxx.xxx:8080. If you let it automatically find your isy it will go through portal credentials. It really would be fine if it weren't for java updates. Seems like every windows update triggers a java update.

This will all come up again in a years time and I will ask again. One method has never worked more than twice yet for years now. I have given up trying to document a method that will be useless next year.. LOL

Iox finder would be perfect if it weren't for Java updates. You would load it once and be done. Any isy that it finds or you direct it to find (port 8080 or an isy on a vpn or vlan) would populate and be there indefinitely regardless of isy firmware current or future. But for some stupid reason java makes you redo it with every update.

I just bookmarked the page for the start.jnlp link so I can quickly redo it after each update of java. I have not tried where iox finder lets you save/load your configuration. Probably that would let me not manually add back my off-site isy and port 8080 preference.

12 minutes ago, apostolakisl said:

Iox finder would be perfect if it weren't for Java updates. You would load it once and be done. Any isy that it finds or you direct it to find (port 8080 or an isy on a vpn or vlan) would populate and be there indefinitely regardless of isy firmware current or future. But for some stupid reason java makes you redo it with every update.

I just bookmarked the page for the start.jnlp link so I can quickly redo it after each update of java. I have not tried where iox finder lets you save/load your configuration. Probably that would let me not manually add back my off-site isy and port 8080 preference.

I had it bookmarked also but that quit working about 6 months ago again.
That is what I am doing here again, annually...LOL

I save the IoX finder list to a file. Then if something happens (like a java update) I just reload the file and I'm back in business.