apostolakisl

I set it to run at startup and changed "is red" to "is not green". I have since reboot eisy twice and both times it connected, so I believe that solved the issue.

I put an Insteon filterlinc in my IT room and then I plugged my UPS into the filtered side of it and then everything in my IT closet is powered off of the UPS, except the PLM. I plugged the PLM into the passthrough plug on the filterlinc. This setup has worked perfectly for like a decade.

The above program isn't working for me. I just updated packages and I had the above program set to run at startup. It didn't run true because the server status was unpopulated, not red. I can probably fix the not running at startup by switching to "is not green" instead of "is red". Unfortunately I didn't remember to wait a whole minute for the re-discover to see if that worked. I ended up restarting the node manually.

Here is a forum describing it as well as an example of mine. I have only done this from routines.

If you activate the scene from the admin console, does it behave the same as with Alexa? Likely the answer is yes. Which means your scene links are corrupt. Try restoring all the devices in the scene. If that doesn't work, trying removing the device that isn't responding from the scene and then adding it back in. If that doesn't work, start deleting devices, factory resetting them, adding them back to ISY, then creating the scenes again.

There is only Google and Alexa that natively integrate with isy. For that matter, I am not aware of any cross platform voice system besides those two regardless. I use Alexa, and while I agree that it is a bit convoluted, it consistently works once you know what you are doing. I find that using Alexa routines is really the way to go. I prefer to expose my ISY devices to Alexa with the "spoken" purposefully not the logical name. I prefer to use routines to trigger things which opens up your phrase structure, not just "turn on x". You can also specify that only certain Alexa's respond to certain commands.

@DennisC Thanks for the info. I can confirm that it is fixed. i did the update and all is well again on that front. I did not have any of the other issues you refer to. My IOX launcher still works like normal. EDIT: I don't seem to be able to login into PG3x. I tried admin/my not portal password, admin/admin, and email/portal password. I also can't login into eisy-ui. Won't accept the portal username/password. I can login into portal using portal user/pass and I can login into admin console using both the local port 8080 user/password and the portal user/password @Javi

I have had this same problem after adding a device. It did add the device, and the device worked properly, but the popup just keeps happening every time I opened a new admin console session. After rebooting eisy it stopped. I feel like it is a firmware bug. I have added multiple devices and it didn't happen every time. I never saw this problem in the 15 plus years I have had an ISY until just a few months ago. Regarding the OP's issue. I think the scene is corrupted. I would delete the device completely from ISY, factory reset it, add the device back into ISY, and then put it back into the various scenes. Hopefully it isn't a super complicated set of scenes/programs.

So the problem is with ISY, not Alexa. If the light doesn't turn on when you turn the scene on from the ISY admin console it isn't going to turn on when Alexa triggers it either. I have also had this (edit, by this I mean it keeps doing the pop up) happen after adding a device and ended up having to power cycle ISY. A bug in one of the more recent firmwares I guess. I have now seen at least a couple other people report this. I would start with rebooting your ISY (eisy/polisy/whatever model). Then see if the scene works. My bet, however, is it will not. Perhaps the "replace with" command did not function correctly. You can always try a "restore device", but I usually just completely delete the device, add it back, and configure it back into all the scenes.

If Alexa is controlling the scene, then Alexa won't know if you swapped out a device in the scene. Alexa doesn't see the individual devices in a scene. Alexa triggers ISY to issue a "scene on" and from there it is all Insteon configuration as to what responds to the scene. What happens if you trigger the scene from the ISY admin console? If that works, then I can't understand how Alexa isn't unless Alexa isn't triggering a scene but rather a device. When you open the ISY portal and go to Amazon echo: Is the "ISY category" for whatever it is listed as a "scene" or "device"?

I'm going to assume that you have a scene and that in the portal you set the scene to be controlled by Alexa (not individual devices). Since Alexa still is controlling the scene, it sounds to me like the new switch isn't in the scene. If you did a "replace with", then it should be in the same scenes as before. If you deleted the old device and added the new switch, then perhaps you never put it into the scene.

I was going to say the same thing about the caps. For fun I replaced capacitors on some old 2476D's I had and sure enough, they came back to life. For the most part though, it doesn't make a lot of sense repairing them. Just in case it is a link table issue, it would be easy enough to factory reset it, delete the device from ISY, then add the device back to ISY and re-create all the scenes and stuff. Before you delete it from ISY, take some screen shots of the scenes and stuff so you can quickly put it back as it was. I have had mis-behaving switches in the past where this fixed them. EDIT: Just to be clear, ISY can have bad/wrong links tables and simply factoring resetting the device and restoring it will just put the same bad links on it. If you delete it and start from scratch, this won't be a problem. I have had this happen a handful of times over the years.

If for whatever reason your ISY is stuck in this state, you will just have to power cycle it, even though it says don't do that. There are legit reasons for this message, but they shouldn't persist. So if hours go by and this still happens, you will need a power cycle.

Don't use status of the kpl button in your second program. Use "control", so it will say if KPL... is switched off. In that case, the only action that runs the program is someone physically pushing the button on the kpl to shut it off. Furthermore, if the only thing you use that kpl for is to shut things off, I would change the KPL toggle mode to non-toggle off. In this case, pressing the button will always send an "off" command. The KPL button backlight can still be turned on by a program or by responding to a scene, but pressing it will only ever send an off command. Finally, you would probably be better off creating a scene rather than listing out all the devices one by one in a program. You can put the KPL button in the scene as a controller and all the other devices as responders. Then you can do away with the second program altogether.

I would start by opening your program summary page on a laptop and then, while watching the page, click on the light switches and see if any programs run. That would cover what @oberkc was proposing. If it proves that no programs are running, then I would move on to what @Guy Lavoie suggested. If that doesn't work, I would delete them from ISY completely, factory reset them, then add them back in to ISY. Be sure to note all of the scenes and programs they may have been part of prior to deleting them so that you can quickly create them again.