Geddy

@Sner please open a support ticket with UD and maybe they can give you additional troubleshooting steps or get things sorted out. https://www.universal-devices.com/my-tickets If nothing happens when even trying to open start.jnlp it seems like something in Java is blocking it. If you have Java installed correctly try going in and clearing cache (be sure you check all 3 boxes in the process). There is also sometimes people reported (it was more in Win10 though) that you have to forcefully remove it from Java then run start.jnlp again (I might reboot in between). Look up "Configure Java" on Win11. It will open the Java Control Panel. On the "General" tab look for "VIEW" (next to settings in the "Temporary Internet Files" area. It will open another window "Java Cache Viewer". Select IoX Launcher then click the red X. (thanks to @larryllix for this gem a few years ago) While you're in the Java Control Panel look at the "Security" tab and make sure it's set to "High". Still the security warning screenshot you posted above doesn't appear to be a Windows based error screen. Is that some 3rd party software alert window? I feel that something you're running might be blocking this process. While I have Win11 machines I haven't switched to them full-time...just not familiar with that error frame appearance as a Windows alert.

Is this the outcome you expected or is there still an issue? Glad it's sorted out once removed from the folder with conditions. It's a tricky thing. If you don't want a program to run until called on by another program then disable that program. When disabled the program will not trigger. But other programs can trigger the "IF" or even the "Then" or "Else" portions specifically. So if the program isn't working as you hoped if it's on, but then turns off right away it's because that program's "IF" has gone true and thus turning the light off. Disable the "Toggle On Keydrop Light" program and the light should stay on. If you eventually want the light to be off you'll need another program to turn it off. You might also want to look at the summary tab of this program and be sure it is not enabled to run at startup.

@RPS welcome to the UD forums. There was a strange link to a file that didn't exist in your original post. What were you trying to post? If you'd like help with the program please right click the program and select the last item in the menu "Copy to Clipboard" then you can post the program as text in your reply. It will help those that try to help with the program by being able to edit the actual program and not describe what to change in a possible screenshot of the program. Be sure you use "COPY" option. Then paste into your reply. I'm not sure how Caseta items are seen in IoX as I don't use them. Do they have a status and do they send on/off commands? I would suggest not controlling a scene, but controlling the actual device if you're just trying to get it to come on 100% or go off. Since the folder conditions are false it will not allow any programs in that folder to run. Try removing it from the folder and saving the programs. Then test it again.

@aeroRC you might need to click "refresh store" on the production store page. It appears that 1.4.22 is now showing there.

If you are on Win11 just get the default Java from java.com. It works just fine on several systems I run Win11 on. You need to remove the openwebstart and remove any old/custom versions of Java. Then download a new start.jnlp (delete any old version you might have downloaded). Be sure any 3rd party antivirus or VPN software is disabled the first time you run start.jnlp. You will need to use javaws.exe (found in the Java bin folder) to run .jnlp files. If you still have issues also look at the wiki for adjusting the memory used by Java (https://wiki.universal-devices.com/Main_Page#Admin_Console_is_very_slow_or_hangs). If your system has a lot of memory (over 4GB ram) you can increase the amount to 1024.

@TInoue welcome to the forums. In order to help please let us know a few more details. What eisy firmware are you running? Please see admin console “Help” -> “About” and give exact number you see for firmware. Also confirm UI matches that Firmware version. Please share your program. Right click on the program you need help with then select the last option “COPY to Clipboard” (be sure you “COPY” to clipboard). Then paste that as text in your reply. (Please don’t post a screenshot of the program. It’s much easier for us to help modify the program as text rather than a picture.) More than likely you have multiple “to” items and they are not all “True” at the same time. Another option to review is if the program is in a folder. Does the folder have conditions that are not true? This will not allow any programs in that folder to run. If it is in the root “my programs” folder be sure there are NO conditions in that folder. For that it would be fine to post a screenshot of the folder conditions to share with us. For the program itself is the icon partially red? That would mean the last time it ran it was “False” so it triggered, but just ran the “ELSE” section. If “else” is blank then it did nothing. Please refer to the wiki for color meanings: https://wiki.universal-devices.com/index.php?title=ISY_Programs:Icon_Colors Lastly, confirm the program did not run by looking at the “Summary” tab in programs. It should have a “Last Run” time and ”Next run” time showing. There should be a way to get Google Home to work with UD. You need an active portal license. I don’t use Google Home so can’t help you, but lots of others do use it. There should be help in the Wiki to find the proper connection. Or some help in the Google Home area of the forums.

@xlurkr check out this thread:

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

I've also been using the Yolink leak sensors. Only a few months with them, but they seem to work well. I have some other YoLink temp/humidity sensors that I've been using for longer and they really operate good with the eisy + plugin. Since you posted in the ISY994 area it's not a product you would be able to integrate into the ISY as it does require the plugin to bring into the IoX/ISY system. Outside of the ISY I do like the YoLink app (it's basic) and expect that with their hub and app you would be able to monitor for and be notified of leaks easily. The range on the YoLink devices is fantastic. I expect battery life to be great as I have been able to get ~18 +/-months on the temp/humidity sensors.

If you just renewed the subscription open a support ticket with UD and see if they will refund the purchase and expire the portal now. https://www.universal-devices.com/my-tickets You can use the ISY994 without a portal account and/or active license. If you want to access the device while remote you would need to open ports on your router (not usually advisable for security reasons these days). I'm not 100% sure as I haven't tried it, but you should be able to use UD Mobile locally as long as you have setup local IP connection method. Make sure to remove any portal connection method in the UD Mobile app.

@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

@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

@DBC Glad you're up and running. Yeah, from what you were describing it seemed like a corrupt update. UD's top notch support wins again!

Looks like Guy has a method if you're able to access it still via SSH. I wasn't sure about that. If you've updated in the last couple of months it would be 5.9.1 (has been out since Feb). I'd just go with that unless you don't think you've updated since February. Or there appears to be a "N/A" option for firmware. If you cannot find it as @Guy Lavoie describes above I would choose "N/A" and they can find it out as you progress through the ticket troubleshooting.

@DBC the best course of help on this would be to open a support ticket with UD. Please don't dig into SSH and running random commands at this point because it could put your system into an unrepairable (or more difficult to repair) state. Please contact support: https://www.universal-devices.com/my-tickets UD has posted elsewhere if issues like this happen to open a support ticket right away. This not only can get your system back online (quickly - hopefully), but it also helps them find the actual cause of the situation. By running SSH commands could change what was the cause to the issue and makes it more difficult for UD to troubleshoot/learn what caused the issue in the first place.

@JWBDolphins split your post out to it's own topic since the old topic was a little stale (OP hadn't updated the issue since early April) and your situation is different coming from a migration. Please update after reviewing the tips @Techman and @paulbates have suggested.

When you log into my.isy.io there should be a green dot/circle next to the device. Just hover over that and it will show when it connected. If it isn’t green then it means disconnected and hovering over it will show when it disconnected. Disconnections don’t always indicate portal issues. It could be ISP/local network issues. If you get login errors when trying to log into my.isy.io might indicate a portal issue.

No issues here. Portal page shows my device has been online since Thursday evening (6/12).

All Insteon devices have set buttons. That's how they begin the linking process. While wiki the information is old it still somewhat applies to the current day controllers. Here's the information about linking devices: https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Link_Management_Menu#Start_Linking You can also review in the ISY Cookbook that can be downloaded from the wiki. It too was written for older controllers, but still applies for most general Insteon setups.

@Ray95xxx your best bet is to open a support ticket with UD to get help to see if they can get things working again. https://www.universal-devices.com/my-tickets Do you have the Z-Matter board installed internally or via the USB dongle? If it's via USB try a different USB port and power cycle the device again (by pulling the power supply - waiting 60+ seconds before plugging back in). Since you said you ran the "upgrade packages" process please share your Firmware you're running. Don't just say "it's current", please give specific version number. Should be able to find it in admin console, but it would also help to get the full number/build info. Please go to this page when local to your device: https://polisy.local:8443/WEB/sysconfig.txt (NOTE: You might need to replace "polisy.local" with the IP address for your polisy. If you get a warning about security please press advanced and "continue to site". Since this is an internal device it's fine to proceed.) If you do open a support ticket please post an update for what is done to get this working again so it might help others in the future.

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 yes - see post in the UD Portal area: This was the initial issue. Apparently there was another brief drop in the evening of 6/12 (eastern time), but that only lasted a few minutes. Then the time to reconnect all devices meant some were offline longer than others.

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

@midrar from my personal use of the plugin it works fine. Others have had issues getting it to work or other issues, but for my simple setup this works fine. I haven't attempted to "cascade" lights, but having lights activate when other triggers occur has worked well since setting this up when I got my eisy. Be sure you set an IP reservation for the Hue hub in your router so it is always at the same IP address. The plugin doesn't like if/when the hub IP changes.

Was a portal outtage overnight - shoudl be back to normal. @bmercier posted an update -