Geddy

Glad it (finally) worked out. I'm with you keeping Win10 as long as I can. My primary home laptop is Win10 and not able to upgrade to Win11 for hardware reasons and I don't want to skirt those just to force an update on that system. I've got work systems that are running Win11 so I'm good keeping the Win10 operational as long as I can. All businesses are "all about the money". That's what makes them businesses...and some are more successful than others! Seems like some crazy stuff if your system kept forcing an install or re-install of Win11. You must have really been doing some risky adjustments.

Note that the update to 5.9.1 is a MAJOR update since you're still running 5.8.4. If you run update please run from admin console and allow a lot of time for the update to run. Some reported as much as 30 minutes depending on the size of your install (number of devices and plugins). Be sure you read the release post regarding 5.9.1 update process. Edit: Fixed link. Thanks @Steve L for pointing that out.

@gschoffstall interesting that some work fine and the one isn't working. I've got Win10 and Win11 laptops and both work fine. I'm not sure what chip is in the Win11 computer, but it's a simple Dell model so probably not a "core 9". Typically, based on your description, simply clearing the java cache and running start.jnlp again will work. I know this is the fix after a Java update if the link to IoX Launcher is "broken"/not working. Will you try this approach: In a web browser open this: http://eisy.local:8080/admin.jnlp (I'm on Chrome and it puts a "keep" option in the download area in the top right of the browser window. That should save it in your default download directory. Double click the saved file (admin.jnlp). That should take you directly to the eisy IoX login screen. If it doesn't then something is wrong with the Java install or how the Java Web Launcher is linked to open .jnlp (even though you appear to have it correct in the screenshot above). Speaking of the screen shot...you've got jp2launcher.exe showing. That's an odd thing to have on Win11 (at least I haven't noticed it before...I remember that on old Windows systems (Visa age). You might need to run the Java Uninstall tool (https://www.java.com/en/download/uninstalltool.jsp) to remove outdated or random installed java versions on your system. If the admin.jnlp file doesn't work then next step would be to open a support ticket to get some help with the issue. https://www.universal-devices.com/my-tickets If you end up going through a support ticket please post back with the fix so that it might help others should this issue come up again.

Clear the Java cache - checking all three boxes! Make sure that you have the "Java(TM) Web Launcher" selected as the "Opens With" for the start.jnlp and not just "java.exe. Java Web Launcher is the javaws.exe file found in the "bin" directory of the current installed Java version. Be sure you have standard java downloaded from java.com (currently: Version 8 Update 441 / Release date: January 21, 2025). What you're describing is related to the java cache. The start.jnlp thinks the icon is already on the desktop so it's not making a new link/icon. Once you clear the java cache just run start.jnlp again (as long as it's using the java web launcher) and it should add the icon to your desktop again. If you did an update from Win10 to Win11 on the computer you might need to perform an uninstall and reinstall of Java and perhaps get the java cleaner to remove any "old" or random versions of Java on your system before reinstalling, but that's only if the simple process above doesn't resolve your issue.

Glad it's sorted out. Odd that it went into an error issue. It could have been a build issue or corrupt update somewhere along the way. When I made my post I had updated earlier yesterday (3/21) and my version was 5.9.1_18. Guess another one got pushed out sometime yesterday if you're up to _19. You mentioned the tests were failing. Do you have multiple recipients setup? If you do I think you have to select one before you run the test or you might get errors on the test process because it doesn't know where to send them. That's mostly from memory though. I only have 1 address and don't trigger the test message often. I prefer to trigger a program that sends a message just to know that process is running correct.

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

Might be worth reviewing the wiki for the setup: https://wiki.universal-devices.com/ISY994:Configure_Mail_Server_Settings#Configuring_gmail_Account It's possible that Gmail changed something again, but this setup seems to still work. I've had a notification program with Gmail account setup since early on and just tested the program and got the notice within seconds. Where are you sending the notification? It might be blocking/delaying delivery? I send from Gmail to Outlook email, but I don't send large amounts of notifications. If you're sending a bunch it could be triggering your messages as spam and bouncing/delaying them.

@EJones01 can't help directly as I'm an iOS user, but if you have the geofence area on the app at the bottom there should be an option to "Trigger Enter Command" and/or "Trigger Exit Command" (it shows on my app - again iOS). If you manually trigger the geofence does it do anything? As for the logs are you looking in the "My Geofences" area? I still have a log icon (looks like a dog-eared piece of paper) that does tell me when I've entered/exited for the last few days.

First: To post programs please right click on the program and select the last menu item of "Copy to Clipboard". Then paste as text into your forum post. This allows the program to be copied and edited by those helping you if edits are needed. Rather than the helper having to create a program or try to describe edits to an image. What makes you think they stopped working? Please review the Program -> Summary tab to see the "last run time" for these programs. The "Towel Bar Morning" program appeared to have last evaluated true (it's partially green - see the wiki for what the colors mean) and I would assume ran at 5am as expected. Were you awake to check if it turned on? As @SJK points out the "Towel Bar 2 hour off" program seems to be running since it is fully green (means it's running the "Then"). It might be good to also share this program. The "Master Bath Fast On" appears to have last evaluated "false" and ran the "ELSE" because it is partially red. Maybe the last time that light was turned on it was simply a single on and not a "fast on" that the program is looking for. Also, why are you attempting "fast on" for the devices in the "THEN"? Would "ON" achieve the same desired result? I might test with just "ON" rather than a "FAST ON". Again, right click on this program an select "RUN THEN". Do the devices respond to the commands? On the "Towel Bar Morning" program - right click the program and select "Run Then". Does the device turn on? If you've edited any programs be sure that you SAVE them. Lastly, please let us know what ISY device you are using (ISY994, Polisy, eisy) and let us know what firmware version (actual number - not just "latest/current version) you are using.

Which upgrade are you talking about and what device are you using? I updated my eisy to 5.9.1 a few weeks ago without issue. You have to expect that those that have issues will post to the forums to get help. Those that have simple updates tend not to post about their successful updates. Don't be in a hurry. Don't expect it to be done in 60 seconds. This (5.9.1) is a major update and took a while to process. I suggest using a computer with the admin console to run the update. Be sure you follow the directions on the release post from Michel. @SRS glad you're back up and running! Support at it's finest I'm sure.

@skunkiechris can you confirm what model Kasa you have? I see the KP405 is indeed an outdoor dimmer type. More than likely the developer (@Jimbo.Automates) doesn't have this type of device and thus hasn't tested with the plugin to have the dimming function. Might want to contact them to work directly with debugging some code additions.

Can always read the wiki troubleshooting: https://wiki.universal-devices.com/Eisy:User_Guide#Can't_Find_eisy

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.

Something seems odd with this process. I just ran the IoX Launcher and compared my console and it never had the manifest line. Have you downloaded a fresh start.jnlp from the UD website lately? Make sure you're not using an old downloaded file! Seems that you've got the current Java version installed (8_411). When you're clearing the Java Cache are you checking all 3 boxes? It's looking for a .state file that says it cannot find. That's usually added with a successful launch of the IoX Launcher applet. Are you running any antivirus or firewall software that might have removed .state files in the referenced directory? Typically they'll be recreated, but for this to be looking for it and not being there is a concern.

There was a post by @bmercier (hidden) in another thread that had a tip about MAC users...maybe this will help. If this doesn't help gain access on MacOS then you might be best to get a support ticket started so they can check if indeed it got messed up during the update and directly support you the proper way to resolve any such issue. There have been others posting random SSH commands, but Michel asked not to do that and to only open support tickets so they can get things ironed out internally too (in addition to repairing the system "properly"). Please be sure to post back if the info below helped and ultimately how the device is recovered.