In this guide
- Why the protocol matters more than the brochure suggests
- The contenders: how each one actually connects
- Head-to-head: the comparison table
- Six real-world tests for a Hyderabad home
- Matter and Thread: what they mean for Indian buyers today
- Which protocol for which job — and why Pert chose Zigbee
- Questions to ask any installer about protocols
- How Pert delivers it (designed, not DIY)
- FAQs
This article is part of our wider coverage of home automation in Hyderabad. If you want the inner workings of a Zigbee network — coordinators, routers, end devices and how the mesh heals itself — read how a Zigbee mesh network works in a smart home alongside this one. Here we step back and compare Zigbee with the alternatives.
Why the protocol matters more than the brochure suggests
Product brochures talk about finishes, colours and app screens. The protocol decides five things you only notice after you have lived with the system:
- Reach. Whether a signal from the gateway gets to the curtain motor in the far bedroom, through two RCC walls and a steel-framed wardrobe.
- Crowding. Whether 60 or 80 devices can share the airwaves with your Wi-Fi and the 20-plus neighbouring networks in an apartment tower.
- Timing. Whether a scene feels instant and together, or ripples across the room.
- Independence. Whether keypads, scenes and sensor automations keep working when the internet, the Wi-Fi router or a manufacturer's cloud is down.
- Batteries. Whether door and motion sensors run for a year or more, or need charging every few weeks.
None of these is visible on the day of installation, and all of them are expensive to change later, because the protocol is tied to every switch module, driver, motor and sensor in the house.
The contenders: how each one actually connects
Wi-Fi (star network through your router)
Every Wi-Fi smart device joins your home router as a client, just like a phone or laptop. Nothing relays for anything else: if a device cannot hear the router, it drops off. Most smart plugs, budget smart switches and bulbs use the 2.4GHz band because it travels further than 5GHz. Wi-Fi has lots of bandwidth, which is why it is the right choice for cameras and video doorbells, but it draws more power, and most budget devices are controlled through the manufacturer's cloud rather than locally.
Zigbee (low-power mesh through a gateway)
Zigbee uses the IEEE 802.15.4 radio standard at 2.4GHz, at a modest 250 kbps — plenty for "turn on", "dim to 40%" or "door opened". A gateway (the coordinator) forms the network; mains-powered devices such as keypads, relay modules, drivers and curtain motors act as routers that pass messages on; battery sensors are end devices that sleep most of the time. More mains devices mean more paths, so the network gets stronger as the home fills up. Zigbee 3.0 unified the older application profiles, and group and scene commands are built into the standard.
Bluetooth SIG Mesh (flooding mesh, phone-friendly)
Bluetooth Mesh, published by the Bluetooth SIG in 2017, runs on Bluetooth Low Energy. Instead of choosing a route, it uses managed flooding: a message is rebroadcast by relay nodes until it reaches its destination or its hop limit runs out. It is popular in Indian smart lighting because a phone can talk to nearby fixtures directly without a hub. Remote access, schedules and automations when nobody's phone is nearby still need a gateway.
Thread and Matter (IP mesh plus a cross-brand language)
These two are often mentioned together but do different jobs. Thread is a low-power IPv6 mesh on the same 802.15.4 radio as Zigbee, connected to your home network through a border router (several smart speakers and hubs include one). Matter is an application standard from the Connectivity Standards Alliance — the same body that maintains Zigbee — that describes devices in a common way so that different brands and platforms can control them locally. Matter runs over Wi-Fi, Thread and Ethernet.
Wired: KNX and RS-485
Wired systems run a dedicated bus cable to every keypad and controller. KNX is an open international standard with a long track record in high-end projects; RS-485 is an industrial serial link that some Indian wired systems use underneath their own protocol. No radio means no interference, but the bus has to be planned before plastering, and changes later mean new cable.
Head-to-head: the comparison table
Figures below are typical, not guarantees; real behaviour depends on the product, the firmware and above all on how the system is planned.
| Wi-Fi | Zigbee | Bluetooth SIG Mesh | Matter over Thread | KNX / RS-485 | |
|---|---|---|---|---|---|
| Topology | Star, every device to the router | Routed mesh; mains devices relay | Flooding mesh; relay nodes rebroadcast | Routed IP mesh; mains devices relay | Wired bus |
| Hub needed? | No (router only) | Yes, a gateway | For remote access and automations | Yes, a Thread border router | Yes, bus power and controllers |
| Radio | 2.4GHz / 5GHz, high bandwidth | 2.4GHz, 250 kbps | 2.4GHz BLE | 2.4GHz, 250 kbps | None |
| Battery sensors | Weeks to months; slow to wake | Typically a year or more on a coin cell | Possible via low-power nodes | Typically a year or more | Usually wired power |
| Practical scale in a home | Many home routers struggle past a few dozen clients | Comfortable at 100+ devices with good router placement | Large networks need careful relay tuning | Designed for hundreds of devices | Hundreds; limited by bus design |
| Many lights at once | Usually one command per device, so lights can ripple | Group and scene commands built in | Group addressing supported | Group commands supported | Group addresses; very precise |
| Without internet | Often fails for app and voice on cloud-only devices | Keypads, scenes and automations run on the local gateway | Local phone control nearby; gateway for the rest | Local control by design | Fully local |
| Best at | Cameras, doorbells, streaming | Whole-home control: keypads, lights, curtains, sensors | Lighting fixtures, phone-first control | Cross-brand control, future platforms | New builds wanting a fully wired backbone |
Six real-world tests for a Hyderabad home
1. The RCC wall test
Hyderabad homes are built from reinforced concrete, often with granite or tiled walls in kitchens and bathrooms and mirrored or steel-framed wardrobes. Every one of these eats 2.4GHz signal. A single Wi-Fi router in the living room that reaches phones fine may not reliably reach a curtain motor behind a pelmet in the master bedroom. Mesh protocols handle this better, because the keypad in the passage and the driver in the bedroom ceiling relay for each other, so no device needs a direct line to the hub. On a star network, the only fix is more Wi-Fi access points.
2. The apartment-tower congestion test
Open the Wi-Fi list on your phone in a Gachibowli or Kokapet tower and you may see 20 or 30 networks. All of them, plus Bluetooth devices and microwave ovens, share the same 2.4GHz band. Zigbee's narrow channels can be placed in the gaps: Zigbee channels 15, 20 and 25 sit between the common Wi-Fi channels 1, 6 and 11. A designed system picks its channel after surveying the site. Our guide to planning Wi-Fi and the network for a smart home covers the Wi-Fi side of the same problem.
3. The "all off" test
Press Leaving at the door and ask 30 to 40 lights, three curtains and the AC to change together. If the system has to send each device its own command — common with app-driven Wi-Fi devices — lights go off in a visible ripple, and one or two may miss the command on a busy network. Zigbee, Bluetooth Mesh, Thread and KNX can all address a group in one message, so a well-configured scene lands together. This is one of the biggest reasons a designed system feels premium; see why scene-based automation is better than app-only smart devices.
4. The broadband outage test
Unplug the internet and try everything: keypads, scenes, motion-triggered passage lights, schedules. On a local-first system with a gateway, all of that should keep working, and only remote access and phone notifications pause. On cloud-dependent Wi-Fi devices, app and voice control commonly fail even though your phone is in the same room. Do smart homes work during power cuts and internet outages? goes through each scenario.
5. The battery test
Door contacts, motion sensors and wireless remotes are battery powered. Wi-Fi is too power-hungry for a coin cell to last long, so Wi-Fi sensors either need bigger batteries and frequent changes, or sleep deeply and take a second or more to wake and report. Zigbee and Thread were designed for sleeping end devices, which is why a door sensor can report instantly and still run for a year or more.
6. The power-cut and inverter test
After a power cut, a Wi-Fi device has to rejoin the router and often reconnect to its cloud before it responds to the app. A Zigbee network rejoins its gateway locally. Either way, put the gateway and router on an inverter-backed circuit, and make sure switch modules restore to a sensible state (usually off) rather than all lights coming on at 3am when power returns.
Matter and Thread: what they mean for Indian buyers today
Matter is genuinely good news for the industry. It gives devices a shared language, keeps control local, and allows multi-admin — the same device can be controlled from more than one platform at once. Over time it should make it easier to add a new brand's product to an existing home.
Being fair about where it stands in India today:
- The device range is uneven. Matter smart plugs and bulbs are easy to find; Matter wall keypads, dimmers suited to Indian wiring and switch boxes, and curtain motors with local installer support are still limited.
- Matter is not a design. It standardises how devices describe themselves. It does not decide which lights belong in which scene, where the mesh routers go, or what happens when the power comes back. That still has to be designed.
- Thread and Zigbee share the same radio. The mesh physics — walls, routers, channels — are the same, so the planning principles carry over.
- Waiting has a cost. Holding off for years means years without the comfort, security and energy savings of a working system.
Our advice: do not choose a system just because it carries a Matter logo, and do not delay a project waiting for one. Choose a local-first system that is designed and supported properly, and ask how it connects to voice assistants and other platforms today. For voice specifically, see home automation with Alexa and Google Home in Hyderabad.
Which protocol for which job — and why Pert chose Zigbee
No single protocol is best at everything, and a well-designed home uses more than one, each where it is strongest:
| Job in the home | What works best | Why |
|---|---|---|
| Keypads, lighting, dimming and tunable white | A low-power mesh with a local gateway | Group scenes, local control, strong coverage through walls |
| Motorised curtains | The same mesh as the lights | So curtains are part of the same scenes and automations |
| Door, motion and presence sensors | Zigbee or Thread | Long battery life and instant reporting |
| Cameras and video doorbells | Wi-Fi or wired Ethernet | Video needs bandwidth that low-power meshes do not have |
| ACs and IR-controlled appliances | An IR blaster on the control system | Brings existing appliances into scenes without replacing them |
| Very large new builds wanting a wired backbone | KNX or another wired bus | Maximum robustness, planned before plaster |
For whole-home control, Pert builds on Zigbee. Pert's Stella keypads, smart lighting, motorised curtains and sensors work together as one Zigbee system through the Pert gateway, so scenes and automations run locally inside the home. Where Wi-Fi is the right tool — cameras and the video doorbell in our security range — we use it. We chose Zigbee because it is mature, low-power, a true mesh that gets stronger as more devices are added, has groups and scenes built in, and does not depend on the internet for everyday control. Its limitations — it needs a gateway and it needs mesh and channel planning — are exactly the kind of thing a solution business solves at design stage, rather than something the homeowner lives with. The broader wired-versus-wireless picture is covered in wireless home automation: what homeowners should know.
Questions to ask any installer about protocols
- Which protocol do the keypads, lights, curtains and sensors use — is it one system or several apps?
- If our internet is down, what exactly keeps working? Ask for a demonstration with the router's WAN cable unplugged.
- How do you make 30 lights change together? Listen for group or scene commands, not "the app sends them quickly".
- How do you plan coverage through our walls? A good answer mentions router devices, gateway placement and a site survey.
- Which channel will the system use, and how do you avoid our Wi-Fi and the neighbours'?
- How long do the sensor batteries last, and who reminds us to change them?
- How does the system work with Alexa, Google Home or other platforms?
- What happens when power returns after a cut?
Our guide to the best home automation companies in Hyderabad lists the wider questions worth asking before you sign.
How Pert delivers it — a designed solution, not a DIY kit
With a DIY setup, the protocol is whatever the cheapest device in the shopping cart happened to use, and the homeowner discovers the consequences later: a Wi-Fi plug here, a Bluetooth bulb there, three apps and no scene that reliably covers all of them. On a Pert project, the protocol is a design decision made once, for the whole house. We survey the site, including walls, wardrobes and the neighbouring Wi-Fi networks; place the gateway centrally on inverter backup; plan where mains-powered keypads, drivers and curtain motors will act as mesh routers so every sensor has strong paths; choose a Zigbee channel clear of your Wi-Fi; build scenes as group commands so they land together; bring ACs in through an IR blaster and keep cameras on Wi-Fi where they belong; test everything with the internet unplugged before handover; and support the system after that. The result is one coherent system on the wall, not a collection of gadgets.
Not sure which protocol your home needs? We will survey your flat or villa, explain the trade-offs in plain language, and show you how a Zigbee system behaves at our Begumpet experience centre. Request a consultation →
Frequently asked questions
Is Zigbee better than Wi-Fi for home automation?
For switches, keypads, lights, curtains and sensors across a whole home, Zigbee is usually the better fit: it is a low-power mesh where mains-powered devices relay for each other, battery sensors can last a year or more, a gateway in the home runs scenes locally, and group commands switch many lights at once. Wi-Fi is better for devices that move a lot of data, such as cameras and video doorbells. Most well-designed homes use both.
Should I wait for Matter before installing home automation?
Usually not. Matter is promising and supports local control, but in India the range of Matter wall keypads, curtain motors and professionally supported systems is still limited. Install a well-designed local-first system now, with wiring, neutral wires and the network planned properly, and ask your installer how it connects to voice assistants and other platforms today.
Why do some Wi-Fi smart switches stop working when the internet is down?
Many budget Wi-Fi switches are controlled through the manufacturer's cloud, so an app tap or voice command travels to a server and back. If the broadband is down, that path breaks and app and voice control fail, even though the switch is a few metres away. The physical button usually still works. Gateway-based systems such as Zigbee keep keypads, scenes and automations running inside the home.
Can Zigbee, Wi-Fi and Bluetooth devices work together in one smart home?
Yes, but not directly — they use different radios and languages, so they are brought together through a gateway, a platform or a voice assistant. A designed home uses one main control protocol for keypads, lights, curtains and sensors, and adds Wi-Fi devices such as cameras and video doorbells where they make sense. Mixing many unrelated apps without a plan is what makes smart homes feel unreliable.