[RELEASE] Echo Speaks V4

⚙️ Custom Apps and Drivers
,
2337

I’m seeing this error now, too. ES is still functional for me as well.

And also still seeing the same warning I noticed after updating ES in September.

2338

I was asked by @tonesto7 himself to submit my code changes for this specific reason (that and some image issues as well). That was like a week ago - I'm hopeful he finds time to roll up that PR into his code soon!

1 Like
2339

Wasn’t that me that asked you? Or also tonesto7??

2340

actually you both did - he came at me DM

1 Like
2341

That’s great, hoping he has the time to make updates since things are clearly changing on Amazon’s end.

2342

If I can be so bold, I'm not holding my breathe. It feels like over a year since he really put some love into this tool - it's why I forked in the first place last year!

2343

I'll plan to send @tonesto7 some pizza and beer money in hopes it motivates him. I invite all that love this tool to do the same.

3 Likes
2344

If I may be so bold as to paste the author's donation link below, as another gentle encouragement for us devoted users to support his efforts...
Echo Speaks

Please consider donating if you find this integration useful.

2 Likes
2345

more info i found: this needs to be fixed in the server

ie

Screenshot 2025-11-14 211542
Screenshot 2025-11-14 2115421340×1281 90.2 KB

the url is returning this

Screenshot 2025-11-14 211719
Screenshot 2025-11-14 2117191858×953 128 KB

this fix seems to be updating some definitions and constants at least it was for home assitant
ie

2346

Outstanding…. I sent him $25. I’ve used the heck out of this app for years.

1 Like
2347

Mine is still running

1000003810
10000038101047×2293 277 KB

2348

Yes, but your cookie has not updated in over 100 days.

So you have a different issue.

IMG_0061
IMG_00611620×402 42 KB

3 Likes
2349

image

No ES problems here.

2350

Yes, but you also have not received a cookie refresh in over 180 days. So, you too, have a different issue.

1 Like
2351

That is sorta what I was implying....I don't seem to have any issues. And I am somewhat reluctant to update my cookie knowing that others are having problems. :slight_smile:

1 Like
2352

I understand, but you still have an issue. A cookie not refreshing at the scheduled interval indicates an issue with your ES server. Default refresh is every 5 days.

I now experience the latest authentication issue mentioned above, but my cookie still refreshes every 5 days. You can see this in my screenshot above.

2353

I'll prolly get wonderful feedback on this - but I don't have a problem and mine refresh is 273 day old.
image

Let's review. When I first started to use ES you ran it at Heroku which was complex and painful. Then Heroku wanted to charge money and a local tool was created. We fought with that for a month or two and everyone seemed to get past it. Then the ES status app (thanks to @thebearmay I think) came out so we could monitor. AT THAT TIME, if your cookie got old, you had to manually go into your browser, muck with some stuff and get your cookie refreshed - but the local server and the cookie status gave us a way out.
Months (5? 6?) later Amazon tweaked and the cookie no longer had an expiration. No one here really noticed that I recall (I try to read all discussions about this stuff) and the Cookie problem really was no longer. I left my ES Cookie status on screen as an ODE to @thebearmay and @tonesto7 as a tribute, but I ran perfectly for the next year or more.
Recently everyone is excited because the original dev put some love and care into this amazing tool. I had forked it - maybe 1.5 years ago so I had gone my own way. But @tonesto7 is by far, the best person to bring us forward a little bit now that A+ is out.
I have been hopeful, but not really holding my breath - I rolled some stuff back into his latest drivers so some errors and image failures stop but we all get the mornning '404' error but it's not related to cookies AFAIK. Anyways. thats the little history I can recall. ES is a critical part to my HE but the code is pretty sophisticated stuff so I don't see any other dev that can step in to help on this. I think we just need to be patient and coerce the man himself to give his baby some attention!

2 Likes
2354

It can run on the same cookie for a long (undetermined) length of time. It will work fine, until one day it doesn't. The refresh that ES does is obviously much more often than needed but it ensures no interruption of service.

1 Like
2355

Agreed. I'm taking the "if it's not broken, don't fix it" approach and I'm not going to refresh my cookie. I'm not sure if that makes any difference at all.

1 Like
2356

Agree, mine is at 323 days, no issues. If it fails I will fire up my es container and refresh it

1 Like