Geddy

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.

I don't think it went that drastic. If you're not in the eisy why worry? What's being installed when people update is the early form of the eisy-ui. It's been in alpha and beta test for a few months now. Lots of feedback elsewhere.

FYI - has NOT been released yet. The announcement basically said to stay tuned.

What makes you say this? From the wiki: https://wiki.universal-devices.com/Eisy:User_Guide#INSTEON_Support Perhaps @Brian H is more accurate with the reason(s) not to use. However, if the eisy indeed supports the 2412S and that's what @windrockwater has then perhaps it would work with the correct cable for connecting to the eisy. Of course the serial PLM kit is needed. NOTE: @windrockwater if you have the old serial cord that came with the serial PLM (I'm not even sure if the 2412S might have included it...I know it came in my 2413S). You could try an adaptor from Amazon (this cable has worked for me since getting the eisy) to try the PLM you already have. Otherwise, you'll need the PLM Kit that UD is selling. That's the best (single cable) way to go from older Serial PLM connector to USB. And the only way UD supports troubleshooting possible PLM issues by using their cable/kit.

@mmb what are you using to take thermal heat images like this?

@mvgossman based on your screen shot you're using the ISY Portal address for your device. You'll need to use your portal credentials to log into admin console. Don't do this! You should be fine if you use the correct credentials.

@Breezyken I too have several Fanlincs installed. They all work with 6 button keypads. I set them up in the old ISY994 4.x days and then updated to 5.x and now to eisy. They work just fine. The wiki has been updated to how to program them with 5.x firmware and there was a lot of discussion for this method and others elsewhere in the forums (you might need to use Google Site Search as sometimes the forum search doesn't correctly find/show old (possibly archived) threads). https://wiki.universal-devices.com/ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration I've neve set them as % ranges. The buttons on my keypad are set to High/Medium/Low settings. Then there are scenes that have that. Sadly, because IoX just estimates scene settings in UD Mobile sometimes it just shows the percent (for the fanlinc motor, but the scene for the speed will be active. I don't worry about it. Our fans are usually voice controlled through Echo to change speeds. As long as you have the motor setup as a fan in the portal it works just great. I use programs to keep the keypads in sync (again, goes back to how I set things up originally).

Yes, if you use z-wave. If you buy an eisy and use z-wave and want to use the ZMatter device then get it from UD. I'm not 100% sure if 3rd party z-wave controllers work on the eisy. I haven't tried other controllers and kept up enough to recall if others use them with the eisy or just the Polisy. The board inside the ISY994 is not compatible with anything for the eisy. See this post for information about identifying your z-wave board in the ISY994.

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.