Hi there,
Thanks for that updatešš¼
I guess if the other app is back to business, this one here should be able to get fixed as well 
So hopefully we can get Jamie to have a look into that
I have at least 30 flows running with that app. Would be really painful if those get useless 
Jamie? Are you there ? 
Certainly annoying but at least there is a workaround for some things - mapping command cards of the other Echo app to the error output of this appās cards is working for me now. But, of course, you need to set up new cards from the echo app instead.
So far its been running ok. Wonāt get my hopes up yet as it sounds like it was a change to the API. Iāve been using an Ikea Symfonisk (sonos) speaker for announcements in the house as well. only used the sonos/amazon echo for anything critical like house doors open or garage left open as a backup. Unfortunately i only have the one speaker and missed out on buying more before they were discontinued. Hopefully black friday sales i can pick up a sonos speaker or 2 for cheap.
Iāll definitely have some sort of backup in place as i use speakers to deter intruders/unwanted animals within my property. this is probably the first time ive had it gone down for this long. just need to find the time.
thats interesting the way you have the notifications come up @DJG3. might include that in my setup 
if there are any issues with the other app amazon echo, i would suggest posting it over here - [APP][Pro] Amazon Echo - Looking for testers and contributors as well as their github page noted on their homey app page.
Iāve created a fix, Im just going to make it so you can also add all the new devices then I will release.
Note it requires you reconnect.
Thanks for the update. Will test it out once itās available
Hi Jamie
Oh thats great News 
Thank you very much for that 
New version available in the test channel : Alexa | Homey
BEWARE the connections are still super flakey, especially reconnecting, ill update when the community figures out what is going on. (Both my app and the echo app use the exact same way to connect, so you will see the exact same issues in both)
A while ago there was an experimental way to add new devices, that was successful and this is now the only way to add devices. This means any alexa device can now be added - but not all will work as well as others, especially third party ones.
Iāve disabled Echo Auto (Gen 1), Echo Auto (Gen2), Echo Buds (Gen 2), Bose Headphones as testing in my house showed they didnāt really work, if you have other devices not working let me know.
I attempted to publish it - but Athom want to review it - honestly this process is partly why I stopped updating my apps a couple years ago - so we will see, it might just stay as a test version if it becomes to painful.
No worries. thanks for providing the update. Just installed the test version. still getting the same error i noted here - [APP][Pro] Amazon - Alexa - #2064 by loy80y
will try over the weekend when i have more time.
iām sure users will be happy at the least that it has been updated. thanks again for hard work and effort in providing this app to the community.
You can only reconnect from your local network, At a glance it looks like your using the web interface?
Thank you so much for that update.
Unfortunately it doesnāt seem to work for me yet.
athom should support you guys, putting so much knowledge, effort and time into your developmentsā¦.
Apparently there seem to be few more problems around as some other apps donāt work flawlessly anymore as well 
I wish I had some skills to join you guys 
Greets from Germany
Correct. Tried on the homey app. Connected to wifi but on a different vlan/wifi to my IoT. It should have access to the IoT wifi/network at home. Will try again later tonight and over the weekend.
I have the same error 
, same wifi.
Just tried 6.0.1 same error
20054561-0010-4c16-b6cd-015095dbb106
I had a look Kath, yep thatās the flakey error - give it a minute and the try to reconnect - then wait 10min and try again.
Whatās happening is Amazon is sending back a webpage saying down to maintenance instead of the (json) connection string - but there is no rhyme or reason behind when it shows ..
Hey Jamie,
I tried to re-connect at least 20 times in the last 40 minutes or soā¦. With different brakes in betweenā¦
Still the same 
Do we know if there is actually some maintenance work going on ?
No they have have changed something which is dropping the reconnects and making new connections harder.
iāve tried a few times also via web and homey app tonight. still same error atm.
