Signal Coverage
Selora evaluates repeater and mesh coverage from the floor plan — walls, floors, and device placement — so installers see weak or missing signal before the homeowner does.
Summary
Floor Plan Management gives Selora the geometry of a home: the walls, the floors, the placement of devices. The installation manifest gives Selora the networking hardware — the access points, the repeaters, the nodes. Combine the two and a question that is currently answered only after the home is built becomes answerable before the first brick is laid: does this mesh actually cover this plan, and where will it fail? Signal Coverage evaluates repeater range, per-device bandwidth headroom, and dead zones from the plan and the manifest — so the installer fixes a repeater position on paper instead of re-dispatching after the complaint arrives.
The installer’s problem
- Coverage is verified with a phone, in the dark, after install. The only way to find a dead zone today is to walk the finished home with a client device. The installer has already left, so the walk happens as a callback — and the fix is another dispatch
- Repeaters are placed by intuition, not geometry. Where the second repeater goes is a feel decision — “somewhere between” — because there is no model of how far a signal gets through the specific walls of this specific plan
- Weak links hide until they matter. A device that gets 5% of its designed bandwidth passes install, works until the fridge starts, and becomes a support ticket. The plan knew where that device was; nobody checked what it could hear
What’s included
Coverage evaluation from the plan
- Repeater range checked against the walls: given the plan’s walls, the floors, and the repeater positions on it, Selora computes whether each area of each level is inside a repeater’s plausible range — and flags the gaps before install day
- Per-device bandwidth prediction: every device in the manifest gets an estimate of the link quality it will see from its nearest access point or repeater — devices likely to be bandwidth-starved are called out on the plan
- Dead zones surfaced, not hidden: areas with no usable coverage are marked on the floor plan with the offending gap named — “no line-of-sight path from any repeater through this wall run” — so the fix is a placement change, not a guess
- Cross-floor evaluation: levels are distinct surfaces in the plan, and signal crosses floors with real loss; the evaluation treats floors explicitly instead of pretending the home is flat
What it is for
- Installers sizing the mesh on paper: add or move a repeater on the plan, watch the coverage map update, and carry the corrected layout to the site — the plan is the design tool
- A defensible installation: the manifest and the plan together document why the mesh was laid where it was, which is the answer to every “why does the kitchen drop out” ticket that follows
Why it matters
- It moves the failure mode from the customer’s house to the installer’s laptop. A dead zone found on the plan costs a drag-and-drop; found by the homeowner, it costs a dispatch, a return visit, and the customer’s trust in the install
- It makes the manifest honest. The manifest says what is going in; coverage evaluation says whether what is going in is enough, there — the difference between a bill of materials and a design
- It compounds with the floor plan data. Every placed device and every uploaded plan makes the model better; the feature gets stronger with the same data the 3D floor and placement features already depend on
The complexity
- Distance on a plan is not distance in a home. The plan is 2D and imperfect; measuring “how far is the repeater from the device” means mapping plan coordinates to real dimensions, which the drawing itself does not state. Floor scale has to be established and respected, or every prediction is a confident fiction
- Floors break the 2D assumption. Signal crosses floors — through joists, ceilings, and the void between — with loss that depends on the construction, which the plan does not draw. Cross-floor evaluation needs an explicit model of what a floor boundary does to a signal, not a plane
- Walls are not one material. A sheet-rock wall and a concrete core and a double-brick exterior absorb signal differently, and the plan’s linework does not say which is which. The model has to accept the installer’s correction (“this wall is concrete”) rather than guess from line weight
- Prediction, not measurement. This estimates; it does not measure. Every output has to be framed as “likely weak” with the reasoning shown, because a false “coverage confirmed” is worse than no answer at all
Out of scope (for now)
- Live RF surveying — meshing with a phone or probe in the real home; the evaluation runs on the plan before the home exists
- Auto-placing repeaters — Selora flags gaps and predicts; the installer decides the fix
- Backhaul and LAN topology — the evaluation is radio coverage, not switch design or cabling
Last modified November 16, 2026: docs(roadmap): add Signal Coverage (cd5a136)