About once a week Alexa integration will completely fail to interact with any devices.
Asking Alexa to turn any device on/off (Zigbee generic bulbs, outlets, ZWave generic outlets) results in Alexa saying "[device] is not responding." The requested operation is not completed either.
Inquiries for motion sensor status e.g. asking for the temperature on a Generic Zigbee Motion Sensor results in the same 'not responding' message.
I have enabled the 'respond immediately without waiting for device' option in the Amazon Echo skill per instructions there "If you are getting the 'device not responding' message from Alexa enable the below option:." This setting has had no effect on my issue.
The only workaround so far is to reboot the hub via the web UI. The issue will reoccur approximately a week later. This has happened 3 or 4 times so far, or in other terms happened about once a week since I set up my hub about 4 weeks ago.
Hubitat support claimed 'known issue' but also referred me to the community for further guidance.
Starting around the same time as your post, I too am occasionally getting Alexa saying "[device] is not responding." I fiddled with my hub, removed most tasks, thought maybe my hub was bogging down, but to no avail.
I would love to be able to get more logs out of this thing and figure out why, for the past 12+ weeks, Alexa integration has broken after exactly one week of uptime.
Support is useless. Aside from acknowledging my case, vague statements about engineering 'looking into it' and confirmation that Bobby from support NEVER had this problem with HIS Alexa, I have nothing to go on here. I am happy to get into the weeds and help solve this but there is no information to work with here.
I haven't seen any other reports on this forum about this happening. I would have to believe that if it was a widespread issue, there would be dozens of people complaining about it being broken. Hence the engineering team having to dig further into it and trying to find a very rare bug, if it even exists in the software.
I suspect there is something unique to your network or your hub that is causing this, or it is a very, very rare bug.
That's all well and good that it's a rare issue, but I'm hunting for how to figure out what's so 'unique' about my network and I cannot even find information on how I might troubleshoot this this.
Why is there nothing in my logs? Is it that there are more detailed logs somewhere else on the hub that I just don't have info on how to access? Or is the failure external to the hub on a cloud server that I can't see the logs for?
They don't dig. They close the case. When I reach out a week later to report that it failed again after additional troubleshooting that I did, it's like it's the first time I'm reaching out to them.
If they can't find anything, and everyone else is working, what should they do? They don't have infinite resources.
Again, I suspect something unique to your particular setup. I am not sure how to troubleshoot this exactly, but I would start with logs. You sure there are no errors of any type there?
You also could or should take screenshots of your gear icon menu pages for this app. Probably shouldn't post them publicly, but at some point support will likely want to or need to see them. And you also can look at things like your token refresh, token expiration, and so on, and compare it before and after.
Just one quick idea... Do you have your router's DHCP server configured to reserve an IP address for your Hubitat hub? Is there any chance your hub is being assigned a new IP address after its DHCP lease expires? I know this temporarily has disconnected the hub from cloud service for some users. Using the same LAN IP address helps to prevent this loss of connectivity.
I get that they don't have infinite resources, but I don't get the impression that they can't find anything. I get the impression they aren't looking, nor are they asking me ANY follow up questions for what I should look for.
I would start with logs. You sure there are no errors of any type there?
Yes, I'm sure. I'm sure I'm sure.
gear icon menu pages
What? Where?
token refresh
Again, can you elaborate? What/where is this and how is it relevant?
Are you using a mesh router? And if so, have you restricted the Echo to the nearest access point (or the one that works the best) so it’s not jumping back and fourth between them?
It's not specific to any one Echo device. Control of the smart devices is also possible via Axela smart phone app and web UI. Those are also affected by this weekly issue.
That doesn’t answer the question I had at all. Not talking about your Echo devices in particular. I asked if you have a Mesh WiFi router. These questions are to try to help.
symbol next to the app in question. Scroll down through that page that comes up.
