Alexa heartache all weekend

Any one else having issues with Alexa ... dropping out ... working for a while then dropping out again ..... something to do with oauth????

Was working perfectly for weeks ... Have uninstalled and installed and intermittently when re subscribing in Alexa oauth freezes up after selecting my hub then reports failure ...

Been working fine for me all weekend. I use lots of voice control.

1 Like

Well it looks like it’s all back up and winning again this AM .... ! Yea

i had issues with alexa with the new update. It would work when i would access my HE, then stop working again. I downgraded it and everything is working again.

I just migrated from Wink to HE this weekend and the connection to Echo devices seems to "go to sleep" very frequently and we are told the "device is not responding." If I turn any device off/on manually, then the integrations all work perfectly until there is a 15-20 gap in use and then it's back to sleep. Anyone know if there is a tweak for that? Wink is lightning fast to respond but that company is going to disappear any day now....I like the HE. Hope I can get it to be more stable.

Yes I have that very issue. the Latest updated screwed mine. I had to downgrade to get it working again. Not sure what the issue is. but it is definitely the update that messed it up

I upgraded my hub to 2.1.9 and have not experienced any issues with the Amazon Alexa integration.

1 Like

Fair point, I upgraded and that’s about when the trouble started ... that said it felt more like a server side issue ....

In that :

A > On a number of occasions: when I when to resetup the skill in Alexa it failed before i was prompted for a uid and PWC
B > more common : was that I’d authenticate and then Alexa reported the account linking failed
B > most common ; authenticated and got my hub listing ... but would fail thereafter before I see what devices to link
C> very common : linkage worked and all worked for a little while then back to square 1 and nothing working

I’ll go downgrade if the issue persists this week

Lol tested again just now and it’s broken again! ... downgrade here I come

It is odd how it doesn't seem to affect everyone. But I have seen at least 3 or 4 on here with issues with alexa after the update. What makes it worse is my wife screaming how she hates smart devices for the past few days lol.

Yea mine 2 ,,,, I hear her upstairs screaming at Alexa .... it’s funny until she comes downstairs!!!!!

1 Like

Just as a different data point, I had problems with Alexa in general over weekend, nothing to do with HE. Music stopped playing, Alexa didn’t react when called, needed to reboot Alexa. Maybe Amazon had some localized issues and you saw it while trying to interact with it from HE.

That was my initial thought but the issues persist and come and go... have raised a ticket with Hubitat to see what the rub is

Just another data point... I've had no problems with Alexa since the upgrade to 2.1.19.114.

Every now and then I do have problems with Alexa, but I can almost always tie them to problems with my wifi, problems with my LAN in general, or problems on the Amazon side. The first two are usually solved with a router reboot. The last is annoying but usually short lived, and I just wait it out until Amazon gets it back together.

Thing is with me is I downgraded the firmware and I have had zero issues since. I was having issues after a few minutes before. it has been 2 days since i downgraded and no problems.

I am going to give the downgrade a go. I already rebooted wifi, router, etc. thinking it was a LAN issue but no change. I will drop one rev and see what happens. They made that process easy. Updates as I have them.

Thanks!

Well I went and reset up the Alexa skill again and things worked for a while however we’d getting an earning of

warn Received cloud request for App 546 that does not exist, path: /device/366 from 34.239.163.155

And that while Alexa worked I got those errors from various AWS servers And different device ID’s
( The “from” address is registered as a AWS one and changes periodically)

When Alexa stops working the errors stop...

Checked my device list and there is one device with an Id of 2366 , not sure if I’m comparing apples to apples here but if that’s the same device the Id Alexa is trying to talk to is being truncates by 1 from the left ....

Edit

And a few more

Received cloud request for App 130 that does not exist, path: /device/50 from 18.232.54.118

Received cloud request for App 546 that does not exist, path: /device/51 from 18.206.59.16

What’s interesting is that the app is is diffrent

Just checking the Alexa skill on Hubitat and the device list does not list those devices

deviceList [64, 373, 369, 199, 254, 97, 280, 397, 227, 37, 16, 55, 362, 285, 129, 130, 131, 132, 133, 139, 140, 134, 136, 138, 135, 137, 39, 40, 301, 262]

Questions in my mind are :

  • where the hell is alexa pulling those numbers from ? An old integration?
  • ok so a uninstall and install gets Alexa going again with errors .... then it fails again... is it because Alexa and or Hubitat hit some type of error limit ?

Do I need to reset up all my devices in Alexa ???? Hole the hell not cuz that’s going to be a material issue .....

End of day don’t think this is a communication issue but some sort of integration mismatch or residual from previous installs of the skill ??

Ok removed all devices from the skill... added one light and it works however am getting load of warnings

amwarnReceived cloud request for App 546 that does not exist, path: /device/51 from 3.231.228.192

sys:12020-02-25 07:23:00.458 amwarnReceived cloud request for App 130 that does not exist, path: /device/50 from 34.207.103.255

sys:12020-02-25 07:22:43.582 amwarnReceived cloud request for App 546 that does not exist, path: /device/51 from 3.231.220.84

sys:12020-02-25 07:22:43.579 amwarnReceived cloud request for App 130 that does not exist, path: /device/50 from 34.207.103.255

sys:12020-02-25 07:22:17.617 amwarnReceived cloud request for App 546 that does not exist, path: /device/51 from 3.221.158.18

sys:12020-02-25 07:22:17.582 amwarnReceived cloud request for App 130 that does not exist, path: /device/50 from 3.231.228.192

sys:12020-02-25 07:21:20.449 amwarnReceived cloud request for App 546 that does not exist, path: /device/51 from 3.221.158.18

sys:12020-02-25 07:21:20.449 amwarnReceived cloud request for App 130 that does not exist, path: /device/50 from 54.197.25.166

Than I added another 2 devices and more errors

sys:12020-02-25 07:32:06.712 amwarnReceived cloud request for App 546 that does not exist, path: /device/51 from 3.91.106.126

sys:12020-02-25 07:32:06.696 amwarnReceived cloud request for App 130 that does not exist, path: /device/50 from 3.232.134.19