I started the v6 upgrade (with admin console Upgrade Packages) over two hours ago.

I never got any acknowledgement that it completed, but all the checks I know how to perform seem to indicate it may have.

Checking https://eisy.local:8443/WEB/sysconfig.txt says:

FreeBSD eisy 14.3-RELEASE-p3 FreeBSD 14.3-RELEASE-p3 #4 releng/14.3-n271444-30ad842dd970-dirty: Sat Sep 20 23:18:26 PDT 2025     root@bsdev143.isy.io:/usr/obj/usr/src/amd64.amd64/sys/eisy amd64
*** Package Information ***
************ UDX ************
udx-4.0.4
Name           : udx
Version        : 4.0.4
Installed on   : Sat Oct 18 14:06:04 2025 MST

When I call up https://eisy.local:8443 in a browser, I get a login that responds to my portal ID, and an invitation to add stuff to a blank page.

When I SSH into the unit, it has reset the admin password to the default.

The unit still responds properly to manual device and scene commands from my iPhone MobiLinc Pro app (won't try the admin console as it hasn't officially announced completing the update).

How do I know if everything is cool despite the lack of completion dialog?

Edited 7 hours ago7 hr by lhranch

In the admin console you should have had a popup window telling you the the update completed.

Now when you login from the IoX Launcher your user name will be your email addres and the password is your portal password

Your config file confirms the update is installed

It's best to reboot the eisy then clear your java cache, be sure to check all 3 boxes, and download the IoX Launcher from here: https://isy.universal-devices.com/start.jnlp

I didn't get any completion popup at all, which was the reason for my post.

I rebooted the eisy and cleared cache, and I haven't run into anything yet that isn't working. Thanks for your advice.

I'm not happy to have to use the Portal login info (which has a strong PW) instead of the weaker local credentials I used to type in every time I needed to fix something, especially since Java doesn't interface with any of my PW managers OR honor the Keyboard Shortcuts / Text Replacements feature of MacOS.

1. Is there any way (SSH, whatever) to set up an alternate (local) user ID/PW I can use for frequent logins?

2. Does this imply that I will not be able to login to the admin console during an Internet outage because I cannot reach the portal?

You can add the attached URL entry to the admin login which will bypass eisy ui and use your previous (local) login info

Not sure what happens during an internet outage, we haven't had one.

9 minutes ago, lhranch said:

I didn't get any completion popup at all, which was the reason for my post.

I rebooted the eisy and cleared cache, and I haven't run into anything yet that isn't working. Thanks for your advice.

I'm not happy to have to use the Portal login info (which has a strong PW) instead of the weaker local credentials I used to type in every time I needed to fix something, especially since Java doesn't interface with any of my PW managers OR honor the Keyboard Shortcuts / Text Replacements feature of MacOS.

1. Is there any way (SSH, whatever) to set up an alternate (local) user ID/PW I can use for frequent logins?

2. Does this imply that I will not be able to login to the admin console during an Internet outage because I cannot reach the portal?

The new login in method is an option (makes going between admin console, PG3 and portal seamless). You can continue logging in using the previous way too, as long as the URL contains the port number (8443) as it always has. Good ole "admin" and your IoX password.

I'm confused by both these responses.

My standard method of maintaining the eisy (and the subject of my password complaint) is the Admin Console. There aren't any URLs involved in that process, so I'm not sure how to apply this advice.

If I pop the URLs offered above into a browser, I get varied results. Using either https or http to the name of the eisy (with appropriate ports 8080 or 8443), I get a blank page. If I add /desc onto either of those, I get the same config file both ways, so I know the ports are working OK. But neither case requires a password.

If I simply browse to the name of the eisy, http or https, no port specified, I get the new login window regardless, which does require a name and password, but I haven't set it up to be useful yet and might not for a while. I'm assuming this is the interface Techman suggests I can bypass or augment. But in that case, I am unsure how to interpret the shorthand instruction, "add the attached URL entry to the admin login."

In the IoX Launcher window, click on ADD, then enter the URL info on the 2nd line, then click on Save.

This will create an additional entry in the IoX Launcher for local access using your previous login credentials. The login window will either ask you for your ISY login info or your portal login info dependinng on which line you click on

Oh! Genius!

Thank you!