Guided check
0/4 checkedMatch the symptom, then work through the safe checks.
1. What best matches what you observe?
2. Complete only the checks that are safe for you.
4 user-level checks are available in this guide.Stop immediately if any warning condition applies.
Show stop conditions
- The node or adapter overheats
- Resetting would remove a complex working network configuration
Likely causes
- The node has lost power or network backhaul
- The node is too far from the main router or another node
- Ethernet backhaul is connected to the wrong port or VLAN
- Firmware or app account state is inconsistent
Quick checks, in order
Check power and the node LED legend
Use the exact mesh system guide.
Move the node close to the main unit
Confirm it can reconnect before returning it to position.
Restart the node and main router in the recommended order
Wait for the main unit to become fully ready.
Remove and re-add only as a last setup step
A reset can erase topology and custom settings.
How is the node connected?
Wireless backhaul
Placement and signal overlap are priorities.
Ethernet backhaul
Check cable, switch, port, loop prevention, and network mode.
The app sees the node but says offline
Cloud account state can lag behind local connectivity; test a nearby client.
Stop and get qualified help when
Do not continue troubleshooting if any of these apply:
- The node or adapter overheats
- Resetting would remove a complex working network configuration
Frequently asked questions
Should a mesh node be placed in the dead zone?
No. It needs a strong backhaul link, so place it between the main router and the weak area.
Can an Ethernet switch break mesh backhaul?
Managed VLANs, loops, or incompatible topology can interfere, while a simple correct switch normally works.
Did this guide move you closer to a solution?The response is stored on this device and sent to aggregate analytics.