Valveman

OK. Thank you. I will keep that in mind as I figure out what to do.

Thank you for the comments DennisC. I have been wondering if the electronics might be failing, but hoped that was not the case. I have been considering the upgrade to eisy. I read on the web site somewhere that the eisy still requires java web start for the administrative console. This is a real problem for Linux users, because javaws is no longer included in most Linux distributions due to licensing issues. I was hoping to get away from the java issues by upgrading, but that is apparently not possible. Thanks again for your comments, DennisC. I really like the ISY because of the ease of programming, but javaws is a never ending problem for me. Looks like I have a decision to make.

I performed a factory reset of the ISY. Then I added 4 devices (wall switches) to the Zwave network. I was not getting any "cannot communicate with device xx" errors, and I was able to turn the lights on and off manually using the Administrative Console. I recreated programs for the lights, saved everything and shut down the computer. The programs subsequently ran correctly. Problem solved, I thought. However, when I restarted the computer and opened the Administrative Console, I got the "cannot communicate with device" errors again, but I could turn the lights on and off. Same problem as before. I cleared the java cache and restarted the computer, but running the Administrative Console again produced the "cannot communicate..." errors. I have deleted all of the ud*.state files, but that did not help either. Your comments will be appreciated.

Thank you for the response, Geddy. Since running IoX, the Firmware Version and UI match (see attached screenshot). I tried running a Zwave Heal operation, but as before the operations mostly fail. No Windows computers here. Oddly, this system worked perfectly when first installed (4 or 5 years ago). Over the years, performance has slowly degraded. I have resisted doing a factory reset of the ISY and starting over, but I;m afraid that is my only option.

I uninstalled the JAVA in the Linux OS that I use, then installed the JAVA in the link from kzboray and corrected the JAVA_HOME environment variable. When I run the IoX launcher, the software now finds the ISY, which it would not do previously. However, I still get error messages from the ISY saying that the ISY cannot communicate with most of the devices on the system, even though the controller turns most of them on and off programmatically. Your comments will be appreciated.

Thank you for the responses Mr. Bill and kzboray. I will attempt to install the Java Version 8. Thanks again.

Mr. Bill I don't know anything about Java. According to the information on java.com, the current version is Java 20. Java 8 is no longer available to me, as far as I know.

Mr. Bill -- When I enter: java --version I get: java 15.0.2 2021-01-19 Java(TM) SE Runtime Environment (build 15.0.2+7-27) Java HotSpot(TM) 64-Bit Server VM (build 15.0.2+7-27, mixed mode, sharing)

I downloaded and ran start.jnlp. The IoX finder launched and I had to enter the URL for my ISY. I entered the URL and the ISY was found. When I then selected the ISY, I got 2 choices (Admin Console (LAN) and Admin Console (Cloud)). I selected the first as the ISY is connected to the router via Ethernet but is not on the internet. Then, nothing happened. Following this, the ISY would not operate any of my devices programmatically. I switched back and ran the original admin.jnlp. Nothing there was changed. I still have to enter the URL into the ISY finder, and I can operate all of the devices manually in the Administrative Console, but I get error messages saying that the ISY cannot communicate with any of them. I also did as DennisC suggested, and turned on the event viewer, set to Level 3, then lowered one of my shades (node 19). The results in the event viewer are attached. According to the event viewer, the operation failed, but the shade in actuality was lowered. Your comments will be appreciated. Errors.txt

Thank you for the responses. I am running Linux (kernel 6.2.14). My ISY setup is all Zwave, all lighting with the exception of 2 shade controllers. Not sure about the model number of the Zwave dongle. When I got the ISY, the dongle was already installed, so never looked at it to determine the model number. When I first got the ISY, everything worked very well. When I first got the ISY, javaws was included as part of the Linux distribution. Since then, javaws is no longer open source, so is no longer included in the distribution. I use icedtea-web instead because this is available open source. Best that I can tell, icedtea-web is set up properly. Not sure if this could be part of the problem. I will follow the suggestions above to see if they help. Thank you for the input.

I have the subject controller (firmware 5.0.16C and UI 5.0.16) that is having issues: 1. When I first start the administrative console, the ISY can never be found. I enter the URL in the pop-up window, and then the ISY can be found until I restart the computer. Then, the ISY cannot be found again. The ISY finder writes a file, which I save to the starting folder specified in the desktop shortcut for the administrative console. There are several of these files in that folder, but that doesn't seem to make any difference. 2. When the administrative console starts, I get error messages that the ISY cannot communicate with most or all of the devices on the system. However, I can turn the devices ON/OFF using the administrative console. 3. If I try to "Heal the Zwave network", most of the operations fail. 4. The programs work most, but not all, of the time. Frequently, lights will not turn ON, but if I turn them ON manually, the ISY will turn them OFF later in the evening at the prescribed time. I have tried clearing the java cache, but that does not appear to help. I would appreciate any suggestions to make this system work better. I have been considering an upgrade, but am reluctant because this system is working so poorly.

lilyoyo1 - Clearing the Java Cache largely resolved the issue. Now when I run the network heal process, all of the devices are successful except the 2 shade controllers (class C motor controllers). ISY will raise and lower the shades without problem, and I do not get the "can't communicate" messages, but the network heal process fails on those 2 devices.

Thank you for all of the responses. On the back of the ISY, to the right of "Port A", is what I think is a light that is not lit.

Thank you for the response. The UI: INSTEON_UD994_OADR v.5.0.16 (2019-10-08-09:13:00 I have 13 devices, 8 are wall switches, 3 are appliance modules and 2 are shade controllers. All are having the same problem. The heal process generates "can't communicate" messages, but the devices are still turned on and off by ISY.

Thank you for the response. In the "About" Window, the Firmware line says: INSTEON_UD994_OADR v.5.0.16C (2020-01-25-12:36:41)