Both sound very interesting, so ideally break them down into at least 2 self contained PRs and I will take a look!
staeff,
The problem is not DNS cache, the problem is about Amazon using cloudfront.
Itâs the same on my PC at home or my PC at work.
Here are the nslookup every 10 seconds on alexa.amazon.fr :
Serveur : one.one.one.one
Address: 1.1.1.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 18.239.24.145
Aliases: alexa.amazon.fr
layla.amazon.com
tp.799c43337-frontier.amazon.com
Serveur : one.one.one.one
Address: 1.1.1.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 3.164.158.58
Aliases: alexa.amazon.fr
layla.amazon.com
tp.799c43337-frontier.amazon.com
Serveur : one.one.one.one
Address: 1.1.1.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 18.239.24.145
Aliases: alexa.amazon.fr
layla.amazon.com
tp.799c43337-frontier.amazon.com
Serveur : one.one.one.one
Address: 1.1.1.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 3.164.158.58
Aliases: alexa.amazon.fr
layla.amazon.com
tp.799c43337-frontier.amazon.com
And nslookup every 10 seconds on alexa.amazon.de :
Serveur : one.one.one.one
Address: 1.1.1.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 13.33.55.234
Aliases: alexa.amazon.de
layla.amazon.com
tp.799c43337-frontier.amazon.com
Serveur : one.one.one.one
Address: 1.1.1.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 3.164.158.58
Aliases: alexa.amazon.de
layla.amazon.com
tp.799c43337-frontier.amazon.com
Serveur : one.one.one.one
Address: 1.1.1.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 3.164.158.58
Aliases: alexa.amazon.de
layla.amazon.com
tp.799c43337-frontier.amazon.com
Serveur : one.one.one.one
Address: 1.1.1.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 13.33.55.234
Aliases: alexa.amazon.de
layla.amazon.com
tp.799c43337-frontier.amazon.com
And itâs the same on alexa.amazon.co.uk or alexa.amazon.comâŠ
I found that d3rsqup3tcxj1a.cloudfront.net was always the same for each domain.
Do you use IP resolving on first connexion to keep IP setting ?
If so, maybe dynamic get/put at each fetch would help (using domain name, not IP) ? donât really knowâŠ
Regards,
SoPhos
Thanks, that helps, and it rules out my first suspicion. The app never stores an IP, it looks the name up again for every request, so rotating CloudFront addresses cannot strand it.
I measured the answer for alexa.amazon.fr: a single address with a 60 second lifetime. So every minute something in the path has to fetch a new one, and if that refresh comes back empty there is nothing left to connect to.
One question: which DNS setting did you change? On Freebox the DNS panel sets what the box itself uses, while the DHCP panel has a separate field for the servers handed to your devices, which defaults to the Freebox. If it was the first, Homey is still asking the Freebox. Devices also keep the old DNS until their lease renews, so Homey needs a reboot after any change.
To prove where it breaks, from a computer on the same network, ten times each:
nslookup alexa.amazon.fr 192.168.1.254 # (or whatever your router address is)
nslookup alexa.amazon.fr 1.1.1.1
If the first sometimes returns nothing and the second always works, it is the Freebox.
I ran the test against both the Freebox DNS (192.168.0.1) and Cloudflare (1.1.1.1). Both returned valid responses every time, with the same CloudFront host and normal IP rotation.
I could not reproduce any timeout or empty DNS response on the Freebox side.
Logs with Freebox DNS :
22/08/2026 17:26:00,62
Serveur : UnKnown
Address: 192.168.0.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 3.164.158.58
Aliases: alexa.amazon.fr
layla.amazon.com
tp.799c43337-frontier.amazon.com
22/08/2026 17:26:00,62
Serveur : UnKnown
Address: 192.168.0.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 13.33.55.234
Aliases: alexa.amazon.fr
layla.amazon.com
tp.799c43337-frontier.amazon.com
22/08/2026 17:26:00,62
Serveur : UnKnown
Address: 192.168.0.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 13.33.55.234
Aliases: alexa.amazon.fr
layla.amazon.com
tp.799c43337-frontier.amazon.com
22/08/2026 17:26:00,62
Serveur : UnKnown
Address: 192.168.0.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 3.164.158.58
Aliases: alexa.amazon.fr
layla.amazon.com
tp.799c43337-frontier.amazon.com
22/08/2026 17:26:00,62
Serveur : UnKnown
Address: 192.168.0.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 3.164.158.58
Aliases: alexa.amazon.fr
layla.amazon.com
tp.799c43337-frontier.amazon.com
22/08/2026 17:26:00,62
Serveur : UnKnown
Address: 192.168.0.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 3.164.158.58
Aliases: alexa.amazon.fr
layla.amazon.com
tp.799c43337-frontier.amazon.com
And Logs with Cloudflare DNS :
22/08/2026 17:26:01,52
Serveur : one.one.one.one
Address: 1.1.1.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 13.33.55.234
Aliases: alexa.amazon.fr
layla.amazon.com
tp.799c43337-frontier.amazon.com
22/08/2026 17:26:01,52
Serveur : one.one.one.one
Address: 1.1.1.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 3.164.158.58
Aliases: alexa.amazon.fr
layla.amazon.com
tp.799c43337-frontier.amazon.com
22/08/2026 17:26:01,52
Serveur : one.one.one.one
Address: 1.1.1.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 13.33.55.234
Aliases: alexa.amazon.fr
layla.amazon.com
tp.799c43337-frontier.amazon.com
22/08/2026 17:26:01,52
Serveur : one.one.one.one
Address: 1.1.1.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 3.164.158.58
Aliases: alexa.amazon.fr
layla.amazon.com
tp.799c43337-frontier.amazon.com
22/08/2026 17:26:01,52
Serveur : one.one.one.one
Address: 1.1.1.1
Réponse ne faisant pas autorité :
Nom : d3rsqup3tcxj1a.cloudfront.net
Address: 3.164.158.58
Aliases: alexa.amazon.fr
layla.amazon.com
tp.799c43337-frontier.amazon.com
Regards,
SoPhos
Version 2.1.4 is out on test now. Three things in it that matter here.
It now asks your network for Amazonâs addresses far less often, keeping each one for two minutes instead of ten seconds. It also keeps them across a failed attempt, so if the first connect fails you can press Connect again straight away and only the last address still needs looking up. And when a lookup does fail, the app names the address instead of showing âConnection error during GETâ.
That is honestly all I can do from inside the app. It asks the system for an address and either gets one back or does not, and no amount of retrying changes that answer. Your tests showed both your Freebox and 1.1.1.1 answering correctly when asked from a PC, so whatever is going wrong sits between your Homey and your network, where the app has no visibility and no influence.
If you do see the new message, post the address it names. That would at least tell us whether the same one fails every time.
Hello,
The problems continue. I connect using a different server; it works for 12 hours, but thenâwithout disconnectingâI lose control via the app.
Here is a new report: 807dfcc4-69b4-497f-b855-49f2f6ebeb7e
Hello again
Sorry I was really busy with no time to follow discussion here. I have exactly the same results as @SergeP when i search nslookup alexa.amazon.fr. : both return a valid response each time I tried to. I have also a freebox, and i removed all ads block parameter so from my side my routeur canât block anything.
I have tried to reconnect today :
- First attempt on amazon.alexa.fr : FAILED
- Second attempt on amazon.alexa.de : FAILED
- Third attempt on amazon.alexa.com : SUCCESS
Even if I am well connected, routines are no more displayed in the app AND when I tried some flow, I obtain an error message with the exact name of the routine
cb217590-89ed-44cd-b5cc-5fc7fdd04ccc
I tried to reconnect with amazon.alexa.de several times until it works :
When I am connected, routines are displayed in the app BUT when I tried some flow, I obtain an error message with âcannot resolve alexa.amazon.de - your network returns no address for itâ
- â amazon.alexa.de is reachable in the same time by cmd promptâŠ
Routines are no more visible after error message
I really donât understand what the problem could be
Version 2.1.5 is on test now, with something for each of you.
@thierry_arguimbau, losing control after about 12 hours without disconnecting matches a specific failure. The app renews its Amazon session in the background every few hours, and if Amazon stops accepting the renewed one, reading state keeps working while commands get refused, so the app still shows connected and only Flow cards fail. In 2.1.5 the app notices that, renews the connection and runs the command anyway. It also logs it, so a new report will show whether that was it. One question: when it happens, does restarting the app give you control back straight away?
@Jeremy_Gout, that error is the new message from 2.1.4 and it is telling the truth. At the moment the Flow ran, Homey got no address for alexa.amazon.de while your PC resolved the same name at the same time. Same network, same resolver, so the resolver is not broken. Something specific to Homey is not getting an answer.
Worth checking on the Freebox: there are two separate DNS settings, the one the box uses itself and the one it hands out by DHCP. Check what Homey actually received, and if it is wrong, set the DNS to distribute explicitly and restart Homey so it picks up the new value.
Being connected through amazon.com signs you in, but routines belong to your accountâs own region, so the .com server returns none. That is why the list is empty and a Flow naming a routine fails. It connects, but it is not a fix.
Please both update to 2.1.5 and send a fresh report if it happens again.
EDIT: you can run this homey script return Homey.system.getInfo(); and check either âwifiDnsâ or âethernetDnsâ to see what the actual DNS server of your Homey is set to.
Hello,
I updated to version 2.1.5, but the problem persists.
After a freeze, restarting doesnât fix the issue. The app seems to reconnect, but none of the controls work. I have to go through the entire connection process againâtrying different servers and making multiple attemptsâbefore it finally works.
The Freebox allows for 5 DNS entries for DHCP; Iâve tried various combinations, but it makes no difference. My PC uses these DNS settings without issues, whereas Homey fails to do so (see screenshots).
Here is the latest diagnostic ID: 66cf03a7-63e4-43c6-8660-dfcbb015c6fb
Thanks
Did you try this?
you can run this homey script
return Homey.system.getInfo();and check either âwifiDnsâ or âethernetDnsâ to see what the actual DNS server of your Homey is set to.
But to be honest Iâm pretty much at the end of things I can do from my end. As this issue also happens when you just run the fetch command via Homey script this problem is clearly outside the control of my app.
EDIT: Sorry just checked your screenshots. So seems like your Homey is pointing to 1.1.1.1 and the fetch request still misbehaves. But my assessment is still that those are the addresses we need to use and we somehow need to resolve somewhat current IP addresses via DNS lookup.
Since recent updates, my Echo devices and the Advanced Flows I have set-up for them, have all been working rock solid. Zero authentication or connection issues. (Many thanks @staeff hugely appreciated)
Just a thought, but I donât have WiFi connected on my Homey Pro, Ethernet only. Would it be worth trying a single connection for a while, to make sure your network is not having issues with a device having multiple connections. Iâm presuming your PC only uses one connection at a time, either Ethernet or WiFi, not both simultaneously.
The odd dropped packet here and there could be an issue for repeated DNS queries. I donât know how Homey would handle that, or if it could.
If many of us can use the app just fine without issue. And your testing from other devices like your PC shows the actual DNS is working. It sounds like it has to be something local network related.
I also immediately noticed that @thierry_arguimbau has both configured. And definitely something to try, but it wonât explain why resolving api.amazon.com always seems to work. Something else to try is that I noted there are 5 DNS servers configured. If Claude is to be believed the Homey network stack will ignore anything besides the first 3 and the second one points again to your local Freebox. So ideally you should only be giving out 1.1.1.1 and 8.8.8.8 via DHCP to make sure it will always try to reach an external DNS server.
@thierry_arguimbau @Jeremy_Gout
Version 2.1.6 is on test. App settings has a new button, âRun network testâ. It looks up Amazonâs address twice in the same moment: once the normal way through Homey, and once over an encrypted connection straight to Cloudflare that bypasses the normal path. Then it tries each step of the address chain separately and writes it all to the app log.
Nobody has been able to make that comparison so far. Every test in this thread ran either from a PC or against one server by hand, never two paths on the same Homey in the same second.
Running it on my own Homey already showed something useful: a Homey does not ask your router directly, it asks a resolver running on the Homey itself. That part of the path is invisible to nslookup on a PC, which would explain how your tests keep coming back clean while Homey keeps failing.
So: turn on diagnostic logging, press Run network test while the problem is happening, and send a diagnostic report. If everything works when you read this, run it anyway, since I need a healthy result to compare against. The app also runs the same check by itself when a lookup fails, so a report sent after a failure will contain it even if nobody pressed the button.
Hi staeff,
Sorry, Iâm back with the same problem (Freebox and Amazon) as @thierry_arguimbau and @Jeremy_Gout.
I just sent you a report log as asked : 146f2623-9e5f-4083-b2bb-36ba242b69d2
Regards,
SoPhos
Hello
I was disconnected after 2.2.0 update. I tried to reconnect under amazon.alexa.de but it was not working (3 attempts). I tried under your automatic setup and it works in the first attempt.
Following connection I have tried some flow, and the routine seems to work ! First time ever 
healthy report : c8524ce9-a7dd-4d5c-bdcb-021b2904e1db
I have tun several routines during 5 minutes : all is working well. Tomorrow I will let homey manager all routines during the day. If an error message appear I will inform you and add a diagnostic report
Great achievement !! Thanks 
Error came back quickly⊠
maybe 10 minutes
screenshot and report number :
96f37b5c-1fc8-4889-8680-e72d8a9408f7
Hello,
here is my latest diagnostic report after running the test for version 2.2.0.
39ab47c8-4f95-4f62-a7f8-28ca31eec224
@SergeP @Jeremy_Gout @thierry_arguimbau
Thanks for running the network tests, they turned up something concrete.
Your Homey can find the final address behind alexa.amazon.fr fine. What it canât do is follow the chain of nicknames that leads there, and Amazonâs address is really four names pointing at each other. Every name in the middle comes back empty in about a millisecond, which is too fast to have actually asked anyone. Thatâs also why api.amazon.com always worked, itâs a plain address with no chain.
Then the interesting bit. In one log the app asked for an address three times and got nothing, then asked the same name in a slightly different form and got it straight away. Same second. Everything else started working after that too.
Why itâs only the three of you I still canât say, but every Homey asks the same way, so whatever is answering differently sits somewhere past the Homey itself. Most likely your router since you all use a Freebox if I understood you correctly.
So 2.2.2 asks the broader way whenever the narrow one fails. This might not be enough on its own, the same lookup has failed both ways in other logs, but it costs nothing to try. So please try that version and if it still fails more reports are appreciated.
After installing 2.2.2 version, as usual I was disconnecting automatically I tried to reconnect on automatic setup, then .fr .de but I never achieve the connection
Hi staeff,
Unfortunately, I tried with 2.2.2 version and itâs stil the same.
Report log id is e70a768c-db6d-452e-9bda-e930e02ba22e
Regards,
SoPhos
Hi staeff,
Iâm keeping my fingers crossed, but since the latest update (2.2.3), no disconnections have been detected. Iâm waiting to see if this lasts; however, itâs impossible to connect to amazon.fr. I had to connect to the amazon.nl server instead. For now, itâs working well. It had been several weeks since Iâd heard a peep from my Alexa devices. Iâm keeping a close eye on the situation. Letâs hope it lasts.
