In this guide
- The theoretical limit versus the practical limit
- The three constraints that really decide capacity
- Routers and end devices: not all devices count equally
- Illustrative device counts for Hyderabad homes
- Signs a system is outgrowing its design
- Planning headroom for rooms you add later
- How Pert delivers it (designed, not DIY)
- FAQs
This article is part of our wider coverage of home automation in Hyderabad. It builds on how a Zigbee mesh network works and what a smart home gateway does, because capacity is really a question about those two things working together.
The theoretical limit versus the practical limit
The Zigbee specification can address tens of thousands of devices on one network. That figure is real, and it is nearly irrelevant to a home. It describes the size of the address space, not the number of devices a particular gateway, in a particular building, with a particular radio environment, will run reliably.
The practical limit is set by the weakest of several things: how many devices the specific gateway is built and tested to manage, how many routing and child slots the mains-powered devices offer, and how clean the radio channel is. A buyer should therefore ignore the biggest number in any brochure and ask a narrower question: what is the tested figure for the exact gateway you will install, and what is the plan for my floor plan?
For comparison, Wi-Fi smart products hit a different wall. Every device joins the home router, and consumer routers typically become unreliable well before they reach their advertised client counts, which is one reason we explained in Zigbee vs Wi-Fi vs Bluetooth mesh vs Matter why Pert builds on Zigbee rather than putting every device on the family's Wi-Fi.
The three constraints that really decide capacity
1. Gateway capacity
The gateway keeps the device list, the network keys, the scenes and the automation rules, and it coordinates the network. Each gateway model is built and tested for a certain number of devices; beyond that, behaviour can degrade in ways that are hard to trace. Treat the manufacturer's tested figure, not the protocol's theoretical one, as the ceiling, and keep the installed system comfortably below it. Capacity also covers scenes and automations: a home with a hundred devices and a few hundred rules asks more of the gateway than the same home with simple scenes.
2. Mesh health
In a Zigbee network, mains-powered devices can act as routers, passing other devices' messages along. A mesh with routers spread evenly through the home has many short, strong links and several alternative routes; a mesh with the same number of devices bunched in one room has long, weak links and single points of failure. Concrete walls, lift shafts, false-ceiling metal and the gap between floors in a Hyderabad villa all weaken links, which is why placement matters as much as count. The planning method is covered in our Zigbee mesh explainer.
3. Radio congestion
Zigbee shares the 2.4GHz band with Wi-Fi, Bluetooth, cordless phones and microwave ovens. A dense apartment tower, where dozens of neighbouring routers all shout on the same band, is a harder environment than an independent villa. The fix is design, not luck: choose the Zigbee channel with the Wi-Fi channels in the building in mind, keep the gateway away from the Wi-Fi router, and do not rely on a single weak route. Our post on planning Wi-Fi and the network for a smart home covers the router side of the same problem, and why home automation becomes unreliable shows what congestion looks like in practice.
Routers and end devices: not all devices count equally
A device count of "80" can describe a strong network or a fragile one, depending on what the 80 are. Zigbee devices fall into two groups:
| Device role | Typical examples | Effect on capacity |
|---|---|---|
| Routers (mains-powered) | Light controllers, curtain motors, many keypads and in-wall modules | Each one adds links and routes, so more routers spread through the home make the mesh stronger |
| End devices (usually battery) | Motion sensors, door and window contacts, some small sensors | Do not carry traffic for others; each attaches to a nearby router (its parent) that can only serve a limited number of children |
The design rule that follows is simple: count routers and end devices separately. Twenty door contacts clustered on one balcony wall with no mains-powered device nearby is a bigger risk than sixty light channels spread across the house. The planning habit we use is to ask, for every battery device, "which mains-powered device will this sensor talk to, and how many other sensors share that parent?"
Illustrative device counts for Hyderabad homes
Every home is different, and these are planning illustrations, not Pert specifications. They show the shape of a typical device list, to help you judge whether a quotation is in the right range. The routers-versus-sensors split is the useful part.
| Home type | Mains-powered (router-capable) | Battery sensors | What drives the count |
|---|---|---|---|
| 2BHK flat | Roughly 20–45: lighting channels, a few keypads, a pair of curtain motors | Roughly 4–12: door contacts, a few motion sensors | Number of lighting circuits you dim or group, curtains in the living room and bedrooms |
| 3BHK flat | Roughly 35–70 | Roughly 8–20 | Extra bedrooms, a pooja room, a study, balcony and foyer lighting |
| Villa, 3–4 floors | Roughly 70–160 or more | Roughly 15–40 | Staircases and corridors, outdoor and facade lighting, double-height spaces, every floor's rooms |
Notice that the big drivers are circuits and rooms, not gadgets. A lighting plan with many separately controlled circuits generates the device count, which is why the work in planning dimmer channels and lighting loads and the electrical points checklist sets the size of the system before any product is chosen. A villa is not simply a bigger flat: stairs, floors and outdoor areas add distance, and distance is what stresses a mesh.
Signs a system is outgrowing its design
A system rarely fails at a number. It gives early warning signs, and they are worth knowing:
- Delays that vary. A scene that used to be instant now sometimes lags by a second or two, and the lag differs by room. This often points to a weak link or an overloaded route.
- Devices that occasionally do not respond to a scene, especially those in far corners or on another floor.
- Battery sensors that report late, or drop offline and return, usually clustered in one area.
- Problems that started after adding something. A newly added room or batch of devices followed by flakiness in an old room suggests the mesh around them is thin.
- Troubles that coincide with busy times, such as evenings with many Wi-Fi devices active, which points to radio congestion.
These are fixable. The usual remedies are adding mains-powered devices in the gaps, re-homing sensors to stronger parents, moving the gateway, reviewing the channel choice, or splitting an oversized scene. Our guide to why home automation becomes unreliable and how to fix it walks through the diagnostic order.
Planning headroom for rooms you add later
Most homes grow: a study becomes a nursery, a terrace is finished, a second floor is added. Systems that cope with growth were planned for it from the start:
- Leave capacity on purpose. A sensible design stays well below the gateway's tested figure rather than at it, so a new room is an addition and not a redesign.
- Keep the device list on record. Every device, its room, its role (router or end device) and its keypad and scene mapping should be documented. Without that record, growth means guessing.
- Put wiring in early. Spare conduits, neutral at switch points and a few extra points in likely future rooms cost little during construction and are expensive afterwards. See how to future-proof a new home for automation.
- Place the gateway for the final home, not the first phase. A gateway in a corner of the ground floor works for a flat and fails for a villa that later gains two floors.
- Plan the second gateway or extra routers for separate buildings. An outhouse or a cottage across the garden is a design decision, not a surprise.
- Re-test after every addition. A short check of the far rooms and the busiest scene after each expansion catches a thin mesh while it is still easy to fix.
Honest installers will also tell you when you should not add a device. Fifty more sensors do not make a home smarter; thoughtfully chosen scenes and a few well-placed sensors usually do more, as we describe in how to design home automation scenes. When comparing quotations, the questions in the guide to the best home automation companies in Hyderabad include how an installer plans for growth.
How Pert delivers it — a designed solution, not a DIY kit
Capacity is a design outcome, which is why Pert designs and installs rather than selling a kit. Our keypads, tunable and dimmable lighting, motorised curtains and sensors and security devices work together as one Zigbee system through the Pert gateway. Before commissioning we list every circuit and device by room, mark which are mains-powered and which run on batteries, place the gateway for the finished home, and check the mesh at the far rooms and outdoor areas. We keep that list as the system's record so that when you add a room or a floor, the work starts from a documented design and not a guess. After handover we look after changes and additions with you.
Planning home automation for a Hyderabad flat or villa — and want it to grow with the house? We will map your circuits, plan the mesh and leave room for what you add later. Request a consultation →
Frequently asked questions
How many devices can a home automation system handle?
It depends on the gateway's tested capacity, the mesh's health and the radio environment. The Zigbee standard can address tens of thousands of devices in theory, but real homes typically use a few dozen to a couple of hundred, which a properly designed system handles comfortably. Ask for the tested figure for the exact gateway and how the mesh will carry it.
Does adding more smart devices make the system slower?
Not by itself. Scenes and keypad presses are short messages, and a local gateway runs the logic. Slowness points to a thin mesh, an overloaded route, an oversized scene or a crowded 2.4GHz band, all solvable by design: more well-placed mains-powered devices, sensible scenes and a clean channel.
Do battery sensors count against the limit the same way as lights?
No. Mains-powered devices act as routers and strengthen the mesh; battery sensors are end devices that depend on a nearby router. Many sensors in one corner with few routers nearby is a capacity risk even if the total looks small, so count the two types separately.
Can I add rooms or devices later without redoing the system?
Usually yes, if the first design left headroom, kept the device list on record and placed the gateway for the finished home. New devices pair with the gateway and the mesh grows as mains-powered devices are added. The risk is a system sized to the exact count with no spare capacity or documentation.