you didnt do it correctly most likely
Got mine set to 30 days and I am at 8 days and all is well.
Same here
Anyone else seeing this? Seems to have hapenned after updating to latest beta. Trying a roll back now.
**EDIT - Rolling back to previous beta fixed it. Will try another update to see what happens.
**EDIT 2 - The update to the latest beta kills this app.
**EDIT 3 - Hate to say it, but I think this app is seeing it's final nail in the coffin.
That is a bug in the beta, not the app.
Unless Hubitat has announced breaking changes in the update.
Most of our breaking changes are unannounced. And unintentional 
Most.....
Yes, I understand that. Didn't realize it was a beta issue until after I initially posted here and hence the reason for my edits.
I’m seeing the same errors and the AP wont open, but it is still running and working, ie making announcements.
Everyone, you might want to check your Amazon account too…I found about 50+ devices registered on Amazon after my various auth restarts. I am not sure if it hurts anything, but…
Nope, no issue with that for me.
Thanks for the link. I also had over 50+ devices. Some where old devices that I no longer have or use along with the 47th Echo Speaks.
I didn’t see it at first. I was looking at the devices not below in “Amazon apps installed on devices”. Alexa app showed 50+ devices.
Most of the EchoSpeak duplicate devices were from the days when I was cutting over to the local instance on Proxmox. The latest duplicates seem to align to each time I have to manually re-authorize.
I built a small standalone project called Echo Whispers Server for local Echo/Alexa text-to-speech control. I also added some Echo Speaks compatibility, so it may be useful to Hubitat users until the current cookie server issue gets resolved.
Fair warning: this was built for my own setup so buyer beware, your mileage may vary, and my support will likely be pretty limited.
The docs are mostly AI-generated, and I have not exactly given them a full legal or valid review.
Should look something like this if configured correctly. Once you add the Echo Speaks App Callback URL, hit Save Settings, then Send Info, and Send Cookie.
That should configure Echo Speaks to start listening to this cookie server.
I forked echo speaks and working on solving 2 issues: 1. My version caches the token so the app does not need to hit the echo speaks server. 2. It also knows how to refresh the token by itself. The plan is not need the server at all. I have a simple page to login to amazon with, no need for the server.
Nice. I attempted something earlier and ran against Hubitat environment software limits. Would be awesome not to need a standalone solution.
I also created a forked version that successfully refreshes tokens. I’ve tested it running locally (not inside a container) and deployed in Heroku. While doing so, I noticed that Apollo77 made a similar update to its GitHub code.
Is this fork available for public usage?