Direct answer
For the eero Beacon, node power, parent signal, firmware, account and backhaul should be separated. First, place the node near the primary and observe status.
What this covers
- eero Beacon (eero Beacon D010001)
- Wireless-only mesh node without Ethernet ports.
- The specific fault this record addresses: mesh node or satellite is offline
What it does not cover
- ×The same symptom on a different eero 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
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
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
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
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.
Read the offline node's light to split power from backhaul
ReversibleDark is power; a fault colour is a reachable-but-not-connected backhaul issue.
Confirm power, then move a wirelessly-backhauled node closer
ReversibleWithin sight of the previous node so the backhaul is solid.
Test the cable and port for a wired-backhaul node
ReversibleA wired node lives or dies by that single link.
Let firmware finish, then re-add the node only if needed
Reset / data riskRemoving 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
- eero Beacon D010001. Wireless-only mesh node without Ethernet ports.
- Type — plug-in mesh EXTENDER (no Ethernet ports)
- The eero Beacon is a plug-into-the-wall mesh EXTENDER node — it has NO Ethernet ports, so it can ONLY use wireless backhaul (you cannot wire it), and it is not a standalone router. It extends an existing eero network and includes a small nightlight.
- Wireless backhaul only
- Because it has no Ethernet, its performance depends entirely on a strong wireless link to another eero — plug it into an outlet within good range of the main eero or another node, not at the far edge of coverage. A weak/offline Beacon is almost always placed too far.
- eero app
- Managed in the eero app like any eero node; it must be added to an existing eero network.
- Symptom boundary
- This record covers eero eero Beacon when it mesh node or satellite is offline. A different symptom on the same hardware, or this symptom on a different eero 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. eero publishes this as "Why does my eero have a red LED?". a red LED is how an eero reports that it has lost its connection to the gateway or the internet. Probed 2026-08-21: title-verified. What that article does not carry is the model boundary — it is written for a product line, and eero Beacon D010001 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
How do I connect my eero Beacon by Ethernet?+
You can't — the eero Beacon has no Ethernet ports, so it only supports wireless backhaul. That makes placement critical: plug it into a wall outlet within good wireless range of your main eero or the previous node (a room or two away, not at the far edge), so its backhaul is strong. If you need a wired backhaul or wired device ports, use a standard eero unit (which has Ethernet) instead of a Beacon.
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 eero model?+
No. It is scoped to eero Beacon D010001. Wireless-only mesh node without Ethernet ports.
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.
Answer for the exact device and software version shown above.