Wi-Fi coverage
Estimates Wi-Fi strength in every room from a router spot, finds dead zones, the best router spot for the bedrooms and office, and where a mesh node helps most.
What it answers
Section titled “What it answers”- Where should the router go?
- Will Wi-Fi reach the back bedroom?
- Do I need a mesh node?
For the agent, the tool is described as: Wi-Fi signal estimate per room through the scan’s wall graph (COST 231 multi-wall model, wall materials assumed from thickness), for 2.4 and 5 GHz. Give router_room or router_point, or leave both empty to find the best spot for the bedrooms and office. Returns a per-room lens (5 GHz dBm), checks per room, dead zones, router and mesh node pins. Low confidence estimate.
Who it is for
Section titled “Who it is for”Family planning home security, Remote worker.
Inputs
Section titled “Inputs”| Input | Type | Required | Default | Notes |
|---|---|---|---|---|
scan |
string | yes | Scan id. Filled from the selected building. | |
router_room |
string | Room id where the router is; empty to let the tool find the best spot. | ||
router_point |
array | Router position [x, y] in the scan frame (metres). | ||
router_floor |
string | Floor id of router_point, when the scan has several floors. | ||
router |
string | "typical" |
typical: 20 dBm at 2.4 GHz, 23 dBm at 5 GHz. long_range: 4 dB more. Saved preference wifi.router_class. One of: typical, long_range. |
|
targets |
array | Room ids that must have good signal; default the bedrooms and office. |
An input that nothing fills (the selected building, a saved preference, a persona’s preset) becomes a question to the person. The agent asks only for those.
Data used
Section titled “Data used”| Layer | Id | Needed | If it is missing |
|---|---|---|---|
| Wall outline | matterport.walls |
required | The verdict is unknown, with the reason. |
| Doors and windows | matterport.openings |
required | The verdict is unknown, with the reason. |
| Room names | matterport.room_labels |
optional | The tool runs without it. |
What it returns
Section titled “What it returns”A tool result: a verdict (pass, warn, fail or unknown), metrics, checks and findings, each with its source.
- Draws on the building: a colour per room; pins on what it found.
- Panel blocks:
VerdictHeader,MetricRow,MiniChart,CheckList,FloorPlanMini,AssumptionChips,StepLog. - Speed: fast. Read-only.
How it works
Section titled “How it works”Wi-Fi coverage: expected signal per room from a router, through the walls and floors of the scan.
Reliability
Section titled “Reliability”Sources this tool gave on the test home:
| Where it came from | Layer | Method | Reliability | Note |
|---|---|---|---|---|
| Simulated from the scan | matterport |
simulation |
low | COST 231 Final Report (1999), 4.7.2, multi-wall model over the scan’s walls; wall materials assumed from thickness; furniture, doors and interference not modelled |
The tool sets the label for each value. A model never does. The tools give a scan’s wall graph the layer matterport whichever device made the scan, so a phone scan’s geometry carries that label too.
Limits
Section titled “Limits”- Needs: wall outline, doors and windows. On a scan without them, the verdict is
unknownand says why. - A result is a planning aid, not an inspection.
On the made-up test home
Section titled “On the made-up test home”This section was written by running the tool when the docs were built, on a hand-made RoomPlan export (no real place was scanned), with no sponsor keys and the network switched off.
Pass With the router in Bedroom, 2 of 2 bedrooms get good 5 GHz signal. The scan labels no office, so only bedrooms were targeted. Estimate from the walls alone.
| Value | Result | Where it came from | Reliability |
|---|---|---|---|
| Rooms with good 5 GHz | 6 of 6 | Simulated from the scan | low |
| Dead zones (5 GHz) | 0 rooms | Simulated from the scan | low |
| Weakest target: Bedroom 2 | -37.2 dBm | Simulated from the scan | low |
| Dead zones (2.4 GHz) | 0 rooms | Simulated from the scan | low |
| Bedroom | -31.1 dBm | Simulated from the scan | low |
| Bedroom 2 | -37.2 dBm | Simulated from the scan | low |
| Bathroom | -41.3 dBm | Simulated from the scan | low |
| Hallway | -44.5 dBm | Simulated from the scan | low |
| Living Room | -45.3 dBm | Simulated from the scan | low |
| Kitchen | -50.4 dBm | Simulated from the scan | low |
| Check | Measured | Against | Status |
|---|---|---|---|
| 5 GHz signal, Bedroom | -31.1 | -67 dBm | pass |
| 5 GHz signal, Bedroom 2 | -37.2 | -67 dBm | pass |
| 5 GHz signal, Bathroom | -41.3 | -67 dBm | pass |
| 5 GHz signal, Hallway | -44.5 | -67 dBm | pass |
| 5 GHz signal, Living Room | -45.3 | -67 dBm | pass |
| 5 GHz signal, Kitchen | -50.4 | -67 dBm | pass |
Findings: 1 pass.
What it reported while it ran:
- Cut 25 wall pieces at their doors and windows; 111 sample points in 6 rooms
- Trying 58 router spots against 2 rooms (bedrooms)
- Router placed in Bedroom
Run it
Section titled “Run it”threshold run wifi_coverage --scan <scan-id>curl -X POST http://127.0.0.1:8787/api/tools/wifi_coverage/run -H 'content-type: application/json' -d '{...inputs}'Over MCP the tool is named wifi_coverage. See MCP server and CLI.