Network technician helping fix WiFi mesh restarting issues

Steve H.

Expert ★★★★★ 27,853 satisfied customers

Specialities: mesh firmware-update fallout, node pairing/sync failures, eero/Orbi/Deco/Nest WiFi setup checks, backhaul (wireless/ethernet) stability.

After an update, mesh nodes may stop syncing due to version mismatch, stalled pairing, backhaul changes, or app/setup state — what to check first (safely)

Technician avatar Technician
Firmware updates can make a mesh feel “broken” because the main unit and the satellites stop agreeing on the same setup state.

Let’s start with the safest checks first. I don’t want you factory-resetting anything until we know what’s actually stuck.

Three quick details help a lot:
1) Which brand/model (Deco, eero, Orbi, Nest WiFi, Velop, ZenWiFi)?
2) What exactly is “not syncing” — satellites show offline, they won’t rejoin, or the app shows “update required” and never finishes?
3) Did this happen immediately after the update, or a day later?
Customer
It’s a TP-Link Deco system with 3 units. Right after the firmware update, the two satellites won’t sync properly. They show red/offline and the app keeps saying “pairing” but it never completes.
Technician avatar Technician
Got it — that’s a classic “post-update pairing stall.” It’s usually one of these:
• One unit updated, another didn’t (version mismatch).
• The app is stuck holding an old pairing session.
• Backhaul changed (ethernet/wireless path) and the satellites can’t complete the handshake.

First, a low-risk question: did the update run on all units, or only the main Deco? If you can see firmware versions for each node in the app, that’s helpful.
Customer
I only saw the update on the main one. The satellites are stuck “connecting.” I’m not sure how to check their versions when they won’t connect.
Technician avatar Technician
That’s okay — many apps hide node details when a satellite is offline.

Trust moment: don’t press “reset” on the satellites yet. If the system is mid-update, a reset can make the “stuck” state harder to diagnose.

Safe checks that don’t change your settings:
1) Confirm the main node is fully online and stable (internet works on a phone/laptop).
2) Check the app’s update screen once more to see if it says “up to date” or “updating.” If it’s still “updating,” give it time before trying to re-pair.
3) Look at the satellites’ lights: are they steady red, blinking red, or switching colors?
Customer
Internet works on the main node. In the app, it says the main is updated. The satellites blink red for a while, then go solid red.
Technician avatar Technician
Solid red usually means “not joined / can’t complete sync.” After firmware changes, the safest next step is to remove variables, not add more.

A few environment checks (order matters here):
1) Are the satellites currently wired with ethernet, or are they wireless only?
2) Did anything else change around the update — new switch, new router/gateway, or moving units to different rooms?
3) Is your phone on the same Wi-Fi network when you try pairing (not on mobile data)?
Customer
They’re wireless, no ethernet. I did move one unit farther away recently. My phone is on the Wi-Fi when I try to pair.
Technician avatar Technician
Distance can matter more right after an update because the satellites need a clean backhaul link to finish syncing.

Safe diagnostic idea (temporary and reversible): bring one satellite into the same room as the main node and try pairing again. This isn’t “the fix,” it’s just a test to see if the issue is backhaul quality versus something else.

Also, one small risk check: are you running any “security filtering” on the router or using a DNS ad-block feature? Sometimes the app can’t reach the cloud service it needs to complete the join process.
Customer
I moved one satellite close to the main unit. It got farther in the pairing and then failed again. We also use a DNS ad blocker on the router.
Technician avatar Technician
That’s useful. This is common after updates, but we should rule out anything that could make it worse.

Two “proof” checks that stay safe:
1) Try pairing while temporarily using a plain connection path (for example, disable the DNS filter for a short test window, or use a basic ISP DNS just to see if the pairing completes). If you’re not comfortable changing DNS, you can skip this and we’ll use another signal.
2) Check if the Deco app has any pending permissions on your phone (Bluetooth / local network). Pairing often needs local network permission to discover nodes reliably.

When it fails, what does the app say — “can’t find device,” “timed out,” or “network error”?
Customer
It says “timed out” most times. I’m on iPhone and it asked for local network access earlier. Bluetooth is on.
Technician avatar Technician
A timeout after getting “farther” usually means the device is seen, but the final sync step can’t complete consistently.

Let’s narrow it down with one controlled comparison (no mass changes):
• Try pairing from the same phone, same Wi-Fi, satellite close to the main node, but restart only the satellite (power off 15–20 seconds, then back on) and try once more. This clears a stale pairing state without touching your saved network name/password.

Trust moment: don’t keep repeating pairing over and over. Too many attempts can confuse the app and you end up not knowing which change mattered.

If it still times out, we focus on two likely buckets: cloud reachability (filtering/DNS) or firmware mismatch on the satellites.
Customer
I did one restart of the satellite and tried again. Still timed out. I’m worried the satellites didn’t update and now they can’t talk to the main one.
Technician avatar Technician
That’s a reasonable concern, and it’s one of the most common post-firmware issues in mesh systems.

Here are the safest ways to confirm it without erasing anything:
1) In the app, look for a devices list that shows “offline” nodes and check whether it offers an “update” or “retry” option for satellites.
2) If your model supports it, connect a satellite by ethernet to the main node just for a test (single cable, direct path). This can help a stuck unit complete update/sync because the backhaul becomes stable. If you don’t have ethernet available, skip this — distance testing is still valid.
3) Watch for the pattern: if it always fails at the same point and the main node is stable, that points to either satellite firmware state or the app’s ability to reach the vendor service through DNS/filtering.
Customer
I see the offline nodes in the list, but there’s no update button for them. I can’t run ethernet easily. If it’s DNS filtering, I can try turning it off briefly, but I’m nervous about changing router settings.
Technician avatar Technician
That’s completely fair. If you’re uncomfortable changing DNS, don’t force it.

A safer approach is to change only one thing for one short test, then put it back:
• If your router has a “DNS filter” toggle, pause it briefly and attempt pairing once while the satellite is close to the main node. Then re-enable it right away.

If pairing succeeds only with filtering paused, you’ve identified the cause without doing anything drastic. If it still fails, the next likely bucket is the satellites’ firmware state, and at that point a planned reset (with notes/screenshots) may be the cleanest path — but we don’t jump there first.
Customer
Okay. I like the idea of one controlled test and then putting it back. I’ll do that and stop repeating attempts. This already feels less scary.

Quick answer: the accepted fix

Accepted first approach when a mesh won’t sync after a firmware update: pause repeated pairing attempts, bring one satellite close to the main node, and confirm the main unit shows “up to date” in the app. Then run one controlled comparison to rule out reachability issues (for example, temporarily pause DNS filtering and try pairing once, then restore it). If the same timeout repeats across a stable setup, document the exact message and the node light pattern, because that points to either a satellite firmware state mismatch or a blocked pairing step — without rushing into a factory reset.


Why mesh nodes can stop syncing right after a firmware update

After an update, a mesh can fail to “rejoin” if one unit is on a different firmware version, if the app is holding an old setup session, or if the backhaul link is weak during the final handshake. Another common reason is network filtering (DNS ad-block, “protect” features, or strict firewall rules) blocking the service the app needs to finish the join step. That’s why the safest plan is to change one variable at a time and watch for a clear pattern.

What to check first before resetting your mesh system

Start with low-risk checks: confirm the main node is stable and updated, move one satellite close for a pairing test, and make sure your phone has local network access in settings. If you use DNS filtering, try a brief one-time pause during pairing, then restore it. Avoid repeated pairing attempts, because it can create confusing “stuck” states in the app. If you keep notes (exact error text, lights, and what you changed), you’ll know whether this is a reachability issue or a firmware mismatch problem.

WiFi mesh not syncing after an update — safe checks

Most cases are fixed by power/ventilation checks and correcting wired backhaul topology.

Start with the basics: wall outlet (not a shared power strip), original power adapter, and good airflow to prevent overheating. Then confirm your mesh firmware is updated and that you don’t have two routers handing out IPs (double NAT/DHCP conflict). If your mesh started rebooting after adding a switch or wiring satellites, run a 24-hour wireless-only test — if it stabilizes, rewire to modem → main node → switch → satellites. Avoid changing multiple advanced settings (DNS, IPv6, fast roaming, band steering) at once; do one change, test, and move on.

Disclaimer: This information is AI-generated and intended for general guidance only. Do not open hardware or attempt electrical repairs. For steps specific to your mesh brand/model and ISP setup, consult a verified expert on Whizz-Tech or the manufacturer’s support before making decisions.

Understand what these prompts mean


Getting Started Is Easy

Ask for help, 24/7

Members enjoy round-the-clock access to 12,000+ verified Experts, including mesh Wi-Fi support, router specialists, smart home connectivity, and more.

Expert will respond in minutes

We match you with an Expert who specialises in mesh networks (Deco/eero/Orbi/Nest WiFi), node dropouts, and reboot loops. Chat in real time.

Save time & money

Stop guessing and fix mesh Wi-Fi reboots and node disconnects without expensive visits. The right wiring and settings can stabilize your network fast.

FAQ

Why did my mesh stop syncing right after a firmware update?

Updates can leave one node on a different version, or the app can keep an old pairing session. A weak backhaul link during setup can also cause timeouts. Sometimes DNS filtering or “protect” features block the final pairing step.

Did this happen after an update, or is it a hardware failure?

If it started immediately after firmware changes, it’s usually a setup state or connectivity issue, not broken hardware. Try a close-range pairing test and compare results with filtering paused briefly. If one node never joins in any safe test, it may be that specific unit.

Is this a settings issue, or are my nodes too far apart?

Both are possible. Right after an update, distance matters because the satellite needs a clean link to finish syncing. A quick test is placing one satellite near the main node to see if the behavior changes.

Can this be checked safely at home without resetting everything?

Yes. Use read-only checks in the app, do one controlled pairing attempt, and change only one thing at a time. Avoid repeated attempts and keep notes of exact error messages and light patterns. Reset is usually a last step after you’ve identified the likely bucket.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant