I haven't modified the Echo Speaks V4 apps code since it was last updated 09/11/2025. While I did have the "Auth Status" issue, it appears to be gone as of 11/29:
Last message (and was spammed a lot with): EchoApp (v4.3.0.1) | 400 validCookieResp
1 Like
Same here, my Auth status now has a check mark.
1 Like
Same with mine. Auth Status is now Green
Hmm, I hadn’t tried manually refreshing the cookie during this time, in case it somehow resulted in loss of the old cookie info but no new cookie.
But refreshing the cookie manually from the ES Hubitat app page seems to have done the trick.
3 Likes
This question is about track data of Amazon music on an Echo. The music starts playing before the HE Echo device track data is updated, by about 2-5 seconds. I am cycling between Amazon playlists, Christmas Classics music and Christian Christmas music, changing playlists every 3 songs. But the next song starts playing, for about 3 seconds, before the track data updates. That messes up my programming to cycle through the above playlists. I'm changing playlists based on when the track data changes (ie the next song starts). Is this track data delay inherent to ES? Suggestions on programming?
Is anyone able to use this app to get the length of the song playing on an echo?
When playing a song on my Echo, when looking at the Echo device, the song information falls off the right of the screen. I have tried to adjust the text and window sizes, but it is still truncated. Any suggestions on how I can get all of the data to fit on my screen?
I just went through a setup, setup Heroku and when trying to authenticate to Amazon in the Heroku app, im getting a 404 page. Any suggestions? Also looks like Heroku is no longer free... i did add my card just to get through the install, but wonder what this will cost.,, maybe better to setup own server?
Thanks
There are multiple discussions on the Heroku topic. Just do a search for "heroku" and browse the results. Personally, I don't mind paying the $5 a month. I have never set up a Docker container before, so I took the "easy" way out. YMMV.
1 Like
1 Like
I dont either if it works. May move to own server later though anyway.
I ran through my guide myself not too long ago after someone else said it was not working, it does in fact work correctly still if you follow the guide I posted above. That being said, if you have any always-on machine in your home it is very easy to setup locally. Even if its not always on, just on most of the time would work as well.
5 Likes
I used your guide to set mine up in WSL2 on windows 11. Works like a charm
1 Like
I can't get the cookie setup to complete. Getting timeouts at this address:
Proxy-Error: Error: connect ETIMEDOUT 92.249.37.147:443
Im trying different devices, I also don't see any firewall blocking going on.
Heres the docker errors:
cho-Speaks | getRemoteCookie...
Echo-Speaks | 1-14-2026 - 12:13:51pm debug: config(/) page requested
Echo-Speaks | Alexa-Cookie: Use as Login-Amazon-URL: amazon.com
Echo-Speaks | Alexa-Cookie: Use as Base-Amazon-URL: amazon.com
Echo-Speaks | Alexa-Cookie: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
Echo-Speaks | Alexa-Cookie: Use as Accept-Language: en-US
Echo-Speaks | Alexa-Cookie: Proxy-Mode enabled if needed: 192.168.0.95:8091 to listen on 0.0.0.0
Echo-Speaks | Proxy Init: loaded temp data store ■■■ fallback former data
Echo-Speaks | Proxy Init: reuse frc from former data
Echo-Speaks | Proxy Init: reuse map-md from former data
Echo-Speaks | Proxy Init: reuse deviceId from former data
Echo-Speaks | 1-14-2026 - 12:13:52pm error: generateAlexaCookie: You can try to get the cookie manually by opening http://192.168.0.95:8091/ with your browser.
Echo-Speaks | 1-14-2026 - 12:13:52pm debug: Alexa Login Status: There was an error
Echo-Speaks | getRemoteCookie...
Echo-Speaks | 1-14-2026 - 12:13:52pm debug: config(/) page requested
Echo-Speaks | 1-14-2026 - 12:13:52pm info: ** ServerVersion Sent to Hubitat Endpoint Successfully! **
Echo-Speaks | Alexa-Cookie: Use as Login-Amazon-URL: amazon.com
Echo-Speaks | Alexa-Cookie: Use as Base-Amazon-URL: amazon.com
Echo-Speaks | Alexa-Cookie: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
Echo-Speaks | Alexa-Cookie: Use as Accept-Language: en-US
Echo-Speaks | Alexa-Cookie: Proxy-Mode enabled if needed: 192.168.0.95:8091 to listen on 0.0.0.0
Echo-Speaks | Proxy Init: loaded temp data store ■■■ fallback former data
Echo-Speaks | Proxy Init: reuse frc from former data
Echo-Speaks | Proxy Init: reuse map-md from former data
Echo-Speaks | Proxy Init: reuse deviceId from former data
Echo-Speaks | 1-14-2026 - 12:13:52pm error: generateAlexaCookie: You can try to get the cookie manually by opening http://192.168.0.95:8091/ with your browser.
Echo-Speaks | 1-14-2026 - 12:13:52pm debug: Alexa Login Status: There was an error
Echo-Speaks | 1-14-2026 - 12:13:53pm info: Checking for Server Version Updates...
Echo-Speaks | 1-14-2026 - 12:13:53pm info: ** ServerVersion Sent to Hubitat Endpoint Successfully! **
Echo-Speaks | 1-14-2026 - 12:13:54pm info: Server Version is Up-to-Date.
Echo-Speaks | Router: /proxy / GET / {"host":"192.168.0.95:8091","user-agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:143.0) Gecko/20100101 Firefox/143.0","accept":"text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8","accept-language":"en-US,en;q=0.5","accept-encoding":"gzip, deflate","connection":"keep-alive","referer":"http://192.168.0.95:8091/","upgrade-insecure-requests":"1","priority":"u=0, i"}
Echo-Speaks | Alexa-Cookie: Initial Page Request: Amazon Sign-In
Echo-Speaks | Alexa-Cookie: Proxy-Request: GET /proxy
Echo-Speaks | Alexa-Cookie: Headers: {"priority":"u=0, i","upgrade-insecure-requests":"1","referer":"http://192.168.0.95:8091/","connection":"close","accept-encoding":"gzip, deflate","accept-language":"en-US","accept":"text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8","user-agent":"Mozilla/5.0 (iPhone; CPU iPhone OS 13_5_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 PitanguiBridge/2.2.345247.0-[HARDWARE=iPhone10_4][SOFTWARE=13.5.1]","host":"www.amazon.com","authority":"www.amazon.com"}
Seems to have a cookie, cant clear it.
Alexa-Cookie: Headers: {"priority":"u=0, i","upgrade-insecure-requests":"1","referer":"http://192.168.0.95:8091/","connection":"close","accept-encoding":"gzip, deflate","accept-language":"en-US","accept":"text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8","user-agent":"Mozilla/5.0 (iPhone; CPU iPhone OS 13_5_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 PitanguiBridge/2.2.345247.0-[HARDWARE=iPhone10_4][SOFTWARE=13.5.1]","host":"www.amazon.com","authority":"www.amazon.com","cookie":"frc=(redacted cookie)"}
1 Like
I must have missed the memo where Echo Show 15's no longer could process TTS!? Both of mine show that they don't have that capability anymore. ugh!
Must be just the newer generation. My Gen 1 Show 15 still works, but I see that my Gen 2 Show 21 doesn't.
Just found that if you use the 'sequence' command instead of text to speech, it does actually play the text. hmmm. volume::40,, speak::your text here,,
Confirmed this also works in WebCore (using the execute sequence command) ! Winning, and shhh so this doesnt get taken away 
1 Like
Finally figured it out. If you want to add it to Echo Speaks maybe very cool. Take a look here GitHub - gilderman/Amazon-Thermostat: Alexa based integration with Amazon Thermostat (requires) Echo Speaks · GitHub
just realized the echo all devices created is no longer working..
no errors but no sounds come out..
each individual device still works fine..
not sure if this is a new issue with hubitat but my feeling is it is something with the echo speaks.
there are no errors in the app or the device logs even with debugging on.
this is going to be a major issue to workaround as i have a lot of warning rules accross 4 hubs and locations that rely on this to give me alerts.