Yes all of us are, scroll up to see more details and work around
The fork is public, if anyone wants to try it. It successfully refreshes the cookies from the HE app. GitHub - jdc72/EchoSpeaksServer: Echo Speaks Server with fixes · GitHub
I forked this to my own repository with lowercase name because everything complains about the caps in the name, and got the server setup in Docker on my Synology NAS. I want to keep this version separate from my main server which is running as a Docker container on my Unraid server.
@JDC I am up and running and logged into Amazon with a successful cookie refresh. Is there any indicator that one is successfully using your forked version?
I just changed to GitHub - jdc72/echo-speaks-server · GitHub as well. You can check the logs, as I enabled more logging for cookie refreshes. (It’s not excessive, since the server is not hit very often to create cookies.)
Not sure if this helps, but I built these:
There is a exe for mac. windows and linux. It runs a login server to get an amazon cookie. You can run it as often as needed to get a cookie refresh. What makes it unique is it does not need to run all the time, just fire it up when you need a cookie refresh. It automatically send the new cookie/token to the hub, and bingol you are good to go.
If you have cookie refresh working you probably don’t need this, BUT it eliminites the need for the echo-speaks-server entirely. While the latter required the hub app to trigger a login, this does not. You just run this when ever you like or need to. Then kill it. My token dies every 3 days no matter what I do so I built this.
This app on Linux x86_64 works. Just needed the chmod +x. Linux Mint 22.2
Windows .exe works beautifully. Ran it as a quick test in case it is ever needed. Thanks for your efforts on this.
You’re welcome. I am still working on the refresh, will update when/if I get it working
Mine definitely has to be re-authorized very 6 days exactly. I went in and deleted about 30 old “echo speaks #22 etc.” device on the amazon page. So @kahn-hubitat what did you do exactly that has you going on 29 days without reauthorizing? Mine started on 6/16 and has needed to be reauthorized every 6 days since.
Not pushing the solution, but this was configured specifically for a Pi to replace the ES server, I am sure it would run on other things, but...I have no time to test and/or support.
As an alternate solution/backup to everything else I have setup for Echo Speaks, I managed to get this running in Docker on Unraid.
It works well.
@Bloodtick_Jones does your solution refresh the cookie automatically, or does it still require a manual refresh?
Whisper will refresh on its own when the cookie gets old. Right now that is hardcoded at 10 days.
If you configure it as the Echo Speaks server, it also listens for the refresh request from Echo Speaks and will refresh/send the updated cookie back based on your Echo Speaks refresh schedule. I think the ES default is 5 days. I have mine set in ES to 2 days just to make sure everything is working, and it has been solid for a couple of weeks.
I've updated the server image for the Docker container and the ES code under applications. However, ES cookie checking still only shows 5 days until the next renewal. Am I assuming this is not working correctly?
Maybe I didn't import the docker image correctly, but I'm pointing it to the location that's listed above so I'm not sure what I'm doing wrong.
For me, it still bombed out after the time listed above. I cannot seem to get past the five-day.
I guess I’ll find out in 9 hours.
