the velop app says "node unreachable" but the light is blue and wifi works.

Diagnosis

This is a classic "ghost" status error specific to the Linksys Velop MX5300 cloud architecture. When you see a solid blue light on the node, it indicates that the hardware has successfully established a backhaul connection (either via wireless 5GHz or wired Ethernet) and is actively routing traffic. The "Node Unreachable" message in the app is not a report of network failure, but rather a failure of the Linksys Cloud Management API to poll the status of that specific node. Essentially, the node is communicating perfectly with your devices and the parent node, but the "heartbeat" signal it sends to the Linksys servers has been interrupted or timed out. This often happens after a firmware update or a momentary dip in the WAN connection, causing the app to cache an old "offline" state even after the hardware has recovered. You can confirm this by connecting a device to that specific node; if you can browse the web, the issue is purely a reporting glitch in the app's dashboard.

How to Fix It

To force the Linksys app to resync with the MX5300 hardware and clear the unreachable status, follow these precise steps:

1. Force-close the Linksys app on your mobile device. On iOS, swipe up from the bottom and flick the app away; on Android, use the App Switcher to swipe the app off the screen.
2. Disable the Wi-Fi on your smartphone and enable Cellular Data (LTE/5G). This forces the app to establish a fresh connection to the Linksys cloud servers rather than trying to route the request through the local mesh network.
3. Open the Linksys app and navigate to the account profile icon in the top right corner.
4. Select Log Out and confirm the action. This clears the local session token which may be holding the cached "unreachable" status.
5. Restart your smartphone completely to clear the system cache.
6. Re-enable Wi-Fi, reopen the app, and log back in using your Linksys account credentials.
7. Wait 60 seconds on the main dashboard for the cloud polling to complete. The node status should now update to "Online."

If That Didn't Work

• Perform a Soft Reboot via the App: If the app allows you to access the node settings despite the error, navigate to Network Settings > Advanced Settings > Restart Node. This forces the node to re-authenticate its cloud handshake without wiping your configuration.
• Power Cycle the Parent Node First: Unplug the primary (parent) node from the wall for 30 seconds, then plug it back in. Wait for it to turn solid blue. Once the parent is stable, unplug the "unreachable" child node for 30 seconds and plug it back in. This re-establishes the backhaul chain from the top down.
• Check for Firmware Mismatch: Sometimes a node is "unreachable" because it is stuck in a pending update state. Go to the app's Administration menu and check for firmware updates. If one is pending, trigger the update manually for all nodes to ensure they are on the same version (e.g., v1.0.11.xxxxx).
• Toggle the "DHCP" Setting: If you are using the MX5300 in Bridge Mode, the app often struggles to locate nodes. Ensure the primary node is in "Automatic" or "DHCP" mode if you are not using a separate third-party router.

Heads Up

• Avoid Factory Resets: Do not press the physical reset button on the bottom of the node unless you are prepared to set up the entire mesh from scratch. A factory reset will delete your SSID and password.
• Placement Matters: Even if the light is blue, if the node is on the edge of its range (more than 30 feet or two walls away), the cloud heartbeat may be the first thing to drop. Move the node slightly closer to the parent to see if the app stability improves.
• App Cache: If you use an Android device, go to Settings > Apps > Linksys > Storage and select Clear Cache. This is often more effective than simply logging out.
• Cable Check: If you are using wired backhaul, ensure you are using Cat5e or Cat6 cables. A degraded cable can cause "flapping" where the node is online for traffic but offline for management.