Geddy

What you describe above sounds like a failed or corrupted update that somehow allowed the eisy to become visible again (without you doing too much other than what you described). I would suggest opening a support ticket with UD to have them review your information and give you troubleshooting tips. https://www.universal-devices.com/my-tickets I'm not sure what OS you had if you were still on 5.8.4. It's possible you had an updated OS that the update attempted to run and what you describe about the portal being available in eisy-ui is something that @bmercier commented on elsewhere in a reply to somebody. But if you're not able to get into eisy-ui to approve the portal connection then I'm not sure what to suggest. Don't go trying random SSH commands until you've opened a ticket and UD tells you if you need to connect via SSH and they'll tell you what commands to issue. If you just randomly find commands mentioned on other replies they might not directly relate to your issues and could put your system into more trouble than it might be currently.

@apostolakisl nope, doesn't seem like you're the only one...from the sounds of it from @Jimbo.Automates it might be a bigger issue with the company that hosts the product.

You might need to re-enable or re-link the UD/Echo skill. If nothing is working then seems like the skill got broken in the update to plus and/or in the reversion back to the old style. https://wiki.universal-devices.com/ISY_Portal_Amazon_Echo_Integration_V3

@cmaciag it's been a while, but I don't think there was ever a method to migrate from PG2 to PG3. I know there was going from PG3 to PG3x that's outlined in the wiki, but not seeing anything for PG2 to PG3/PG3x so don't think it is/was possible. You might be able to open a support ticket with UD to see if there is anything they can do with this, but I think there's such a huge change from PG2 to PG3x that it's best to buy them specifically for the eisy and install them fresh. Open a support ticket here: https://www.universal-devices.com/my-tickets I'm sure there is/was, but it's been so long since I used it and was on Polisy at the time so not sure what the process would be. If you can log into PG2 there might be a menu to change the password. If you never changed the password maybe try admin/admin for the default.

At the top level of just the file level of backup...since I will make random changes or programs to help others here just about anytime I open Admin Console I run a backup right away. That way I know I have a "that moment" backup to rever to if something I do goes south. Otherwise, if it's just for personal change reasons I always make sure to make a backup after I make a change in something (either device setting or program change). Again, so I know I have a backup right then. All my backups are saved to a Dropbox folder so they're available on other computers I have so if my primary computer crashes the backups are available. Operationally I have 1 backup PLM that is "NIB" (new in box) that I got from Insteon before they closed so it has a couple of years on it being in the box. I have a backup serial conversion cable in case my current cable from eisy to PLM goes bad. I have a box of "spare" Insteon devices that would replace the most used devices in the house. It's not a large box, but it's enough to replace devices should they fail and get me back up and running quickly rather than having to order new from Insteon (again, from before their close when items were more difficult to source than they are currently). Z-wave - I only have a small number of devices in use that if they die they won't be replaced. They aren't mission critical currently and only used in random programs. Zigbee - never got into this one. Only have one device and that's just a thermometer/humidistat device so if it goes south I'd probably never know. I only got it for testing Zigbee when it went live. UD Portal - I'm not sure what you mean by having to recreate definitions if UD moves your license to a new UUID. I think they made a process that you can migrate the license to a new device and it does move everything over. If you have them manually move it then I do think you have to recreate everything. Gret thought and conversation start. I probably don't fit the mold of so many here that tend to have things so tightly integrated and reliant on commingling different systems. I'm no ultra power user, by any means. If my system went down (for a few hours, or days) I would be able to manually turn on any light in the house that I would need on (or off). My eisy and Insteon devices are more for convience and my automation is built around 7+ years of how we want our house to look/feel during the day and based on where we are in the house. It's not overly complicated and just works for us.

@MFBra or @zorax2 Please give more details so others might be able to help. But there have been reports of the new Alexa+ is having issues with home automations or skills in general (Other posts on the forums have mentioned issues). Please post more about your situation: UD Device in use? Firmware number (specific number not just "current"/"latest")? What kind of devices are not responding (Insteon or other tech)? Are you controlling an actual device, program, or scene? Always best to include more information rather than just saying, "something isn't working 100% of the time". It's kind of hard to troubleshoot...that's probably why there were no replies to initial post a couple of weeks ago. Simple troubleshooting: Power cycle Alexa device(s) Powercycle UD Device Control device with other method (UD Mobile, Admin Console, Physical switch) Confirm UD Portal license is current Confirm UD Portal is using proper device (UUID) and linked to Alexa Look at "My Profile" and see that preferred UUID is correct Click on Connectivity and confirm UUID is active UD device Confirm Alexa Skill is linked to UD Portal account - might need to unlink/disable skill and then re-enable to re-link

@Jeredvh welcome to the UD forums. I'm not familiar with the product that you're using, but there was another post about this a few years ago that might be worth reviewing. I'm sure some of the same people that lend a hand in that thread might jump in here to offer help. Good luck!

This looks like you'd be better off asking UD through a support ticket. Since we're all just users helping users we'd only be speculating at the reason for this. Yes, UD does monitor the forums, but with the level of activity of late many posts might be missed or cannot be answered easily in the forum setup. If this is still happening and you've rebooted the device then I would open a support ticket and see if they can help review the logs and let you know what might be going on. Perhaps something got hung in the update. https://www.universal-devices.com/my-tickets And yes, @mmb is correct if it's Amazon traffic that UD does use AWS to host the portal and other UD cloud data.

I think you've got to try to run it or download it and within a period of time it might show in the list. I think @Bumbershoot had a post a few years ago about this and might have indicated that the entry only stayed for a period of time (maybe an hour). That if it wasn't shown it would need to run again to be available. I don't run macOS so can't help, but recall there being a post about that in the past.

@TJF1960 there's been several other posts (they're probably way down in other threads, and let's face it who reads every thread?), but basically "eisy-ui" is still being developed and is not fully functional at this point. It's been in Alpha/Beta testing since June. It has improved based on reading other posts in this area of the forums, but @bmercier has said several times that it's not fully functional yet. As to how to log into the system once you have eisy-ui instaleld you can see that's covered in the wiki: https://wiki.universal-devices.com/Eisy:User_Guide#eisy-ui Glad the update went well. That bodes well for when I'm able to take the time to be home and dig into it.

What problem is this? There's been several problems in this thread. Which do you have? You can highlight a previous post (a portion similar to what I have done) and click "quote selection" to reference prior comments. This is expected and outlined in the wiki for eisy-ui. Please referr to the wiki: https://wiki.universal-devices.com/Eisy:User_Guide#Changes_introduced_with_eisy-ui Glad to hear the update worked well.

If using https add :8443 to the end of the URL. That might help. No port used is usually looking for :80. Since you're local to the device there's no real need to use https. There's no external comunication happening. Just browsers default to https these days. That's why only local devices need to add specific port that the eisy might be listening to. I think the ultimate goal is to make it the 443 port, but it's been 8443 for a while. If able to access with http that is fine. Don't complicate things that don't need to be complicated.

Try putting eisy.local:8080 then the above lines in a browser. http://eisy.local:8080/rest/nodes (xml display - I'd save to text file to put on ticket) http://eisy.local:8080/rest/profiles?include=nodedefs,editors,linkdefs (copy text and save to text file) It should ask you to login to display. Since it's local try the local credentials.

https://wiki.universal-devices.com/Eisy:User_Guide#eisy-ui

Anyway this can be avoided? While so many seem to dislike the Java version I find it meets the needs of simple adjustment and easy handling just fine. From what I've seen of the web UI it's "cute" and acceptable, but the current access to admin console is ideal (what we "grew up with") that I don't really see the need to completely do away with it just for a web version. Just my 2 cents. Please keep current system as long as possible!

I'm assuming you're using IoX Launcher to get the Java version of Admin Console. The "eisy-ui" is a different method of attempting to use the admin console. It's still in the early stages of working, but seems to be good for most that are trying it out. I haven't tried it yet. Learn more in the wiki or other posts around here: https://wiki.universal-devices.com/Eisy:User_Guide#eisy-ui

The release note seemed to indicate there would be an indication as to when to reboot. I have not updated yet so not sure if it does. I think after 2 hours would be okay to reboot. More than likely (are you on macOS?) the admin console window lost the connection to the device and isn't updating. If your mobile device said the device restarted it might be fine to force a reboot. Since I haven't updated not sure what to expect. Letting all you early adopters go through this before I take the plunge. I'm also not local to my device and don't want to blow an evening trying to update it just for a web ui that I don't really want/need to use.

@Athlon correct. The port 3000 should still take you to the PG3 login just as it always has. That is NOT the new UI for IoX. From the eisy-ui release info back in July: Last I saw/heard around here was that it was being tested for use on Polisy, but not sure if it would be available. Since it's "eisy-ui" I'm not sure if it's active for Polisy users. That's something UD would need to answer. More about the eisy-ui is on the wiki: https://wiki.universal-devices.com/Eisy:User_Guide#eisy-ui

Correct. You won't have to use SSH. Just follow the directions in the announcement post form earlier.

@TROSEMAN your post is kind of wide open. Can you give some specifics? The Elk system requires the Elk plugin. You can find help in that area of the forums, but also through the plugin store with the "more info" on that plugin. There's lots of directions you'll need to read and understand to get things sorted out. For programming lights take a look at the UD wiki and the ISY Cookbook (yes, it's written for the older generation ISY994, but all the program still relates to IoX today).

I'm not 100% sure if works in the linking method, but open event viewer and set it to level 3. It might show stuff while items are trying to link, but not sure...I've never attempted it. If you're "FAR" away from the PLM it makes me wonder about the PLM itself or noise in your electrical system that isn't letting the Insteon traffic get back to the PLM or ISY994. How old are most of your other Insteon devices? If all/most are recent (last 10 years) then they're usually 2 methods of communicating via powerline or RF. As long as you have other devices close they should be repeating the signals and should be able to add something you have within inches of another.

How are you linking devices? Are you typing in the code or using automatic linking? I would try the automatic way and see if that adds everything for you. Wiki info: https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Link_Management_Menu I usually just use the "Start Linking" option. I don't get into the specific type. It's simple enough. If the devices are new you might still want to perform a factory reset (see Insteon's manual for steps for each device you're adding). It's usually a good thing to remove any links found as even "new" devices can have ghost links from any factory testing performed.

While you might have figured it out you might look at the screen again. I don't use z-wave devices like this, but if they have a screen similar to Insteon devices on the "on level" when you set it to 50% is there a button/label next to that setting? click THAT "button". This is for an Insteon dimmer. A long mentioned UI issue since 5.x came out meant the button next to this setting is what writes it to "memory". I'm not sure if z-wave works this same way or not, but I would hazard a guess that it does.

@awysocki when you're rebooting how are you achieving this? I would suggest you open a support ticket with UD. I know they're working on updates to the eisy-UI and other updates in the system so it might be best not to randomly try things, but to get UD on a ticket with this so they can see/verify the logs and see what happened to help them troubleshoot the release so more people don't have issues. https://www.universal-devices.com/my-tickets You've got a few things working against you in that the java admin console window isn't designed to be up 24/7 so just leaving it up all night if the computer went into hibernation or sleep state it could have been an issue and even though you had a message didn't properly reboot the eisy. Not sure what's happening in the reboot you've been doing now, but if you have it connected locally then it should be mostly coming up. I would think UD would have the best indication as to what needs to happen to get it fully operational again.

@ta2four ****BEFORE YOU RANDOMLY UPDATE**** Know that there is a huge change from 4.x to 5.x. Hopefully you haven't updated yet. You need to prepare yourself for the update. Make a copy of all your programs - on program tab right click the "My Programs" (root) folder and select "Copy Folder to Clipboard" (note COPY...do not "export"). Paste that into a text editor (Windows PC use Notepad). SAVE THAT FILE! You should be able to add devices you're adding to your existing ISY994 with 4.9.0 firmware. You might want to resolve that issue first. Only things that would have issues is if you're adding i3 devices from Insteon (the newest devices they've released). Legacy type items should add without issue to 4.9.0.