zorax2

When I click on this sequence "Configuration" -> "Portals" to show Portal Integration, I get the error message shown in the screenshot. Everything works perfectly with my system including Alexa and Elk integration and time module. I am on same network as my EISY. I think some information showed here once upon a time. I don't think I used this screen for important information but I'd like to find out how to have everything working correctly with the app.

We have about 20 different Echo Dots and Echo Shows throughout our house - that makes for a lot of different devices listening for our voice commands. I actually feel better that all the devices can hear as it's nice when you have multiple levels in your home. We have found it much easier to use a very clear syntax when putting together the names of all devices we want to control. We do things like “Turn on bedroom light” for primary bedroom and “Turn of name’s lights” for children’s bedrooms”, “Turn on names/room fan on / speed / etc.” as appropriate. Other examples: “Turn on Christmas Lights” for outside lights, “Turn on Christmas Tree lights” for the tree in our living room, “Turn on kitchen lights”. We try to use naming conventions that would allow someone who has never been in our home to have a high likelihood of controlling the device or scene they want. When we have a visitor we basically tell them exactly that along with the primary commands – “Turn on…” / “Turn off…” . We point to something and say “Turn off kitchen table light”, "Turn on sunroom fan”, “Turn on main floor lights”, “Turn off basement lights”. I’m guessing the success rates of properly executing a device by our children’s friends or guests is well over 95%. The new version of the Alexa operating system didn't work great at first release but it seems to be doing an excellent job at this point differentiating between voice commands and it works really well

This isn't related to 6.0.0. I'm also on 6.0.0. Alexa has been doing some odd things with both Alexa and Alexa+ for a while now. A temporary solution that might work for you is to add an alternate spoken to "Basement" such as "Lower Level". I found that renaming / alternative naming worked for me in a few instances. You can test by changing "Basement" to something odd like "Turtle" to temporarily test it (if "Lower Level" sounds too close to some other spoken Alexa knows) and it will likely work as it worked for me. I think there is something going on with AI learning that is making it challengeing now. Within the past week, my "Alexa, turn on main floor lights" suddenly stopped working without any changes to my setup. It's all on Alexa for the time being.

SOLUTION - The problem is not UDI, EISY, ISY related - all Alexa Plus - see below: By happenstance, my neighbor was over for lunch and I mentioned how I've experienced some inconsistencies with my home automation using Alexa. I've had voice commands work intermittently or delayed. Just weird stuff. My biggest gripe recently was I could not turn on my mudroom lights via Alexa voice command. The mudroom lights work instantly via the Admin Console, the UD Mobile app and via the Alexa app on my phone using turn on/off. I played around with a few things and renamed my voice command (spokens) for the mudroom lights to "Romeo" and the mudroom lights ended up working properly. I switched the spoken back to "Mudroom Lights" and it wouldn't work even though it sometimes did the beep to acknowledge the command. IIRC, my neighbor uses both Hubitat and Homekit. He said he was having the exact same problems I demonstrated and described to him stating he spent hours trying to figure out why one chandelier wouldn't work correctly. The common thread was we both purchased Amazon Echo Shows that had the software updated to the new Alexa Plus. While we might be able to rollback to regular Alexa (I haven't decided whether to look at doing that), we're probably on the Alexa Plus train as I'll bet they won't want to maintain separate software for an extended period of time. Alexa Plus is initially going to be a premium / paid option that does have value but I sure hope there is a way for them to better integrate smarthome devices as we UDI device users aren't the only ones having this issue.

I tried a few variations of this: "Alexa, UDI device take priority over all other devices" and Alexa to prioritize U.D.I. devices, or Universal Devices devices, or any variation of that. Alexa replies that she can't prioritize specific device manufacturers. All smart home devices will work regardless of their brand.

Same issue here. Things will work fine for a while and then they don't. As an intermittent issue that isn't always repeatable, I don't know that there is an easy way to troubleshoot. There are some ideas on other threads regarding room / group names that might be helpful. As a side note, I think these errors are more recent within the past couple of months. I don't think the new version of Alexa made things any better.

I changed to Alexa+ about a week ago. Recently, voice commands seem intermittent - "Alexa, turn on bedroom lights". Sometimes it works, sometimes it doesn't. Alexa makes the "ding dong" sound acknowledging the command but it's often not executed. It might have started before Alexa+ but I don't recall to be certain. Does anyone else have a similar experience with voice commands not executing at all or intermittently? The scenes always work if I use the UD Mobile app so I don't think it's an Insteon communication issue.

Definitely - I'll be digging into what may have been happening here with communication issues. It's possible that any of our AV equipment or UPS power supplies might have had something change to signal suck or create noise as eisy responsiveness started sliding downhill. I put Filterlincs on the UPSs and may have to do a bit more of that.

Everything back up and running! I'm a bit puzzled why I got so many devices marked cannot communicate even when I could see they were being written to. Additionally, I could operate the devices from the Admin Console in many cases. Nevertheless, the below steps worked. Following all of your advice: I did a factory reset of PLM I followed the Replace Modem (PLM) instructions I then followed the Restore Devices procedure (Weird quirk on Wiki in that a search does not find it. I think there are a number of great procedures and explanations on the Wiki that seemingly don't show up with search function) I ran the Restore Device procedure at least 4 times and each time a few more devices popped up with the green 1011 icon. I then used the Write Updates to Device. Went to Java and deleted the applet and temp files each time before doing the Restore Device procedure. This time around I made sure to backup everything - programs, IOX, PG3, etc. Everything seems to be working perfectly and all devices are responsive without delays. Again, thank you for your help - I couldn't have done it without all of your great advice!

Some good news - finally. I did another Restore Devices and some of the devices are now communicating. I think I'll run Restore Devices a couple of more times to see what happens and maybe I'll get lucky and make some more progress.

It seems as though what you described is happening in a good way. I currently have a device in the Restore Device procedure at Link 52 and counting. It appears that things are writing as that in many of the small print messages. It says things like "Writing High Water Byte" Memory: Write, Writing Controller as it continues though the small writing of changes goes very fast so it's hard to keep up as it keeps going through the process so fast. I do see an error message like ERR 0 or ERR 1 occassionally but not with every device - again the text showing the changes move too fast to keep up with it..

@apostolakisl I'm going to follow up reading your post in a minute. Simultaneously, I put my progress to this point below. Well – no luck again after doing Replace PLM and the Restore Devices. Red ! exclamation marks next to every device. The Restore Devices Wiki says you might need to do the process multiple times for new devices so I’m in the process of doing that. I’m at a real loss that I’m not establishing communication with the existing devices. Again for troubleshooting purposes, I took a factory reset switch on a pigtail and went to the spot in our house (large house) farthest from the panel. Put the eisy in linking mode and added the switch without any problems. From the Administrative Console, on/off commands work almost instantaneously. This a brief log from turning the switch on an off and nothing seems strange to me from my limited understanding of these things: Tue 08/12/2025 06:51:12 PM : [INST-TX-I1 ] 02 62 28 A2 F4 0F 13 00 Tue 08/12/2025 06:51:12 PM : [INST-ACK ] 02 62 28.A2.F4 0F 13 00 06 LTOFFRR(00) Tue 08/12/2025 06:51:12 PM : [INST-SRX ] 02 50 28.A2.F4 43.71.52 2B 13 00 LTOFFRR(00) Tue 08/12/2025 06:51:12 PM : [Std-Direct Ack] 28.A2.F4-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 08/12/2025 06:51:12 PM : [D2D EVENT ] Event [28 A2 F4 1] [ST] [0] uom=100 prec=0 Tue 08/12/2025 06:51:12 PM : [28 A2 F4 1 ] ST 0 (uom=100 prec=0) Tue 08/12/2025 06:51:15 PM : [INST-TX-I1 ] 02 62 28 A2 F4 0F 11 FF Tue 08/12/2025 06:51:15 PM : [INST-ACK ] 02 62 28.A2.F4 0F 11 FF 06 LTONRR (FF) Tue 08/12/2025 06:51:15 PM : [INST-SRX ] 02 50 28.A2.F4 43.71.52 2B 11 FF LTONRR (FF) Tue 08/12/2025 06:51:15 PM : [Std-Direct Ack] 28.A2.F4-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 08/12/2025 06:51:15 PM : [D2D EVENT ] Event [28 A2 F4 1] [ST] [255] uom=100 prec=0 Tue 08/12/2025 06:51:15 PM : [28 A2 F4 1 ] ST 255 (uom=100 prec=0) Tue 08/12/2025 06:51:15 PM : [INST-SRX ] 02 50 28.A2.F4 43.71.52 23 11 FF LTONRR (FF) Tue 08/12/2025 06:51:15 PM : [Std-Direct Ack] 28.A2.F4-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 It just makes no sense the other devices aren’t communicating. Any other ideas?

@Techman I'm definitely learning a hard lesson about backups on the eisy. I kick myself because I do a 3-2-1 backup strategy with all my other data. I even use two cloud services to supplement my NAS and offsite data storage. Most of that backup process is fully automated so I don't have to even think about it much other than to check it periodically. To give you context as to how I got in this pickle (it wasn't alcohol), I was in a bad accident a couple weeks ago and broke my scapula / shoulder blade in multiple places (one of the hardest bones in the body to break) and fractured multiple ribs. Doing anything simply hurts a lot and I've got at least 12 weeks of physical therapy ahead of me. I had been using voice commands with everything and haven't touched a light switch for years. Then the system gets slow or doesn't execute commands properly. It's hard to sleep with fractured ribs and when voice commands stopped working my brained turned off and I started this mess out of frustration as I didn't want to keep moving around to go to switches. My little PLM endeavour added a bit more misery to the whole situation by not backing up properly but hopefully I can get things going on this attempt.

@apostolakisl Thank you for listing the full procedure in order for me in the order to try. I did vary my factory reset a bit by unplugging everything, then plugging in the PLM with the button held to do a factory reset. I then removed the PLM from the outlet 30 seconds after the factory reset. Next I plugged the eisy back in (while the PLM was still unplugged) and then restored the backup. After the reboot, I logged into the eisy again to ensure the restore went correctly. I then unplugged the eisy and followed the instruction sheet for Replace Modem. I was trying to cover all the bases in terms of resetting the PLM and making sure the backup was restored properly prior to moving on. I'm now waiting for the system to initialize. @Techman Thank you for mentioning to disable devices not being used - I hadn't thought of that. I also don't have any wireless devices so that should also make things a bit easier.

I did some more forum searching regarding noise and forgot that I had two UPSs that I’ve been using for a long time. I had some extra Filterlincs in my spares kit and plugged the UPSs into the bottom filtered outlet. @TechmanInterestingly, I think some of the noise troubleshooting posts were actually yours. My latest isy backup was in March 2024 with firmware version 5.8.0 with eisy (not my old 994). I imagine I made that backup prior to upgrading to version 5.8.4 which I’m currently using. That backup was not made with the PLM that I posted in the previous post. It was made with the backup of the PLM I removed from the system. I already gave it a go with the new PLM with the current results. Now that I moved the eisy next to the electrical panel, does it make sense to: 1st: Do another factory reset on the PLM and do the Replace Modem procedure 2nd: Follow with the Restore ISY procedure and Restore Devices (restore my backup and then Restore Devices)?

The PLM info status shows connected. I moved my EISY and PLM to an outlet right next to the service panel (they had been further away in a mechanical room). I installed an access point on the other leg in another outlet near the panel. I also added one more access point further away as we have a large house. Moving things to next to the panel didn’t seem to improve things. The cookbook mentioned counting the number of links with the 2413s being limited to around 900 links. The count was 615 for my system. @apostolakisl You mentioned that perhaps the devices not communicating. Would my troubleshooting of successfully adding and removing the 2334-2 switch suggest that the eisy and PLM are working correctly?

Unfortunately, no luck with the Replace Modem (PLM) steps. I had the series of nodes with green 1011 icons. I tried Right mouse click | Write pending updates... for several devices and all failed. I then followed the steps for “Restore Devices”. I believe every single device had a red ! exclamation sign. For each device with green 1011 icons, I did Write updates to device which didn’t work. I think every device had the error box “Failed Communicating With” – Cannot Communicate With “Device Name”. Please check connections. However, some devices with the red ! exclamation point could be toggled on / off from the Administrator Console though the commands to turn on or off took about 4 to 5 seconds to occur then I would get the “Cannot Communicate with “Device Name” error. Note: One possible wrinkle is the “new” replacement PLM modem is a 2413S V2.2 1629 that I sent in for re-capping and upgrading to Nilachi Data Systems in 2023 when there was concern about the viability of Insteon and getting parts. The PLM Info/Status shows connected. To test this PLM modem, I factory defaulted a spare switch 2334-2, pressed the Set button on the switch for 3-5 seconds and the “New Insteon Devices” dialog box appeared with the Status “To Be Added” with the correct address of the switch. I added the device and then turned it on and off via the Administrative Console and then removed it. Given that was all successful I don’t think the connection issues are due to the new PLM. Would the next step be to try this again by factory resetting the PLM, going through the Replace Modem (PLM) instructions and steps and followed by Restore Devices procedure? Would the next step be to try this again by factory resetting the PLM, going through the Replace Modem (PLM) instructions and steps and followed by Restore Devices procedure? And, if that doesn’t work, do I simply factory reset every switch and device and rebuild the system? I’ve saved the topology and took screenshots of all scenes. I also took screenshots of all the programs and of the configuration for the PG3 apps for Elk and TimeData. The Alexa integration is a bit of a headscratcher given the commands are tied to specific scenes or devices though I can try to delete all of those prior to resetting anything else. I’m just wondering if starting from scratch puts me in an overall better place knowing all internal device links are correct and perhaps saves time vs. troubleshooting. Each refresh and change takes a long time likely due to retrying each communication before timing out.

Thanks @TJF1960- I had already done IoX backup, PGx backup with the new PLM. Also did topology report and saved to PDF files. I already started @DennisC process prior to your message. I'm crossing my fingers and hoping for the best.

Hate to admit it but – eisy was getting worse and worse executing commands. Lights weren’t turning on when doors were opened (Elk integration), voice commands via Alexa were spotty / inconsistent, etc. It was a late night after a rough day, lights weren’t working again with voice commands and then frustrated and clearly not thinking, I removed the existing PLM and attached a new PLM… My overworked brain somehow diagnosed that the old PLM was the problem and plugging in a new PLM would fix it. Stupid – I know…. Everything is a mess and the new PLM isn’t talking with the devices. I’m currently running IoX version 5.8.4. My last backup was v5.8.0. in March of 2024. Not too smart. I’m thinking the backup may have been either before upgrading the firmware version or when I went from a 994 to the eisy. Since that backup, I have replaced some Insteon switches for various reasons. I also likely did some additional programming since that backup. Today, I went to the Administrative Console and did screenshots of virtually everything – especially programming syntax. I read in the forum that depending on the restoration process used, I could end up with orphan links slowing down the system. I’m guessing I probably have at least 50 light switches (mostly 2477D switches and 2344 5 button keypads), a bunch of 2476ST SwitchLinc Relays, LampLink devices, 2365 On/Off Modules, 2475F FanLincs. I’m using Elk and Timedata plugins and use integration with Alexa. I also have some access points in a couple places around the house (don’t know if they help or not given switches are dual band). Before I mess things up even more, what do I do next? Restore ISY, Restore Modem (PLM), Delete Modem (PLM) and then Restore ISY followed by Restore Modem? Thanks in advance for recommendations!

Down in MN. Maybe somewhere around 10 PM Central time.

Down in MN. I have the same error. I also can’t use the UD mobile app.

Issue solved - my router not the portal. Thank you Michael for determining that outbound traffic for the eisy was blocked. In case anyone runs into a similar issue, here is the rundown: I use a VPN on my ASUS router along with its built-in VPN director (with the eisy’s address specifically assigned to the WAN which had been working correctly with that configuration). At some point yesterday, I had to change my personal computer connection for its IP address from the VPN to the WAN for a financial transaction with a dropdown box to switch the connection type and applied the new setting for that specific device. It appears that even though I made no changes to the eisy’s WAN assignment in the VPN Director, something must have went awry when the change was applied. I turned off the VPN entirely and the eisy is now back online with the portal. I never would have expected the change I made on the VPN for my personal computer’s IP address shouldn’t have affected the eisy and I would have never thought to check that setting as there seemed to be no reason the change I made would have affected another device on the network.

My Alexa integration on my EISY stopped working. My EISY is hardwired ethernet on battery backup. I did a full power-off reset. Logged in to administrative console and "Portal Integration - UDI" showed offline. Any ideas? Local issue on my side or with the portal?

@Javi Any recommendations or should I turn in a support ticket?

@DennisC I'm on eisy running the current firmware version 5.8.0 I am on the latest UD Mobile I have rebooted the eisy via Configuration / eisy System Settings / Reboot