gschoffstall

Thank you all for sharing. I am sure I have dug myself in pretty deep. Yes, I have uninstalled all versions of Java and reinstalled the latest for my Windows 10 laptop. I have, just in case, cleared the cache with all 3 boxes checked. I have deleted all instances of start.jnlp before downloading the directed start.jnlp app. I still come up with a "Not Found" after trying the official start.jnlp app. I guess I can forage to find the ISY's IP address, but I don't know it off hand. Maybe I should try my real old laptop with Windows 7 OS, but really??

Here's an interesting twist: I tried the web interface with my wifi connected laptop. (http://isy/WEB/udajax.htm#/nodes/devices/). It found the ISY and I can manually control Insteon devices. BTW, in the interim before I tried the web interface I had reconnected the original PLM and factory reset the ISY99Ir. I still cannot connect through the UD launcher or start.jnlp app.

I changed power supplies for the ISY99ir. When following the startup procedure, powering the PLM first, then the ISY, it appears to be working. The Power led lights, then the tx and rx lights come on solid and the Memory led starts flashing. Next the tx and rx begin acting like they are communicating. There are random flashes for about 20 seconds, then only the Power led remains on. At no time does the Error led light. I can get some reaction on the controlled lights for a few seconds with a RemoteLinc that I have configured, then it appears to lock up and does not respond to any RemoteLinc commands. The UD launcher and start.jlnp still report "Not Found". It acts the same with bot the original PLM and the new PLM. Stick a fork in it? Dig a hole?

Also, the IoX launcher reports "Not Found". I have already updated Jave and cleared cookies, as that has been a problem in the past.

The system is a small Insteon setup with only light and appliance modules plus a couple motion detectors. It has worked flawlessly for years, but just stopped working with modules in the state they were when it quit. The ISY has no blinking lights and just the power led is on solid. Cycling power on the PLM and ISY changed nothing. I tried a replacement PLM (new) with no change. The finder finds no device. I's been so long since I had to troubleshoot, I'm not sure where to start if it's not just a hardware ISY failure. Can the ISY be communicated with over it's "Monitor" port to see if it is even partially functional? Assuming I have a cable, how would that work? Thanks for any help you can offer.

Thanks for confirming, Tom.

I already have a program that turns lights on and off with the RemoteLinc buttons 1 - 6. My issue is that the ISY doesn't seem to have a way to recognize other than the 6 (12) buttons. The idea was simple, use the Bright / Dim buttons to execute that command for X-10 devices. It looks like that isn't possible.

Thanks guys. So the answer then is no, those buttons only work on Insteon responders that were already directly accessed by that RemoteLinc.

I am using an ISY 994 ir pro running on v5.3.4 with mostly Insteon and some X-10. I have a couple of Insteon RemoteLincs . They link and respond to On / OFF commands in my programs. My issue is that I cannot figure out if the Bright / Dim/ All On /All OFF can be programmed. I don't see options in the program screen for using them. What am I missing?

You're my new hero! Thanks for your response. I figured there was still something amiss in the radio portion of the PLM, and it was not going to recover. Nothing else worked. Thanks again. Now to order caps for the other PLM that went South......

I recently had an episode with my PLM. It quit, no surprise. I replaced most of the caps on the main board except the 100 microfarad, of which I had no stock. I had to re-link all my devices and mostly it was just a time consuming nuisance. All the Insteon plug-in modules came back on line. The RF only battery powered devices decided not to participate. Changed batteries, tried re-linking x amount of times, tied getting closer to the PLM. No joy. My devices are older ones, a RemoteLinc 2440 and 2413 motion sensor for two of them. Everything is out of warranty, and the act of messing with the PLM would have derailed that anyway. Can't buy a new one, as they will only warranty replace. Any ideas? .