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?

Holding the button for ~10 seconds is enough to get a factory reset. I found my other 2477SA1(NO). Both are now listed in admin console and have been factory reset. Device 1 [14.58.4C] beeps on command. I can switch it on manually, but the admin console doesn't seem to have that level of control. (There's a 'loud' click when the device switches on.) Device 2 [14.5C.58], while on the list, is not available. I'm not sure why that's the case, but it might not matter. That device is the one that's not sending a load through the purple wires -- the switch doesn't appear to be working. (There's no click when the device is switched on.) Here's the Event Log (Level 3) for both devices when I attempt to perform a Query on each. Sat 04/02/2022 19:39:07 : [INST-TX-I1 ] 02 62 14 5C 58 0F 19 00 Sat 04/02/2022 19:39:07 : [INST-ACK ] 02 62 14.5C.58 0F 19 00 06 LTSREQ (LIGHT) Sat 04/02/2022 19:39:16 : [INST-TX-I1 ] 02 62 14 5C 58 0F 19 00 Sat 04/02/2022 19:39:16 : [INST-ACK ] 02 62 14.5C.58 0F 19 00 06 LTSREQ (LIGHT) Sat 04/02/2022 19:39:25 : [INST-TX-I1 ] 02 62 14 5C 58 0F 19 00 Sat 04/02/2022 19:39:25 : [INST-ACK ] 02 62 14.5C.58 0F 19 00 06 LTSREQ (LIGHT) Sat 04/02/2022 19:39:42 : [INST-TX-I1 ] 02 62 14 58 4C 0F 19 00 Sat 04/02/2022 19:39:42 : [INST-ACK ] 02 62 14.58.4C 0F 19 00 06 LTSREQ (LIGHT) Sat 04/02/2022 19:39:42 : [INST-SRX ] 02 50 14.58.4C 44.D1.A5 2F 00 2E (2E) Sat 04/02/2022 19:39:42 : [Std-Direct Ack] 14.58.4C-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Sat 04/02/2022 19:39:42 : [D2D EVENT ] Event [14 58 4C 1] [ST] [46] uom=100 prec=0 Sat 04/02/2022 19:39:42 : [ 14 58 4C 1] ST 46 (uom=100 prec=0)

Out of curiosity, I tried both stickers. The first was the correct one. Regarding finding the device on the list, it sure would be nice if that list was sorted alphabetically! Anyway, I have it connected now, but things still aren't working 100%. I cannot get the ON/OFF/DON/DOFF to change the switch state. When I press Query, it shows me a %age. I've seen 15%, 13% and 11%. When I press ON/DON, the %age is replaced with ON. OFF/DOFF replaces it with OFF, as you would expect. Every time I press Query, though, I get a %age. If I press the ON/OFF button on the 2477SA1, I do NOT see a change in switch state in the admin console. With a voltmeter, I have confirmed that when ON, it is producing ~240 volts. Still, even when I have physically switched it on using the button, Query registers a %age (I have yet to see higher than 15%). At this point, I assumed the device has zero connected to the ISY994, but that is wrong... By pressing the BEEP button, I can produce a beep at the device. I can change the beep duration using admin console. So, I know the admin console can touch the device. I tried to do a factory reset -- power circuit breaker off, hold ON/OFF button, power circuit breaker on, release button after 3 seconds. It should produce a double beep at this point, but I never get this feedback that the reset has been successful. I've tried holding the button for over 10 seconds as well. No difference noted. Any more thoughts?

Thanks for your attention. I'll do another test tomorrow. Funny how it looks to have two addresses inside? I did only use auto-discover. I had trouble finding the 2477SA1 on the list and gave up.

I guess this shows my age (rather, the age of my Insteon devices). I have a 2477SA1 (240v Insteon ON/OFF switch) that I want to install on my pool pump. I had this specific 2477SA1 hooked up to a hot water tank in a prior house that we no longer own. That house was using an ISY994 (non-pro). This house is using a ISY994 Pro (w/Zwave). I hooked up the 2477SA1 on a 30A breaker as close to the ISY/PLM as I could get. The set up process gave me a message telling me the 2477SA1 is incompatible with the ISY994. Is this truly the case? If not, is there something I should be doing to get around this? Thanks, Bill

I'm not finding Insteon switches available at smarthome.com or amazon. For that reason alone, I would be taking all the switches with me the next time I sell a house. I left them the last time.

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!

I have the catchup field set to 10 minutes. The coop door opens 10 minutes before sunrise and it was well past 11am when this occurred. For these programs, I only use sunrise and a "bad error" variable to prevent the program from running. I actually have open/close sensors in place but they aren't reliable (yet). I'm finding the sensor that marks when the door is all the way down works great. I'm not seeing status for the sensor marking when the door is open all the way. There's an extra sensor that marks when the door has gone up too far as well, which flips the "bad error" variable to 911. Since I haven't seen reliable results for the open/close sensors yet I haven't included them in the program. It just seemed odd that the program runs at reboot.

I've never fully understood what is supposed to happen after the ISY reboots. Hopefully someone can educate me. Today, I rebooted my ISY. Then, I got an alert that the chicken coop door was opened via my "sunrise" program. It is well past sunrise. So, does that mean the program activates because the time is conditional? Is there something I can do to stop this from getting triggered? (I do not have this program set to run at startup.)

I've been testing the sensitivity reducing pins in a couple of places and so far it doesn't reduce things enough. So, I didn't think that would be useful enough for my situation to implement. One sensor "sees" a plant's leaves move and starts alerting me even after being desensitized. I'll look at where I have the sensors mounted. Maybe I can change their orientation. But lower usually equates to being more noticable, which isn't ideal from my perspective. Where they are mounted now, people don't notice them at all. I have been thinking that I could point them straight down in specific areas to create a detector that only announces when something crosses a line.