Geddy

I'm not an Android user so can't help specifically. My guess is the settings have changed since the wiki was written. Perhaps other Android users can chime in or @Javi might have an update to this. So people know how to help what version Android are you running? What IoX version are you running (please give actual version number - check here: https://eisy.local:8443/WEB/sysconfig.txt and look for ISY-6.0.4_x )

@JSchumann the wiki lists what sounds are available: https://wiki.universal-devices.com/UD_Mobile#Sounds

@jkraus try a power cycle on the device. Unplug the device. While unplugged I would remove and reinsert the dongle to confirm good connection in the USB port. Plug the device back in. Wait 3-5 minutes for it to fully boot. Then log back into what you're using to see "not responding". Or you can try "reboot" from the web ui (http://polisy.local/system/upgrade - or replace "polisy.local" with the ip address of your system). If you're running 6.0.4 it's at the bottom of the screen). If you are running java admin console try the reboot button on the configuration tab. If a power cycle does not work then please open a support ticket with UD to get further assistance. https://www.universal-devices.com/my-tickets

Where do you see this? I went to UD's site and the price is showing $152. https://www.universal-devices.com/product/zmatter-usb/ I don't see anything on thier store that would be close to $800. https://www.universal-devices.com/store/

@GreyFox there is probably a different value stored in the .state files that UD uses in the temp area on the computer. Check this part of the wiki: https://wiki.universal-devices.com/Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored I think @Guy Lavoie and @dbwarner5 have offered valid suggestions for making them work similarly. If both computers are always local to the system then I would probably lean more toward the direct login as @dbwarner5 outlines. I've got Win10 and Win11 laptops and use admin console on my local eisy, but also a remote eisy system sometimes. It gets tricky if/when I'm traveling to the remote location as it will find it, but still list the home device (sometimes). There seems to be a real disconnect in IoX Finder window if/when the computer is not on the same network as it will keep some of the cache info, but other times it is blank and/or just finds/lits the local system. I suspect the valuse stored in one of the UD*.state files (probably: udi_launcher.state) is what keeps the addresses stored locally. Since it's in a "temp" file that Windows controls there's no telling when they'll get wiped out. Saving the list that includes all systems that I might randomly connect to is simple to load if/when the finder comes up without all the options. Perhaps the one thing I do look forward to with eisy_ui is the lack of unpredectibility of how you'll log in. I just hope remote access is as easy as it has been wirh the java admin console.

@JDeRose If you have an eisy then I would just use that device to learn about the portal and UD mobile options. For the ISY994 I would suggest just using Mobilinc and using the local connection setting. If you want to open a port on your router you can do that and still access the device with Moblinc, but it's not as "secure" (since you are opening up your network to risk by having a valid port open. I might suggest using a non-typical port number). The ISY994 can work with UD Mobile, but only with 5.x firmware. Again, I'd say probably just use the local connection. If not able to add the portal to the ISY994 you can still use the local connection option. I haven't taken the time to learn all about the UD Mobile options as I don't really need an app. I still use Moblinc with the eisy since it controls nearly everything I have (I'm basically 99% Insteon devices). It's just more comfortable for me and easy to use what I've had for about 10 years now rather than taking time to set up UD Mobile when it's still changing (and randomly breaking stuff) as eisy and IoX continue to evolve.

I believe UD made an announcement soon after the ISY994 was no longer supported that the portal would cost more for the ISY994 due to underlying security issues that the ISY994 couldn't work with at the time. I know they raised the price for people keeping a portal account with the ISY994. So marginal additional revenue stream might be overcome by having to "support" the connection from unsupported devices. I think it was even said that the portal couldn't be added to ISY994 devices at one point. So I'm not sure even if it wasn't registered to somebody else if you would be able to add it at this point. Perhaps you could, but UD really doesn't want to keep having to support them with the portal connection. Since the ISY994 works so well off line there's little gained by adding the portal at this point. What is your desired outcome by having the portal connection?

@Techowl the instructions in the wiki for setting up the gmail account still work as of somebody using them to set up within the last few weeks. https://wiki.universal-devices.com/ISY994:Configure_Mail_Server_Settings#Configuring_gmail_Account One thing to try is change the time out to 10,000. You might also want to add something in the "From" portion. Then when you try a test message make sure you have a recipient selected for it to send the test to. If you're only using x10 devices and you've had it working on 4.9 as long as you have then I agree with you that I wouldn't want to change the firmware. There were "big" changes in the ISY994 from 4.x to 5.x that would probably require some adjusting. As for using the "default" in 4.9. That was changed due to additional security steps added on the UD side in a 5.x update due to server settings to block unrelated parties from using UD servers to send messages. It was behind the scenes (as best as I recall) and was not implemented in older firmware versions so you more than likely would have an issue using the default server.

Is/was your spoken really “turn off all the lights”? It would appear (to me) Alexa+ thinks it “got smart” and was controlling anything you had in the system as a “light” and turned them off within Alexa(+) rather than the program/scene you have in IoX. I would suggest making the spoken a simple word/phrase. That way Alexa+ knows you want to control something from IoX. I think some have just a “goodnight” scene or program that is run. If you just said, “Alexa, turn on bedtime” and your bedtime spoken ran a program or turned the scene off it would work as you expect. But by using the command “Alexa, turn off all lights” it’s looking for smart devices that are lights and turning them all off. It’s goofy, but the Alexa programmers are trying to be “smart” by trying to control things within their system rather than using linked skills. The proof is basically that you used UD Mobile and it worked as expected. Meaning Alexa+ wasn’t using the skill at all.

Click the label next to the setting you are changing. That will update the setting. This is a change that UD introduced in 5.x many years ago and is discussed here many times. Don’t use the “write changes” at the bottom of the screen (for these changes). Also, some have noticed that if you set a specific on rate or other settings I might not show on that device the next time admin console loads as there seems to be a display issue. No known workaround known for that issue.

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