In this guide
- Seven signs you have outgrown app-by-app devices
- Why Wi-Fi collections hit a ceiling (and where Wi-Fi is still right)
- The audit: keep, replace or repurpose
- A migration order that keeps the home working
- Rebuilding routines, voice and apps without double control
- A worked 3BHK before and after
- Migration mistakes to avoid
- 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 protocol background first, Zigbee vs Wi-Fi vs Bluetooth Mesh vs Matter compares the technologies head to head. This guide is about the practical move: from what you already own to a system that behaves as one.
Seven signs you have outgrown app-by-app devices
Individually bought smart devices are a good way to discover what you actually want automated. The problem is not any one device; it is what happens when there are many of them and nobody designed how they fit together. If three or more of these are true, the home has outgrown its setup:
| Sign | What is really going on |
|---|---|
| You need three or more apps to run the house | Each brand is its own island. Anything that spans brands has to be stitched together through a voice assistant or a third-party service. |
| Guests and elders switch the bulbs off at the wall and then nothing responds | A smart bulb needs constant power. A normal switch cuts it off, so the "smart" part only works if everyone remembers not to use the switch. |
| Routines fire late or partly — two lights change, one does not | Each device is commanded separately, often through its own cloud; one slow or offline device breaks the scene. |
| Devices drop off after a power cut or a router change | Wi-Fi devices reconnect at their own pace after an outage, and some need re-pairing when the router, its password or its band settings change. |
| Nothing works when the internet is down | Control runs through the brands' cloud services rather than a controller inside the home. |
| The Wi-Fi itself feels slower since the devices were added | Dozens of low-traffic clients on a crowded 2.4GHz band in a tower, competing with neighbours' networks. |
| Only one person knows how it works | There is no wall control, no common naming and no written list of what does what. When that person travels, the house goes back to manual. |
Why Wi-Fi collections hit a ceiling (and where Wi-Fi is still right)
Wi-Fi was designed to move large amounts of data to phones and laptops. A light or a curtain sends a few bytes a few times a day. Using Wi-Fi for every switch works at small scale and becomes awkward at large scale, for four reasons:
- Every device is a separate router client. Thirty smart devices plus the family's phones, laptops, TVs and tablets can mean fifty or more clients. Many consumer routers handle that badly — especially the ISP-supplied units common in Hyderabad apartments — and the symptoms look like "random" device dropouts. How to plan Wi-Fi and network for a smart home covers the network side in detail.
- Each brand usually means its own cloud. A command from the app typically goes from your phone to the brand's server and back down to the device. A routine involving three brands depends on three services and your internet connection all being up at once.
- No shared local brain. In a collection of devices, there is nothing in the home that knows a "Movie" scene means curtains, cove light and downlights together. Each device obeys separately, which is why scenes "popcorn" — lights changing one after another instead of together.
- 2.4GHz congestion. Most smart plugs and bulbs use 2.4GHz Wi-Fi only. In a high-rise with dozens of neighbouring networks, that band is already crowded before you add your own devices.
A designed Zigbee system — the kind Pert installs — takes lighting, curtains, keypads and sensors off Wi-Fi entirely. They form their own low-power mesh run by a gateway in the home, so scenes, groups and schedules are executed locally and the Wi-Fi is left for the devices that need it. How a Zigbee mesh network works explains the coordinator, routers and end devices behind this.
To be fair to Wi-Fi: it remains the correct choice for high-bandwidth devices — security cameras, video door phones, TVs, streaming boxes and voice speakers — and for a handful of standalone gadgets in a home that does not want a full system. The point of an upgrade is not to remove Wi-Fi; it is to stop using it for jobs a wired-in control system does better.
The audit: keep, replace or repurpose
Before anything is bought, list every connected device in the home with its room, brand, app and what it actually controls. Then sort each one into a column. In most homes we see, well over half of the investment in cameras, speakers and entertainment stays exactly where it is.
| Device you have | Usual decision | Why |
|---|---|---|
| Wi-Fi security cameras, video door phone | Keep | Video needs Wi-Fi or wired Ethernet bandwidth. Keep them on the network, ideally on a properly placed access point. |
| Voice speakers (Alexa, Google) | Keep | They become a voice front-end for the new system's scenes. Home automation with Alexa and Google Home covers how that link works. |
| Smart TV, streaming box, IR-controlled AC | Keep | Their own control is fine; scenes can include them through IR or the assistant where appropriate. |
| Smart bulbs in ceiling fixtures or downlights | Replace | Move the intelligence to the circuit: dimmable and tunable lighting on controllers behind a wall keypad, so the wall switch and the automation are the same thing. |
| Smart plugs switching lamps or light strips | Replace where the lamp is part of a scene | A plug is a weak link in a scene: it can be unplugged, moved or knocked off Wi-Fi. Lamps that belong to a scene go on a controlled socket or circuit. |
| Smart plugs on a heater, kettle or study lamp | Repurpose | Standalone timers and occasional remote switching are exactly what a plug is good at. Keep them out of scenes. |
| Retrofit curtain robots on rods | Replace where curtains are used daily | Daily-use curtains are better on a proper motorised track that can join scenes and schedules reliably. |
| Wi-Fi door and motion sensors | Replace if they trigger lights or alarms | Sensors that drive automations should be on the same local system as the loads they control, with long battery life. See Pert's security range. |
The audit also surfaces what you actually use. The device that gets used every day — usually the bedroom lamp and the living-room lights — tells you which scenes matter. The plug that has not been touched in a year tells you something too.
A migration order that keeps the home working
The household should never be without working lights. A good migration is staged so each room switches over cleanly, and rooms not yet done keep running on the old devices.
- Survey and plan on paper. Map every switchboard, circuit and window; check which switch boxes have a neutral and enough depth (how to add home automation to existing modular switches explains this survey). Write the scenes per room before choosing hardware.
- Backbone first. Install the gateway in a central position on an inverter-backed circuit, and fix the Wi-Fi: router placement, set channels instead of auto, and an access point where the signal is weak. Nothing else is reliable until this is.
- Living and dining next. This is where scenes are used most and where the old setup usually frustrates most. Lighting circuits go onto controllers, the keypad goes in at the entrance to the room, curtains go on tracks.
- Bedrooms one at a time. Bedside keypads with Good Night and Morning, master-bedroom curtains, and the bedside lamp moved off its smart bulb.
- Passages, entrance and sensors. Motion-triggered night paths and door contacts are added once the mesh is in place across the home, because battery sensors rely on nearby powered devices to route through.
- Whole-home scenes last. Leaving, Arrive, Master off and away mode only make sense once every room they touch is on the new system.
At each step, the room's old devices are removed in the same visit they are replaced. That is the single most important rule of a migration, and the next section explains why.
Rebuilding routines, voice and apps without double control
The worst outcome of a half-finished upgrade is two systems controlling the same light. An old voice routine switches the living room off at 11pm while the new Good Night scene is fading it down; a smart plug timer switches a lamp the new scene thinks it owns. The rule is simple: one owner per load.
- Delete, don't disable. When a room moves over, remove its old devices from their apps and from the voice assistant, and delete every old routine that touched them. Disabled routines have a way of being re-enabled by an app update.
- Factory-reset devices you remove. Before a bulb or plug goes into a drawer or to a relative, reset it and remove it from the brand account, so it no longer holds your Wi-Fi password or appears in your account.
- Rename for people, not for brands. Use one naming pattern across the new system and the voice assistant: Living – Cove, Living – Downlights, Master – Sheers. Duplicate names are the main cause of "Alexa, which one?".
- Voice calls scenes, not bulbs. "Movie time" should trigger the Movie scene, which the gateway runs locally, rather than a voice routine that commands five devices one by one.
- Rebuild automations deliberately. Do not copy across every old timer. Most turn out to be workarounds for the lack of a wall keypad, and disappear once there is one. The ones that remain become proper schedules and sensor automations on the gateway.
A worked 3BHK before and after
A typical example: a Gachibowli-area 3BHK, about 1,800 sq ft, with devices added over three years.
| Before | After | |
|---|---|---|
| Lighting | 14 Wi-Fi smart bulbs in pendants, lamps and two downlights; the rest on normal switches | All living, dining and bedroom lighting circuits on dimmable or tunable controllers; bulbs removed from fixtures |
| Control | 4 apps, 1 voice speaker, wall switches that disable the bulbs | Keypads at the entrance, living, dining and each bedside; one app; the same voice speaker calling scenes |
| Curtains | 2 rod-mounted curtain robots, frequently out of battery | Motorised tracks on the living and master-bedroom windows, in scenes and on a sunset schedule |
| Sensors | 1 Wi-Fi door sensor sending phone notifications | Door contacts on the main and balcony doors, motion sensors for the passage night path, all on the local mesh |
| Plugs | 6 smart plugs, 4 of them switching lamps | 2 kept for a study heater and a kettle; 4 retired after their lamps moved onto controlled circuits |
| Wi-Fi clients | About 45, on an ISP router in a bedroom corner | About 20 (phones, laptops, TVs, cameras, speakers), on a centrally placed router plus one access point |
| Kept unchanged | 2 cameras, the video door phone, the TV and streaming box, the voice speaker | |
The visible difference for the family is not the device count. It is that every room has a wall control that always works, scenes change together instead of one light at a time, and the evening lights still come on when the internet is down.
Migration mistakes to avoid
| Mistake | What goes wrong | Do this instead |
|---|---|---|
| Buying hardware before listing the scenes | Circuits get grouped wrongly and a scene cannot be built later without rewiring | Write each room's scenes first, then plan circuits and keypads |
| Leaving smart bulbs inside a newly controlled circuit | Two dimming systems fight; flicker and dropouts | Use ordinary compatible lamps on a controlled circuit |
| Keeping old routines "just in case" | Ghost actions at odd times; nobody knows which system did it | One owner per load; delete old routines as each room migrates |
| Skipping the network fix | Cameras and phones still struggle, and the upgrade gets the blame | Fix router placement and channels as step two |
| Doing whole-home scenes first | Master-off misses half the house | Build whole-home scenes only after every room is migrated |
| No handover list | The family still does not know what each button does | A written scene list per room and engraved keypads |
How Pert delivers it — a designed solution, not a DIY kit
An upgrade is a design job before it is an installation job. Our team starts by auditing every connected device in the home with you and marking what stays, what is replaced and what is repurposed. We survey the switchboards, circuits, windows and Wi-Fi coverage, write the scenes for each room in plain language, and plan the migration in stages so the home keeps working throughout. We install the gateway and fix the network backbone first, then move rooms over one at a time — removing old devices and routines in the same visit — and finish with whole-home scenes and voice linking. Pert's keypads, lighting, curtains and security devices work together as one Zigbee system through the Pert gateway, and before handover we test every room with the internet disconnected and leave you with an engraved, labelled set of keypads and a written scene list.
If you are comparing who should take on the upgrade, best home automation companies in Hyderabad lists the questions worth asking — including how they handle the devices you already own.
Got a home full of smart devices that never quite became a smart home? We will audit what you have, keep what works, and plan a room-by-room move to one designed system with keypads, scenes and local control. Request a consultation →
Frequently asked questions
Do I have to throw away my existing Wi-Fi smart devices when I move to a designed system?
No. Wi-Fi is the right technology for some devices and they should stay: security cameras, video door phones, smart TVs, streaming boxes and voice speakers all need Wi-Fi bandwidth. What usually gets replaced are devices doing a job that belongs in the wiring, such as smart bulbs in ceiling fixtures and smart plugs used to switch lights. Those loads move onto keypads and lighting controllers. Retired plugs can often be reused for a heater, a kettle or a study lamp.
Why do Wi-Fi smart devices become unreliable as I add more of them?
Every Wi-Fi device is a separate client of your router, and most depend on their own brand's cloud. As the count grows, the 2.4GHz band in an apartment tower gets more congested, many consumer routers struggle with a large number of clients, and a routine across three brands needs three clouds and your internet to be working at once. A designed Zigbee system moves lighting, curtains, keypads and sensors onto their own low-power mesh run by a local gateway, leaving Wi-Fi for phones, laptops, TVs and cameras.
Can I migrate one room at a time, or does the whole home have to change at once?
Room by room is the usual and safer approach. The gateway and network backbone go in first, then rooms move over one at a time, typically starting with the living and dining area. Old devices keep working in rooms not yet migrated. The rule is that a load has only one owner: when a room moves over, its old bulbs, plugs and app routines are removed, so two systems never fight over the same light.
Will my Alexa or Google Home voice commands still work after the upgrade?
Yes, but they are rebuilt rather than carried over. The new system's scenes and devices are linked to your assistant with clear, room-based names, and the old devices are deleted so there are no duplicates. Old voice routines that called individual bulbs are replaced by routines that call a scene, such as "movie time" triggering the Movie scene. Voice becomes one of several ways to run the same scenes, alongside the keypads and the app.