The list should already show up without typing anything, are you seeing nothing at all here?
Can you enable the additional logging in the app settings, restart the app, wait a bit and then send me a diagnostic report?
I hope you will see something
a501720f-a862-4637-83f2-3d05f5f1e56e
@Jeremy_Gout just out of curiosity, if in the Amazon Alexa mobile app you go to your Echo settings / WiFi Network / Advanced Network Information and look under the heading Network Quality… what does it say for Signal Strength and Noise? And just above that it should also say what Frequency in GHz it is using?
And if you try one of the other action cards that has a drop down list of options, does that populate okay?
Is your account registered to amazon.com or amazon.fr? Or did you ever change countries or anything? Are you by any chance french canadian?
It seems like the app is for whatever reason trying to use the us server for your account but it does not match with your language / where your devices are registered to. While letting the diagnostic logs enabled can you logout, restart the app and login again and then send me another report?
I might add back the option for a manual country selection, but I want to confirm your specific account setup first.
Thanks for you comment @Drako74
signal strengh and noise
- F : 2.4Ghz
- S : good
- N : bad - can i change that ?
Any other action card display well the list.
My account is registered on amazon.fr
Selected country in Amazon settings : France (not canadian 
)
Before the connection was authorized, I had an error message “CannotConnect: conection error during GET”
Now it’s OK : here the report number : e49018ff-6c08-4bbe-a654-f102328b2647
Can you check for me if it works now? From the logs it looks like that the region was now correctly resolved after logging in again.
Yes, you can improve your WiFi, but unfortunately it’s not an exact science… I can’t offer you a magic bullet that will just fix it. I suggest looking at where your WiFi access point (or router if you just use ISP provided WiFi) is located, checking for sources on interference near it like other electronics or large metal objects. And similar for your Echo.
You could also try installing a WiFi analyser app on your phone, and look to see if the frequency band your WiFi is using is being drowned out by neighbours WiFi signals. And if so change you WiFi channel to a less congested one.
Ideally the smaller the number for Signal strength the better (-20 to -40dBm is excellent strong signal, -70 to -90dBm is pants). And the reverse for Noise, the larger the negative number the better… anything larger than -70dBm is fine, anything larger than -90dBm is excellent.
Also, I don’t know what Echo devices you are using, but if they support 5GHz WiFi, getting them to use it will improve their responsiveness a fair bit. As the 2.4GHz frequency band is massively congested… used by Bluetooth, Zigbee, Microwave ovens (every time I use the microwave my Perfect Draft beer machine goes off-line because they are both in the kitchen, and the PD only uses 2.4GHz WiFi… first world problems 
)
Unfortunately my guess was wrong, and this won’t fix your routines problem as that’s an Amazon nationality at authentication problem. But if you can improve your WiFi at all, it will make your home network a happier place 
Just out of sheer curiosity, why was that removed?
I’ve pushed a new version on test with some additonal logging and a mechanism to verify the region after the connection is established. Give this a shot and if you still run into problems send me another report.
Because users kept getting it wrong 
And it’s already part of your account information either way.
Fair point… I’ve worked in IT support and systems admin enough years to totally understand that
Without another diagnostic report, my best guess would be that you didn’t use a new OTP code during the login (it’s only valid 30s and you need to use a new one for every initial login).
Here the last report created after failed connection: 89ffe82a-b012-4cd2-b5c7-95d74c1d1790
I use (and change) for every connection tentative the OTP code but GET error is still appearing..
I even tried disabling two-factor authentication on Amazon and logging in without an OTP on Homey but the connection didn’t worked
OTP is a hard requirement so you can’t remove that.
Which version of the app are you using now? I can’t find any crash reports with that id. But I’m also not sure if Athom forwards those for uncertified test versions to be honest.
