paulbates

I have had great experience with couplers. I had a signallinc from Insteon at my last house. Now that they don't make them any longer, I built my own from parts I found on mouser from a recommendation from Insteon for my new house . The parts were like $15 delivered. They have to go into your electric panel, so you have to be comfortable with that or find an electrician to do it for you.' If you're interested I can dig up the order from mouser

Do you have battery devices like motion or door sensors? Those have to be individually put in set mode for their turn. There's a little battery icon with a +/-on the top of the admin console you can click. It will avoid all battery devices so powerline devices finish. Then you unclick it and do each battery device one at a time

To add to @Techman's comments... outdated firmware means that it's i1, not i2 Insteon protocol and it wont support more modern Insteon devices, or not as well as they should be.

It's probably worth a factory reset it. Press the set button in and hold it till it beeps. Then go back and put the eisy in linking mode, and the go tap the set button quickly till it beeps.

For X10, enter the house code and unit code, eg C14. For Insteon, use the "Start Linking" option under the linking menu, and then press the set button. Do it order, or even one at a time if all over the house to keep it straight... or have a helper with a smartphone or walkie talkie to help keep it straight

I would order it from Insteon. I think the USB is cleaner, but if you have the cable and your eisy is already configed for it, serial probably makes sense. This is the procedure You would back up the eisy first. If your PLM is dying there may be some polluted links in the eisy's Insteon tables that will get backed up with it... usually fixed with individual "restore device"s based on which ones have problems. Also wireless devices have to be put in set mode and restored individually

That's an old PLM... 21st week of 2016. And if memory serves me correctly, 2016 was in the era of bad capacitors = bad PLMs. I'd order a new one and replace it on your terms rather than when it dies at an inopportune time You have a backup from right before you set up your eisy? When you get a new PLM, I'd restore that backup to the eISY, and then "Restore PLM" from that backup. Also, if your PLM is with in 15' of your eisy, you can get a USB PLM

It's never a bad idea to suspect a PLM 🤪. Seriously, the age of the PLM matters. Can you shoot a picture of the back with all numbers/IDs/stickers shown and post back here? Also, I would: Unplug the PLM, wait 10 seconds and plug back in Repeat the eisy power on/off.. did it report the same problems? Run the "4 tap test" on your access point or other plug in devices. Go look at your Insteon devices and see how they respond to it. Keep track of which is on which power leg, that will help with the next recommendation below. Start keeping track of the devices it reports in the messages, look for commonalities like which power leg they are on.

From an older manual https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Scope,_Precedence_and_Execution_Order Another one: https://forum.universal-devices.com/topic/6507-program-order-of-execution/

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

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

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

Pretty sure the 3000 port was either eisy, pg3 or both. I think earlier PG was 8080 Having said that, its not clear to me that eisy will talk to both at the same time (?)

Another thing is that devices can be dragged into scenes, but scenes cannot be dragged into other scenes. However, you can have almost unlimited scenes (in most installations) and can create many similar ones to create the lighting effects you want for different switches, programs, etc

You can add the center switch to the existing scene...but be sure to click the box to make it a controller. If you didn't do that, remove it from the scene and re-add it as a controller

You need to know how to log when you have an plugin issue and developer asks you to send them a log. What's important to know about that is: you go to the dashboard in pg3x go into the individual plugin itself click details Click log Click "debug" from the list Do the steps that recreate the error you are seeing Click download log package Send that zip file in a message to the developer There's a new wrinkle in the Session and Session Verbose options. I'm going to not select those unless instructed to by the developer.