Wednesday at 12:45 AM2 days I am using eisy.ui 1.3.9 and IoX 6.1.2_7. I can access the admin console fine via start.jnlp launcher as always. There is an icon at the upper right hand corner of eisy.ui that downloads something calls admin.jnlp. When this is run the ac tells me that there is a version mismatch -- ac 6.1.1 vs IoX 6.1.2. No problem for me and quite possibly the glitch would go away if I cleared Java cache etc, but it seems a little weird to have this not work when the launcher does.
Wednesday at 01:08 AM2 days 20 minutes ago, stillwater said:I am using eisy.ui 1.3.9 and IoX 6.1.2_7. I can access the admin console fine via start.jnlp launcher as always. There is an icon at the upper right hand corner of eisy.ui that downloads something calls admin.jnlp. When this is run the ac tells me that there is a version mismatch -- ac 6.1.1 vs IoX 6.1.2. No problem for me and quite possibly the glitch would go away if I cleared Java cache etc, but it seems a little weird to have this not work when the launcher does.try this: log into admin console using IoX finder, but select "Admin Console (Cloud)" this time, which should upgrade your local copy of admin console on your controller, Then retry launching it from eisy-ui again.
Yesterday at 01:25 AM1 day Author I tried this and it did not change what version of admin.jnlp was being summoned by the icon at the upper right of eisy.ui. I always use the cloud rather than the lan option from the launcher). I usually use the url that allows the older ISY password to be used, rather than portal., but for this test I used admin console (cloud) from the standard (portal password) url. Not an issue for me personally but i could see that this behavior could be troubling for someone unfamiliar with the old ways.This is on a Windows laptop pc. Eisy-ui is version 1.3.10 and IoX is 6.1.2_8 Edited yesterday at 01:27 AM1 day by stillwater added my configuration
Yesterday at 05:25 PM1 day @stillwater I don't know for certain, but this might be a move by UD not to update the admin.jnlp file on the device now. Since it will end support for the java version soon. Usually my best way of being sure to have a current version is to download directly from UD's site. What you're doing is downloading the "admin.jnlp" that's specific to your firmware. If UD isn't updating that as the firmware updates then you're best bet is to use the start.jnlp downloaded from UD's site (clicking "My ISY" on the top right of their homepage) or the wiki. When you get the alert that there's a mismatch of firmware it's usually been by not clearing the java cache. That's been the best way to clear it out and download a fresh copy of start.jnlp to have the "IoX Launcher" icon added to your desktop. Admin.jnlp has always bypassed the "launcher" method. That goes back to the ISY994 prior to 5.x firmwares. Admin.jnlp would launch directly to the device. UD developed the "IoX Launcher" so that you wouldn't have to clear tha java cache so frequently when IoX 5.x (previously just ISY firwmare 5.x) was being updated often. Since IoX is being updated often again perhaps UD has quit updating the admin.jnlp file that's stored on the device. If you must use admin consolel I would suggest only using the IoX Launcher method and that's by getting start.jnlp from the UD site(s). As @Guy Lavoie suggests use the "Cloud" option and you won't have to clear tha java cache each time. If you use the "Local" option and there's been an update you might face an issue of the same warning.
23 hours ago23 hr Author Thanks. I want to be clear about this. I use the launcher method (start.jnlp) with the local password option and the cloud admin console option. (:8443 option and cloud choice on drop down). What I was talking about was admin.jnlp found and invoked by the (new to me) icon at the upper right corner of the eisy.ui screen. This icon was new to me and I was seeing what it did. So in my mind UDI is inviting users to access the admin console via this method. I was just trying to be helpful to UDI and others in flagging this. Based on what you say if UDI wants to leave the icon on the screen it should invoke a compatible launcher via the cloud if accessible rather than whatever admin.jnlp happens to be on the local machine. Or if it's going away the icon should be eliminated rather than inducing frustration for more naive users. Or it can be left as it is as it may work for people who have never upgraded or under some other obscure circumstances. Obviously it is likely to go away when the ac is no longer supported.@Guy Lavoie 's suggestion that running the launcher with the cloud option would reset the admin.jnlp that would then be invoked by the eisy.ui icon did not pan out on my machine. I was just trying to be helpful in flagging this. I don't care what UDI decides to do about this. Using the launcher versus the icon does not complicate my life --it is what I did before I noticed the icon.
Create an account or sign in to comment