Schlyguy

Just tried this with one of the "non-working" later model On/Off 2635-222 modules I just replaced. I re-added it to EISY, and it set up no problem, and able to control it remotely with no issues. Saved one module Tried it with the older ApplianceLinc - I get the "cannot determine insteon engine" error - so I supposed that module was bad. Did a hard reset by unplugging, holding in set button and replugging - and was able to add it to insteon also. Will now work through the others....

I'm working my way through an EISY upgrade with a new USB PLM. Restored the new PLM, and most of the direct wired devices updated without major issues (about 200 devices in total). However - I've got about 8 plug-in modules of various types - older ApplianceLinc and newer On/Off style - and 5 of them won't communicate following the transition to the new EISY and USB modem. I started replacing them out with new modules, but after doing 2 and realizing I've got at least 3 more - is there some possible reason I'm having this level of difficulty? I've been doing hard resets of the non-communicating modules and restoring them from within the EISY - still - communication errors. I've updated all the packages on the EISY - it's up to date. Java cache cleared. Any insight would be appreciated.

Just an update on this - I think that I may have some bad devices installed which may be causing the "All Off" symptoms I'm experiencing - I'm still getting this a couple times a week but Alexa may not be the only trigger - I have a few keypads which may have bad caps / power supplies - so I'm going through my installation - resetting devices which aren't responding properly, replacing devices which won't reset correctly, etc. Once I get my installation rebaselined, I'll come back to this and test again. It will take some time - I've got about 130 devices of all types - and I've fallen behind in my system maintenance due to workload. I also let it go with the Insteon business interruption, now that someone has picked up the technology and seems committed to supporting it, I'll double down and keep my Insteon network running.

I had a similar issue with my email notifications not going out through the "Default" SMTP settings on the Emails/Notifications panel. Played around with this for a while - couldn't get it to work - and then I manually upgraded my ISY994i firmware from 5.3.0 to 5.3.4. Rebooted the ISY and bingo - email notifications working again through the "default" settings. I am interested however in the Pushover notifications that @MrBill suggested ... have that on my list of fixes now. Just need to figure out how to use Node Servers.....

I'll try that - report back. Will be a few days - occupied for the next two evening with family. Thanks all for your input.

No insteon Hub - just the ISY 994i. This is all I have configured so far in the ISY Portal for the Alexa connection. The first scene - all lights off bedtime - I don't think is the culprit - it's a scene I've created using the ISY with just the interior house lights - controlled by Keypad buttons - to make it easy to ensure all the lights are off in the house before leaving / going to bed.

That's not what's happening. I've got 10 devices set up in the ISY portal / connection to Alexa. But if I say "all lights out" to Alexa - all 200 of my insteon devices switch off at one - including my water valve, bathroom fans, etc. It's seems to be transferring a command to my ISY which triggers a global "lights off" command at the ISY..... That's where I'm unclear what's going on.

Hello all - I just recently set up the Alexa integration with my ISY 994i. I've got about 200 devices in my home - every light circuit is insteon switched or dimmed, every closet has open/close sensors, water leak sensors at all water sources, on/off main water shutoff valve, you name it. I finally got around in installing a few Echo dots and starting Alexa integration, set up the ISY Portal, linked it to Alexa - all straightforward. I started simply - just added 10 devices / scenes to initially control through Alexa. Works fine - very straightforward - however - if I say "Alexa - all lights off" - that triggers an X10 style All Lights Off command with my entire installation. All lights go off, but the water valve closes, the coffee machine (plug-ins) all turn off, and so on. I found one post on Reddit related to this here: and I implemented the routine to disable the command on the Alexa side of the integration. However, still curious how this command makes it throught the "ISY optimized for smart home v3" skill.