Geddy

@shawnv not sure of a limit, but if you're not able to get more recognized you can install the plugin into another slot and see if that will recognize the other devices. That might be a workaround if there is a limit. Perhaps @Jimbo.Automates can chime in to advise if there's a limit.

What device are you using and what is your IoX firmware version? As this is not widely reported as an issue doubtful there's a "resolution". My notifications continue to work as normal. Tests and random program runs trigger email notifications just fine.

Yes. Thanks. Please post what support steps are completed to correct this issue, if you can. This is strange that it's unable to be deleted. How many customizations do you have? Since you mentioned you migrated from ISY994 to eisy would you also try clicking/opening each one (slowly). Then hitting save. Just close IoX Admin Console (don't reboot the device). Then log back into IoX Admin Console and try deleting again. It's a long shot, but I know that Network Resources needed to be opened and saved in the migration steps. I wonder if it might help/work on the customizations as well.

@larryllix I'm not sure what links you've been following in the past, but I'm fairly certain the wiki links haven't changed in ages (mostly because the old pages the links to start.jnlp haven't been updated in years - in fact I just looked it up - wiki link hasn't changed since 2018.). But more than that UD has always hade the "My ISY" link on the top of their home page that links to start.jnlp. I don't think that's changed in at least 5 years and probably even more than that. At least since they changed to the IoX Launcher method (using start.jnlp rather than admin.jnlp). Fairly certain this has been the link for YEARS https://isy.universal-devices.com/start.jnlp But what's funny is the link @dbwarner5 suggested (http://192.168.68.76:8080/admin.jnlp) has been around since the ISY994 days. It's been the method since browser quit supporting the java web method. And I'll echo what @apostolakisl says...if it wasn't for Java updates and having to clear the Java cache and reloading start.jnlp the java admin console method has been flawless for my use case for as long as I've been an ISY user. I can count perhaps ONE time that UD had to update the start.jnlp file due to an error that somehow got introduced. But that was when a "not found" issue popped up and they had to change the code in the start.jnlp file. That issue lead to my usual suggestion of downloading a fresh start.jnlp each time it was needed. Just in case it happened again, but there haven't been reports of really needing to do that recently.

@leadfoot interesting. I just created a new customization and reloaded IoX Java Admin Console and it deleted just fine. It's an outside shot, but I might clear java cache (be sure to check all 3 boxes) and download a fresh start.jnlp file (delete any old start.jnlp or admin.jnlp files). I wonder if it's a random cache/visualization bug - that has happened in the past. What IoX version are you currently running? (Please give actual number, not just "latest/current"). What Computer OS are you using? Make sure you are logged out of any PG3 or eisy_ui web interfaces while in Java Admin Console.

I might have suggested migrating the portal license from eisy1 to eisy2 then getting a new license for eisy1 when you set it up at the other property. I'm not sure if this would have migrated the plugin licenses (I think it does, but at least did in the past), but would have migrated all the Alexa controls. https://wiki.universal-devices.com/ISY_Portal_Migrate_configurations_to_a_new_ISY The rest looks fine. I'm sure it's fairly simple with the way backups are used now. The only risky thing would be PLM related, but that should be handled with the IoX restore.

@BCreekDave and @Ross no issues running a test message or triggering a program notification using Gmail settings that I've had for many, many years. I don't have a regularly scheduled notification setup so just based on testing now things worked as expected. Make sure you are not sending a lot of messages (not sure what would be "a lot") perhaps Gmail is blocking too many attempts to send notifications. Be sure you've setup in accordance to the wiki information: https://wiki.universal-devices.com/ISY994:Configure_Mail_Server_Settings#Configuring_for_Use_with_gmail Be sure that your timeout setting is high.

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.