GaryK4

OK, just ran a long ethernet cable to the next room and connected the PLM. I walked around with the keypad and tried various rooms and outlets including the office. It appears that they all work. Hopefully, I am all set on what I need to do. Thanks for the help!

Lots of stuff in the office. Computer, (2) Proxmox servers, Printer, 3D printer, Router, MoCa coax to ethernet adaptors. I will experiment with other locations. There is no wired ethernet in the house. Starting to use MoCa to help. Placement or router, AP, ISY is up in the air at the moment. The wall seem to have metal studs. That may be affecting poor WiFi coverage. Trying to get all my options to determine what to try next.

Yes, I tried many locations. It appears to work only in that room. I'm not sure, but I don't think keypads or the IO Link is dual band. Is there something that I could add to get the dual band. I have been going with WiFi on all the new stuff.

I ran many devices in my old house. Now, I live in the villages, FL. So, I have not done this in a while. I put the PLM in my office. I can link devices in that room like a keypad or I/O link. When I try them in the hallway just outside of my office, will not work. ISY can not communicate with them. This is not even where I want to place them. I tried rebooting, re-linking, query, restore device. I'm not sure what I am missing.

OK, I got that to work. Had to tweak the environment variables a little. Thank, I am good to go.

That is Java 8! Java is up to version 18. I do some software development and some features require the later versions. I don't know if I can have the old and new on the same computer.

From what i understand newer versions of java does not include javaws.exe. IcedTeaWeb added it back. What am I missing.

Some time ago, the console would not load. I had to install IcedTea.web on windows 11. That kind of worked. It went directly into the console without using the Finder. The finder did not work with IcedTea. Now when I try to load the console an error message appears (XML Parse Error http://isy:80/desc. I did upgrade my java from 8 to OpenLogic-OpenJDK Build jdk17u). I don't go to the console often, but that may be the problem. After upgrading Java, I did not do anything with IcedTea. I tried manually loading the IoX finder and selecting the pull down menu Admin Console (LAN), but that did nothing (wheel spun, then closed). There must be a better way to run the console. Need third part software like IcedTea, every java update seems to break something. I don't make many changes, so it is always a pain to figure out how to get it running again. Side notes: I use Home assistant with ISY and many other devices and love it. I have Debian Linux running on a VM within Proxmox. Is it better to run ISY from there? It has OpenJDK 17.0.9 installed. IcedTea web is NOT installed and I don't know hot to install it yet or if it will work with OpenJDK and ISY. When I bring up the web app on Linux and select Admin Console, Java 2+ Required is diplayed. Will the new EISY have the same console startup issues?

Interesting, I found a program called IcedTea-Web 1.8.8. It did not work with start.jnpl. Did not find Iox. However, with admin.jnpl, it worked and brought me to the login. So now I can use Win11 or my VM.

You must have read my mind. I have a Win10 VM running on Proxmox where I installed jre 8 and that works.

The new versions do not have a control panel, so you can't clear the cache. Other programs require newer versions of Java. So, my isy console is basically dead? ☹️

I upgraded from Java 8 to OpenJava 17. There is no javaws.exe file in this version. How do I get the console to startup? I don't want to have the old version installed.

All name have a red x next to them. Google says that it can not reach universal devices. I tried sending spoken to Google and got "Error sending your spokens. Google home API returned: INTERNAL Internal error encountered." Rebooted my computer and ISY. Made sure java was up to date. Troubleshooting reports "Everything appears to be configured correctly!" Now what? OK, I got it working. I had to go into the Google Home App, then unlink Universal devices. Fortunately, there was an option to reconnect. That worked and I did not have to actually unlink the devices.

I don't think my response was complete. I converted from V4 to V5 in late Oct 2020 timeframe. Was running V5 until this issue occurred. I used a new 32GB sd card and installed insteon_5_3_0.zip. I created a V5 backup file when I did the original upgrade (Oct). The restore was with the V5 backup. So, I did not use a v4 backup to get up and running again. Sorry for the confusion. Everything appears to be working fine, except a flaky Motion sensor which I don't think is related.

No, I did not even think of that! When I updated from V4 to V5, I followed the forum instructions. I have the file insteon_5_3_0.zip in my download folder. Then I did a manual upgrade using that file. Afterwards, I restored the last backup that I did. There were a couple of minor changes that was not in the backup which I fixed. Is that process OK? Next time, I will use the portal. I need to put that in my notes. Regards, Gary