snazareth

@MrBill, I was hoping for a solution that would work for Linux, rather than a MAC or WINDOWS solution. With linux, I can install java8, but then that doesn't have java web start (javaws). Trying to install javaws (IcedTea-netx) automatically upgrades java to java11. Javaws is what enables you to run the .jnlp file to launch the console. --Sean

Hello, My ISY994 with Insteon installation has been stable for a long time. However, recently, I wanted to get back into the "console" application. However, all my computers with Java on them have been retired. For security reasons, I don't intend to install java on my "existing" mac computers, I attempted to create a Debian Virtual Machine in parallels to run the console. This way, I can take the machine (and java) offline by just not running the VM. I successfully setup the VM (just using the default Ubuntu image from parallels), did an "sudo apt install icedtea-netx" to install the javaws support. I then downloaded the IoX Launcher.jnlp from ISY. I've verified that I can run "java -version", and I get a response showing that "openjdk-11" is installed. However, I seem to have problems actually launching the console from the .jnlp file. The launcher does run and show the ISY device, but I cannot actually bring up the console. The ISY finder finds the ISY, but I cannot "launch" the console. I get a security pop-up warning to approve, but I'm unable to click the "OK" button. After the attempt, no other buttons in the ISY finder are responsive. Can someone share any info on how to solve this issue? Thanks, Sean

Rabbit: I've followed your instructions and have my first sensor basically working. I've got a few questions though. Eventually, I'll have something like 14 leak sensors. At the very least, each sensor has a line like "$variableHB init to $variableHB" to preserve the state variable across reboots. With 14 sensors doing a heartbeat at different times of the day, this is a number of accesses to non-volatile memory each day. Is there a reliability issue with this long term? Also, you have a comment that "the Leak Detection" state for each sensor is only reported once at re-boot, and then only after a heartbeat. Is there a reason that you do not check if a sensor Leak detector has remembered a leak and re-trigger the Leak Detected program for that sensor if it was last detected in Leak State? Thanks, Sean