All of my devices stopped working with Alexa today. I am able to log into ISY portal. Is my payment due? How can I enter my credit card information securely? Please note, I'm still using the old ISY.

reCaptcha repeatedly failed when I tried to enter a ticket.

@Yoda since you say you can log into the portal you'll want to check that your license is still active.

Log into the portal then under "Tools" check "Information" then "USY Portal Access License". Make sure it is current. If not there should be a button to renew.

After you confirm the license is active make sure you're using the proper Alexa Skill (https://wiki.universal-devices.com/ISY_Portal_Amazon_Echo_Integration_V3). You might need to re-link the skill in the Alexa app.

For a support are you using: https://www.universal-devices.com/my-tickets/ ? It requires Portal Login. Be sure you turn off any VPN or popup blockers for the browser. Use a different browser (perhaps a different browser on a different device - like phone or tablet). Try in private/incognito mode.

My alexa is down as well using eisy, Also my mobile link app will not connect to my eisy. I have restarted eisy, router and phone to no success. I can connect to portal and license is good. Any suggestions?

Not sure if this is related, but my Portal access just stopped working with my ISY 994. See:

Universal Devices

My Tickets

Designed for Energy Conservation Enthusiasts, DIYers, Makers, and Hackers. Automate Everything in Your Home/Business, Save Energy/Money, and Save the Earth!

I've got the same issue, losing both Alexa and Google integration this morning. I can still control from the administrative console, and my license is still active.

The fact that I lost Google and Alexa at the same time point to a backend issue.

I'm experiencing same issue today. Was all working last night. I am using EISY.

All of my devices stopped working with Alexa today. I am able to log into ISY portal. (I did have to reset password but all good now) I can still control from the administrative console and control devices, and my portal license is still showing as ACTIVE.

Alexa can successfully discover devices but cannot control them. I tried removing some and it re-discovered them without issue.

When I ask to turn on a light, after a short delay Alexa responds with "<Name of device> is not responding"

I've rebooted everything. I am not using Alexa+. Alexa is still using the ISY Optimized for Smart Home V3 skill.

21 minutes ago, LVaden01 said:

Any suggestions?

I would suggest opening a ticket with UD - https://www.universal-devices.com/my-tickets

Since OP posted in ISY994 area I thought it more likely to be a license issue. I've tried Alexa to turn things on/off and it works fine. Might be localized, but nothing on Amazon's AWS status page to indicate issues in the US. Maybe UD can dig into it from their side to see if they have issues with AWS or see something device specific.

@LVaden01 I wouldn't mention Mobilinc in the ticket since it is not "supported" with the eisy. But I use it and it still connected and could sync and control devices while remote.

11 minutes ago, tech_dog said:

The fact that I lost Google and Alexa at the same time point to a backend issue.

Agreed. This is odd if both are indeed not working. I'd open a ticket as well.

One of our AWS servers was no longer responding. Not our code, the actual AWS instance. I just terminated and restarted it, units that were “attached” to this server are reconnecting gradually as we speak.

That did it. Thank you everybody!

Awesome. That was it. Hung EC2 instance.
Working now. Alexa is responding and controlling lights again.

Maybe add a health check to those EC2 instances so they can fail-over if necessary?

Edited Friday at 05:02 PM4 days by tonedr

4 minutes ago, tonedr said:

Awesome. That was it. Hung EC2 instance.
Working now. Alexa is responding and controlling lights again.

Maybe add a health check to those EC2 instances so they can fail-over if necessary?

eisy with current firmware are using newer servers behind an AWS load-balancer that will not route units to non-responsive proxy server.

That instance that hung is running older code that is used for 994 and polisy/eisy running older firmwares. We leave those servers running for backward compatibility, but we are not planning to make changes to them. That failure scenario is extremely rare.