A node on another floor must still reach the main network; placing it at the farthest dead spot can leave a weak backhaul.
Before you change anything
This is a diagnostic entry point. The source supports the general check, not a confirmed root cause for your device.
What to check first
What does the vendor app report for the node relationship and backhaul?
Record the exact model, hardware revision, firmware and recent change before adjusting settings. If you cannot answer the question, keep the cause open.
Narrow the likely path
| Observation | Next check |
|---|---|
| Node cannot pair | Check exact model ecosystem, node role and firmware first. |
| Wired backhaul fails | Trace cable order and mode; avoid an upstream loop. |
| Wireless node drops | Move it to a location with a usable uplink, then retest a client. |
Decision after the first test
Test a landing or stairwell position and inspect actual link quality. Use Ethernet across floors if wiring exists.
Use a documented next step
Verify before escalating
After each change, repeat the exact failed task. If the result is unchanged, restore the previous setting and use the official support link for your exact hardware revision. Don’t assume a menu or capability from a related model.
Official sources
- TP-Link US Wi-Fi signal and range troubleshooting (full_text; checked 2026-11-01)
Check your exact US model, hardware revision, and firmware on the linked support page before changing settings.