Geddy

@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. 
 

Do you have a backup from before folder creation? I'd restore that backup and see if that puts things back to "normal". 
  
Can you share a screen shot of this? 
There should be a root folder then a sub folder that would have devices and other folders in it. Didn't think it was possible to add another folder higher than root. What probably happened is you just renamed the root folder. I've done that one  on mine and it's not an issue.
I think the default was "Network" then "My Lights". It's been ages since I renamed mine so don't know for sure. Just going off some old images in the wiki. 
But as @DennisC make sure you remove everything from the folder first. Right click on any devices in the folder and select "remove from folder". Once the folder is empty you can right click on the folder and select "Delete folder". 
Reference: https://wiki.universal-devices.com/Tree_View_(Navigation)_Pane
 

@kewashi I think in this instance you'd be better off opening a support ticket with UDI rather than trying to get help on the forums. If this isn't a common issue not too many users would be able to help on this and UDI would be able to troubleshoot quicker/deeper/better than waiting on forum posts.
Support ticket: https://www.universal-devices.com/my-tickets
 

Try accessing Polyglot from a different browser. 
If that doesn't work, I recall another user recently that had a similar problem. 
If I recall they did the following:
login to https://eisy.local:3000 go to System | Switch Portal Profile then login (to the portal) Screen will refresh back to Polyglot  click the Logout button (polyglot web access - top right)  Log back in  
 

As @auger66 points out it's probably the portal subscription has expired. 
Check by logging into the portal (my.isy.io) and then follow the image for License Information

Renew that for a year or two. Note the rate did increase in the last year (or so). But still a deal by any means!
 
This sounds like you've had a Java update and it wiped out the link with the shortcut on the desktop.
To resolve this follow these steps:
Clear Java Cache (temporary internet files) Check all three boxes! The 3rd box will/should delete the desktop icon (if you have iox launcher on the desktop). If it doesn't just delete it. You mention "Click to launch console.jnlp", not sure where that came from or how old that is. The "IoX Launcher" method has been around since 2018 and the preferred method since browsers dropped Java support. Make sure Java is up to date Just get the "standard" java version available directly from java.com https://www.java.com/en/download/ As of today it is Version 8 Update 391 Delete any start.jnlp or admin.jnlp files you have on your system Download a new start.jnlp file from UDI website https://isy.universal-devices.com/start.jnlp Go to Universal Devices site Click on "MY ISY" on the top right and you'll get the same file linked above (start.jnlp). Run "start.jnlp" and accept any Java warnings This should add the icon to the desktop for "IoX Launcher" Run IoX Launcher and you should now get a window showing as "IoX Finder". If you're local to the ISY994 it should auto populate, but if it doesn't you would need to add it manually.  
More information can be found in the UDI Wiki should you need more help:
http://wiki.universal-devices.com/index.php?title=Main_Page
 
Post back and let us know how it's going.

@DualBandAid Did you attempt to directly connect bulbs to the eisy? Best I've seen is to simply use the Hue plugin (formerly Node Server) and control items that way.
It's possible that the Hue Hub changed IP addresses in your network. Do you (or did you) have an IP reservation in the DHCP settings on the router? If the hub changed IP address during this the eisy is looking for it at the old address. You will need to hardcode the current IP in for the bridge.
From the plugin "more info" config page:
Make sure you include the square brackets [ ] and quotes around the IP address.
I had an issue with the IP address changing when I first set it up and PG2 had a rough time getting the bridge connected again. When I setup PG3 I had a reservation made and haven't had to hard code the bridge.
 
Make sure you've got all the lights in the bridge before you connect to it. Also, if any devices are on outlets that can turn them off (making them unreachable to the Hue Bridge) be sure to have them powered ON or at least "reachable" when you begin the linking process. 

I'm not sure if it's needed, but could be. The plugin has to authenticate with the Ring service. I've never attempted without an active Ring subscription. 
One of the release notes though indicates this:
So might be a requirement. Maybe just an account...not an actual Ring subscription. 
This is normal. It's the same for my doorbell pro "motion" node. My floodlight cam has information on the Motion, but the "lights" node is blank on that device.
 
My motion program triggers for middle of the night motion runs as expected.  
 
~Door-Motion - 
If
        '~NodeServers / ~Ring / ~FDoor (Motion)' is switched Motion
    And From    11:50:00PM
        To      Sunrise - 60 minutes (next day)
 
Then
        Set '~NodeServers / ~Hue / Couch' On
        Wait  5 minutes 
        Set '~NodeServers / ~Hue / Couch' Off
 
Else
   - No Actions - (To add one, press 'Action')
 
 
 

When you access using the my.isy.io link you should use the portal user/pass credentials. This is usually an email for user ID.
When you connect locally or using port forward (meaning directly to the device from outside your network) you should use the local/direct connection credentials. This will usually be admin/pass (whatever pass you use when local to the device). 
Security tip…since port forwarding means you bypass all security to connect to the device you should make sure you’re not using the “default” user/pass combination. 
This is always how it has been…nothing new for those connection credentials.