again not seeing it. I think this might have something to do with this being the test version. I have now published it as the live version. so lets try if I’m now seeing a report when you submit it.
I upload the latest version. Do you see this one ?
96bc2157-a23a-4498-9a62-10b6e0dbb7d1
Your sign-in is actually working — Amazon accepted the password and the 2-step code. What fails is your network looking up the address of alexa.amazon.fr (the European Alexa server your account belongs to): your DNS returns “no address” for it, while alexa.amazon.com resolves normally on the same Homey. It worked earlier today at 10:59, so something changed on your network since.
Please check, in this order:
1. If you run a DNS blocker (Pi-hole, AdGuard Home, or blocking/“privacy” features on your router), look in its query log for alexa.amazon.fr, layla.amazon.com and d3rsqup3tcxj1a.cloudfront.net, and allow them. layla.amazon.com is on several blocklists and is exactly the address this chain needs.
2. Restart your router (or flush its DNS cache) — a stale “not found” answer can stick for hours.
3. From a computer or phone on the same Wi-Fi, run nslookup alexa.amazon.fr. It should return an address like 99.84.94.61. If it returns nothing there too, it’s your network’s DNS, not Homey. Setting your router’s DNS to 1.1.1.1 or 8.8.8.8 fixes that class of problem.
Please don’t keep re-signing in — it can’t help with a DNS problem, and each attempt registers another device on your Amazon account (you’re at 41 now; you can prune the old “AioAmazonDevices” entries under Amazon’s Content & Devices).
Hello again
sadly I have followed all the step you are mentioning above in the order but I have still the same message “CannotConnect: Connection error during GET”.
- I have noDNS blocker and I have checked just in case directly in the routeur parameter
- I have flush all cache (computer, router and browser) + restart the router
- address was well displayed and I still change for 1.1.1.1 or/and 8.8.8.8
I have unregistered all Eco devices in my amazon account (a lot of them !!)
Thanks again for all, I am the only one to face this issue, so I will continue to look for the reasons with my actual setup but I don’t really understood what can be the issue
Hello,
I see I’m not the only one!
For several days now, I haven’t been able to use the “Amazon Echo” app. I installed version 2.1.1, but that didn’t help.
The app seems to be running and the Alexa devices are active, but if I ask to adjust the volume or get a weather report, I get a “Connection error during POST” message.
After checking the configuration, the app appears to be connected, yet nothing works.
So, I restart the app. Sometimes it reconnects and I can use all my Alexa devices, but often it remains disconnected and the devices are unavailable.
I enter my login details and the OTP code, but I get a “KeyError: ‘openid.oa2.authorization_code’” error message and cannot log in.
I struggle with this several times a day; sometimes it works, but it doesn’t last, and I have to start the process all over again every day.
I don’t understand why the connection is unstable now, given that it used to work perfectly.
Thank you for your help. diag : d4efc4be-9cf1-4175-aaea-45124ec65ccf
I removed it to update my Studio, and now it’s no longer working. Texts are not being spoken anymore. I also can’t select the Amazon.com.br country/region, for example, even though my Alexa is linked to a Brazilian account.
Even the previous version used to work, but now it doesn’t. It is connected and there is no error code. The Flow completes successfully, but nothing is heard.
@thierry_arguimbau Thanks for the report. Two things in it.
First, KeyError: ‘openid.oa2.authorization_code’ means Amazon rejected the sign-in, usually the 2-step code. Each code is valid about 30 seconds and only once, so take a fresh one every attempt. The next update shows a readable message instead.
Second, the real problem: your Homey cannot look up the address of alexa.amazon.fr, the European Alexa server your account uses. Interestingly @Jeremy_Gout report shows the identical failure on the identical name, two unrelated households, both in France. alexa.amazon.com resolves fine on both your Homeys and the address for alexa.amazon.fr is correct and reachable from elsewhere, so this is not Amazon and not your Homey. Something in French networks is failing on that specific name, which is a chain of aliases (alexa.amazon.fr to layla.amazon.com to an Amazon CloudFront address). A resolver that stumbles anywhere in that chain answers “no address”. Which ISP and router are you each using? If it is the same one, that is the culprit.
Worth one more try: restart the Homey itself, not just the app. It caches DNS answers, including the failed ones, and only picks up changed router DNS settings after a reboot.
Otherwise, the new test version brings back manual server selection. Set the Amazon server to amazon.de: that is the same European server as amazon.fr behind another name, resolving to the identical address, so routines, devices and the language of spoken messages stay exactly as they are. You can also try amazon.com, but that is a different server on the other side of the Atlantic, so your routines will not be there and the routine list will come up empty.
One more thing, Thierry: the “works but doesn’t last, and I start over every day” part was a real bug, now fixed. After a single failed connection the live update channel stayed dead until the app was restarted.
Your region is already correct. The log shows the app talking to alexa.amazon.com.br, so there is nothing to select. Manual server selection does come back in the next update, but you will not need it.
The missing TTS was a bug in the app. It sent Amazon the wrong form of your account id, so Amazon rejected every spoken message while everything else, devices, volume and Do Not Disturb, kept working normally. That is why it looked like only speech was broken.
For now, restart the app and speech should work again. No need to sign in again. If you do sign in again later it can go quiet until the next restart.
Properly fixed in the next update, so speech works straight after signing in. Thanks for the report, it had exactly the detail needed to find this, and it turned out to affect everyone who had signed in recently.
Hi staeff,
I use your App from the begining and till few weeks/versions, I have the same problem as Jeremy_Gout, also with 2.1.2 Test version :
Sometimes, it “falls working” but for few hours only and then, when I try to reconnect, same message “CannotConnect: Connection error during GET”.
I also use amazon.fr and tried with amazon.de or amazon.us with same result.
Do you want me to send a report log ?
Regards,
SoPhos
Please try again with version 2.1.3 and if this still does not work send me a diagnostic log.
Hi @staeff
With your new version 2.1.3 it’s working from my side, routines are well displayed and avalaible !! 
But when i try to launch some flow, each card send an error message “connection error during get”
de0cb987-f455-4b83-8cef-793f84fa4ced
Again this seems to be a DNS issue on your side. Can you try to run the following homey script to see if the DNS resolution fails from time to time? Did you try to reboot your Homey?
const wait = async (timeout) => {
return new Promise((resolve) => {
_.delay(function (text) {
resolve();
}, timeout);
});
};
const hosts = ["alexa.amazon.fr", "alexa.amazon.de"];
for (const host of hosts) {
for (let i = 1; i <= 10; i++) {
try {
const res = await fetch(`https://${host}/`, {
method: "HEAD",
redirect: "manual",
});
log(`${host} try ${i}: reached, HTTP ${res.status}`);
} catch (e) {
const dnsFailed = /getaddrinfo|ENOTFOUND|EAI_AGAIN/i.test(e.message);
log(
`${host} try ${i}: ${dnsFailed ? "DNS FAILED" : "reached"} (${e.message})`,
);
}
await wait(5000);
}
}
return true;
Hi reboot my Homey Pro, I was disconnected of Amazon Echo and now i can’t connect anymore (on amazon.de) with still the same error message “CannotConnect: Connection error during GET” but in amazon device I saw on new device created by tentative of connection.
As you were saying yesterday, 1 try = 1 new device even if connection is failed
As soon as I return to my home I try your script
Can you please try to run the Homey script mentioned above as well? This is still some kind of DNS issue in some part of your setup.
Also just to have it for comparison. Which internet provider and kind of router are you using?
You should be right, something seems going wrong :
alexa.amazon.fr try 1: reached, HTTP 302
alexa.amazon.fr try 2: reached, HTTP 302
alexa.amazon.fr try 3: reached, HTTP 302
alexa.amazon.fr try 4: reached, HTTP 302
alexa.amazon.fr try 5: reached, HTTP 302
alexa.amazon.fr try 6: reached, HTTP 302
alexa.amazon.fr try 7: DNS FAILED (request to https://alexa.amazon.fr/ failed, reason: getaddrinfo ENOTFOUND alexa.amazon.fr)
alexa.amazon.fr try 8: DNS FAILED (request to https://alexa.amazon.fr/ failed, reason: getaddrinfo ENOTFOUND alexa.amazon.fr)
alexa.amazon.fr try 9: DNS FAILED (request to https://alexa.amazon.fr/ failed, reason: getaddrinfo ENOTFOUND alexa.amazon.fr)
alexa.amazon.fr try 10: DNS FAILED (request to https://alexa.amazon.fr/ failed, reason: getaddrinfo ENOTFOUND alexa.amazon.fr)
alexa.amazon.de try 1: DNS FAILED (request to https://alexa.amazon.de/ failed, reason: getaddrinfo ENOTFOUND alexa.amazon.de)
alexa.amazon.de try 2: DNS FAILED (request to https://alexa.amazon.de/ failed, reason: getaddrinfo ENOTFOUND alexa.amazon.de)
alexa.amazon.de try 3: DNS FAILED (request to https://alexa.amazon.de/ failed, reason: getaddrinfo ENOTFOUND alexa.amazon.de)
alexa.amazon.de try 4: DNS FAILED (request to https://alexa.amazon.de/ failed, reason: getaddrinfo ENOTFOUND alexa.amazon.de)
alexa.amazon.de try 5: DNS FAILED (request to https://alexa.amazon.de/ failed, reason: getaddrinfo ENOTFOUND alexa.amazon.de)
Btw, nslookup alexa.amazon.fr gives :
Serveur : dns.google
Address: 8.8.8.8
Réponse ne faisant pas autorité (Non authoritive answer) :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 3.164.158.58
Aliases: alexa.amazon.fr
layla.amazon.com
tp.799c43337-frontier.amazon.com
Seems to be a AWS/CloudFront DNS.
Regards,
SoPhos
@staeff UK user here.
I’ve installed version 2.1.3 and been testing it all day. Have had zero issues. Several times TTS has been triggered by a flow getting Alexa to announce something. As well as a calendar appointment being announced from a Homey flow. I have also checked the routines card, and that display correctly. Not had any errors or authentication issues.
I’m on BeFibre FTTP broadband. My Amazon account is on amazon.co.uk but I can access layla.amazon.com alexa.amazon.fr alexa.amazon.de
I run a pair of Pi-Hole servers with recursive lookups via Unbound, so I don’t touch my ISP’s DNS, or other hosted service. But it does do DNS blocking, and I have been testing with that enabled.
I have tested with Echo Show 5 (3rd gen), Echo Show 8 (3rd gen), Echo Show 15, and Echo Spot (newest gen).
I would be intrigued to know what exact models/versions of Echo devices are having these issues? And if it is affecting any other functions of the Echo devices themselves, or the Alexa app.
Amazon mucking up their DNS is not unheard of, they’ve caused global outages in the past. But if it is the DNS for Alexa in European countries, I would expect some other functions to be impacted.
Hello @staeff ,
I use your Homey Amazon Echo app and I added two important features:
-
Voice reply on the originating Echo
When a user asks a question to a specific Echo, Homey retrieves the latest Alexa voice event and automatically replies on the same Echo. This works with Flow cards and allows a Homey Flow to be triggered from an Alexa routine, then reply on the device that heard the command. -
Alexa shopping list retrieval
The app retrieves the Alexa shopping list through Amazon’s API, can announce it on the originating Echo, and stores it in Homey. I also added a Homey dashboard widget displaying the current items with a refresh option.
These features could be useful to other users. Would you be interested in integrating them officially into your project? I can provide the changes and explain how they work.
Thank you for your excellent work.
Olivier
Message “CannotConnect: Connection error during GET” comes when trying to connect App to Alexa.
My provider is FREE (free.fr) and I’ve tried many DNS to be sure (I can change DNS in router config).
Regards,
SoPhos
Can you try to run nslookup every few seconds on your PC as well, just to see if it happens there as well. That would help to confirm if the problem is maybe with Homeys DNS cache or in your network.
