I thought perhaps it was “just me” but last night, I definitely encountered several unusual Alexa-related roadblocks, where my usual command phrase came back “Not Responding”. Had to repeat several times and/or wait a minute for things to get executed.
Had to be a server issue, but I never checked the Status page to see.
I am encountering the same thing. Last night I got the “Not Responding” messages. I could not logon to getvera.com either. Today it is very slow to logon and Alexa is still giving the “Not Responding”. Some commands will work after 1-2 min delay. Up until last night it was working flawless.
I’m having the same issues also. It told me to disable the skill and re-enable it. I tried logging into the Vera Android app and it’s telling me no internet connection which is a problem we’ve had in the past. My automation is completely useless now. Couple hours ago it was only running half of my scenes which was odd. 5 devices but only two responded.
@Sorin looks like problems again!!! Someone tell us WTF is going on please!!!
This is really starting to get old. Vera app, webpage login and Alexa app not working. Tried reset password get account unknown. My internet is working for everything else. Needs fixed again…
Yeah I’ve looked at Home Seer and even bought a license, however I’m waiting for the Hubitat Elevations to come back into stock and I’ll buy one of those.
The problem has been addressed now. It is working fine for me.
When I contacted them, they mentioned that it was a temporary issue and it took about 15 min for them to address it once we reported it.
Please, take a look again at the login page home.getvera.com and the connection with Alexa.
Yes, Alexa and Web Services are operational again.
Looks like you guy’s need to improve your Monitoring and Alerting solution - I highly recommend PagerDuty for on-call alert and incident Management. I’m spending roughly $140k USD per year on it for 300 engineering staff and it’s worth every cent. My staff can even trigger micro-services to be pulled down and replaced to restore incidents from within PagerDuty. It also integrates with Slack and Teams exceptionally well.
PS, If you aren’t going to reflect outages in your status page, perhaps reconsider paying Atlassian for its use.
This issue that was present for at least 6 and a half hours - I first found issues when I got home from a day out, yesterday @ 3pm Australian Eastern Standard time (27/6). This was still an issue at around 9:30am AEST today (28/6).
Sort of working. Used web GUI, took almost 2 minutes to connect. Said “attempting direct connection” at one point so I’m guessing there are portal issues.
Alexa still doesn’t see it & the Vera app is saying “no internet connection” still.