It took 5 complete run throughs. But now appears to be synced again with the correct number of days till next refresh
So, this is the way to fix it once it breaks (remedial or corrective action). What is the "why it broke" (root cause) and the "How to prevent" (preventative action)?
Just a data point. I started receiving the error (every hour for days, on the phone!). Finally got around to trying to fix it. For me, just logging back into Amazon took care of it. For now.
Same here, just had to log back in again. Noticed an echo speaks routine was not making it’s announcement. Went through the logs on all my rules and everything seemed ok. So I opened Echo speaks and had a error message saying I wasn’t logged in to Amazon.
I just had to login again. Weird
My guess is something on the Amazon side of things has changed/keeps changing to cause this. I have 2 more days until my next refresh, so who knows what will happen?
I’m not sure if @tonesto7 is still monitoring this thread or even actively maintaining this app. Unfortunately, it seems as if it has seen better days and may eventually cease functioning completely at this point. Might be time for me to look into Homepods.
And I just made the switch for my speakers from the chromecast integration LOL
yes mine expired now a 2nd time. somehting is broken.
I am due to refresh in 4 1/2 hours. Will post results after.
Give it a bit after the actual refresh time, as it can take a little while to fully show that is has refreshed.
Thanks for posting that. I’m no expert, but it seems to me there’s been a change on the Amazon side that is not allowing for/accepting the scheduled cookie refresh. So a fresh login seems to be the only way around that for now.
I’m going to see if my setup continues to work when the cookie fails to refresh in 2 days.
I’ve had to re-do mine every day for the last 3 days, it’s very odd.
PS, Im running mine on a local server.
There appears to be something going on over at amazon. The native Amazon Echo skill is throwing bad server errors also
Error making Call to Alexa message gateway: < new weird error in logs??
In addition, when logging back in to the server this afternoon, it made me change my password - even with the OTP app matching.
I just checked mine again, also running on a local server. Still says connected and last update 1 day and 7 hours ago. I will try to remember to check each day and see if/when it disconnects again.
I concur with the group here, the scheduled cookie renewal isn’t working, I had to fall back to my legacy lannouncer hack with an old cell phone and wire the cell phone to my intercom to get voice announcements working at least for weather and other voice alerts.
As for other use cases like commanding music to play and other items it’s a loss but not mission critical.
Looks like it is happening on the HA side as well. Not 100% sure it is the same issue. But very similar.
I’ve got a couple of minis and they work well, might be time to buy some more. Apparently there’s a some new ones in the works.
