raymondjiii

Also, before this in "Privacy & Security" down near the bottom you will see a little box saying that start.jnlp was prevented from starting (because it's not signed by a developer or whatever) so you have to enable that first - it's hard to see and you would not think to even look there - at least I didn't. I was trying to do "Open With..." etc and that's when I found that at cmd prompt you could run: javaws ./start.jnllp and that did not have any issues. But I do see javaws in the list now (the same list you are showing above.) Every upgrade, I think more is broken than added. Maybe it will be nice that I can access the iphone screen on the Mac - time will tell if that's useful for me.

It wasn't adding it. I knew exactly what the IP address as I could see it's MAC address in the router (MAC address is on the bottom sticker) - so I was 100% positive I had the right IP address. I tried http:8080 and https:8443. As I said after "pushing buttons"...for a while...it was able to show and then I had to restore it from a backup.

Okay thanks I'll try that. Currently I have 10 items there including "IoX Launcher". I was just going to create a shortcut to run "javaws start.jnlp" - that avoids all of this (at least it did last night). I had a ticket open with UD but that was for the weirdness I was experiencing with the Eisy - which I think is also resolved...I hope. I just installed Sequoia last night. I was waiting until December when I knew that if something would be altered (like my other programs) I would have time to resolve but I wasn't expecting this problem. I doubt apple is going to fix this anytime soon. I have a large list of UI bugs in MacOS Apple Music (been there since day 1 when it was "iTunes") not a single one was fixed. These are not common things that the average person would do but I spend a large amount of time using Music but you'd think Apple's QA department would have caught some of these. Thanks for your reply!

Well, I wish I knew what the hell I did....pushing the button 10 times, 5 times, 2 times (not in that order just trying different things) IoX Launcher found the Eisy once (after countless failures) but couldn't could not connect to it again, even though it was right there in the IoX list. So I deleted it from IoX, got it showing up in IoX again - did a restore which oddly was from a 5.8.3 firmware backup made back in June 2024 (I have not added any devices since before June 2024). Then, either before or right after the restore I see that I am now at 5.8.4. I think the only safe way to do a firmware update is through UD Mobile. IoX is very odd in the UI when you try to update firmware. It does not give you any status, and tells that you need a reboot - really? After 0.0001 seconds from claiming to "start" to do the firmware update it has to be rebooted? What a mess. I was about to try the HDMI video and USB keyboard and mouse next (never tried that). I still cannot figure out how UD Mobile "lost" contact with this Eisy. UD Mobile must get into a state or save something about the Eisy and that after the hard reset, reboot, failure, whatever - it loses access even though everything goes through UD portal. I eventually got UD Mobile going with 2 Eisy's (1 was ending with a (1) I think). I got my favorites listed but there was a big red triangle at the top of UD Mobile anyway. I just did a synchronize on one device and trashed the other. Thank god, I had a lot of lights on outside that I didn't want the neighbors bitching about and I really didn't want to be out in the 20 degree weather fiddling around on the snow trying to turn off every damn outlet outside at 2am. Even after a reboot, shouldn't the Eisy automatically show-up in UD Portal? UD-Portal was stating that it had not seen my device online since XX:XX:XX (a couple of hours before I was trying to resolve this). Also, what does "holding" the Eisy button do, which turns the power button red - I assume that turns it off??? Okay, but if you push it again it immediately goes blue but I guess it's not really "online" for a couple of minutes or so. There is a bit of documentation that said to not try to connect to it until after 5 minutes from starting and if you try to connect before the 5 minutes then bad things will happen (I'm paraphrasing here). It would be nice if maybe the indicator light went red (off) to yellow (starting) to blue (ready) - or something like that so you know exactly when things are online and ready to go. I find it odd that you could screw things up by "trying to connect to the Eisy too early" - at least that's how I read it. I would think/hope that the connection would just fail if the device was not ready and there would be no long term effects to the device, IoX or UD Mobile configs. Well, hopefully "at least" another couple of years before another "connection" problem.

Here you go: On MacOS Sequoia, once you try to start start.jnlp it will fail. Open "System Settings" go to "Privacy & Security" and towards the bottom will be something about how start.jnlp tried to start do you want to allow it? Click Yes/Always. I used to really love Macs. One time I had a decent high power Macbook Pro that I did not have to reboot for over a year! And this was while doing development work on it. No joke. But these were the days when Steve Jobs really cared about quality. Now every MacOS update is a bunch of absolutely useless sh*t that the hippsters can go on social media and say "LOOK AT ME!, Ain't I cool?" No, you're not. I'd take performance and stability ANY day over these horsesh*t UI "features" - Okay, enough about Macs. I realize that the general audience here is Pro Windows. I used to be that way but then in 2011 I changed....maybe it's time to change back!

Answered one of my questions: For MacOS Sequoia open a terminal window, cd to the directory where start.jnlp is and enter: javaws ./start.jnlp That works but I sill cannot find my eisy. My cable modem shows the mac address at 192.168.1.151 and I can ping that address. I cannot ssh to it - connection refused.

I should add that I can ping it at 192.168.1.151

I don't even see an option to get around this. Most apps you can say "Open with" or something - nothing here. I did the uninstall of Java, then the re-install as shown on the Eisy: User Guide page.j I have never rebooted this thing...ever. How do I do that? Push button once, twice, hold? Nothing seems to work. UD Mobile cannot connect so that's when I tried the start.jnlp which will not run.

One way to fix this problem, if anyone else every experiences it, is to just disable "Check for Updates Automatically" in the Java Control Panel (nothing changed in IoX launcher). Not ideal, you just have to periodically remember to check for updates. But then you can at least start/stop IoX launcher as much as you want.

When you say updated, I assume you meant the Java version (as opposed to the device)? Yeah, macOS just isn't what it used to be unfortunately. In the past, I could go over 6 months of heavy development on a macbook pro and never need a reboot. I have to believe the recent issues are due to the loss of Steve Jobs. I feel it's been downhill since his death. Think about it, he was all about the quality and these pathetic "features" that get added to every new version, I do not think that he would have found useful..I certainly don't.

Yes, I can see that in general that is of macOS here with respect to UD, especially with the bulk of users using Windows. I honestly do not think there is an issue of running Java on macOS at all. But something is and has been (as described by many) with the combination of all 3: Java, macOS, IoX Launcher.

So, back at the beginning of this thread I showed the Java exception being thrown that can be seen if you have the console enabled when you start IoX Launcher. I just found that that exception is only thrown when you start IoX Launcher, click on your device, the big screen opens with the little dialog window prompting for userid and password. If you now hit Cancel here, this is what throws the Java exception. As I stated, so many Java exceptions get thrown when they really should not (in almost all Java apps). One other thing that I discovered is that the Java uninstall is very thorough on a Mac, removes tons of stuff in many directories. I found that it leaves ONE thing behind: /Library/Preferences/com.oracle.java.Helper-Tool.plist Suspicious I know. So I did another Java 8 uninstall and then went and manually deleted this file (need to use sudo). After re-installing Java 8 this file showed up, as expected, but now the date of this file is today. This is a binary file but from what I can see it looks like it contains the data and time of when to auto-run the Java Updater.

Narrowing this down further...I just did a full uninstall, then a reinstall (using the latest Oracle download jre-8u411-macosx-x64.dmg) In the "System Settings" --> "General" --> "Login Items", the Java installer adds this: You get a notice during the install that this setting has been added to the "Login Items". But if I deselect this item, start IoX launcher, stop IoX launcher, the "Java Updater" is still running. So it seems that disabling this option does not do anything ASSUMING that this option is used for either running or not running the Java Updater.

HA! I figured this out! But...I do not understand why.......so the one shot run is still true, BUT looking at the Activity Monitor and sorting by process name...I found that "Java Updater" was running and I tried quitting that process (regular quit not a force quit) THEN I can relaunch IoX Launcher desktop shortcut. I have to keep quitting the Java Updater in order to run the IoX Launcher shortcut again. It used to be, weeks ago, that when I would launch the IoX Launcher shortcut, I would get an error that "the Java Updater failed" - I wish I captured that screen. That error was in a Java style window as opposed to something that looks like an IoX window. So, I used to get that error, and I have not since a few days ago when I cleared cache and downloaded another start.jnlp BUT BEFORE this last Java update. I was able to launch multiple times the IoX Launcher without having to do anything (reboot or kill any process). I know this because I had a lot of starting and stopping when I got the new EISY and I was trying to get this migrated and working 100%, and also because this machine has not been rebooted in weeks. But this process is still running. But the Java Control Panel says the last time the update was run was at 12:56pm EST today. However, it is now 2:48pm EST and that process is still running. I guess an uninstall of java - which I believe you can do by launching the installer, it gives you the option to "uninstall" - is now in order.

I have seen this before but I found that if you double click it a second time, you get the window which gives you the option to "Open".

Alright...so check this out....I just rebooted this Mac (could not reboot last night due to long test needing to complete) and after reboot finishes I CAN double click the IoX desktop shortcut and it launches the console. BUT, if I close IoX console, I cannot restart it from the IoX desktop shortcut...UNLESS...I reboot again. Now that is weird. So it's like a one-shot deal between reboots.

INTERESTING...I added the URL: isy.universal-devices.com and now the JVM console for start.jnlp shows more details and NO exception from .../5.8.0/chart.jar The full contents from starting start.jnlp: Java Web Start 11.411.2.09 Using JRE version 1.8.0_411-b09 Java HotSpot(TM) 64-Bit Server VM JRE expiration date: 8/16/24 12:00 AM console.user.home = /Users/ray ---------------------------------------------------- 😄 clear console window f: finalize objects on finalization queue g: garbage collect h: display this help message m: print memory usage o: trigger logging p: reload proxy configuration q: hide console r: reload policy configuration s: dump system and deployment properties t: dump thread list v: dump thread stack 0-5: set trace level to <n> ---------------------------------------------------- https://isy.universal-devices.com/iox/5.8.0/iox.jar https://isy.universal-devices.com/iox/5.8.0/ce.jar https://isy.universal-devices.com/iox/5.8.0/bc.jar https://isy.universal-devices.com/iox/5.8.0/chart.jar Z-Wave event: control=[_25] action=[1.3] -- Extended Info -- <eventInfo> <zwave CBP="false" CONNECTED="false" RELAXDELAY="0" INTERVIEWTIMEOUT="0" SECUREINC="2" HOMEID="0" NODEID="0" RELAXDELAYDEFAULT="15"/> </eventInfo> -- Z-Wave event: control=[_25] action=[7.1] -- Extended Info -- <eventInfo> <options> <files ZMATTER="false"/> <dongle ZMATTER="false" ZWAVEOTHER="false"/> </options> </eventInfo> -- Z-Wave Backup Options: - zmatterFile= false - 500SeriesFile=false - zmatter connected=false - other connected=false AND I JUST REMEMBERED, I did add the add the POLYGLOT V3 yesterday! (due to finally getting an eisy)

Hi, Yes, I definitely checked all 3 boxes on the clear cache (multiple attempts). I could verify that the IoX Launcher app did get deleted, etc. I can get the icon to add back to the desktop by double clicking the start.jnlp, but the newly added IoX Launcher shortcut does nothing. If I view the "Get details" of the shortcut, it looks good. I do think the java update has something to do with my issue since all was working well (with my old ISY994i for over 2 years and even with my two week old eisy) prior to yesterday's Java update. I did download and and install a new Java install package from Oracle at the standard Java 8 download location. I did clear all 3 cache options before and after the install. I tried to download a new start.jnlp - just in case. I'm positive that I am using the new start.jnlp and not an old copy laying around. I do not run any anti-virus or firewall applications on my Macbook. But I do have a lot of "built-in packet rules" on my Synology (access point), but for any packet that is dropped, I do get an email alert about it. There are very few rules that actually drop packets despite the alert descriptions sounding quite serious, I guess there are many false positives in the packet monitoring space. I thought exactly what the second link you posted shows was the problem (without even seeing those details). I added these two entries yesterday (but they were never needed prior to this update): I can try to add "https://isy.universal-devices.com" without the suffix as well to this list. So, I only have Mac's in this house, and using the standard Oracle Java 1.8 (Version eight) has never been a problem. I have fiddled with other Java versions in the past only because I needed certain things for work related software development. But right now, in the Java Control Panel, only the 1.8_411 shows (no other versions) I don't know if the Java exception thrown, that I see in the Java console, is serious or not. I find that in the "java world" many "exceptions" are oddly not important, seems odd to me. My full security pane looks normal: My Advanced panel: I did add the "Show console" option last night to help debug. More of the advanced settings... and lastly... I added the "Use TLS 1.1" last night just to test if that would have any effect. The JAVA_HOME env setting is correct (for a Mac): echo $JAVA_HOME /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home In the past, I also used to have two other shortcuts from earlier ISY994i days: "admin" and "dashboard" and neither of them worked as well. They got deleted but I do still have the jnlp files for them. I never really used two app before so not a big deal but maybe that's another clue. Unfortunately, this sounds like an incompatibility between the Java update and IoX launcher on a Mac. Way back in the day...(around 1998??) the Java idea was your code would run on ANY JVM despite the OS and machine type but that always seemed like a high bar to reach. Just a wild guess, but if I had to bet on something I would guess there is some path in the install code that maybe does not work correctly on the Mac and this last Java update was bothered by that. Just a guess though since the start.jnlp does run the IoX console, it just doesn't install it. Thank you for your help.

I had all of the java cache files cleared, installed a new start.jnlp - everything working. I then got an update for Java 8 update 411 today: java -version java version "1.8.0_411" Java(TM) SE Runtime Environment (build 1.8.0_411-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.411-b09, mixed mode) I have the latest start.jnlp from: https://isy.universal-devices.com/start.jnlp Double clicking start.jnlp puts a shortcut to IoX Launcher on the desktop (where I want it) but if I double click the shortcut - nothing happens. I have to keep using start.jnlp anytime I want IoX Launcher to work. I started over again with a new install of Java 8.411 from here: https://www.java.com/en/download/ Here is the start.jnlp spec: <jnlp spec="1.0+" codebase="https://isy.universal-devices.com/launcher/" version="6.3" href="https://isy.universal-devices.com/launcher/start.jnlp"> <information> <title>IoX Launcher</title> <vendor>Universal Devices</vendor> <homepage href="https://www.universal-devices.com"/> <description>This utility finds ISY Services and launches the correct version of the UI/Admin Console/Dashboard</description> <description kind="short">IoX Launcher</description> <icon href="https://isy.universal-devices.com/launcher/udlogo.png" kind="splash"/> <icon href="https://isy.universal-devices.com/launcher/udlogo.png" kind="shortcut"/> <shortcut online="true" install="false"> <desktop/> <menu submenu="IoX Launcher"/> </shortcut> <offline-allowed/> </information> <security> <all-permissions/> </security> <update check="background" policy="always"/> <resources> <jar href="https://isy.universal-devices.com/launcher/isyfinder-3.5.jar" download="eager" main="false"/> <java version="1.8+"/> </resources> <application-desc main-class="com.universaldevices.isyfinder.ISYFinder"/> </jnlp> Looks okay, I think. If I enable the java console and double click start.jnlp I do get an exception: https://isy.universal-devices.com/iox/5.8.0/iox.jar https://isy.universal-devices.com/iox/5.8.0/ce.jar https://isy.universal-devices.com/iox/5.8.0/bc.jar https://isy.universal-devices.com/iox/5.8.0/chart.jar java.lang.NullPointerException at com.universaldevices.ui.UDMenuSystem.setActivated(Unknown Source) at com.universaldevices.ui.UPnPClientApplet.authenticate(Unknown Source) at com.universaldevices.ui.UPnPClientApplet.onDeviceOnLine(Unknown Source) at com.universaldevices.upnp.UDControlPoint.onLine(Unknown Source) at com.universaldevices.upnp.UDControlPoint.updateDeviceInfo(Unknown Source) at com.universaldevices.upnp.UDControlPoint.addDevices(Unknown Source) at com.universaldevices.ui.UPnPClientApplet.start(Unknown Source) at com.universaldevices.ui.UDIDefaultLauncher$2.run(Unknown Source)

@hart2hart I saw your question before you deleted it and yes you are right, that would work perfectly as an alternative to being locked into the .150 IP address. But, my cable company does not let anyone have access to their router with the exception of one and only one setting: where do the DHCP addresses start. So I can't do what you suggested. I am considering getting another Synology RT6600ax and put that as the "head router" within my home network. I have all RT6600ax's throughout the house but working as a full wifi 6 tri-channel "access point" mesh. If I buy another unit, for $300, and this time install it as a "router" and not an "access point" then I can do what you propose. It will add one more hop to all of my network traffic but maybe it's not a bad idea just to have control (not just for the EISY device). I have heard that my cable company will give you a one-time shot to convert your cable modem (router) to an access-point device (basically a fiber "cable-modem") but then there's no return and they offer no assistance if it "doesn't work for you." Sounds like a setup to me and having no network for a week is not going to fly with my employer.

I can appreciate the fact of why UD fixes the IP address with DHCP for the reasons stated, I just wish they chose a higher up IP address. My current router only lets me have one "starting point" for dhcp addresses, so I have to now set the start address to 192.168.1.150. I will never have 254 - 150 + 1 = 105 devices that will use DHCP. I'm sure I could move say 5 devices from static to DHCP but that still leaves a block of 100 internal (internal to the house) IP addressed wasted. I understand that in theory it's possible to setup DHCP to mac address mapping which basically gives you the same IP on every dhcp lease renewal. My cable company locks down what you can do to their routers for the exact same reason that UD does, people screwing up their home network and then calling support. Oh well.

I have not seen one that doesn't. The new fiber unit from my cable company, Synology routers, Apple routers...just to name a few.

When you have an IP address collision it's usually made quite fairly clear to the user. Most routers have a range for static vs dhcp and if you have table kept in a note somewhere, it shouldn't be a problem. The default gateway, dns, network mask is exactly the same for every single entry...unless you've got some fancy "subnets in your house". I use static for almost everything, in part because everything is wired except iphones and tablets.

One other thing that's annoying me is that on "Configuration"-->"Network Settings" Automatic DHCP is checked and greyed out, no way to turn it off. I always used a static IP and would prefer to keep doing so but it looks like that is no longer possible. Maybe the "scanning at start" is on this same page "Query at Restart" - I unchecked that.

Well holy &^$& ! Downloading another start.jnlp (despite it being the exact same version as before) launching that, creating the desktop shortcuts, etc. No more "Not Found Error" !