Alexa control didn't work for me this morning, 1 week after last reboot, so it's a general issue. And since it's on a hub I have full control over, I can investigate properly.
Edit: the skill recovered without a reboot, but not right away. Interesting...
@gopher.ny how long after the last reboot did it recover itself? Mine has never come back on its own but I've never given it more than maybe 16 hours past when it fails.
My next failure should happen Weds morning. Happy to leave it broken to see if it comes back eventually.
Looks like last hub startup on the Alexa hub was at 2021-02-02 13:40 UTC time, with no proper shutdown. My guess is power might have blinked during the snowstorm. That new timing means Alexa should be out in about an hour from now, not yesterday as I have thought.
It's been 7 days and 5 minutes since last reboot. Tested a few times this morning -- cloud dashboards and Alexa were working as recently as 10 minutes ago but are now offline again. The failure after 7 days of uptime is truly like clockwork here.
@gopher.ny anything you want to check here or on your end before I reboot?
Got as much information as I could out of the hub - thank you.
I have a pretty good idea what times out, just can't figure how it happens. None of us at Hubitat can reproduce it. Sometimes Alexa ignores me, but there's no pattern, and it doesn't require a reboot.
It's on my list of things to be implemented in 2.2.6. The idea is to simply obtain another Alexa token before a week passes. I haven't been able to reproduce the behavior, and a weeklong testing cycle doesn't help.
@d114, did running 2.2.5.131 as opposed to 2.2.5.119 happen make a difference?
There was a DNS issue in 119 (it defaulted to DNS server 8.8.8.8) that got fixed in later revisions.
I am experiencing this as well. I haven't been monitoring the exact 7 day period but I have been rebooting my hub when Alexa wouldn't work. But exact problem for a bit now just didn't realize it. I came to search for an answer and because I was tired of the manual reboots all of the time and stumbled on this thread.
What platform version is on your hub? And, until there is a resolution, you should consider setting up a scheduled weekly/daily reboot that happens automatically.
I have not been able to reproduce the issue so far. It just doesn't seem to happen for me, and each attempt has to wait for at least week, so testing isn't a quick process.
For what it's worth, there will be an easy, built in way to set up a scheduled reboot in the next firmware version.
Sorry, Went on vacation and just got back yesterday. Been gone for more than a week. Had to reboot the device though to get Alexa talking with my devices again.
I know there was talk about it before in this thread but I am using DHCP with a reservation. I am going to set it to static on both my router and hub and see if there is a different result next Monday.
Here is my info:
Hub Details
Hubitat Elevation® Platform Version
2.2.7.126
Hardware Version
Rev C-7
Hub UID
3272d87d--4aa6-ae69-********
IP Address
192.168.1.178
MAC Address
34:E1:D1:80:CD:62
Default Text To Speech (TTS) Voice
Kimberly, Female, US English
Current Hub Time (as of last page load)
2021-06-14 9:54:38 PM MDT Update Time from Browser Time