TP-Link · node offline

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

TP-Link Deco M5 mesh mesh node or satellite is offline: node power, parent signal, firmware, account and backhaul should be separated. Scoped to Deco M5, with the model boundary and safe stop points made explicit.

Direct answer

For the TP-Link Deco M5 mesh, node power, parent signal, firmware, account and backhaul should be separated. First, place the node near the primary and observe status.

What this covers

  • TP-Link Deco M5 mesh (Deco M5)
  • TP-Link router/Deco; EasyMesh/Deco controller, Wi-Fi generation, HomeShield and Ethernet ports vary.
  • The specific fault this record addresses: mesh node or satellite is offline

What it does not cover

  • ×The same symptom on a different TP-Link product line, which has its own record and its own cited source
  • ×An on-screen error code whose meaning has not been checked against this exact model's manual
  • ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step

Differential

What actually causes this, and how to tell them apart

These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.

  1. 1

    The node has lost power

    What separates it The node is completely dark, with no light of any colour.

    How to confirm Confirm the outlet, the node's own adapter and any switch on that outlet; a dark node is a power problem, not a mesh one.

  2. 2

    The node is placed too far for a reliable backhaul

    What separates it The node shows a fault or 'weak connection' colour, and it sits far from the main unit or the next node, or across heavy walls.

    How to confirm Move the node closer to the main unit — roughly within sight of the previous node — and let it re-establish; a node beyond backhaul range keeps dropping offline.

  3. 3

    The wired backhaul or its port has failed

    What separates it A node set up for a wired (Ethernet) backhaul goes offline after a cable, switch or port change.

    How to confirm Test the backhaul cable and port with a known-good cable; a wired-backhaul node depends entirely on that link.

  4. 4

    The node's firmware is out of sync with the system

    What separates it A node dropped offline after a system update, or will not finish re-adopting.

    How to confirm Let the system push the pending firmware to the node, keeping it powered and close during the update, before removing and re-adding it.

Before you touch a setting

Record this first — changing settings destroys the evidence

Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.

  • The node's light colour: dark (power) versus a fault/weak colour (backhaul).
  • Where the node sits relative to the main unit and any walls between them.
  • Whether it uses a wireless or a wired backhaul, and what changed before it dropped.
Try in this order0 of 4 completed
  1. Read the offline node's light to split power from backhaul

    Reversible

    Dark is power; a fault colour is a reachable-but-not-connected backhaul issue.

  2. Confirm power, then move a wirelessly-backhauled node closer

    Reversible

    Within sight of the previous node so the backhaul is solid.

  3. Test the cable and port for a wired-backhaul node

    Reversible

    A wired node lives or dies by that single link.

  4. Let firmware finish, then re-add the node only if needed

    Reset / data risk

    Removing and re-adopting is a last step, after power and backhaul are confirmed.

Model-specific

What is true of this model and not of its siblings

Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.

Model scope
Deco M5. TP-Link router/Deco; EasyMesh/Deco controller, Wi-Fi generation, HomeShield and Ethernet ports vary.
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).
Symptom boundary
This record covers TP-Link Deco M5 mesh when it mesh node or satellite is offline. A different symptom on the same hardware, or this symptom on a different TP-Link product line, has its own record with its own causes and its own cited source.

Stop boundary

When this stops being a self-service repair

Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.

  • !Do not place a node where heat or moisture can reach it to close a backhaul gap — add a node or a wired backhaul instead.

Evidence ledger

Sources behind this answer

Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.

Where the manufacturer's article stops. TP-Link publishes this as "Fix Deco Disconnecting & Internet Instability – Step-by-Step Guide". TP-Link's Deco article for a mesh unit that keeps dropping off the system. Probed 2026-08-21: title-verified. What that article does not carry is the model boundary — it is written for a product line, and Deco M5 is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.

Exact questions

Common follow-ups

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.

One of my mesh nodes keeps showing offline.+

Look at that node's light first. If it is completely dark, it is a power problem — check the outlet and its adapter. If it shows a fault or weak-connection colour, it has power but cannot reach the rest of the system, which means its backhaul is too weak: move it closer to the main unit or the previous node, roughly within sight, so the link is solid. A node placed beyond backhaul range will keep dropping no matter how many times you re-add it.

Does this answer apply to every TP-Link model?+

No. It is scoped to Deco M5. TP-Link router/Deco; EasyMesh/Deco controller, Wi-Fi generation, HomeShield and Ethernet ports vary.

What should I record before troubleshooting node offline or satellite?+

Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.

Why is a factory reset not the first step?+

A reset can erase accounts, networks, maps, schedules or preferences without distinguishing node offline, satellite. The ordered checks preserve that evidence.

When should I stop and use qualified service?+

Do not reset the entire mesh for one failed node.

Change recordSept. 1, 2026 — Built out with researched, cross-checked per-model specifications and model-specific guidance. Aug. 17, 2026 — Published with explicit Deco M5 applicability, a mesh-node-offline diagnostic boundary and first-party support provenance.
Report a correction
Wrong device or version?

Match the path before repeating the steps.

Match another device