Why Should Network Cables Be the First Item on the List for a Five-Story Villa with a Wireless Smart Home?
A five-floor home design study separates cable outlets, switch ports, PoE budgets and video storage, with explicit assumptions and a downloadable planning sheet.
Consider an unfinished villa with two basement levels and three above-ground floors, each about 200 square meters, where the plan is to use both Matter and Bluetooth SIG Mesh. The first question is usually: How many gateways should we buy?
But at the unfinished-construction stage, gateways are often the easy part to replace. What gets buried in the renovation is the conduit, power supply, network points, and maintenance access. Get those wrong first, and even excellent wireless devices may not be able to make up for it later.
This article uses those requirements for a preliminary engineering assessment. There is no floor plan or on-site testing yet. All quantities are suggested provisions or examples based on explicit assumptions, not figures from a completed installation.
First, Map Where a Command Travels
When someone taps a basement light on a phone from the third floor, the command may pass through the home network, a central controller, and a Mesh gateway before finally reaching the light. If all communication between floors depends on wireless relays, potential failures will include attenuation through floor slabs, powered-off nodes, and wireless contention.
My preliminary choice is to use a wired network for paths between floors, then wireless for the final segment near each device. Matter over Thread devices connect to the IP network through a border router; SIG Mesh devices connect to the higher-level system through a compatible gateway. A border router and a Mesh gateway are not interchangeable.[1][2]
This does not mean every floor needs a switch. If all data cables can reach the main rack within the specified link-length limits, centralized cabling can simplify power supply and maintenance. Floor-level access switches and a fiber backbone become necessary only when there are many floors, cable routes are too long, or conduits are congested.
| Option | Benefit | Cost |
|---|---|---|
| Home-run cabling to the main rack | Centralized UPS, patching, and maintenance | More copper cable; greater demands on riser space and distance |
| Floor-level switches | Nearby connections and a simpler backbone | Each floor needs power, cooling, and maintenance access; a power outage affects that floor |
Spare fiber strands can address termination failures or expansion, but they cannot help if the same fiber cable is cut. When discussing redundancy, ask whether the backup route shares a conduit with the original route.
Cable Points, Ports, and Device Counts Are Three Different Lists
You can reserve three AP locations per floor without installing three APs immediately. Two locations may already cover the main rooms, leaving the third for a dead zone found during a survey. You can also reserve two candidate gateway locations and ultimately use only one.
Reserved cables should be terminated at a patch panel, labeled, and tested. Cables without installed devices need not be patched into a switch yet. Accordingly, size the patch panel for the number of cables installed, size the switch for active connections plus spare capacity, and determine AP and gateway counts from actual coverage and functional needs.
This avoids two opposite mistakes: installing too few cables to save switch ports, or buying fifteen APs just because there are fifteen AP locations on the walls.
Take one floor as an example. Assume it has two APs, three cameras, one SIG Mesh gateway, one Thread border router, and four fixed endpoints: eleven active copper-cable connections in total. Add 25% spare port capacity and round up to fourteen ports.
A 16-port switch might suffice, provided the uplink uses a separate port and future expansion does not exceed the assumptions. If the uplink occupies a copper port, a third AP is activated, or access control is added, the count must be redone. “Sixteen ports” cannot be treated as a fixed answer for every floor.
Having PoE Ports Does Not Mean Having Enough Power
Suppose the maximum power draw is 18W for each of two APs, 12W for each of three cameras, and 8W for each of two gateways that support standards-based PoE. The total is:
2 × 18 + 3 × 12 + 2 × 8 = 88W
Adding 25% gives 110W. That is a useful first-round budget check, but it is not enough to select a “110W PoE switch.” The switch may allocate its power budget by PoE class, cables incur losses, and each port has its own limit. Check the selected model’s power-sourcing class and the manufacturer’s power-allocation rules.
A camera that works during the day but goes offline when its infrared illumination turns on at night is one situation that calls for checking power capacity and the power-supply path. Insufficient network bandwidth is not necessarily the cause. Acceptance testing should cover high-load operating conditions, not merely whether devices come online when first powered up.
Make the Recording-Capacity Assumptions Explicit, Too
For example, assume twelve cameras, an average of 4Mbps per camera, and thirty days of continuous recording:
12 × 4,000,000 ÷ 8 × 86,400 × 30
= 15,552,000,000,000 bytes
= 15.552 TB (decimal)
The easiest mistakes here are treating Mbps as MB/s or treating a drive’s advertised capacity as fully usable recording capacity. Adding an illustrative 20% margin gives about 18.66TB, before accounting for array and file-system overhead and bitrate fluctuations. The actual field of view, nighttime image noise, and encoding settings will all affect storage consumption.
First, make trial recordings of representative daytime and nighttime scenes. Then use the measured averages and peaks to decide on storage. Check the NVR’s connection, recording, and decoding capabilities separately: being able to record twelve streams does not mean it can display all twelve at high resolution simultaneously.
What Actually Needs Sign-Off Before the Walls Are Closed
For each location, record at least the floor, room, purpose, cable ID, locations of both ends, whether it uses PoE, whether it needs an independent power supply, whether it will remain accessible for maintenance, and whether it is currently a provision or a confirmed installation.
For this villa, a starting point could be two primary AP locations and one spare per floor, plus two candidate gateway locations, to be revised once the floor plan is available. Camera locations must be planned around fields of view; their number cannot simply be distributed evenly by floor area. Communication cables for air conditioning and underfloor heating must follow the manufacturers’ wiring diagrams. Do not promise that one network cable will cover every interface.
When confirming the plan with the contractor, the most valuable questions are: “Can this cable be replaced if it fails? Can this device be removed if it fails? Which functions will stop together if the switch on this floor loses power?” Clear answers reveal whether the wireless plan has a sound foundation.
Download the point-planning CSV. This Chinese-language template must be adapted to the floor plan; it is not a confirmed procurement list.
Sources checked on 2026-11-15: 1 Home Assistant Matter, 2 OpenThread Border Router. The port, power, and recording calculations are hypothetical examples in this article, not configuration recommendations from those documents.
AI-generated scene illustration, not a photograph of this project or a wiring instruction.
Discussion
Share a question or your experience. Comments appear after moderation. Your email is never displayed publicly. Comment privacy
Loading comments…