Mesh Node Offline in App Despite Working Wi-Fi

You're Not Alone—This Happens With Every Mesh System

You open the app. One of your nodes is grayed out with a red "Offline" badge. But your phone still connects to it. Your laptop still streams YouTube. The smart plug plugged into that node still responds. What's actually happening here is that the node is connected—it's passing traffic just fine—but the management software can't see it. The app thinks it's dead. The node thinks it's fine. They're having a communication breakdown.

This happens most often after a power flicker, a firmware update that didn't fully apply, or a DHCP lease renewal that went sideways. I've seen it on Eero, Orbi, Google Nest Wifi, and TP-Link Deco systems. The trigger is usually the same: something changed on the network (a new device, a router reboot, a switch being unplugged and reconnected) and the mesh's internal heartbeat mechanism got confused.

Root Cause: mDNS and the Heartbeat Gap

Every mesh system uses a proprietary or mDNS-based protocol to keep nodes talking to the app. The app sends a query: "Who's alive?" The node answers. If the answer doesn't arrive (because the node's DNS cache is stale, because the router's DHCP table changed, or because the node's internal clock drifted), the app marks it offline.

The real culprit is often the router's DHCP lease time. By default, most ISP routers use 1 hour. When a node renews its IP, the DNS record doesn't update fast enough. The app still points to the old IP. The node answers from the new IP. The app doesn't recognize the response. Stalemate.

Another common cause: the mesh node is stuck on a different Wi-Fi channel or band than the main router, because the backhaul negotiation failed after a reboot. The node is alive, but it's shouting into a void the app can't hear.

The Fix: Step-by-Step

1. Don't unplug the node yet. Open your router's admin page. Find the DHCP client list. Confirm the node has a valid IP address—something in your subnet, not 169.254.x.x (that's a link-local address, meaning DHCP failed). If it's 169.254.x.x, the node didn't get an IP. That's a different problem—check your router's DHCP pool isn't full.
2. Power-cycle the main router (the one connected to your modem). Wait 2 minutes. Then power-cycle the mesh node that's showing offline. Wait for it to fully boot (all LEDs steady). What happens here is the router issues a new DHCP lease, the node grabs it, and the mDNS registration happens fresh.
3. If that doesn't work, force a channel rescan. In the mesh app, find the setting for "Optimize Network" or "Channel Scan" (Eero calls it "Run a network test"; Orbi has "Channel Selection"; Google Nest has "Mesh Test"). Run it. This forces all nodes to renegotiate backhaul channels. Sometimes a node gets stuck on a DFS radar-avoidance channel that the app can't reach.
4. Manually set a static IP for the offline node. This is the nuclear option, and it works every time for Eero and Deco. In your router's DHCP reservation list, assign a fixed IP to the node's MAC address (printed on the bottom). Reboot the node. Now the app always knows exactly where to find it—no lease renewal confusion.
5. Update the node's firmware—manually if needed. Some mesh systems let you download the firmware from their support site and install via USB or web interface. If the app can't see the node, but the node is reachable via its IP (try pinging it), you can often load the firmware directly. This fixes known bugs where the heartbeat daemon crashes silently.

Still Offline? Check These Three Things

• The backhaul medium. If you're using wired Ethernet backhaul, check the Ethernet cable. A loose or damaged cable can pass some traffic but drop management packets. Swap the cable with a known-good one. If the node is wireless backhaul, check if there's a thick wall or metal appliance between it and the main node. Move it closer temporarily—if it comes back online, range is the issue.
• IPv6. Some mesh apps hate IPv6. If your router has IPv6 enabled (and most ISP routers do by default), try disabling it for 10 minutes. The mesh node might be prefering an IPv6 address for management traffic, but the app only talks IPv4. I've fixed three Eero installations just by turning off IPv6.
• Third-party DNS. If you use Pi-hole, Cloudflare, or Google DNS instead of your ISP's, the mesh node's mDNS queries might get blocked. Add an exception for your mesh app's domain (e.g., *.eeros.com or *.orbi.net) in your DNS filter. Or temporarily switch back to ISP DNS to see if that's the blocker.

The One-Liner Summary

The node isn't offline—it's just not talking to the app. Give it a fresh DHCP lease (step 2), force a channel rescan (step 3), or pin it to a static IP (step 4). If that fails, check the backhaul cable or your DNS filter. Nine out of ten times, one of these three fixes brings it back without a factory reset.