Geddy

Go to this site: eisy.local:8443/WEB/sysconfig.txt (if you're on Polisy use "polisy.local"). If you are on 5.7.0_4 then it "should" be fixed, based on @Michel Kohanim's comment linked above. If not they apparently have additional debugging code that you would need to open a support ticket for them to learn more and to help (everybody). @oskrypuch What "fix"? Are you replying to the program disable issue or still about your concern for being bricked? Did you open a support ticket as @Michel Kohanim suggested? If you're wondering about the programs issue being resolved it does not appear to remain an issue for updated beyond 5.7.0, but there might still be an issue going from 5.6.x to 5.7, but according to other posts if on the 5.7.0_4 build another reboot should repair the programs to their expected state. I know all updates post 5.7.0 for me have not impacted the program status. I did have issue when 5.7.0 first came out and I updated from 5.6.x, but nothing since. One step that helps is taking that backup just before you update. You can restore that update and programs will return to their expected status. Then perform another reboot (or power cycle) and see if programs are as expected.

This is normal and not an issue. There’s no real explanation for this. Some have this and some don’t. But it doesn’t cause any problems.

Yes, this should be fixed according to a post from @Michel Kohanim yesterday. Requires an update to run. It doesn’t change the version number, but it is a fix from UDI’s side for IoX. Updating your system for the latest PG3x update should also update to 5.7.0_4. But to be certain make sure you make an IoX backup before you update.

@rick.curl I just tried logging into the system and didn't encounter an error. Make sure you're using your portal credentials. If you can get logged back in add something to the ticket so it's still open or re-opened. In the meantime maybe @Chris Jahn can help review this issue.

From the sounds of this you're using the very old method of trying to access the admin console. All browsers dropped java support ages ago and that method no longer works. in 2018 UDI release the ISY Launcher (now IoX Launcher) that @Techman mentions above. You need to download the start.jnlp file and it will add an "IoX Launcher" icon to your desktop. Here's the release post about the ISY Launcher (IoX Launcher) from 2018: (more info in the wiki: https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop)

Do you happen to have special characters in your password? If so, maybe remove those and try it. See this post from @Goose66

My question above wasn't answered - when did you update the firmware? That's probably when this happened. If you didn't notice it and you did it a long time ago I suspect it changed then and you just didn't notice it. "easy fix?" Doubtful. I wonder if it wasn't a problem until something else changed meaning you haven't found the real reason for this. During my time with the ISY994 things didn't just randomly happen. Usually it was user induced changes that created other issues. Sure, devices fail and cause problems, but that's not going to cause this type of change. You could get lost in the weeds for trying to test this so depends how large your system is and how deep you want to dig. Make a backup of your current system. Perform a restore just to be sure it's a good backup! Copy all programs to a plain text (.txt) document [right click on the root program folder, select "Copy to Clipboard" then paste into a plain text editor (Windows use Notepad)]. This way you have a "copy" of all your programs as they are CURRENTLY. If you have an old backup (maybe pre-firmware update) you could possibly downgrade the firmware and try to restore that backup to see if it goes back to what you are remembering. If that isn't what you expected then reload the current firmware and restore a current backup and move on from here. But that's rather drastic and might not work or could cause you a lot of other issues. Other options would be to create a random new scene (perhaps with devices not in other scenes) to see how they appear to you after setting up. Another option would be to remove existing devices from scenes, remove from the ISY994 then re-add and put into a new scene to see how that appears. Just a lot of individual trial and error at that point. Ultimately, the forums is the only place you'll get (free) support for the ISY994 as that's been discontinued by UDI and no longer supported (Paid support is available until June 1, 2024).

I'm not entirely sure. I jus know the Admin Console URL is what you need/use to access admin console. The other is used for different (more complicated "stuff") that I've never dealt with. I searched some old posts and found people sending commands to the ISY "back in the day" so not sure what that's really used for. Sorry. But glad it worked now for some reason. You might want to clear the other browser history and cache to see if that might help get things showing over there. Otherwise, maybe it's got some blocking add-on or something that wasn't allowing the information to load. Try that browser in a private/incognito window to see if the information loads.

@Wibar in addition to the suggestion by @Andy P to read through the Wiki the "easiest" way might be to use UD Mobile, setup Geofencing and have the app trigger the program when crossed. More info can be found in the wiki, but I think there's a link to a video in a post in the UD Mobile area on the forums somewhere. It's been a while since I looked for it.

I wonder if you’re dropping local network and it’s jumping outside the geofence area while looking to connect to the cell signal. I had this problem ages ago (before we got more towers near us). But I haven’t had noticed delays with UD Mobile current beta build 1.1.27 or the last few. And I rarely have UD Mobile open or in the background (I am notorious for force closing apps often). I don’t have this issue, but I also don’t have overly complex triggers. Mine works as crossing boundaries if not even running..and yes, Mobilinc HD does as well, and that app runs even less than UD Mobile these days. My experience is running on iPhone 15 pro max with UD Mobile and eisy updated/current as of this post. (I don’t have the specific versions handy as I’m “mobile” at the moment.)

The "enable internet access" isn't anything you need to do. Remote access is either by port forwarding on a local router directly to the device (not very secure) or using the URL found in the UD Portal and using your portal credentials to log in (much more secure...please use a strong password!). To find the URL for the device in UD Portal go to the "Information" area in this screenshot and select "ISY Infomration" then use "Admin Console URL". If you have multiple devices in your Portal make sure you're picking your eisy. Nope. That's all UDI has developed to run Admin Console. UD Mobile is being developed to be able to control most of what you can through Admin Console, but is a whole different issue (for many), and wouldn't be my primary preference for setting up complicated programs.

@GSutherland we get it...you're having HUE issues. No need to start a new thread saying the same thing you've said here already. I'm not sure what's happening, and since the node server hasn't been updated in a while would think it should work since it works for some. Since the developer doesn't seem to be responding on the forums it might be best to open a support ticket with UDI to see if they can get some traction with the developer to try to help. https://www.universal-devices.com/my-tickets Make sure you've read the other posts in the forum as there were hints/tricks to making it work in the past that should still work. It's quite possible something in the PG3x updates might have fouled up new installs and linking to the Hue hub, but I've got this working and it doesn't disconnect. The Hue and the eisy are right next to each other and connected to the same network switch.

@Goose66 I'm no programmer and no network wizard. So a huge assumption is made in how this all works. I've had routers not give a friendly URL and others offer it up quickly, but somehow the local IP also appears. If it's not an issue why bother it and even be concerned about it? It's not broke. Even @Michel Kohanim said "this is normal". I'm just expressing my experience as a user that has experienced both local IP and friendly url address coming up in the IoX Finder window. Try to calm another user that seems to think it's an issue when it's commented in several other places that others have this happening and it's normal and not "broken". Ultimately, the concern is resolved. User can access the system as expected.

@gadgetfreak sorry...can't help much more on this. I'm not running an ISY994 anymore and didn't get carried away in scenes so can't much relate to how the eisy is handling them to how they were in the 994 time. Perhaps others that had more scene knowledge can assist. In the eisy the "Link Type" is showing Insteon for the few devices I have in a scene. My guess is this is because eisy can run Insteon, Z-Wave, Zigbee, and node servers so it might have different entries than the ISY994 did. To see how a scene is setup you need to look at the controller(s) of the scene and the action might show different settings.

Glad you got it working! The 2 entries aren't (shouldn't be) a bother. It's probably your router allowing both the IP and friendly URL replying to the IoX Launcher search for local device process. It's the same device so isn't a concern. They're the same so can be used interchangeably. It's funny so many have considered this an issue of late. I had been used to it for so long that I never paid it any attention until others were worried about it.

As @Michel Kohanim suggests it looks like could be a Java issue. You said you have the "newest" version of Java installed. Which version are you running? If on windows open start menu and type "Java" then run "Configure Java" and click on "About". Should be Version 8 Update 381. I'd perform a full uninstall and clean removal (java removal tool) of Java and download again from java.com and try again. In the file Michel linked to above I think they're looking for some of the last lines. Specifically: <upgradeStatus>inactive</upgradeStatus> Also, make sure you're not running any VPN, Firewall, or Anti-virus software when you're initially running/installing start.jnlp.

@gadgetfreak Unclear exactly where you're looking for this difference. Can you provide some screen shots? Also, what Firmware are you running? You posted in the ISY994 forum so assuming your device is indeed ISY994. Have you updated firmware lately? If you "recently" updated from 4.x to 5.x there were huge changes in how scenes are handled in 5.x that might change whatever screen you're looking at for action = "default". What happens to the action line if you turn the scene on/off manually?

@Envirogreen What computer OS are you running (Windows, mac, other)? If on Windows after you click lan or cloud and nothing happens would you open your Task Manager and see if you have a "Jav(TM) Web Launcher" process running. If you do then you need to delete the .state files as mentioned in the wiki: https://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored The issue of having two entries is/was normal for an older version of start.jnlp. You mentioned you cleared java cache, but have you downloaded a recent copy of start.jnlp? Please delete all versions of start.jnlp or admin.jnlp you might have on your system and download a new copy from UDI site - https://isy.universal-devices.com/start.jnlp

@CoolToys split this out to the Elk node server area as it is a new issue for you. It was hidden in a topic that appeared resolved, but just general chatter.

@oamber not sure if this is new in an updated version of macOS, but see if this topic gives some insight for how to proceed. It seems that macOS doesn't like to allow Java apps from unknown sources. It just needs to be added/approved.

@DualBandAid I’m not sure why it wouldn’t populate if the device has approved the portal. Might need to open a support ticket for help. Check on the Admin Console on the Configuration tab that “Portals” is showing approved. Even though you say it has a green dot on the portal suggesting it is online. It might need to be reset. https://www.universal-devices.com/my-tickets

Exactly, but I think that’s what has caused issues….a reboot doesn’t actually power cycle the device, but more or less stops all services and starts them again. But I’m no programmer and just hypothesizing what is being attempted/done. That’s why when some updates wouldn’t complete a full power cycle was necessary to get the systems started in the correct order again. Reboot basically tells the device to start up fresh. From comments elsewhere it’s basically telling the device to start with the UDX then ISY then PG3 services. I’m sure it’s way more involved, but that’s my simple way of thinking about it. Restart IoX just focuses on that service running on the device. When it was simply an “ISY” device (be it 26, 99, or 994) it restarted the device, but now that the Polisy and eisy have multiple services running then the device needs a “reboot” function and ISY/IoX has a “restart” option. Just like PG3 used to have on the web portion to restart the Polyglot system, but that was removed. To me the reboot is restarting the UDX. Because ISY and Polyglot rely on UDX so much if that gets restarted then the ISY and Polyglot services should be restarted…thus “reboot”. I wouldn’t expect that there would be a simple way to ONLY restart the UDX system. The other services are dependent on it too much to have that core component restart without impacting the other services.

This was something in the early days of Polisy that got added to IoX. I'm not sure if it does anything now, but just hasn't been removed. It's not something I'd push if there's no discussion about it in the forums. Here's a post from @Michel Kohanim about this button. "Reboot" is supposed to reboot the device. Sometimes it works as expected, but sometimes it hangs and doesn't perform a full system reboot and power cycle is needed. "Restart IoX" should just restart the IoX system. It's not used as much as it once was when it was "Restart ISY" on the (old) ISY994 devices. It's probably useful if you're working with support and trying to troubleshoot IoX issues and just want to restart the IoX system, but usually isn't something that many often suggest here. Also, the "Update BIOS" is another button that showed up early in Polisy time that rarely got mentioned and doubtful that it should remain and certainly wouldn't push it unless instructed to do so by support.

@DualBandAid are you clicking on "Select Tool" then "Connectivity" then "Amazon Echo"? From there you should have a window that has this row of menu: Click on Device and there you should have this window: Are you saying this is where nothing shows in "my device"? Make sure you review the wiki for further assistance: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3#Instructions_for_Accessing_ISY_Portal

@Blackbird It would be helpful to know what versions PG3 and IoX you're running. Please share those if you can find them. If you can't find the PG3 since you can't log in try this (https://polisy.local:8443/WEB/sysconfig.txt) and look for a Name and Version for PG3. (if polisy.local doesn't work replace with the IP of your Polisy) Are you running PG3 or had you updated to PG3x? If you've updated to PG3x then the user/pass is the same you use for Admin Console local login. If you cannot get logged in here are the button presses to reset the credentials for the Polisy: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Reset_Credentials This error is common and is simple replace. You need to clear Java Cache (checking all 3 boxes) then download a new start.jnlp from UDI's site (https://isy.universal-devices.com/start.jnlp). The pop up should be gone after loading a new version of IoX Launcher.