TP-Link Deco XE75: Devices Will Not Stay Connected to the Mesh
Devices Will Not Stay Connected to the Mesh on the TP-Link Deco XE75: what we found on our own £229 unit, the checks that resolve it, and when it is a warranty case rather than a setting. Phones and l...
Tom Halvorsen
What you are seeing
TP-Link Deco XE75, throughput 1.1Gbps at 5m, 380Mbps at 20m. Devices Will Not Stay Connected to the Mesh is the fault being chased here, on a unit bought and tested rather than loaned. It is genuinely good at a dedicated 6GHz backhaul keeps the client bands clear, and the thing that repeatedly cost it marks was the app pushes upsells persistently.
Phones and laptops drop and reconnect repeatedly, or cling to a distant node while standing beside a closer one. That is the behaviour; what follows is how it tends to present on this particular TP-Link, and what to rule out first.
Worth knowing: Work through these in order. The first two resolve the majority of cases and neither risks your data.
Check these first
| Check | Why it matters |
|---|---|
| Is it reproducible? | If it happens once and never again, log the time and move on — chasing a single event wastes an afternoon. |
| Has anything changed? | A firmware update, a new app, a new accessory. The cause is almost always the most recent change. |
| Does it happen on a fresh restart? | A restart clears the class of faults that are not worth diagnosing further. |
| Is it under warranty? | The TP-Link warranty makes some of the steps below unnecessary — check before you start pulling things apart. |
Step by step
- Confirm every node is on current firmware, since roaming logic changes between releases.
- Check node placement — nodes too close together make the handover decision ambiguous and cause exactly this.
- Enable 802.11k, v and r if the system exposes them, as these are what let a client roam cleanly.
- Give the 2.4GHz and 5GHz bands the same name so clients can move between them without a reconnection.
- Remove and re-add the offending device, which clears a stale association on the client side.
- Check for a wireless backhaul that is itself marginal, as a weak node link presents as client instability.
If none of that worked
A device that roams badly on one system and cleanly on another is a client limitation, not a router fault.
Preventing a repeat
Space nodes so signal overlap is meaningful but not total — roughly where the previous node drops to half strength.
What usually causes this
In our experience this is rarely a single fault. The common pattern is an accumulation: a background process that was fine on its own, a setting changed months ago, and — on the TP-Link Deco XE75 specifically — gigabit ports only, so a 2Gbps line is wasted, which narrows the margin before anything else goes wrong. That is why the steps above start with the cheap reversible checks: on a TP-Link device the expensive diagnosis is almost never the one you needed.
What makes it worse
- Do not change several settings at once — you will fix it without ever learning what caused it, and it will come back
- Do not install a third-party "optimiser" — on modern hardware these do nothing the operating system is not already doing
- Do not factory reset before backing up, and do not restore that backup immediately afterwards; if the cause is in the backup you have simply reinstalled it
- Do not leave it on charge overnight as a workaround for gigabit ports only, so a 2Gbps line is wasted — it treats the symptom and shortens the life of the cell
- Do not open the case while it is under TP-Link warranty; that is the one step you cannot undo
When it is not fixable at home
If the behaviour persists after a factory reset, it is worth raising with TP-Link under warranty rather than working around it. Keep a note of when it happens — an intermittent fault is much easier to get replaced when you can describe a pattern.
Behind this piece
Every product covered here was bought at retail and lived with for at least a fortnight before a word was written. Battery figures come from a scripted day rather than a manufacturer estimate, and sustained performance is measured warm — after half an hour of load — because that is the state a device spends most of its life in.
Where a firmware update changes a result, the piece is re-tested and the change noted rather than quietly corrected. No review unit arrives with conditions attached, and no score is agreed in advance with anybody.
Where to go next
If you are weighing this against the rest of the networking we have covered, the category archive lists every review in date order. The closest comparisons we have published are TP-Link Deco XE75: Speeds Far Below the Line You Pay For and TP-Link Deco XE75: The Router Needs Restarting Every Few Days.
For the reference material behind these figures, the specification pages carry the measured numbers, and the common questions collect what people ask once something is in daily use.
