Exact model-family answer directory

TP-Link Deco M5 mesh troubleshooting

Choose the symptom actually shown by Deco M5. TP-Link router/Deco; EasyMesh/Deco controller, Wi-Fi generation, HomeShield and Ethernet ports vary. Error codes remain separate records because the same characters can mean different things on another platform.

no internetWi-Fi dropsslow Wi-Fidead zonesdevice won't connectsetup

Reviewed records

16 exact answers

Not sure where the fault is?

TP-Link · DNS

TP-Link Deco M5 mesh cannot open websites because DNS fails

For the TP-Link Deco M5 mesh, resolver, filter, VPN and cache should be separated from a site or provider outage.

Open record TP-Link · 100 Mbps

TP-Link Deco M5 mesh Ethernet link is limited to 100 Mbps or disconnects

For the TP-Link Deco M5 mesh, every cable pair, wall jack, switch and port must negotiate the intended speed.

Open record TP-Link · firmware

TP-Link Deco M5 mesh firmware update will not install

For the TP-Link Deco M5 mesh, exact model/hardware revision, stable power, storage and signed firmware are required.

Open record TP-Link · guest network

TP-Link Deco M5 mesh guest network cannot reach devices, cast or print

For the TP-Link Deco M5 mesh, guest isolation is usually intentional; internet and local discovery are separate permissions.

Open record TP-Link · dead zones

TP-Link Deco M5 mesh has weak signal or dead zones

For the TP-Link Deco M5 mesh, building loss, access-point placement, band and mesh backhaul should be measured at the node location.

Open record TP-Link · no internet

TP-Link Deco M5 mesh has Wi-Fi but no internet

For the TP-Link Deco M5 mesh, provider modem/ONT, router WAN address, DNS and one client should be separated.

Open record TP-Link · slow Wi-Fi

TP-Link Deco M5 mesh internet or Wi-Fi is slow

For the TP-Link Deco M5 mesh, provider rate, wired router throughput, radio link and one service should be measured separately.

Open record TP-Link · node offline

TP-Link Deco M5 mesh mesh node or satellite is offline

For the TP-Link Deco M5 mesh, node power, parent signal, firmware, account and backhaul should be separated.

Open record TP-Link · parental controls

TP-Link Deco M5 mesh parental controls or schedules are not working

For the TP-Link Deco M5 mesh, target identity, randomized MAC, time zone, DNS/VPN bypass and overlapping profiles should be separated.

Open record TP-Link · port forwarding

TP-Link Deco M5 mesh port forwarding is not working

For the TP-Link Deco M5 mesh, local service, firewall, reserved IP, double NAT, CGNAT and provider blocks should be proved in order.

Open record TP-Link · restarts

TP-Link Deco M5 mesh restarts, freezes or overheats

For the TP-Link Deco M5 mesh, power supply, ventilation, load, firmware and hardware should be separated.

Open record TP-Link · double NAT

TP-Link Deco M5 mesh shows double NAT or strict NAT

For the TP-Link Deco M5 mesh, provider gateway/router mode, downstream router, CGNAT and local service state are different boundaries.

Open record TP-Link · VPN

TP-Link Deco M5 mesh VPN client or server will not connect

For the TP-Link Deco M5 mesh, provider/server, credentials, protocol, DNS, MTU, policy route and double NAT should be isolated.

Open record TP-Link · Wi-Fi drops

TP-Link Deco M5 mesh Wi-Fi keeps disconnecting

For the TP-Link Deco M5 mesh, client, band, channel/interference, coverage, firmware and node backhaul should be isolated.

Open record TP-Link · setup

TP-Link Deco M5 mesh will not complete setup

For the TP-Link Deco M5 mesh, modem/ONT provisioning, WAN type, app/account and cabling should be proved before resets.

Open record TP-Link · device won't connect

TP-Link Deco M5 mesh will not connect one device

For the TP-Link Deco M5 mesh, one-client capability, security, band, DHCP, randomized address and access controls should be isolated.

Open record

Confirm the model first

Which units this covers, and how to tell yours is one of them

Every answer below is scoped to these model identifiers. A neighbouring model in the same line can use a different part, a different reset sequence or a different radio, so matching the identifier before following a procedure is the step that decides whether the rest of the page applies to you.

Model numbers and patterns: Deco M5
What that covers: TP-Link router/Deco; EasyMesh/Deco controller, Wi-Fi generation, HomeShield and Ethernet ports vary.

Published specification

What is true of this model and changes how you fix it

These are the properties that decide which procedure applies. Each is read from the manufacturer’s own published figures for this model, not carried over from a sibling that shares its retail name.

Wi-Fi 5 (AC) dual-band MESH (older): An older Wi-Fi 5 (AC) Deco mesh with 2.4/5 GHz — a generation behind Wi-Fi 6/6E/7, so its top speeds are lower. That is the hardware generation, not a fault. Units cover a home; a weak room means a node is too far.
Mesh backhaul: Dual-band, so backhaul shares the 5 GHz band — keep nodes close or use Ethernet backhaul for best speed.
Managed by Deco app only: Managed through the Deco app (no web admin).

Where these figures were read. tp-link.com Deco M5 (Wi-Fi 5 dual-band mesh, older), read 2026-09-01

Manufacturer support for this product line. TP-Link Support — Support center. Official TP-Link Archer, Deco, switch and extender manuals and firmware.

Exact questions

Questions that only have an answer for the TP-Link Deco M5 mesh

Each answer below uses this model’s own published figures. The same question asked about a different model in the line has a different answer, which is why it is answered here rather than on a general page.

My TP-Link Deco M5 seems slower than newer Wi-Fi.+

The Deco M5 is a Wi-Fi 5 (AC) system, a couple of generations behind Wi-Fi 6/6E/7, so its maximum speeds are lower by design — that is not a fault, just its era. It is still fine for browsing, streaming and everyday use across a home. For higher speeds on modern devices you would move to a Wi-Fi 6 or 7 Deco. Keeping nodes close (or wired) and firmware updated gets the most out of it.

Structured depth, not empty permutations

Every published record carries a direct answer, scope, ordered fixes, risk notes and sources.

Device and manufacturer hubs share a consistent record system, but each answer carries the relevant controls, fault boundaries, consequences and official support entry point for that platform.

See the publication gate