Geddy

@awysocki when you're rebooting how are you achieving this? 
I would suggest you open a support ticket with UD. I know they're working on updates to the eisy-UI and other updates in the system so it might be best not to randomly try things, but to get UD on a ticket with this so they can see/verify the logs and see what happened to help them troubleshoot the release so more people don't have issues.
https://www.universal-devices.com/my-tickets
You've got a few things working against you in that the java admin console window isn't designed to be up 24/7 so just leaving it up all night if the computer went into hibernation or sleep state it could have been an issue and even though you had a message didn't properly reboot the eisy. Not sure what's happening in the reboot you've been doing now, but if you have it connected locally then it should be mostly coming up. I would think UD would have the best indication as to what needs to happen to get it fully operational again. 
 

@CoolToys have you performed a full power cycle on the eisy? Rather than just the reboot following the update it might need a full power cycle just to "catch up" or at least trigger things correctly. I would shut it down (6 button presses or press and hold), actually pull the power cord, wait 10 seconds (random amount of time), plug it back in, and power it up (i forget if it turns on automatically or not). 
Your programs are executing exactly at "x" time. Do you have many other things triggered at the same time? Even though it has "worked for years" (famous phrase among many of us), it's possible that there could be a lot of communicating at the same time and something is missed. Shifting something just a few seconds might help. 

Seeing that the hue plugin was developed on unofficial api (based on previous posts about this plugin) and hasn't been updated in a while (years?)...I would hazard a guess that the "pro" hub is not supported. If you tried all the usual tricks and still cannot get it to connect, it might not be using the same methods that the plugin is using to identify and communicate allowing successful connection.
Fun that there's a new hub for hue.

Did you restore the backup file you made? That's what pulls in the devices and programs. 
(Source:  https://wiki.universal-devices.com/Eisy:User_Guide#Migrating - Step 5)
What you're describing seems that you missed the step to restore the backup and went to a process of restoring the PLM, but that's not going to bring the devices in. 
Once you restore the backup you should review your programs. If you have any network resources you'll need to open each one and save them. (Also from the wiki - "during migration": "Network Resources
All Network Resources will be migrated seamlessly, however, you will need to open and save each one individually."
 

@SHM did you follow the directions in the wiki to migrate the plugins? 
https://wiki.universal-devices.com/Eisy:User_Guide#Migrating_Node_Servers_to_PG3x
I'm not sure if this is still possible, but that's the last the wiki mentioned how to move them from Polisy to eisy. 
When plugins show "unmanaged" in the dashboard it means they are being managed by another device. If you have everything that was installed on the Polisy showing on the eisy now make sure you start them (if possible). If not you might need to open a support ticket with UD to see how to get things sorted/moved.
https://www.universal-devices.com/my-tickets
 

@EddieRock you're probably best off getting help directly from UD on this issue. 
Please open a support ticket with them:  https://www.universal-devices.com/my-tickets
Try what @Techman points out, but don't do anything deeper than that unless instructed to by UD. It's almost like something is corrupt and they would be best to work with to troubleshoot the issue and correctly resolve if it's more involved than simply reloading the IoX Launcher process or rebooting the eisy.
 

@tracknut, even though you probably didn't initiate an update it's possible that by pulling power it caused a corrupt process that isn't allowing the eisy to fully boot and initialize the ISY side. 
I would suggest you open a support ticket with UD to have them help troubleshoot with steps they know and know what results they're looking for. This has happened a few other times with various issues causing it and support has been able to get them running quickly. Hopefully your issue is easy to resolve as well. Going into the weekend though you might have limited help until Monday. But rest assured UD will be the best bet of how to resolve.
https://www.universal-devices.com/my-tickets
 

Since you haven't done anything in over a year your best shot is to check the wiki for the update process. Although, there was an update to 5.9 that required an updated operating system in the eisy. I'm not sure if that's been overcome and installed at the same time. It might be best to open a support ticket if your device is out of date for updates to be sure that it will update "easily".
You can open a support ticket here: https://www.universal-devices.com/my-tickets
What I would suggest first is try to go to this page in your browser: https://eisy.local:8443/WEB/sysconfig.txt
See what ISY version you're running as well FreeBSD
Maybe looking for FreeBSD:  FreeBSD eisy 14.1-RELEASE-p6   
(should be the top line of the output of the sysconfig.txt page)
A little ways down you should see:
************ IoX ************
isy-5.#.#
Name           : isy
Version        : 5.#.#_##
Installed on   : Date & Time 
 
You can look at the past (or current) release notes in the release area of the forums to see when the OS updated to FreeBSD 14. If you don't have that then you'll need help getting that installed before you can update to 5.9.x.
Be sure you read the release for 5.9.1. Pay special attention to item #3:
Lastly, be sure you backup your IoX (if you have z-wave back that up first then back up IoX). Then also run a backup of PG3x (just to be safe). I would also suggest you make a text copy of all your programs.
Right click the root program folder and select "COPY folder to Clipboard". Then paste that in a text editor (not a word processor!). That way if your system does not come back correctly and you have to rebuild or start over and you have problems with your programs you have a "hard copy" to reference and not having to go from memory of what items were in what programs.
Good luck if you proceed. It is a good idea to keep the system updated as releases are announced as they incrementally improve the system and take care of bugs along the way.

@hart2hart is the program enabled to "run at startup"? In the summary tab it should show if it is or not. I would turn that on before the catch up schedule option. I'm like you have read about that possibly causing other issues. This way an individual program is running at startup.
I think others have said that could also be an issue if you have a lot of programs running at startup and they have built a startup program to trigger all the other programs they want to run at startup, but with a short wait (a few seconds?) between each run. 
 

@xlurkr what kind of doorbell do you have? I have a Ring doorbell and use the plugin to turn lights on. I don’t “flash” the lights, but I do turn on a light (or lights) that are not usually on. I also have a Hue bulb that will change colors (using the Hue plugin).
it’s then just a program for when there is a Ring event triggering the lights. As said above though if the light is on and you program is on/off/on/off then the light stays off. You’d need another program or maybe a variable to return it to the previous state without “manually” turning it back to the original state. That gets a little more involved and why I only use lights that are usually off.
I like the Ring ability because I also have it turn lights on if there is motion in the middle of the night. 

@TomJ you might need to contact UD again to get help directly from them if not showing up as expected. Not sure what they do to trigger the change on the web portion.
I would attempt the "Switch Portal Profile" open under the "System" menu. Even if you're using the same portal account it might re-trigger the portal login and then associate that device/portal to your developer account.
If that doesn't trigger it then contact UD again.
https://www.universal-devices.com/my-tickets

Even though the test is going through check our "Timeout (ms)" setting. Make it higher. I have mine at 5,000, but it's been suggested to set it to 10,000. What is your setting at before you change?
You're correct to be using the app password. Again, if you are getting the test then it is successfully sending. 
If changing the timeout doesn't resolve the error then maybe reset the app password, but doubt that's an issue.
 
 

@msingold if this has mostly been in the last 24 hours there have been a couple of portal down time that seem to have recovered. If this has been going on a long time you might be best helped by opening a support ticket to see if there are underlying issues. 
https://www.universal-devices.com/my-tickets
 
The eisy does sometimes run warm, but it is designed that way. If you keep it in an enclosed area this could make it run warmer due to low air circulation. 

@JimTurner the specific .state file you need to delete is:  "udi_launcher.state"
That will remove all "found" and added devices. Then the next time you launch IoX Launcher any listed devices will be what are found automatically.
Since you said it's "grayed out" it's automatically being added when IoX Launcher loads the IoX Finder window. 
Another option might to clear the java cache (be sure to select all 3 boxes). Delete any "start.jnlp" or "admin.jnlp" files on your system. Download a new "start.jnlp" from the UD website (click "My ISY" on the top right). Then run the new start.jnlp to re-add the IoX Launcher to your desktop. 
But deleting the .state file should get it cleared up. If it returns again and is unable to be deleted then it must still be on without your system and connected to your network (even though you say it's "offline"). 
 

I don't know what "not chained" means as I don't have any products in this area.
But, couldn't you install the plugin on multiple slots and find each controller independently of the other and have different items brought in from each plugin instance?
 

@RichTJ99 more than likely you would install the plugin in another slot and run the second hub in that instance of the plugin. Plugins can be installed in multiple slots. I don’t use this one so not entirely sure, but would be my best suggestion. 

Take a look at the wiki too:
https://wiki.universal-devices.com/Eisy:User_Guide#Plugins_Store_Menu
You'll see the example window (for Blink not the Notification plugin). You should probably already be logged into the portal as part of the PG3x screen, but if not when you click purchase it should probably take you to the portal plugin then to the payment window. 

Open a support ticket with UD and let them know the plugin and the situation and see if they can refund that way.
https://www.universal-devices.com/my-tickets
 

There should be a box with a "-" in it to collapse it. If you cannot see it maybe your resolution or font size is set at a level it's not showing.

Otherwise, you can also click on the folder and press the left arrow and it should collapse (at least it did when I tried it). 
It might not always be closed, but it should reset the .class file. You can lookup on the wiki for .class files and remove them and see if the display changes on the next load.

@Bill K-B what is the timeout set to? Try setting it to 10,000.
Also, how is the message you’re trying to send formatted? Is it a very long message? Try setting up a new one with very short body text. 
Some older posts with this issue seemed to revolve around a timeout issue or very long HTML notifications that were causing errors. 
Finally, will you open this page in a browser and let us know what ISY version you’re on? (Not just from admin console…from the sysconfig file…looking for the number after 5.9.1…as of today should be _18 for the “current” version)
https://eisy.local:8443/WEB/sysconfig.txt 
(You might need to replace “eisy.local” with the device IP address)

A ticket is the preferred option! As the post (solution) from Michel in the thread linked above DO NOT ATTEMPT TO FIX YOURSELF! It could cause more damage and put the device in a state that's difficult/impossible to fix. Wait for the ticket to receive a reply. It shouldn't go too many days without a reply, but if you don't have a reply soon then post an update to it for it to re-trigger in their system. 
https://www.universal-devices.com/my-tickets
As Michel points out that support tickets also benefits UD as they learn what is causing systems to fail/stall with the update. So please don't go goofing around in SSH and trying random commands that others are posting.

F5 is a browser refresh (for Windows). For the Mac use Command + R.
Might even need to try a "hard refresh" - for the Mac that's Command + Shift + R.

@abrayshaw (split your post out of a resolved topic that had no activity for 4 months so you might get more attention to your situation.)
First off, please confirm you're running ISY994. Let us know (if you can) what Firmware and UI you are running. I realize that if you can't get into admin console (to get the UI), but if you're seeing the ISY on launcher it should say what Firmware the device is running. 
Did you select all three boxes in this process? The 3rd box clears the installed IoX Launcher icon from the Windows desktop. You'll need to download a new start.jnlp from the UD website to put the icon back on the desktop.
Alternate method would be to download the admin.jnlp file directly from the ISY (web browser go to: http://ip.address.of.isy/admin.jnlp).
Last question: What computer OS are you using? Windows, MacOS, other
Make sure you've got "plain" java downloaded directly from java.com and not a special version or higher version than just downloading from java.com (showing current as of today: Version 8 Update 441).

I've got my Z-Matter dongle connected with a standard USB Extension cable of about 3 feet (similar to this one: https://www.amazon.com/Monoprice-3-Feet-Female-Extension-105432/dp/B002KKZAIU/). I've had it this way for the last couple of years just to get the device mounted on the back of my equipment cabinet to be away from the case or other metal cases in the cabinet I have network and other electronics in. I have a few Z-Wave devices and a few Zigbee devices and can't remember a time that they were unreachable or noticed the dongle to not be connected. It has happened, but not often enough for me to worry about it. Usually a reboot/power cycle of the eisy brought things right back. 
Honestly, for the first 6 months or so of having the eisy+Z-Matter it was directly connected to it. I only added the extender as a precaution to remove the weight off the device directly, but also to put the antenna more in the "open".
I believe there were a lot of comments about running USB Extension cables a couple of years ago(maybe when Polisy came out, but again when eisy was released). Might find those posts using Google Site Search since forum search won't find archived topics.

Been that since eisy was released.  UD had so many support issues with people setting static on the ISY994 that they seemed to disable it in a Polisy update and since eisy release.
It’s best to reserve the IP at the router level. Has been the suggested process for many years.