Geddy

okay...different lights, but swear it sounds like same issue. Involving Alexa and that things don't turn off. It sounds like the scenes are not setup correctly and when Alexa is controlling them it's not doing what you think it should. If you attempt to turn off the scene from IoX Admin Console what happens? My guess is the same as when Alexa is used to turn them off.

@SHM have you restarted the admin console? Also, make sure that you're only accessing PG3 via the eisy_ui portion now. There's been mention from others that UD is suggesting only to access PG3 via eisy_ui interface because of how the licenses and ISY connections are being made. It's always been suggested that anytime you do something in PG3 to have the java admin console closed and when you're done changing things in PG3 to log out and then re-launch the java admin console. Since admin console only reloads or refreshes new nodes when it first runs. Anything you might have added if you had admin console open wouldn't appear there until that was restarted.

@andrew77 is this the same issue you started in another thread last month?

When you're local to the machine go to this webpage: eisy.local:8443/WEB/sysconfig.txt What version do you show for ISY? It should be the second section in this file. Even thoug above you said your 6.0.4 there was an issue early in the 6.x that was causing this "AutoUpdate" error, but that was said to have been resolved back in Sept 2025. If you're running 6.0.4 that should be after that time. You might need to run update again (this time run the update from eisy_ui). There has been some differences talked about elsewhere in the forums that the recent eisy/IoX update is better triggered from within eisy_ui than from the admin console side. (I'm not sure I buy into it, but it's based on people posting following up from support tickets). If you run an update from eisy_ui and still have the issue when logging into java admin console please open a support ticket with UD for them to explore more troubleshooting steps so you and they can posisbly learn what happened or what is causing this issue. Open a support ticket here: https://www.universal-devices.com/my-tickets In the meantime, since your initial post said these errors have been going for over a year it's unclear why errors would happen for so long if you're apparently keeping the system updated. I would suggest a full removal of IoX and Java from your system Clearing java cache - checking all 3 boxes in that process Remove java - using computer uninstall process and possibly using the java cleaning tool to be certain any traces of java or old java installs are removed from the comptuer. What computer OS are you using? If Windows, I would then go to the "App Data" and search for any UD*.state files and remove them as well. Delete any admin.jnlp and/or start.jnlp from your computer - using older versions of these can cause unexpected random issues. Fully reboot the computer and start fresh Install current java only from java.com (https://www.java.com/en/download/). Download a fresh start.jnlp file from the UD website (clicking "My ISY" on the top right). Make sure you are not running any VPN or anti-virus/firewall programs and run the start.jnlp to put the IoX Launcher back on the desktop. Then open IoX Launcher and add "https://eisy.local:8443/desc" to your IoX Finder Window - this address alows you to login with local admin credentials. See if you gett he error. If you do not then log out of the java admin console and log into eisy_ui (https://eisy.local - in a browser) and be sure it fully loads. Then if you need to get back into the java admin console make sure you log out of the eisy_ui web interface and then open IoX Launcher again. These are just my thoughts of troubleshooting...you have been given a lot of steps to complete previously and seem to have cleared up all but one issue that if you've been having that issue for over a year something has remained "broken" through updates that you have apparently been keeping up with. Hopefully this might help. Ultimately, at this point UD would be the best bet for final troubleshooting steps if the above process doesn't resolve the issue.

@CTBigman sounds like you might have a corrupt upgrade and the best bet will be to get help directly with UD through a support ticket. Open a ticket here: https://www.universal-devices.com/my-tickets In the mean time try going here: https://eisy.local:8443/WEB/sysconfig.txt What do you get for IoX version? It should be the second section of the sysconfig.txt link. I haven't updated recently so version should be at least isy-6.0.4_1. If it is then perform a full power cycle - press and hold the power button until it turns red. Pull the power supply for about 30-60 seconds. Plug it back in, if the light doesn't turn blue press the button a moment for it to turn blue. Allow it to fully boot (at least 90 seconds or longer - you might get an alert on UD Mobile that PG3x has started). If you're on 5.8.4, but the FreeBSD is 13.2p11 you should be able to update, but something might be corrupt going from 5.8.4 to 6.x. You'll more than likely need to re-flash the eisy. Make sure you have a USB drive (what UD calls an "adapter" in their directions to re-flash).

I'm sure once the future (February?) date is set, I'm sure there will be another email blast about it and an update on the UD site. In the meantime if you didn't get an email about it make sure you're subscribed to get "Product News and Announcements" in your account on the UD site. Go here: https://www.universal-devices.com/my-account/ Sign in with the portal. On the "General" screen on the right should be a "Email Newsletters" section. Make sure to check "Product News and Announcements". I'm guessing that's the list Michel uses when news is posted to the UD site. I got the email on Jan 20th and the news/blog update appears to have been posted 1/19.

There was an email blast from UD a few weeks ago and the announcement posted on their website. You might need to sign up for email alerts from UD. I believe the host (OpenADR) is posting the recording. You might want to check their site for this and past events. Indeed they have released the recording and slides - https://www.openadr.org/webinar-series - "OpenADR 3 Price Signals and Local AI to Automate any Building or Device" Happy watching! I signed up for it and signed in at the start, but had work happen so couldn't listen to the whole thing. Glad the recording is up so quick so can watch it this weekend while snowed in. ❄️

@aguden take a look here - https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Linking_a_KeypadLinc However, if some of the buttons are there you might be able to right click the main node for the keypad and select "restore device". When you say you lost connection with all the switches what happened? Did you remove the PLM or replace the PLM? There's a process to restore the PLM that might have brought things back, but if you have everything working except for this one device not sure what you had happen.

@Ray95xxx review this post: https://forum.universal-devices.com/topic/44943-admin-console-not-working-on-mac/ Does this resolve the issue? I'm not sure about Java on macOS, but if you can clear the cache on it like on Windows machines I would clear the cache first then run start.jnlp again after changing the security settings mentioned in post linked above.

Trying to avoid making a snide comment is difficult. I really dislike the Alexa+ and turned it off as soon as it was forced update on my devices. Aside from the voice being unpleasing the constant follow up being enabled was not appreciated. The fact that I still had to go into the app and find where to turn off follow up made the entire forced "upgrade" even less likable.

@m6bigdog this sounds like could be a browser issue. If you're able to log into the eisy just using "eisy.local", but you're unable to browse to the settings/portal page or it's blank I would think it is browser related. Have you tried a different browser? Or depending on what you're using try a private or incognito browser session to see if plugins or cache might be blocking/hiding the information. Since this is a new setup and you've not been able to get it registered with the portal I would suggest opening a support ticket with UD so they can explore the issue and make sure this isn't a system issue with eisy-ui and hopefully get you up and running quickly if they find the problem. Support tickets can be opened here: https://www.universal-devices.com/my-tickets Either way, please post back what steps they go through to get this resolved so it might be able to help others should they face a similar issue.

Best way to ask UD directly would be through a support ticket - https://www.universal-devices.com/my-tickets While they somewhat monitor the forums they aren't as active as they once were (a lot of development going on). For reference I just changed mine to use the default server and sent to a comcast address and the test and a standard notification (by running the "then" line of a program that generates a notification) were received. So, no, does not appear to be Comcast blocking the messages, but this doesn't mean it isn't blocked on your side if you have a lot of alerts going to that address it could be considered inbound spam and it could be filtered at your user level. I changed the SMTP back to gmail and it still worked for me. I might suggest you setup a different SMTP if you are relying on emails for notifications. Otherwise, if you're using Polisy or eisy you should look at getting and using the notifications plugin for notifications.

In the link I provided above looks like ISY994 could use either FAT 16 or 32. Also there is this comment: Later on it seems there is the ability to go up to 32GB card. I think can use a larger, but ISY994 would only recognize/use 32GB. I’m not sure as I never tried bigger cards. Only replaced my card once (I think for testing purposes) ages ago.

It could be that Comcast/xfinity is blocking the messages. If going through to another server then it’s a receiving server issue. Either blocking UDI server or a relay between the two is broken/blocking. I would suggest setting up to send using a 3rd party SMTP (perhaps Gmail) and testing send to Comcast.

Unsure. And since nobody answered the first time you asked either they didn't see the question or don't know either. Try it and let us know. Strange that formatting in the ISY is causing the telnet to hang. Do you happen to have a different computer to test with? Wondering if a Windows connection would be different. Doubtful, but could be a bad SD card. Do you have a "spare" that can be wiped and tested to see if the PNY card is bad? Probably not likely to have many 32GB micro SD cards laying around. Since this is a "spare"/backup ISY994 do you know if this ever worked? Did you recently buy this device or is it one you've had and just haven't been using?

Just tested a program and a "test" email. No issues for me. I'm using gmail as my SMTP server and going to outlook.com domain. I also setup to send to gmail and yahoo and the "test" email all went to those domains. What SMTP are you using? If "Use Default" is checked try using a gmail account. The directions in the wiki seem to still be accurate since those are the settings I currently use. If you're already using Gmail to send the message make sure you've logged into that account within the last 6-12 months (Google will make an account inactive or not allow sending email if not logged into over a period of time). What domain are you sending TO? You might want to change the TO address and run a test message (be sure to select where to send the test message by selecting it in the "Groups" area (if none are selected it will not send the "test" message).

UD has been updating the wiki here and there with eisy ui information: https://wiki.universal-devices.com/Eisy:User_Guide#eisy-ui It's very much a work in progress. I have a few folders and find the main list very lack luster and difficult to migrate. It had a period of time that folders would automatically expand and they don't seem to keep their memory from one use to another. Because it's not very useful (to me) I haven't used it very much up to this point.

@j.rieff glad you found it. For future reference: Go to Universal Devices site (https://www.universal-devices.com/) and it's available via the "My ISY" near the top right of the site. Or you can direct link to it here: https://isy.universal-devices.com/start.jnlp

@matapan I'm assuming by "per documentation available" you were following the instructions found in the wiki: https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card It says if it was a new SD card you wouldn't need to format it. I'm not sure if formatting it has any impact on the NEW card or not, but perhaps some artifacts from macOS formatting it might happen (not familiar with macOS to know if even doing FAT32 doesn't add some "mac cooties" to the sd card. According to these directions there should be a "Goodbye" message after the formatting in the telnet session and then the ISY should reboot. I think at that point you have a very basic way to access the ISY994 via the admin console and that's why/where you would then need to update firmware to the latest for that specific device. NOTE: do you have a PLM connected to this "backup" ISY994? If not, you should only download/install the non-Insteon firmware. Otherwise, without a PLM connected you will always launch into admin console in "safe mode". I wonder if you could disk copy the working SD card to the new SD card and try that to see if it would boot up. I've never attempted it, so just a swag suggestion. Otherwise, try the telnet formatting again. Is there a way you can wipe the new card of any information and put it in an unformatted state?

Try these directions: https://wiki.universal-devices.com/ISY_Portal_MobiLinc_Configuration Remember, I don't think you can add the ISY Portal to ISY994 any more, but certainly works if/when you get the eisy on the portal. I just checked it out and my setup is exactly as described in the wiki. Online line I think it left out was "Connect Method" and I have it to Auto Detect and it shows as "Auto (HTTPS)". I also have it set to auto sync over wifi and cellular. Oddly enough it does show my plugin folder and the YoLink plugin does show temps of all my temperature devices (that's nice). Other plugins are there and report some info, but I don't typically refer to them in the app and don't use many plugins in automation settings. A couple of my Zigbee smart plugs/outlets do work. I don't have any z-wave currently connected so not sure if they respond or not. They do show up in the list of items, but they are not currently in use (come to think of it I don't even know where they're being "stored").

Did Michel get things cleared up for you through the support ticket?

Mobilinc HD still works just fine with Insteon devices and the eisy. I use it (rarely). I have it on the iphone and know exactly what you mean by being able to sort by name or on/off status. I've set mine up to use through the portal access just as I always had it with the ISY994. The only things I miss by using Moblinc are devices added by plugins. To me Moblinc HD/Pro has/had much better UI for layout. However, UD Mobile has been good the newer things being added with z-wave, zigbee, and plugins. I just don't have much use for those so haven't spend the time learning/transfreing to UD Mobile like others have. I'm using Mobilinc v4.17 on iphone iOS26.2 without issue. The "old" Moblinc Connect option is what broke when UD came out with the Polisy/eisy lines.

If you clear your java cache or look in the windows (I assume you're on Windows) temp folder for UD*.state files and clear one that might say finder or list or something (I forget the actual name and not local to my device currently) it might change the name the next time IoX Launcher is run. I think the name of the device is a cached value. If it didn't change on the following launch. Best to use the ticket option. My guess is something didn't update correctly and UD will look through the logs and probably give you a few commands to run. Since you ran the update packages again in admin console that would be the first suggestion to try an update process again. Odd that the web didn't give you anything on the sysconfig page. That could be a web issue. I would suggest trying a different browser. Also, you mentioned you use the Unifi edgerouterX. Do you run vlans? Are you running any antivirus, firewall clients, or VPNs on your computer? If so make sure you are on the SAME vlan as the eisy. Turn off antivirus, firewalls, and VPN clients.

This would be simple if you had an on/off outlet for the modem. I might wait a little longer than 60 seconds for the modem to be fully offline and the cable provider to "know" the device was offline. Make sure the program isn't set to run at startup in case you have a power outage and it shuts things down just as things are trying to boot up. I would probably go the route that @Ross did and get an inexpensive "smart plug" and just have an automation within that app to turn the plug off for 3-5 minutes (maybe middle of the night). It's tricky though do those power back on if the network is down when the scheduled time to turn back on happens? I don't use them so can't test (haven't tested). But ultimately, it comes down to what are you really fixing? You might still have underlying internet issues somewhere that would be better fixed with the provider. You're just making a work around situation rather than getting them to fix their problems (or finding out that it's something on your side that needs fixing). It's kind of like when router manufacturers added the ability to self reboot on a schedule. Why did they do this? Because they wrote bad code that would cause the router to lock up over time and people felt it was easier to make a reboot schedule than to buy a better quality router. You're just rebooting a problem rather than having the cable provider "fix" or at the very least troubleshoot if they have potential issues.

@stillwater Since the IoX finder window seems to indicate the device is updated to 6.0.4 it's possible you need to perform another reboot/power cycle to the device to bring things up again. Are you able to get information if you browse to this page: https://eisy.local:8443/WEB/sysconfig.txt (If you get a security message click advanced and click continue to site - it's local so it's fine to access) If after a power cycle you're still unable to get eisy UI to come up at https://eisy.local/ then I would suggest opening a support ticket before you go any further. Certainly don't get into SSH and run any random commands. During this time of development it helps UD more if users file support tickets before random attempts of repair that might make things worse. It helps them learn what happened to a system, but is also easier for them to correct what has happened to this point. Open a support ticket here: https://www.universal-devices.com/my-tickets Where will it show as "ISY"? On mine the "Name" is my personalized name given to the top item in the node tree and "Type" shows as "eisy". What's the result when you got to https://eisy.local/?