How to Plan Wi-Fi & Home Network for a Smart Home: Router Placement, Mesh Nodes and Cable Drops

This article is part of our wider coverage of home automation in Hyderabad. Where our guide to wireless home automation explains how the devices talk, this one covers the infrastructure they talk over — and the decisions about it that have to be made while the ceiling is still open.

What actually needs the network — and what does not

Start here, because it corrects the assumption behind most over-specified home networks. In a well-designed system, the everyday operation of the house does not depend on the internet, and much of it does not depend on Wi-Fi either.

Three tiers, in order of how badly a failure hurts:

• Local and essential. A press on a wall keypad, a scene running, a dimmer ramping, a curtain motor travelling, a motion sensor lighting a corridor. These are executed between the keypad, the controller and the load modules inside the home. Target response is under 200 milliseconds from press to light, and it should be identical with the broadband unplugged.
• Local network, non-essential. Phone app control on the home Wi-Fi, camera live view on a wall tablet, casting to a television. These need the local network up but not the internet.
• Internet-dependent. Remote access from outside the home, cloud video backup, voice assistants, notifications, firmware updates. These are conveniences, and they should be the only things that break during an outage.

If a system is designed such that pressing a bedside button opens the curtains by way of a server, that is an architecture decision, not a fact of smart homes, and it is worth asking about before you sign. Our note on whether smart homes work during power cuts and internet outages goes into what should and should not survive each kind of failure.

Where the router belongs

The single highest-value network decision in a home is a position on a drawing, and it costs nothing if it is made early.

The router should sit near the centre of the home, in open air, at height — not where the broadband cable enters. Fibre from the provider terminates wherever it is convenient for them, usually at the entrance, in the utility area or beside the meter board. That termination point does not have to be the router position. Run a CAT6 from the ONT at the entry point to a properly chosen equipment position and the whole problem disappears.

Working rules for the position:

• Central in plan, not in a corner. A router in a corner flat wastes roughly half its coverage radiating into a neighbour's home or out over the balcony.
• Between 1.5m and ceiling height, radiating downward and outward. On the floor or inside a low TV unit is the worst common position.
• Not inside a closed wooden or metal cabinet. If it must live in a cabinet, use a ventilated one with a mesh or louvred front, and never a metal-doored rack.
• At least 1m from the microwave, the refrigerator, a large mirror and any metal-backed television. Microwaves radiate straight into the 2.4GHz band and are the most common cause of a kitchen dead zone.
• With mains power, an earth and at least two CAT6 terminations at that exact point, plus a spare 16A socket for the UPS.

In a villa the same logic points to a small equipment cabinet on the middle floor rather than the ground-floor utility room, so no floor is ever more than one slab away from the core of the network.

How many access points, and how far apart

Coverage planning in an Indian home is dominated by one fact: our walls are heavy. A 230mm brick wall costs roughly 6 to 10dB of signal, a concrete slab between floors 12 to 20dB, and a mirrored wardrobe or a granite-clad feature wall can be worse than either. A number that would cover an open-plan timber-framed house covers about half that here.

Figures we design to:

• One access point per 700–900 sq ft of built-up area on a single floor.
• At least one access point per floor, whatever the area — a slab is a worse obstacle than a wall.
• Mount high: in the false ceiling or on a wall above 2.4m, in open air, pointing down into the space it serves.
• Spacing of roughly 8 to 12m between nodes in a masonry home, less where a core wall or lift shaft sits between them.
• Aim for −65dBm or better at every position you actually use a device — sofa, bed, study desk, dining table, balcony seating. Below about −75dBm devices stay connected but behave erratically, which is what “it works but it's slow” usually means.

Typical outcomes: a 1,200 sq ft 2BHK is usually fine on one well-placed router; a 1,600–2,000 sq ft 3BHK wants the router plus one access point at the far end of the bedroom corridor; a 3,500 sq ft triplex villa wants three or four, one per floor plus one for the terrace and outdoor areas. The two positions that most often come up short in an Indian home are the master bathroom and the far balcony — walk both with a signal test before the ceiling closes.

Wired backhaul beats wireless mesh

A mesh node that relays to its parent over the air spends roughly half its airtime doing so, which is why a two-hop wireless mesh often delivers less usable throughput at the far node than a single router did. Feed each access point with its own CAT6 and that penalty disappears entirely. This is the main reason we ask for cable drops at access-point positions during construction — not because the automation needs the bandwidth, but because it makes every access point behave like a router rather than a repeater.

Cable drops to leave before plastering

This is the section to hand to your electrician, alongside the lighting and keypad drawings. It is a small list and it is cheap while the walls are open.

• CAT6 (or CAT6A), unshielded, solid copper — not copper-clad aluminium, which fails on longer runs and cannot carry Power over Ethernet reliably. Verify with a knife nick on site; CCA is a genuinely common substitution.
• Home-run every drop back to one equipment position. No daisy-chains, no joints buried in the ceiling. Every cable is a single continuous length from the cabinet to its outlet.
• Two drops to each planned access point in the false ceiling — the second costs almost nothing now and covers a repositioned or replaced node later.
• Two drops to the TV niche in the living room, and one to the master bedroom TV position if there is one.
• One drop per fixed camera position, run back to the NVR location, so cameras take both data and power over a single cable.
• One drop to the study desk and one to the equipment cabinet itself.
• Keep data cable at least 300mm away from parallel mains runs, and cross at right angles where they must meet.
• Maximum 90m per run — never an issue in a flat, occasionally one in a large villa with an outbuilding or gate camera.
• Leave 300mm of service loop at both ends, and label both ends before the cables go in the wall. Unlabelled cable in a finished ceiling is effectively no cable.
• A 25mm conduit with a draw-wire from the equipment cabinet to the ceiling void is worth more than any single cable, because it is how a future cable gets added without breaking anything.

Six to ten drops covers a typical 3BHK. That is a few thousand rupees of cable and a day of an electrician's time during construction, against chased walls and a reopened false ceiling afterwards. The same timing logic applies to neutrals at switchboards and to curtain track power points — see when to plan home automation during construction, and how to future-proof a home even if you automate later if the automation itself is a phase-two decision.

Bands, SSIDs and the 2.4GHz pairing trap

Smart-home devices are mostly 2.4GHz only, and for good reason: a curtain motor reporting that it reached its end position sends a few hundred bytes, gains nothing from a fast band, and needs the range and wall penetration that only the lower frequency gives. A device sitting above a false ceiling or inside a pelmet is exactly the case 2.4GHz exists for.

That produces a setup failure people hit constantly. If the router broadcasts 2.4GHz and 5GHz under a single name with band steering, the commissioning phone attaches to 5GHz while the device is waiting on 2.4GHz, and pairing fails with no useful error. Practical handling:

• Give 2.4GHz its own SSID — many installers keep a separate IoT network name on 2.4GHz permanently, which also keeps the device population off the band the family streams on.
• Or disable the 5GHz radio during commissioning and re-enable it afterwards.
• Fix 2.4GHz to channel 1, 6 or 11 and nothing between. In a Hyderabad apartment tower you are sharing the band with thirty neighbours; a scan before choosing is five minutes well spent.
• Keep 2.4GHz channel width at 20MHz. 40MHz in a dense building causes more interference than it wins in throughput.
• Put phones, laptops and televisions on 5GHz, and leave 2.4GHz to the device population.
• Use WPA2/WPA3 mixed mode. WPA3-only will lock out a proportion of older smart-home hardware.
• Reserve a DHCP range for automation devices — or better, give the controller, NVR and access points fixed addresses, so a router restart never renumbers the things everything else points at.

Record the SSIDs, passwords and fixed addresses in the handover document. A household that cannot change its own Wi-Fi password without breaking the lighting has been handed a liability, not a system.

Device counts, cameras and bandwidth

Count the endpoints during design, because the number surprises people. A typical automated 3BHK carries 40 to 60 connected devices once you total the controller, load modules, keypads, curtain motors, sensors, cameras, a doorbell, televisions, speakers and the family's phones, laptops, watches and tablets. Many of the free routers supplied with a broadband connection begin to struggle in that range, and the symptom is not a clean failure but occasional unexplained slowness.

Bandwidth is the part most people over-buy and mis-allocate. Lighting, curtains, keypads and sensors together consume a negligible amount — a few kilobits per second, a rounding error next to a single video stream. Cameras are the real load, and only in one direction:

• A 4MP camera at 15fps on H.265 runs about 2 to 4 Mbps continuously.
• Six such cameras is 12 to 24 Mbps — but that traffic stays on the local network between camera and NVR and never touches your broadband, provided the recorder is on site.
• Remote viewing is what uses your uplink, roughly 2 to 4 Mbps per stream being watched. Since Indian broadband uplinks are often much slower than the advertised download, size for the uplink: 30 Mbps up or better if the household regularly views multiple cameras from outside.
• Storage: six 4MP cameras recording continuously at H.265 need roughly 6 to 8TB for 30 days. Motion-only recording cuts that by half to two-thirds, at the cost of missing pre-event context unless pre-record buffering is enabled.

Plan camera positions and their cable runs together with the network, not after it — our guide to CCTV camera and sensor placement covers heights, angles and coverage, and smart home security in Hyderabad covers how locks, cameras and sensors should work together.

Power backup for the network

An outage in Hyderabad is usually short, but a network that drops takes the app, the cameras and remote access with it even though the automation itself keeps running locally. The networking gear draws very little, so this is inexpensive insurance:

• Router, switch and access points together typically draw 30 to 80W.
• A 600VA to 1kVA UPS at the equipment cabinet carries that for roughly two to four hours.
• Put the NVR and its drive on the same UPS, or a security event during an outage is the one that goes unrecorded. Add its draw — typically 20 to 40W with a single drive — when sizing.
• Where the property has an inverter or generator, put the equipment cabinet socket on the backed-up circuit, which is a decision to take with the electrician at DB stage, not afterwards.
• Remember the ONT at the entry point also needs backed power — a UPS on the router alone still leaves you without internet if the fibre terminal is dead.

A worked 3BHK network layout

A representative 1,600 sq ft three-bedroom flat in Hyderabad, single floor, with lighting, curtains, keypads and six cameras. This is the format the network drawing should take.

• Fibre ONT: entrance utility niche, where the provider terminates. One CAT6 from here to the equipment cabinet, and a backed-up socket.
• Equipment cabinet: ventilated 6U cabinet in the study, above 1.5m. Holds the router, an 8-port PoE switch, the automation controller, the NVR and a 1kVA UPS. Two 16A sockets, an earth, and all data drops home-run to here.
• Access point 1: living/dining false ceiling, central in plan, one CAT6 (plus one spare).
• Access point 2: bedroom corridor false ceiling, roughly 10m from AP1, one CAT6 (plus one spare) — this is the node that fixes the master bathroom and the far balcony.
• TV niche: two CAT6 to the living room media wall.
• Study desk: one CAT6.
• Cameras: six CAT6 from the six camera positions back to the NVR in the cabinet, PoE, no local power needed at the camera.
• Spare conduit: 25mm with draw-wire from the cabinet into the main ceiling void.

Total: 13 CAT6 drops plus 2 spares, one switch, two access points, one UPS. That network carries roughly 50 devices, six camera streams and a full lighting, curtain and keypad system, with every keypad press executing locally and nothing in the house dependent on the broadband to turn a light on. The lighting side of the same drawing set is covered in how to plan dimmer channels and lighting loads, and the scenes it all serves in how to design home automation scenes.

Mistakes that cost a chased wall

• Letting the broadband entry point decide the router position. One CAT6 from the ONT to a properly chosen spot solves it, and only while the walls are open.
• Copper-clad aluminium sold as CAT6. It fails on long runs and cannot carry PoE dependably. Ask to see the drum, and nick a sample.
• Hiding the router in a closed cabinet. Every millimetre of solid door is signal you paid for and threw away.
• Unlabelled cables. Thirteen identical white cables in a cabinet with no labels turns a ten-minute fault into a half-day one.
• Buried joints in the false ceiling. Home-run everything; a joint above a sealed ceiling is a fault you cannot reach.
• Sizing for download speed and ignoring the uplink. Remote camera viewing is an upload problem, and Indian uplinks are frequently a fraction of the download figure.
• Forgetting the ONT when planning UPS backup. A backed-up router with a dead fibre terminal still has no internet.
• No spare conduit. The one item that makes every future change cheap, and the one most often value-engineered out.

How Pert delivers it — a designed solution, not a DIY kit

Pert is a solutions company: we design and install. For the network that means we issue a drawing, not a shopping list. We mark the equipment cabinet position, each access point position in the false ceiling, every CAT6 drop with its label, the camera runs, the spare conduit route and the backed-up socket requirements — and that drawing goes to your electrician before plastering, alongside the lighting circuit drawing and the keypad schedule, so all three sets of requirements land on the walls in one coordinated exercise rather than three arguments.

At installation we terminate and test every drop, position the access points from an on-site survey rather than from the plan alone, fix addresses for the controller, NVR and access points, set the 2.4GHz channel after scanning what the building is already using, and commission the system so that every Stella keypad press, every tunable and dimmable lighting scene and every motorised curtain movement runs locally and keeps running with the broadband unplugged. Handover includes the as-built network drawing, the labelled cabinet, the SSIDs and fixed addresses in writing, and the ability for you to change your own Wi-Fi password without calling anybody. If you are comparing providers, ask each one for the network drawing they would issue before plastering — our guide to the best home automation companies in Hyderabad covers the rest of what to check before you sign.

Frequently asked questions

How many Wi-Fi access points does a smart home need?

Plan on roughly one access point for every 700 to 900 sq ft of built-up area on a single floor, and at least one per floor regardless of area, because a slab attenuates a signal far more than a wall does. In practice that means a 1,200 sq ft 2BHK is usually fine on a single well-placed router, a 1,600 to 2,000 sq ft 3BHK wants a router plus one additional access point, and a three-level villa of 3,500 sq ft wants three or four with one on each floor. The number matters less than the positions: an access point belongs in the ceiling or high on a wall near the centre of the area it serves, in open air, not inside a wooden cabinet, not behind a television, and not in the utility cupboard where the internet cable happens to enter. Rooms with heavy attenuators between them and the nearest access point — a lift shaft, a mirrored wardrobe, a granite or brick core wall, a metal-clad kitchen — usually need their own node even when the square footage says otherwise. In an Indian home the two positions that most often turn out to be short of signal are the master bathroom and the far balcony, and both are worth walking with a signal test before the ceiling is closed.

Do I need to run network cables for home automation, or is Wi-Fi enough?

Most automation devices themselves work perfectly over wireless, but the infrastructure that carries them should be wired wherever it is fixed and permanent. The rule we design to is simple: anything mounted in a ceiling or a rack gets a cable; anything a person holds or moves does not. In practice that is a CAT6 drop to each planned access point position, one to the equipment cabinet, one to the TV niche, one to each fixed camera position or to the NVR location, and one spare to the study — typically six to ten drops for a three-bedroom flat, all terminated back to one small cabinet. Cable is the cheapest item on the entire automation bill of quantities during construction and among the most disruptive to add afterwards, because it means chasing finished walls and reopening a false ceiling. A wired backhaul to each access point also roughly doubles the usable throughput of a mesh compared with wireless backhaul, since the node is no longer spending half its airtime relaying to its parent. If the walls are already closed and no cable is possible, a well-placed wireless mesh is a genuinely workable answer — it is simply the second-best one.

Will my smart home stop working if the internet goes down?

A properly designed system keeps working. Wall keypads, scenes, dimming, motorised curtains and sensor-driven lighting are executed locally between the keypad, the controller and the load modules, so they continue to respond with no internet at all — the press-to-light delay in a well-commissioned home is well under a fifth of a second, and it does not travel to a data centre to get there. What does stop is the part that genuinely depends on the outside world: remote access from outside the home, cloud video backup, voice assistants that resolve commands online, and software updates. Local Wi-Fi is a different question from internet: if the router itself loses power, wireless devices lose each other even though the broadband is fine, which is why we put the router, switch and access points on a small UPS. A 600VA to 1kVA UPS carries a typical home's networking gear for two to four hours, which covers ordinary Hyderabad outages, and if the property has a generator or inverter backing the lighting circuits the network should be on the same backed supply.

Why do smart devices need 2.4GHz Wi-Fi and not 5GHz?

Because range and wall penetration matter far more to a light or a curtain motor than speed does. A device that sends a few hundred bytes to say a curtain reached its end position gains nothing from a fast band, and 2.4GHz travels noticeably further through masonry, which is what a device buried above a false ceiling or inside a curtain pelmet needs. Most Wi-Fi smart-home hardware is therefore 2.4GHz only, and the practical consequence is a setup problem people meet constantly: if the router broadcasts both bands under one name, the phone attaches to 5GHz while the device is trying to join 2.4GHz, and pairing simply fails for no visible reason. The fix is to give 2.4GHz its own network name — many installers keep a dedicated IoT SSID on 2.4GHz for exactly this — or to temporarily disable the 5GHz radio during commissioning. It is also why we count devices during design: a typical 3BHK ends up with 40 to 60 connected endpoints, and the older single-band routers supplied free with a broadband connection start to struggle in that range.