kwmcc

Not sure I want to go that far. I'd worry about file corruption. If it's got an auto-reboot I'd do that weekly or so. I have an unattended Raspberry Pi Zero W that runs a webcam in a relatively remote location. I have cron reboot it weekly.

So here's the result. Rebooted my router. It works now. Immediately. For what it's worth, it's a Rockpi running FriendlyWRT. I have no explanation. The router had been up without a reboot for months if not more. So, who knows. I apologize for not doing that immediately. It just never occurred to me that it could be a cause. ¯\_(ツ)_/¯

Expires next summer. When I'm home, I'll try the router reboot. Then open a ticket if necessary. Thanks for giving it a go.

Let's back up a little. The my.isy.io portal says it can't connect when I try anything, such as checking Amazon Echo integration (Message: "ISY is not online"). UD Mobile says it can't connect (Message: "System: EISY, ERROR: Requested ISY not online. 503") Neither of those can be related to how I enter the URL in the ISY finder, or any cached Java files. There's something deeper going on here between the ISY portal (and UD Mobile) and the device. IoX not finding it seems to be a symptom, not a cause.

Interesting problem here that has popped up today. Everything worked yesterday. Amazon Echo integration failed. So I went to IoX to see what was up. It couldn't find the EISY (I was planning a reboot). When I entered "https://eisy.local:8443/desc", it sees the uuid for the device (matches what shows in the my.isy.io portal). I can't login (it doesn't respond when I click File->Login) and the three tabs are all empty. I did a power off/power on. No joy. IoX still can't find it. my.isy.io sees the device and firmware level (6.0.5), but any attempt to connect or do anything yields "ISY is not online" (note, it's an EISY). UD Mobile says: System: EISY ERROR: Requested ISY not online. 503 System not online or not communicating with Universal Devices Portal. Verify your System is connected to the network. Try reboot. But, I can connect to it directly using my browser, by going to the IP address and logging in. I get the eisy-ui. I can turn nodes on and off using eisy-ui. So it appears the device is working eisy-ui tells that I'm running: PG3x Version 3.3.22 Status: Connected Frontend Version: 3.3.22 IoX Version: 6.0.5 Connected Uptime <about an hour since I power off and back on> Suggestions???

My concern was that I already have the V3 and it is enabled. I do not have Insteon enabled (as was reported by someone above). So it appears that the error message from Amazon is incorrect and was sent to everyone who used V2 in the past?

Thanks for the pointer.

Recieved this notice today: "We're reaching out to let you know about changes to how Alexa works with Universal Devices, Inc. devices that connect to Alexa using the ISY Optimized for Smart Home V2 Skill. The ISY Optimized for Smart Home V2 Skill uses an outdated integration that hasn't been updated by its developer to support all of Alexa’s existing and new functionality." "As a result, the Universal Devices, Inc. devices you have connected using their Alexa Skill will stop working with Alexa on November 1, 2025. This means the devices will no longer work with Alexa voice requests, Routines, or the Alexa app at that time." The Alexa app shows "ISY Optimized for Smart Home V3" is enabled. So I'm somewhat confused and concerned.