Alexa is controlling the devices but says the device is not responding after the latested update today. how do I fix?
I removed the Alexa app and installed the Alexa Skill and took care of this issue
1 Like
Just tried that , still doesn't work. getting a null error in the amazon echo skill. this was working before the update.
Also just did a revert on the firmware, now it's working fine again.
I'm having the same issue after updating to 2.1.0.120 from 2.0.8.113; also using the Amazon Echo App. Is this problem known to be an issue with the App?
It's happened to me a few times in the last couple of days and I'm using the Amazon Echo Skill. I really think this is an issue on the Amazon side because it's wide spread. I had it before upgrading and it hadn't happened at all previously on the same version.
Used to happen with Insteon all the time too. Just seems like something Amazon has never completely eliminated and it keeps popping up. Now that I've started using Google Home more too, and control is an issue on that platform occasionally, and not just with Hubitat. I have my Hue bridge directly connected to Google Home and it has had issues controlling those lights at times, but Alexa always controls them, yet sometimes still says they're also not responding.
Why is it working fine on the ,113 firmware then?
My point is, it’s not the platform. It’s the cloud. I experience this on all platform versions no and again. It comes and goes.
I experience this on other hubs too. It’s not Hubitat, it’s Amazon where the issue sits.
Been using the Echo app since it became available with Hubitat; also still using the Alexa Skill on SmartThings and Wink Relay with a few non-migrated devices on those platforms. I have had the (rare) instances of this happening as you describe; usually it never persisted for more than an hour or two and may likely have been an Amazon-side issue. However since the firmware upgrade yesterday I have observed this behavior which leads me to believe that something in the Hubitat implementation may contribute to this phenomenon:
-Only Hubitat devices are producing the 'not responding' message to Echo voice commands. ST and Wink attached devices do not.
-My Alexa device groups which contain a mix of Hubitat and ST or Wink devices do not produce the 'not responding' message. All device groups which contain Hubitat devices only are showing the problem.
I wonder if there be some configurable AWS 'timeout' parameter in the Hubitat implementation which is shorter than that used by ST/Wink which could be causing the issue.
I am noticing this only when trying to control my ge fan device. Otherwise Alexa seems to be responding normally for all other requests.
1 Like
So I have a workaround to fix this annoyance; unfortunately it requires having access to the SmartThings IDE (though probably not a currently active ST hub). Create an Alexa device group with the name of whatever Hubitat device Echo needs to control, and include within it the Hubitat device and a SmartThings virtual switch (whose only purpose is to mitigate this apparent issue)... no more 'not responding' message.
I removed the Alexa app and installed the Alexa Skills app and my problem with this went away. You may want to try removing Alexa all together and reinstalling it
Thanks, I may try that at some point if I have more problems. Right now my work around has taken care of the issue for me. Way back when the skill was first released, complaints of slowdowns and lockups that couldn't be pinned on WebCore seemed to be on the rise. Likely just a coincidence, but I assumed the app was lighter on resources than the skill so I avoided installing it as the app was adequate for my needs (I still run WebCore with no slow downs and don't want to press my luck).
Just an FYI. I had continuous problems with the Echo skill prior to this update. The alexa app was always marking devices offline and would always show the rooms as empty. About one week prior to 2.1, I deleted the app from HE and disconnected the HE skill in the alexa app. I then deleted all of the HE devices from the Alexa app and reinstalled everything and added the devices back to the Alexa rooms. I saw very little improvement in responsiveness. Ever since the 2.1 update, I no longer have offline devices in Alexa, no more waiting for minutes sometimes while the rooms load in the app (devices are immediately available now), and the devices respond immediately using voice control. BTW, I have 90 Zigbee devices, 33 of which are Sylvania rgbw (9 recessed, 6 BR30, 18 A19), 9 Osram CT bulbs, 8 zigbee outlets, 6 zigbee switches, 29 sylvania end devices (5 motion, 5 contact, 10 2-button & 9 4-button dimmers), and 5 samsung buttons. I also have 22 Hue lights connected to the Hue bridge.
Same problem here. I removed the app, and am attempting to install the skill, but when I enable the skill I eventually get "Unauthorized" at the oauth.cloud.hubitat.com page. At this point I'm not sure what credentials that page wants? The old social account? The new Hubitat account I created to login to the portal/app? Or something else? (The portal front page mentions a Hubitat cloud services account -- is that something else entirely?). Thank for any input -- Doug.
If you migrated your account, you would need to use the new credentials.
We haven't removed the social logins for existing customers that have no migrated their accounts for oauth2 connections.
Thanks Patrick. I have migrated my account. I've just now tried using the new credentials to enable the skill and now get "Linking Unsuccessful" at the skills-store.amazon.com page. (Double-checked the credentials against the Hubitat portal to ensure I was using the correct id/pw).
"Linking Unsuccessful"
Tried again, working now, about a half-hour later -- maybe something needed to propagate.
It's possible there is some cached data somewhere in your browser. Can you try incognito mode or another browser to confirm?
It's certainly possible, however I did try different browsers and browsers on different devices. However, after about half an hour and a few attempts, the login did work.
Currently I can control individual devices via Alexa, however attempting to use groups of devices defined in Alexa->Smart Home fails -- I get a response of " is not responding, please check its network connection..." -- implying, I think, that the Amazon-defined group names which worked in the past are now being treated as devices?
