paulbates

This appears to be an out-of-the-box eisy problem. It happened to me fall of 23 when I bought mine, and there was recently someone else with the same problem. The answer is to leave it alone with the programs as written and give it a day or 2. It eventually starts working right and the problem will not return

The 2413S is what I was referring to. Did you have to unplug and replug it to get things working? If yes, and you start having flaky Insteon problems again, eg not able to control devices, the 2413S is likely going bad.

No, Its the Insteon module that the black box connects to via a cable and plugs into the wall, it connects the ISY to your insteon devices. Older ones are notorious for working great for years, then acting flaky for a while, then failing

There's a couple of ways to investigate, in easy to try order: It's rare, but I have been shipped devices that need to be factory reset to get working How old is your PLM, 5+ years? The "lost connection" to a couple of switches comment makes it suspect. Unplug it wait 10 seconds, and plug back in. If this fixes the problem, its not a fix, you are on borrowed time and need to replace it. Is the switch far away in your home, far away from the PLM and other Insteon wireless devices? It's a pain, but temporarily wire it in closer to your PLM. I have a 3 prong plug-in cord end from the hardware store I use for setting up and testng... see if it works nearby the PLM

@CoolToys Yes, I've had to change my approach to security that was previously local only. I have yolink and ecobee that each require cloud side. Each of their plugins access the devices in my house back through the cloud accounts. One partial advantage vs local only is that I assign ecobee and yolink to an iot/guest network so they can't see my other phone/tablet/pc devices. I also "force feed" both of them NextDNS's ad/spy/malware blocking DNS addresses to limit their data collection or interaction with a nefarious host. I also "caved" and using the Alexa on my ecobee but it's constrained the same as the ecobee.

I've had good luck with the remote sensor that came with my ecobee. Keeps the temps better balanced without resorting to baffles or individual vent control. The 'occupied' feature had the halo effect of it turning off the suite lights off after 30 mins if left on

This is a bit of a long shot, but easy to try; unplug the PLM for 10 seconds and plug back in. If that doesn't do it, post a screen shot of the link table showing the device and indicating which device it is

That's not the log he's asking for. You need to get the log from pg3x and the plugin. Go to the same web page you showed above ... and click log. Set the log level to debug. Recreate the steps for this and other device. Download the log package from the same web page and PM to panda88

Did you factory reset it? Try that and a restore device

With ~50 devices, I've never approached the link limit. One way performance by switching insteon on from iox is already very good. I do notice performance lag with 2 way ..when having a switch turn on an iox program that sends an insteon command back out to turn other things on.... That can be several seconds and noticeable. It's no clear to me how much that performance could be improved via plm based on current device"architecture". To me the weak link is the 19.2kb serial connection from eisy to the plm. I think the insteon white paper mentions that wireless band devices can do 38.4kb so increasing kb beyond that I don't think would be material. In other places the white paper mentions devices communicate at around 2kb - bursting at 14kb (but not what conditions qualify for bursting). So maybe a second of that *could* be shaved off on a wireless device, one hop away uping plm serial to 38.4kb.(?) 2-3 hop insteon wireless bridging will negatively impact that performance. A long way of saying it's not clear what could be done to 2 way iox performance via a new plm talking to devices that "are what they are".

Using Alexa requires an active portal subscription. If the subscription expires, this would happen. I don't think a warning is given, I keep track with a calendar entry It could be something else, but I'd start there

Yes. I have a lamp post photo cell connected to one to turn my premise lights on at dusk.. Based on light level. Same could be done with a motion sensor.

Keeping on the program track, you could try putting a notification at the end to see if the program is finishing regardless of what the device does.

Have you tried moving the statements to another program and calling that program from the one you posted? It would not take much to test the hypothesis

You're certain that the program conditions are not changing to false during the 5 minutes? Without seeing the program it sounds very much like that