Geddy

@62vetteefp Lots of good help above, but your information seems to be all over the place. It appears that your ISY994 might not even be on the network. I think you need to review the setup for your network.
You have an AT&T modem/router/gateway from what you state above.
Connected to that you have an EERO device (this is a router). Do you have the EERO setup as an access point or is it also trying to act as a router? If so you probably have poor network setup and something isn't allowing the ISY994 and your laptop to talk to each other.
What is the network cable of the ISY994 plugged into? 
On your computer what OS are you running? Are you running any VPN or Anti-Virus software? If so turn them all off. 
No, you DO NOT need to have Portal to be able to access your ISY994 as long as you are local to the device. 
 
However when you were logged into the portal could you see the UUID of your ISY994? The UUID should also be the MAC address that you would see on the router. (NOTE: I did just plug my old ISY994 in and it seem to be the case for me. I do NOT have this ISY994 connected to the portal account so it doesn't show up there for me, but did show up in the ISY Finder window and I confirmed by looking at the MAC addresses connected to my router.
I say this so that if/when you get on the router that the ISY994 is connected to you should see a MAC address that matches the UUID when you look at connected devices.
In the end...I suspect this is a networking setup issue that you have that should be worked our.
 
This also points to it being a network related issue. Sounds like the ISY994 is unable to connect to an outside time server. It's possible that it hasn't been working correctly since the time change (if your area adjusts for daylight saving time). Also by not being able to connect to the time server if the device has floated time it's possible it could be far out of sync of the "real" time. 

@Tony-D unsure how to run Java on rpi5, but you need some sort of java platform like what Windows users have for javaws. Perhaps the best bet since you're on rPI would be to use the direct admin.jnlp downloaded from the ISY994 rather than trying the launcher (that has been the standard for over 6 years). 
Try:  http://ip.of.the.isy/admin.jnlp   (be sure to change to put your actual IP address for your ISY994)
No browsers are necessary. It's all independent of the browser. Once you have the admin.jnlp it should log directly into the ISY994. Note: If you ever update the firmware you'll need to clear you Java cache and download the admin.jnlp again from the updated firmware. 
If you still have access to your friend's windows Laptop make sure it's on the same network as the ISY994, download the start.jnlp from the UD website (clicking on "MY ISY" on the top right). It should put the "IoX Launcher" icon on the desktop. Use that to access the admin console. Again, no special browser process is needed. It's directly Java related since all browsers dropped the Java script method used many years ago.
One thing to consider is if you set a static IP address on the device and changed routers you could have changed your DHCP table and the ISY994 might not be connecting to the new DHCP range. Since you still have your old ISP and if/when you can get into the ISY994 make sure you change it to Dynamic IP so the ISY994 will connect to the new router. You should then setup an IP reservation on the new router/gateway so the ISY994 is always at that IP. DO NOT SET STATIC ON THE DEVICE!
 
Review these sections of the wiki:
https://wiki.universal-devices.com/Main_Page#ISY_Launcher_cannot_find_ISY
https://wiki.universal-devices.com/Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop
 

I believe this is normal. You can find other conversion comments in the forums that seem to indicate this is expected. Make sure you follow the rest of the steps that @Techman linked to in the wiki. Pay attention that the user/pass will now be the same as admin console access.
Once you confirm you have PG3x then run the upgrade process again and you should update to IoX 5.8.4 (the current release)
If you did not get upgraded to PG3x in the process then please open a support ticket to get specific help for this issue. 
https://www.universal-devices.com/my-tickets/
If I was running a Polisy I wouldn’t worry about upgrading to eisy until UD made an official announcement that they would end Polisy support/development. No need to worry about it at this moment. Also no major need (from why I can tell) to rush an upgrade to the eisy if you have a working Polisy doing what you need it to do. 

Seems like you didn’t follow the setup instructions that were in the link @Techman supplied. Gmail has required that an app password is set now. Gmail doesn’t allow insecure passwords (I didn’t even think it was possible to turn 2FA off now, but I haven’t wanted to try). 
Be sure you follow these steps: 
https://wiki.universal-devices.com/ISY994:Configure_Mail_Server_Settings#Configuring_(unique)_App_Password
I’m not entirely sure if you need a from, but doesn’t hurt to be sure it’s included. Just pay attention to the formatting (again…as described in the wiki). 
Lastly, if you’re trying to send a test make sure you click on a recipient for the test to go to. If you have more than one it doesn’t know where to send the test and might cause a failure. 
Using Gmail server (if setup properly) does work. That’s what I’ve used from day one. I don’t use many alerts, but know it worked as of the last 3 days. 

@andrew77 looks like something has possibly been corrupted. Since you were on 5.8.0 firmware it's not like you ran an update recently so it likely wouldn't be a failed update. I somewhat agree with @CoolToys that you should bring the system up to date by running the update process. Be sure to allow a lot of time for the update to run. There have been several IoX and PG3x updates that you're probably missing (since 5.8.0 was released in January). Don't pull the power on the eisy until you've run the updates and rebooted and attempted a good log-in with admin console.
Be sure you clear java cache (checking all three boxes) when you run the firmware update. Otherwise, use the "Cloud" so you don't get an error about Firmware/UI mismatch. 
Is you're still having issues perform a full power shutdown (following the wiki for multi-function button presses). Once the eisy is powered down unplug it, then unplug the PLM. Then plug the PLM back in and after 10-20 seconds plug the eisy back in (I think the light should be steady on the PLM before you plugin the eisy). Allow some time for it to fully boot (60-90 seconds - to be safe - maybe longer if you're running a lot of plugins) before trying to open admin console again. 
If you're still getting the EXACT same errors then open a ticket with UD to get help directly. 
https://www.universal-devices.com/my-tickets

@smorgasbord This clearly sounds like you had a Static IP set at the device level. This was once the suggested option for ISY994 devices, but over the last many years UD has encouraged people to remove that setting and handle DHCP reservation at the router level. 
Since your local DHCP table changed from 192.168.50.x to 192.168.1.x and your ISY994 is not connected then clearly the IP was set to only join at the 50.x range of IP addresses.
As @hart2hart suggests changing the DHCP table back to 192.168.50.x would be the best bet. 
I would suggest this to be a temporary change and only to get the ISY994 back on the network.
If you still had your old router you could even handle it that way and directly connect a computer/laptop to the old router and then connect the ISY994 to the old router and connect that way and remove the Static IP setting on the configuration tab then unplug the ISY994 (both power and network), connect the network to the new router and power it back up. It should then connect because the IP address would be assigned by the router.
THEN, you could reserve an IP address from your router so the ISY994 would always connect at that IP address should you lose network or power to the ISY994.
Here's the other option from the wiki: 
https://wiki.universal-devices.com/Main_Page#Changed_ISP/Router_-_Can_no_longer_access_ISY
Sounds like you completely changed the network settings if you're also changing SSIDs for wireless devices. Always fun times! 

@SRS I don't recall it being possible to "migrate" any Alexa settings from Mobilinc to UD/ISY Portal. Since they were completely different portal operations. You would need to setup the Alexa items in the ISY Portal portion and install the UD skill for Alexa (I think the skill is still needed).  (More on that in the wiki)
Also note, Mobilinc does still (somewhat) work for the eisy, but only for native devices (i.e. no plugin devices). I know it works well with Insteon devices (just as it did on my old ISY994) and seems to control the limited z-wave and zigbee devices that I've tested with it.
UD Mobile is being developed by UD and does allow control for plugins and all z-wave and zigbee devices. It's a slight learning curve, but you can get a lot of help in the UD Mobile forum area should you run into any stumbling blocks there.
 

@eduardo_garcia While the forums are monitored for most active issues something like this might be better asked directly with Universal Devices via their "Contact Us" method on their website:
https://www.universal-devices.com/contact-us/
 

@TVC15 take a look at this part of the wiki
https://wiki.universal-devices.com/Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored
Sounds like you might force admin console onto one of the external monitors. It’s trying to put it there and not “smart” enough to force back to the single screen. If you delete the .state files it should come back. 
If deleting these files doesn’t help clear Java cache (checking all 3 boxes in the process) then download and run a new IoX Launcher (start.jnlp) from the UD site (found by clicking on “My ISY” at the top of the page.  
 

@FerventGeek 
I just want to ask and confirm...
Are you currently using an ISY99 (as your text says)? Or are you using an ISY994? There's no migration path from ISY99 as those were discontinued ages ago.
The old ISY99/994 cannot use the USB PLM so you can't set it up with your existing device.
For the rest, you might be causing issues and a lot of extra work trying to change from serial to USB based PLM, but I think it can be achieved if you follow the directions and perform the PLM replacement process along the way.
Mobilinc portal will not work with eisy so will more than likely break what you've got. But I don't think it worked with Polisy either so not sure what you're doing with it. You've probably got it directly feeding to the old ISY (99 or 994?) device rather than IoX on the Polisy.
There's no migration from PG2 to PG3 as it's a completely different system. So more than likely most of those integrations will be lost and need to be purchased and setup in PG3x and set back up any scenes and programs you have for them.
First and foremost, in the ISY99/994 device right click on the ROOT program folder and select "Copy Folder to Clipboard". Then paste that into a text editor (for Windows use Notepad). DO NOT USE A PROGRAM LIKE MICROSOFT WORD! This will give you a full (text) copy of all your programs so you can set them up following getting the eisy/PG3 system up and running.
 

Should be as easy as following the replace modem process in the wiki.
https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:File_Menu#Replace_Modem_(PLM)
Knowing that many have done this with the release of the eisy there have been a few posts of issues they faced. I would expect those that didn’t have issues just don’t post. 
Since you just replaced the PLM if you didn’t have issues then it should be the same process, but plugging in the USB PLM. As always UD is available for support if you run into issues. 
https://www.universal-devices.com/my-tickets/
 

@awysocki eventually “ZMatter” will include the ability to control matter devices. UD just hasn’t released the Matter ability yet. They’ve posted that it is still in the works, but no timeframe given for when it will release. 
Currently ZMatter can control Z-Wave and Zigbee devices. 
 

If you want/need something from the “mfg” you’re best bet is to open a support ticket to ask the question directly with Universal Devices.
https://www.universal-devices.com/my-tickets/
Since we are just like you (users of the devices) we don’t know any more than what’s available on UD’s site. 
My general idea would be that most consumer grade electronic devices don’t typically operate well above 100F. Just from checking a few devices I found by looking up online. 

@LFMc when running the "start.jnlp" file it is trying to connect to UD's site to download the IoX Launcher. If you've got the IoX Launcher icon on the desktop it should open without the need for internet. Then make sure you use the "local" option to connect to your ISY994. 
What computer operating system are you using? I think you're running something other than Windows (if I recall).  Typically, (speaking as a windows user) "start.jnlp" is only needed ONCE to install the IoX Launcher icon to the desktop. Then all you click/run is IoX Launcher. 
Rather than using the start.jnlp file you could attempt to use the local admin.jnlp downloaded directly from the ISY994.  I forget on the ISY994 if you need a port or not, but try:
http://ip.of.isy.994/admin.jnlp
If that doesn't do it add a port :8080 or just :80. 
Then run admin.jnlp and it should get you in.
Otherwise, if you've got a phone you can use as a hotspot to get internet on the computer for the start.jnlp to run that would be an option to at least try to get IoX Launcher back on the desktop.
@Techman - funny suggestion of downloading IoX Launcher if he doesn't have internet!
 

@mnunes 
Will you please browse to this page:   https://eisy.local:8443/WEB/sysconfig.txt    (might need to change "eisy.local" to the ip of your eisy). If you get an alert about the page not being secure click "Advanced" and then "proceed..."
Search for this text: pkg tpm2-tools
What is the result? 
How old is your eisy? Did you just receive it or had you bought it previously and just now installing/activating?
It's possible an update got hung. Have you pulled the power supply to have a full power cycle/reboot?
If you have pulled the power and still getting this alert make sure you follow the update process and allow it to fully run. Don't click away from the "okay" box when you first run the Upgrade Packages button. If you have UD mobile linked you should get some alerts that update has started. Once it completes you should get another update that it's done and needs a reboot. Then your admin console should give the same complete alert and that you should reboot. Press the "Reboot" button on the Configuration/System tab. Allow it to fully boot before you attempt to open admin console again (I usually allow about 3-5 minutes). 
If after those steps are completed you still get the error please open a support ticket and UD will assist you further.
 
With other users reporting similar issues and my tpm2-tools version being earlier than 5.6_1 I wonder if UD released some underlying update before announcing it and it's causing issues to people that ran the update process recently. I have not attempted an update recently (my last update process was after the most recent post from UD - at the end of April).
 
 

Referenced in the Wiki:
https://wiki.universal-devices.com/Eisy:User_Guide#Z-Wave_Support

 
Z-Wave = Yellow
Zigbee = Red

@someguy 
Please review: https://forum.universal-devices.com/topic/43175-pg3x-version-3219-outdated/
 
As @DennisC and the post linked above the option should be on the configuration page. 
If you're not seeing that option it might mean you are running an older PG3 version. Please confirm what version you are running and if you have run the "Reinstall all plugin" routine.
I do not run the Elk plugin so can't give a screenshot, but expect it should be an option with a checkbox. 
 

https://wiki.universal-devices.com/Eisy:User_Guide#Multi_Function_Button
This describes what the button presses will do. I would try the 5 button push to "reboot" it. Otherwise, go for 6 presses to power it down (if it doesn't shut down after 6 presses and 30-45 seconds it's "hung"). Once the light is red pull the power supply for 20-30 seconds then power it back up.  It it appears "hung" pull the power, wait 20-30 seconds then plug it back in. 
Since you already did a power cycle it might be something to open a support ticket to get some assistance:
https://www.universal-devices.com/my-tickets
 
Can you get admin console to load at all?
Can you load this page in a browser: https://eisy.local:8443/WEB/sysconfig.txt
(if it doesn't resolve try replacing "eisy.local" with your ip for the eisy.)
Just trying to see if the device is active and online in any form/shape. 
Typically if PG3 goes offline randomly something might have crashed. It should have attempted to recover. The power cycle should have helped (especially since you said you pulled the power for 15 minutes). Since you've got a blue light it appears it might have started up okay, but if PG3 still isn't running something could have hung in the boot.
 

If you don't know which Universal Devices product you're using you probably aren't using one. You can review their website for information related to what they offer: https://universal-devices.com/
It sounds like you're just using a Hue Hub and directly operating it through Alexa. Not sure how that works so I can't help you. Maybe others can, but you're probably better off looking for specifics for Alexa and Hue products. 
Good luck on your adventures!

No need to change PLM again. I also have the serial and moved it from my ISY994 to eisy without issue using the serial to USB converter cord available at the time the eisy came out. It appears UDI is offering a different cable now that doesn't require going from the serial to USB cables so it might be shorter and one less thing to worry about in the communication aspect.
It does concern me that you just replaced the PLM on the ISY994 and you think either it or the ISY are flaky. Might be worth making sure you have a solid backup from the ISY994 before migrating to the eisy to avoid bringing over any funky issues.
I will make sure to suggest to you that you make a "hard copy" of all your programs currently on the ISY994. On the Program tab right click on the root folder (usually "My Programs") and use the last menu item of "Copy to Clipboard". Then paste into a text app (for Windows I suggest Notepad). NOT into a word processing app/document - you don't want to risk auto formatting changing things. Save this file somewhere so you can reference the programs after your migration. If you have Z-Wave or are not on 5.x firmware on the ISY994 there might be some adjustments needed for the programs and this file will help a lot of steps with correcting any program issues that might occur. 

@Nishal & @737simguy not a direct update from @Michel Kohanim, but posted in another thread that they're "very very close".
 

YES! When you use the Portal URL and connect with the "cloud" option you have to use the my.isy.io portal credentials.
 

Seems the "fix" is out. See if updating helps your issue.
 

@ctviggen1 are you running antivirus and/or firewall software on the computer?
Disable both, clear Java cache (checking all 3 boxes). Delete any old copies of start.jnlp (and/or admin.jnlp). Download a new IoX Launcher (start.jnlp) from UD site (click on “My ISY” on the top right). 
If doesn’t go away, but still able to find and access ISY then you can ignore it (based on old replies from @Michel Kohanim on this issue…used Google Site Search to find old posts with this issue).
 
https://forum.universal-devices.com/topic/32124-socket-open-failed-ssdpclient/
https://forum.universal-devices.com/topic/21736-socket-open-failed-ssdp-client/
 

@SHM when you reboot next try logging in and look at the programs summary tab and sort by "last run time". See if there is something that is triggered as @n_sievers suggests. That will give you an idea if it's a program.
The "Query at Restart" and "Catch up schedules at Restart" options are on the Configuration tab. I might suggest unchecking those as first attempt of troubleshooting. 
Also check for any programs that are set to specifically "Run At Startup". This option can be seen in the Programs Tab under "Summary" and then sorted by the "Run At Startup" column. Right click on any program that has a status "ON" to view the program and see if any conditions were met to trigger that program when rebooted. To disable "Run At Startup" right click on the line and select "Disable Run At Startup" (think about it before blindly doing that though...that's sometime a good option to have on if/when you lose power during the day and it comes back later in the day it will run those programs when the device boots back up).

Otherwise, are any of your devices really old (no set time, but maybe things pre-2013-2015)? They could be having the dreaded "all on" issue from lots of traffic at startup. Hard to tell what's really happening. I'm not sure if there's a sure fast "date" that things were fixed on the device firmware side, but something could be causing issues if it's an older device.
No way to keep admin console open/connected through a reboot to watch the event viewer, but if you're able to log in and get event viewer open and set to level 3 as lights still come on it might also shed light on commands being triggered/sent through the system.