oh2bnMaine

I've tried using InPrivate and removing all extensions. I still see this message. Are there other suggestions I should be trying?

Yes. 8-361. Sorry for the delay, I have been away from my computer for a couple of days. I will update to 5.3.4 regardless. Thanks for reminding me!

I'm using this... I'm using Windows 11. Java 1.08_361-b09. I've been using the same 5.3.3 launcher for a long time. I just downloaded the newest jnlp. We'll see how that does.

I realized after posting that I was rebooting the ISY but not powering it off. I tried the power recycle and that seemed to help. I still got the ProxyDevice IO Error message for a bit longer, but that has stopped it seems. Time to take a new backup. I was realizing my backup didn't have the last 10~ 2477D's that I installed! Now I'm up to 20~ 2477D's not in my backup.

I see this may have happened to others in the past? I'm in a situation where I mis-clicked on Add ZWave on my phone app. I got out of that and went into Linking an Insteon device. The process seemed to work, but the device was never added. The Linking process does what the original poster (link provided) describes. It keeps re-starting the Linking dialog box after reaching 100%. Here's what I currently see. I can get rid of the ProxyDevice message, but it will come back eventually. I've opened the Event Viewer and don't see much information there. As of this writing, the last log entry was at 2:14pm. It is currently 2:31pm. I've even tried hitting the reboot button in Config, but the Linking dialog showed up right after I logged in again. When I open the app on my phone, it gives me the "linking" message (1, press & hold SET button; 2, repeat; 3, finish; 4, UD Mobile sync). What should I be trying to resolve this?

Interesting idea. As someone below mentions, response time might suffer. I still hold out hope that there's something that will "fix" the reliability of the Insteon open/close sensors. I have long-term plans to build my own ELK security system, but I'm not ready to start that project yet. I have plenty of other projects in front of that one.

I have been having this issue for a while now (at least going back to 16A). I'm about ready to give up on the open/close sensors. I installed some new ones and they work for a week or two. Then they stop working reliably or at all. I haven't tried to get them fixed, so I'm curious what people say is the solution!

Thanks for the clarification.

New Issue: I just experienced another odd behavior (5.0.16 RC). I use conditionals on program folders to control some activities. I just realized that a rather complex conditional was showing as TRUE, which made no sense (unless I programmed it wrong). So, I copied the folder using export/import from clipboard functionality. The copy of the folder's icon shows as RED, which is correct. The original showed as GREEN. The logic was untouched after the export/import was performed. I tried to reproduce this issue with a different folder and had no issue. I modified the conditional logic and the folder flipped from GREEN to RED as expected. Prior Issue: Going back to the REST issue I posted the other day, I only see that error on one of my two ISY's. The one in Maine does not exhibit the following. Only the one in Florida does. I'm re-sharing the image for reference purposes.

I am been digging into using REST commands. I just tried to use the /rest/status command and got this error message. Any thoughts?

Has anybody else seen this quirk? I don't want to call it a bug because that makes it sound more serious than it is. I did not notice this quirk until I modified the second program. I was adding a step that would keep track of a variable value from before a reboot by utilizing the INIT TO placeholder. The first time, I flipped from Number to Variable in my variable assignment statement and it worked as expected. The next time -- the second program -- it skipped Variable and went straight to System. I had to cycle around back to Number again in order for it to go to Variable as the next option. You can see this in the video. This seems inconsistent to me. Am I missing something?

I installed the replacement PLM this morning. It took me a couple of attempts at getting it online and working. I never seem to get through the "restore PLM" instructions correct the first time. I had to do a factory reset on the PLM, then it warned me about being in safe mode, but when I rebooted the ISY things started working again. Unfortunately, some switches are still not online (they work fine, but don't register in the ISY interface). I'll start working on those over the next week to see if I can get them to work. Some of the switches are brand new and still don't register. Anyway, now I have 5.0.16-RC1 working on two ISYs with no upgrade-related issues.