Geddy

Seeing that the hue plugin was developed on unofficial api (based on previous posts about this plugin) and hasn't been updated in a while (years?)...I would hazard a guess that the "pro" hub is not supported. If you tried all the usual tricks and still cannot get it to connect, it might not be using the same methods that the plugin is using to identify and communicate allowing successful connection. Fun that there's a new hub for hue.

You've got to. It's the only way Echo gets the information from UD. But you said it's working now. At least all the items/devices showed up on the UD Portal site. So hopefully Echo is working and controlling devices again. Otherwise, make sure you follow the setup in the link provided above. You're looking for: "ISY Optimized for Smart Home V3".

Great to hear! Yeah, I didn't link to that since you said you had already migrated the portal. Seems that you hadn't. The migration process was written when eisy was just released. I don't think much has really changed and seems to still be a viable tool. I am not sure if there's anything in the ordering or setup instructions that might direct users to the wiki for the best/easiest migration process to follow. As far as I know UD Mobile really just lets you setup the device and get it updated to the current version. Moving years of hard work in setup, programs, and voice commands is a daunting process. Thankfully the migration steps are available in the wiki and work. Just knowing about them and being directed to them could probably be better. UD has often said they're programmers...not so much documentation writers. Thankfully there's a good (active) group of forum users to lend a hand, and of course UD Support is top notch! Have fun learning the rest of the eisy. If you've got other issues that crop up please be sure to start a new thread.

Do you have the UD Skill enabled on Alexa? Make sure you're using the v3 skill (released many years ago). Some people setup the Echo connection/skill in the v2 time period and recently received notices (from Amazon) that v2 is no longer supported (or will end soon). You'll need to enable and link the v3 UD skill in the Alexa app. It's possible it became unlinked and just needs to be relinked. This might help: https://wiki.universal-devices.com/ISY_Portal_Amazon_Echo_Integration_V3 Hopefully support can give other tips. I'd be interested to learn if it's possible to restore the spoken/setup you had previously.

Again, since the portal migration might have happened when you didn't have any devices in the eisy it more than likely wiped out anything that was previously there. When you log into my.isy.io go to "Connectivity" -> Amazon Echo. If the list is blank then you can try hitting the "refresh" symbol now that you have devices in your system, but I don't think that will do anything. At this point you might need to open a ticket to see if UD has any "tricks" or tips to get the mappings back, but I think it's not possible. Know that Echo and UD Portal are different systems. Just because you don't have items showing in the portal (I'm assuming you mean my.isy.io) don't assume they don't exist on Alexa/Echo. Confirm in the Alexa app that you don't have any devices through the UD Skill. In the Alexa app (on iOS) click the light bulb in the bottom of the app and it should take you to all the devices it knows. Look for anything you think should be a device from the ISY. Click on the gear icon on the top right. That should take you to "Settings". In there is an "About" and a "Connected Via". For UD Portal it will just show "UDI". If you find any devices connected that way, but in the UD Portal (again, my.isy.io) you should delete them from the Alexa app. No, rebooting the eisy does nothing to the portal mapping. If restoring the devices and trying to refresh through the portal page mentioned earlier (in this reply) doesn't re-map the devices then you'll either have to manually redo them or open a ticket to see if there's a magic way UD can help restore them. My bet would be you'll just need to manually enter them again. Yeah, that wouldn't be advisable. That's "standard". Not many ever click "more info" (I assume). Nothing to worry about there.

Since you migrated the portal before there were any devices it's more than likely everything previously sent to Alexa is gone. Check on the Alexa app to see if devices are still showing there. If they are, but they aren't on the UD Portal then you should probably delete them in the Alexa app and re-map them in the Alexa portal. As you do it the Alexa will discover them and add them back to the app. There's no way to go from the Alexa app to the UD Portal. And it's possible that if you map new devices the Alexa app will find them and treat them as duplicates. So that's why I suggest you delete them on the app first before mapping. To test maybe map one and see if you have any issues with Alexa saying there are multiple devices. If not then keep going, but it's tricky. Glad the other restore helped out. I'm not sure about using UD Mobile for migration since that's a new wrinkle that's been possible since the first migration steps were written in the wiki. UD Mobile is not doing anything with the IoX backups made in Admin Console so there's no way for it to restore it to Admin Console in the migration process. I'm "old school" and don't use mobile apps for "automation" so just handle everything in Admin Console and knew the instructions were written for that in the wiki. Good luck sorting Alexa out!

Did you restore the backup file you made? That's what pulls in the devices and programs. (Source: https://wiki.universal-devices.com/Eisy:User_Guide#Migrating - Step 5) What you're describing seems that you missed the step to restore the backup and went to a process of restoring the PLM, but that's not going to bring the devices in. Once you restore the backup you should review your programs. If you have any network resources you'll need to open each one and save them. (Also from the wiki - "during migration": "Network Resources All Network Resources will be migrated seamlessly, however, you will need to open and save each one individually."

@BJanzen Glad it came back up! Good luck setting things up in it. Make sure you bring it up to date on firmware before you start adding things again. It will be easier now if you're starting fresh/new with everything. Especially since you did a reset. You can find the firmware in the Current Release area of the forums. If you're not running a Z-Wave module in the ISY994 you can go up to 5.3.4.

@BJanzen welcome to the forums. Take a look at the wiki for the front light indication of what might be happening: https://wiki.universal-devices.com/Main_Page#Front_Panel_LEDs/Lights More than likely just a power supply. The ISY994 accepts a wide range of power options. Check if you have any other barrel connector power supplies near what the existing supply is and try those out. Also be sure that you properly attempted the factory reset as outlined in the wiki: https://wiki.universal-devices.com/Resetting_Your_ISY When you reset it the device probably went into auto DHCP to connect to the network. Check your router to see if you find the MAC address of the device connected. It's probably at a different IP address. If you set it up that long ago you probably set a static IP and the initial issue was that it couldn't get a network connection. The current suggestion from UD is not to set the device with a static IP, but to have an IP reservation on the router (to avoid possible IP conflicts if you change network equipment and forget to set the DHCP table to the same as the old equipment.

@stupalermo interesting error. Can't say I've seen that one. Your best bet is to open a support ticket with UD - https://www.universal-devices.com/my-tickets Rather than having other users giving a bunch of random suggestions if you've not done anything, but you did an update and now cannot access the device it's best to get UD help for the best troubleshooting steps and not randomly trying things or suggesting options that could make the situation worse to recover from. Since you said you tried to update to the latest version it's possible something got hung during that process. Even though you didn't think there was anything different something underlying could have been corrupted. Good luck.

@skydvrz you've got to go through the eisy web interface and find the plugin store through that. Looks like hte site you went to is just the list UD keeps for the plugins available. https://wiki.universal-devices.com/Eisy:User_Guide#eisy_(PG3)_Dashboard Once there it should have install options as shown in the wiki: https://wiki.universal-devices.com/Eisy:User_Guide#Plugins_Store_Menu

Apples & Oranges! Plugins do vastly different things than "simple" automation programming. So it has to be in a more traditional programming language. Thankfully, it pulls devices into the IoX world that the "simple" automation can be programmed with infinite variables that we all enjoy having the option to manipulate how we see fit. It's wonderful to have options outside sometimes limited apps for other "automation" systems. This was certainly UD driven, but as a result of "user error" in the time of the ISY994 (and maybe prior). You can find endless posts on the forums and probably even hundreds more support tickets that UD had to handle for people that set static IP in the device then changed their home router and ended up with a different DHCP table. In an effort to limit the total time and energy spent on the support tickets UD did the right thing (IMO) to force the device into automatic DHCP and then allow those that have the need/desire/skill to set a simple IP reservation in the router to achieve the same goal of a "static" IP. I don't blame UD for that one bit. It's been this way since the Polisy came out (almost 6 years ago) so really a moot point to be complaining/commenting about this far out from that change (again IMO).

HA! Highly doubtful since ISY programming has been the same for many years. I only started with the ISY994, but some here go way back to ISY-26. To change it now would break everything that's been done since the early 2000s. But you can always ask UD directly. Use their "Contact Us" link on their website. But I doubt it will get much though (only based as a user that would be completely lost if changed to a programming language). Let's face it...you've even been a member here since 2009, so you go back a ways. Why change now? There's no driving force to change and what's being done works.

Yes. That helps having the program disabled by not allowing that "IF" condition to ever be evaluated until you call on it by another program. Just make sure it's not nested in a folder that has false folder conditions - that can keep any program in that folder from running. Often times people use the underlying program to only run "Then" or "Else" actions, but also being able to run the "If" allows that to be evaluated in case it needs to cause another action. The tricky thing becomes knowing that it will only evaluate when called by the first program and not ongoing. If it's something that might happen over a period of time you might need repeats or other triggers. It's a good process, but takes a little testing for fine tuning depending on the first program. https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Add_to_Program#Action I also like being able to enable and disable programs this way.

While not exactly a “IF” in the “then” portion, but you can run/call another program in the “then” which contains an “IF” statement that you would want to run/evaluate. One trick is to have that other program (the second) disabled so it is only triggered by the first program to evaluate. I do this often with trigger programs for other programs that have waits in them. Since a program would re-trigger during the wait if it was in the first program and not end if it went false.