Please also try new test version 1.3.1 to see if that improves things. If not please send me a diagnostic report after you experienced an error.
No connection to Amazon server possible.
Reported in
3660fcf1-b68d-4200-a402-e6af9e5b213d
Well you are not logged in. Can you go to the settings of the app and login?
Yes, that did the trick. I deleted the app before, so I had to renew the login. Let’s see how stable it is.Thank you very much for your help 
.
Still connected. Looks good
Same here, once logged in, 1.3.1 seems to be more stable and durable.
Looks good, I installed 1.3.1 as soon as it came out.
v 1.3.1 held connection for 2 days. now it disconnected again
1.3.1 not even out 23 hours yet…
Must be longer
… but not important.
Unfortunately the result is the same.
Though, thank you very much for your effort to provide a stable app.
The very obvious AI summary of what 1.3.1 now does about connection problems:
When the connection to Amazon drops, the app automatically tries to reconnect — starting after 30 seconds, then waiting longer between each attempt (up to 15 minutes), for a maximum of 10 tries. Every 5 minutes, the app also checks in the background whether the connection is still alive, so it can catch silent disconnects.
If the issue is a temporary network problem (DNS failure, timeout, connection reset), the app will keep retrying. If it turns out your login session has expired, the app stops retrying and asks you to re-authenticate through the app settings.
If all 10 reconnect attempts fail (e.g. during a longer network outage), the app stops retrying to avoid unnecessary load. In that case, you’ll need to manually reconnect by opening the app settings and re-authenticating. This also applies when Amazon invalidates your session — automatic recovery isn’t possible then, since it requires you to log in through a browser.
While disconnected, your Echo devices will show as “unavailable” in Homey. Once the connection is restored, they automatically become available again and their status (volume, playback, etc.) is refreshed.
Errors are also available as a flow trigger, so you can build automations to notify yourself if something goes wrong.
That said, an unstable internet connection or an unreliable DNS service (such as the default one provided by your ISP) can still cause issues in accessing the API and lead to devices going offline. Another factor beyond my control is the expiration of authentication from Amazon.
Personally, I have consistently been able to maintain a connection for a period ranging from 4 to 12 weeks. This duration is sufficient for me to manually reconnect without significant inconvenience. However, I am unable to reproduce the issue that some users are experiencing, which suggests that the only plausible explanation for frequent disconnects are local network conditions or an issue related to their Amazon account.
From my perspective, I have taken all steps I could think of to address the network-related aspects of the problem (although some edge cases may still persist). Therefore, I hope that version 1.3.1 will be an overall improvement for users. However, I am unable to provide any further assistance. I strongly encourage users who are still experiencing problems to troubleshoot and debug the app themselves. AI agents have made it easier than ever to begin projects and explore unfamiliar technologies.
I will release the new version and its source code to the public in the evening.
Just a bit of info for anyone having re-connect issues after putting account details in where the app says “you can now close this window” and the underlying page says “connect” sending you through a loop, I found if you ignore that close the popup connection window and click connect rapidly until it says connected. Not usre if there is a bug between the two pages
The underlying page just takes 2-3 seconds to update the status.
Thanks for the info staeff, thought I was going nuts, amazon being a pain at moment
