Geddy

@PGME2 so are you on an eisy or Polisy? You've posted in the ISY994 area, but you're running 6.0.3 - that isn't on ISY994. Moving the post to IoX Support area. If you deleted the old device then it's gone. I wouldn't worry about trying ot run replace device again. If you physically had the old device would be the best way to find the address. You can run a Topology and see if you find it listed there, but you've probably deleted it. Perhaps some of the others that use scenes more can help resolve your issue.

@PGME2 welcome to the forums. First off will you please let us know what firmware you're running on the ISY994? If you're on 5.x you might need to click on the lable next to the setting you are adjusting. I do not use scenes much and not able to log into my system currently to see how the screen looks, but know since the 5.x change with scenes it changed how some settings were pushed to the device. Is there a chance the old device is still in the system? If you haven't deleted the old device yet make sure you remove it from any folder it might be in and hten try the replace function again. The replace device process will not work if the old device is in a folder.

What phone OS are you using? Do you mean that you have to open/close UDMobile or another app to get iBeacon to update? More than likely your phone is killing the background processes of UD Mobile.

@MTellevik the program @hart2hart posted above is correct for how it should look if recreated. Note that "My Lighting" would be different if you have changed the folder near the top of the eisy device tree. In ISY994 times the default root folder would be ISY and the next folder would be "My Lighting". I believe that might have changed in eisy times and be "eisy" and "eisy". Sometimes users will change the folder name for be descriptive of their home or loaction. The name may be at (or near) the bottom of the device listing when you update/make the program. So be sure you scroll all the way down the device list to see something that matches the name of the second folder in the device tree. From Polisy to eisy releases UD has not put this query program in as a defacult program in the system. I think as @Brian H points out it's not known if it is as necessary with dual band devices as their communication is much better than powerline only devices. Most that migrated from the ISY994 to Polisy/eisy have kept the query program, but those that just started with Polisy or eisy have not seemed to have any issue with it not bieng there from the start. It might depend on what kind of devices you have as to if it's needed for your system or not. You said you migrated a "while" ago. If things have been running fine you probably don't really need it, but it's not really hurting anything to update it and let it run. I might caution you to adjust the run time to a few seconds off the exact hour mark just in case you've got other thigns running on the hour. The query program does create a lot of Insteon traffic and could cause a colision if other programs trigger about the same time.

Thanks for pointing this out. The wiki has been updated to include a way to get to App Password if you haven't had one setup already.

Yes. That's what I've seen mentioned elsewhere. I don't recall anything official from UD being mentioned about this, but it comes from a few posts about "fixing" things in a few support tickets. Mostly with a few plugins that use the 3000 port and others that require specific logins from the plugins. I would assume as eisy-ui gets further along in development somebody from UD will put this in writing (and hopefully in the wiki).

That's good. Then it's probably how Alexa handles scenes. I don't have many scenes and don't expose them to Alexa so can't help. From what you were describing was sounding more like a scene wasn't setup correctly. Has this always happened or is it a recent issue? What if you add the scene, but in the "Alexa Category" make it a switch (or device)? I have a few 2-way switches that are scenes and have them in the portal as a scene, but "Alexa Category" is "Device". When I turn "Stairs" on both on/off switches show as on.

You can also use FIND in the programs area. If you right click on a program and see "Find/Replace" just before "Copy to Clipboard" (see image below). This will allow you to search for many things directly inside of IoX Admin Console. But copying the program to clipboard and searching the text that way is a good way to find things. That's often what is suggested for posting programs to the forums (if you select the individual program and paste it as text it's easier for people to help make edits). Also when you copy the root of the "my programs" folder to clipboard you can save it as text in case your programs become corrupt over time or during a firmware upgrade. These are great tools we've had in admin console for ages...hopefully they will be incorporated into eisy_ui so they can still be used in the future.

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.