does not resolve that.
entering also 2nd factor to authenticate
I have exactly the same issue. Just tried on my pc and itās the same. Seems like the page has been moved
1 Like
I just one of my old Homey proās to test this out again, clean install and went through the steps. Eu server, username, password, mfa token and I ended up with the success page.
So it is still working for me.
After a succesfull login it shows a page generated from code by the Homey that harvest the tokens and tells you it has been succesfull and you can close it.
So its not a Amazon page at that point.
In fact all steps are reverse proxy versions of the Amazon pages through Homey so that Jamie can capture that last step.
It makes no sense at all why it would work for the first couple of pages and than end up with a Amazon generated page not found.
In my reference case that step, after username and password is the MFA step.
@kai.wagner.83 states that they do perform the MFA step (no screenshot supplied but I believe them) so after the MFA step only the token generation happens.
Like I said, just tested it on the same EU server, and all steps worked. Including (app based) MFA.
The browser used doesnt supply URLās in the screenshots, can either of you tell me what URL your on when this error is shown?
Thanks Kaoh for testing and for sharing your steps.
I just tried it and it works, BUT apparently the 2-Factor-Authentication on my Amazon account was not enabled even though I always got the verification code when logging in.
So I enabled it an the verification code (OTP) this time worked and I could connect my devices.
Iām now one of the 99% who have no problems! I replaced by mesh Wi-Fi and all problems have disappeared. Connection to all my Alexa devices is rock solid and everything works perfectly.
Iāve never had problems with my mesh Wi-Fi but clearly it wasnāt man enough for the job.
In case any other unlucky people read this, here was my solution: I retired my BT Whole Home mesh Wi-Fi and replaced it with TP-Link Deco XE75 mesh Wi-Fi system.
Hope this helps someone.
2 Likes
It might still ādisconnectā every couple of weeks/months, due to authentication, you can create a simple flow to get a notification and authenticate again when needed
Can you make the Sonos Beam 2 supported?
Same issue here, everytime I try to connect my Alexa Echos, it sends me to the dogs page on Amazon. From what I see, I think this happens because Amazon only allow login via https, when homey establishes the connection it s only http.
This happens with sms MFA and also with App MFA
Would be glad If someone had a hint how to fix this 
Since its a reverse proxy method, the homey retrieves the pages before presenting them, it does that using https.only the local network presentation to your phone is done without.
This works as described above for many people so its not a general rule thats breaking it in your (and some others) case.
It is clear thatās mfa related, but since you tried multiple setups its still unclear what setup exactly breaks it for some.
Previous someone posted that they did not have mfa enabled while the page was presented anyway, enabling fixed the process for them.
If you would login to Amazon directly, in a private/incognito session, what screens do you normally get presented with by Amazon?
Thank you for your response!
I checked what will happen if I log in to Amazon with a private window on iPhone Safari.
It works properly without any hesitation. I get my sms with the code and then I am logged in.
When doing this within the homey pro app, and the dogs page pops up, you can click on sign in , then safari tells me that it couldnāt establish the connection, since there is no https O.O
Cheers
Note: this happens on windows laptop too
I got it to workā¦
I disabled and enabled the OTP on Amazon again and suddenly it worked. Everybody who has this problem, log into your account and activate / turn off and on again the OTP. This error had driven me nuts for days, hope to help somebody
Thank you Kaoh for your help too!
Cheers
At least we have a clear trend now for this issue 
I enabled the OTP and it is working now
Just an idea for some added functionality that would be awesome to have:
Thereās an APĆ to manage Alexa Alarms: Alarms REST API | Alexa Voice Service (amazon.com)
It would be nice if we can get the alarm details for a certain device. (Just the next ebabled/scheduled alarm clock time would be enough) So we can create flows based on the time our alarm clock has been set. This way you could create a flow to heat the bathroom so it is warm when you get out of bed.
I can already trigger a Homey flow when an Alexa alarm is dismissed, but that is only good for automations that have to trigger after when you get out of bed.
Heating the bathroom needs to be done in advance and for this it would be nice to know when Iām scheduled to get out of bed
Using the Alexa devices as an alarm clock is super convenient, since you can just ask Alexa to wake you up at a certain time and your alarm clock is set. Times can vary greatly depending on what my work schedule is, so having the ability to get the alarm clock time is very useful.
1 Like
Was ist das?
What is this?
Hi, I have not found something in the top how to report an issue, so sorry I have overlooked something, happy to redo my thing if you point me in the right direction.
My issue:
I am using version 5.4.3 experimantel, because I want to connect an Dot 5. gen
I have a door bell flow configured:
When dorbell rings
Then:
- Echo dot 2 gen volume to 100%
- Echo dot 2 gen play sound dorbell3: delay 2 sec
- same: delay 3 sec
- echo dot 2 gen volume to 25%
And the same for cards for the Gen 5 Echo
The problem I am running into is, that for both devices the first step works, setting the volume to 100.
The other step will time out after 30 seconds
And then something like 1-2 minutes later suddenly the other steps are performed in the right order and at the end the volume is back to 25%.
Is there something wrong on my way doing it or is this an limitation by Amazon or a bug worth investigating?
Thanks for the support and this great App
I just tried this on my setup and this works perfectly. If you have delays you might have to change the server region that you are connected to in the Alexa app setup.
I live in Belgium but my devices are connected to the US servers. Initially I set up my Homey Alexa app with the EU servers but then I also got many delaysā¦ So you can try to change servers and see if this helps.
Next to this, the api is heavily throttled. So delaying steps really can make a difference. Specially if you have many devices included in your tasks.
I ended up making many Alexa routines to interact with multiple echos, or multi step operations so you can trigger those by one call from homey, start routine.
@Jamie I just saw that the beta version of the app now has an experimental device through which Iām able to add my Echo Dot 5. Generation, which is great!
Is the āCan I add a new alexa device?ā section still relevant, because I can provide you with everything needed to support this new device generation or is this currently experimental device the way forward and no new device info is needed?
One Time Password, think 2nd factor to authenticate
