zorax2

@DennisC I don't think it is necessarily related to the "Invalid Credential" error. However, all this happened after I recently updated my eisy IOX and everything else. Thank you for your help in finding that post. I appreciate it.

@Geddy Thank you for your suggestion. Tried turning off wifi and I didn't get the error message I posted above. I do get a spinning blue and then an error - (ERROR - The request timed out). I guess since all the devices and programs work properly I'll just not worry about it as it appears there's nothing I can do on the user side to prevent either error for that page.

Thanks for the link to make it easy - udx is 4.2.0 UD Mobile is current version 1.4.7 Did system reboot twice - no change / same error

Yes. I updated everything within the last week or so. Running IOX / UI version 6.03 and PG3 version 3.4.5 My PG3 error log does have many errors like these from today but I have no idea why: Sat 2025/12/06 09:58:01 AM System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> Sat 2025/12/06 09:58:04 AM System -170001 <s:Envelope><s:Body><u:GetDisclaimerStatus xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetDisclaimerStatus></s:Body></s:Envelope> Sat 2025/12/06 09:59:04 AM System -170001 <s:Envelope><s:Body><u:SetDebugLevel xmlns:u="urn:udi-com:service:X_IoX_Service:1"><option>0</option></u:SetDebugLevel></s:Body></s:Envelope>

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..