Geddy

Are you saying you've set a ramp rate in IoX and it's not reacting as you would expect or the switch arrived unable to ramp as expected? I wonder if that's an issue with the switch and maybe Insteon needs to be involved to troubleshoot. If on IoX then set the ramp rate and click "Ramp Rate" button next to it. That might be like the backlight bug that's been around since firmware 5.x came out that you have to click the button for it to be written to the device. There is a button at the bottom "Write Changes", but that's not the same. Might be for ramp rate as well as "Backlight" (and maybe other settings). Once you click the "Ramp Rate" you'll notice a "writing" briefly appear on the device.

Best bet is like @Guy Lavoie has is for the program to only be true during the time you want the scene to run AND when there is motion. Do you have a program you're trying to troubleshoot or starting from scratch? If you have an existing program you want some help with please be sure to include that in your post by right clicking the program, selecting "Copy to clipboard" then pasting in the port as text so that others can help edit/alter the program easily. Screen shots aren't as easy to help edit.

Given all that you have attempted I would suggest opening a support ticket with possibly BOTH UD and Insteon. It's quite possible that in all that you've done the eisy is in a state of "shock" (i.e. too much going on that it's not correct). That's why I'm suggesting a ticket with UD. UD might have a way to test if the eisy is seeing the communication with the PLM at all. https://www.universal-devices.com/my-tickets If the PLM is new (as you implied) perhaps getting support from Insteon (https://www.insteon.com/support) might be the route to see if it's something they need to replace if in warranty. Insteon might be able to figure out if the device or cable are bad. I'm not familiar with their troubleshooting steps.

Not possible. See post above.

Easier solution is not to control the devices directly (i.e. don't use the hue app!). Use the scenes with UD Mobile to keep Insteon devices in "sync". When devices are controlled outside of the UD/Insteon system there's very little that can be done to control devices. This has always been an issue so nothing new with plugins. Many years ago (and to this day) the issue of keypads and controlling with Alexa was the big thing (I recall a very long thread about keypads, ceiling fans, and scenes - that UD had to update the wiki based on the thread). Now it's any device that a plugin might be able to control. If you adjust it outside of the IoX control only the status of a device might be sent to IoX, but there's nothing telling the IoX what to do with that status. Thus, a program is necessary to give you the visual result you're asking for when something is changed. The point of plugins is to incorporate the 3rd party device into IoX. By using the 3rd party app to operate the light you're ignoring the benefit of the plugin of being able to control that device via UD Mobile or IoX setting(s).

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.

Another issue might be mismatch of firmware and UI for admin console. Is the “out of memory” yellow? Make sure in Help -> About that Firmware and UI match. Clear your Java cache (be sure to check all 3 boxes), download a new start.jnlp from the UD website (found by clicking on My ISY on the top right). Then running to get a fresh IoX Launcher icon. The eisy has tons of memory so unless you have near max amount of devices and tons of programs is unlikely to be a hardware memory related issue.

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.