In this guide
- What a gateway is — and what it is not
- The five jobs a gateway does
- How a command travels: keypad, phone, sensor and voice
- Where to place, power and connect it
- What keeps working when something goes down
- Backups, updates, security and growth
- Eight questions to ask an installer about the gateway
- How Pert delivers it (designed, not DIY)
- FAQs
This article is part of our wider coverage of home automation in Hyderabad. It builds on two earlier explainers: how a Zigbee mesh network works, which covers the radio network the devices form, and Zigbee vs Wi-Fi vs Bluetooth Mesh vs Matter, which compares the protocols. Here the focus is the device at the centre of it all.
What a gateway is — and what it is not
A smart home gateway is a small, always-on computer with at least two connections: a low-power radio that talks to the home's automation devices (in Pert's case, Zigbee), and a network connection to the home's router so that phones, remote access and voice assistants can reach it. It sits between the two worlds and translates.
Three common confusions are worth clearing up first:
- It is not the Wi-Fi router. The router gives your phones and TV internet access. The gateway runs the automation. In a Zigbee system, the keypads, light controllers and curtain motors do not connect to Wi-Fi at all; they connect to the gateway's Zigbee network. That is why adding forty automation devices does not crowd the family's Wi-Fi.
- It is not the app. The app is a window into the gateway. Scenes, schedules and automations you create in the app should be saved on the gateway and run there, not on your phone and ideally not in a remote server.
- It is not always a separate box. In Wi-Fi-only product ranges, each device talks to the manufacturer's cloud directly and there is no local hub; the "hub" is effectively a data centre somewhere else. That design is cheap to start with and is the main reason Wi-Fi setups behave differently during internet outages.
The five jobs a gateway does
Whatever the brand, a gateway in a hub-based system does some version of the following five jobs. When something feels slow or unreliable, it is usually one of these that is under strain.
| Job | What it means in practice | What goes wrong if it is done badly |
|---|---|---|
| 1. Network coordinator | In Zigbee, every network has exactly one coordinator. It creates the network, picks the radio channel, holds the network security key, admits new devices when they are paired and keeps track of how they connect through the mesh. | A poor channel choice next to busy Wi-Fi, or a coordinator boxed in metal, gives a weak mesh: delayed commands and devices that "drop off". |
| 2. Local logic engine | Stores and runs scenes (Evening, Good Night), schedules (sunset − 15 min) and sensor automations (motion in the passage after 11pm → path lights at 15%). | If logic runs in the cloud instead, routines slow down or stop during an outage; if it is not backed up, it is lost when the gateway is replaced. |
| 3. Device and state database | Knows every device in the home, what room it belongs to, what each keypad button is mapped to, and the current state of every light, curtain and sensor. | Badly named or unorganised devices make later changes slow and error-prone; stale state makes the app show a light as off when it is on. |
| 4. Bridge to the outside | Connects the local system to the app on your phone, to remote access when you are away from home, and to voice assistants such as Alexa and Google Home. | Weak links here show up as "works on the keypad, slow from the app", or voice commands that time out. |
| 5. Timekeeper and notifier | Keeps an accurate clock for schedules and sunrise/sunset calculations, and sends alerts — a door left open at night, a sensor with a low battery. | A wrong clock or location shifts every schedule; noisy or missing alerts erode trust. |
Jobs 1 to 3 are the heart of the system and should never need the internet. Jobs 4 and 5 use the internet for convenience — remote access, voice, push notifications and time synchronisation — but the home should not fall apart without it.
How a command travels: keypad, phone, sensor and voice
The same light can be switched four different ways, and each takes a different path through the system. Knowing the paths explains most "why is this one slower?" questions.
| You do this | The path | Needs the internet? |
|---|---|---|
| Press Evening on a wall keypad | Keypad → Zigbee mesh → gateway looks up the scene → commands go out over the mesh to each light controller and curtain motor in the scene | No |
| Tap a light in the app, at home | Phone → home Wi-Fi → router → gateway → Zigbee mesh → light controller (some apps route even this through the cloud; a local path is faster and outage-proof) | Ideally no |
| Tap a light in the app, from the office | Phone → mobile data → internet → secure remote-access service → home router → gateway → mesh → light | Yes, at both ends |
| Walk into the passage at night | Motion sensor → mesh → gateway checks the conditions (time, mode, light level) → passage lights at 15% | No |
| "Alexa, movie time" | Voice speaker → internet → voice service → gateway (via its cloud link) → scene runs locally | Yes |
Two things follow. First, the keypad and sensor paths are the ones that must be rock-solid, because they are what the family uses dozens of times a day; they stay entirely inside the home. Second, a scene is one message in and many messages out. A twelve-load Good Night scene puts more traffic on the mesh than switching one light, which is why a well-designed system uses group commands so that a whole room responds together rather than light by light. How group and multi-way control works explains that in detail, and sensor-triggered automation covers the trigger, condition and action logic the gateway evaluates.
Where to place, power and connect it
Because the gateway is the coordinator of a 2.4GHz radio network, its location matters more than most people expect. The rules are simple, and they are much easier to follow when they are decided at the electrical-drawing stage rather than on handover day.
Location
- Central, not at the edge. The gateway does not need to reach every device directly — mains-powered keypads and controllers relay messages through the mesh — but a central gateway shortens every route.
- In the open, not in metal. Metal distribution boards, closed steel racks and the inside of a metal TV unit all block or reflect the radio. A ventilated wooden shelf or an open niche is better.
- A little away from the Wi-Fi router. Both use 2.4GHz. Keep them roughly a metre apart where possible, and keep the gateway away from USB 3 hard drives and set-top boxes, which are known sources of 2.4GHz noise.
- Somewhere cool. Hyderabad summers push enclosed cupboards well above room temperature; electronics last longer with airflow.
| Home | Typical gateway location | Notes |
|---|---|---|
| 2BHK / 3BHK flat | Ventilated niche or shelf near the centre of the home, often close to the living/dining junction, with the router nearby | One gateway is normally sufficient; RCC walls and shafts are bridged by the mains-powered keypads and controllers in each room. |
| Large 4BHK or duplex | Central on the main floor, near the internal staircase if there is one | Check signal at the far bedroom and the utility area during commissioning, not after. |
| G+2 villa | First floor, centrally, with Ethernet from the router where the gateway supports it | Mains-powered devices on each floor and near the staircase carry the mesh vertically; outdoor areas may need a dedicated router device. |
Power
Put the gateway and the Wi-Fi router on the same backed-up circuit — the inverter or a small UPS. In a power cut, the lights on the inverter circuit keep working, but if the gateway restarts every time the grid flickers, scenes and sensors pause while it boots. A dedicated socket at the gateway location, marked on the electrical drawing, avoids the gateway ending up on a power strip behind the TV. Electrical safety and power protection for a smart home covers surge protection and backup in more depth.
Network connection
A wired Ethernet connection from the router is the most dependable link, where the gateway supports it; a strong Wi-Fi signal works where it does not. Either way, the gateway should have a reserved (fixed) address on the router so that the app always finds it. How to plan Wi-Fi and network for a smart home covers router placement, mesh Wi-Fi and the cabling to leave before plastering.
What keeps working when something goes down
The honest test of any smart home is not a demo on a good day; it is what happens on a bad one. In a well-designed hub-based system, failures degrade gracefully:
| What fails | Keeps working | Stops until it is restored |
|---|---|---|
| Internet / broadband | Keypads, scenes, schedules, sensor automations, app control on the home Wi-Fi (if the app supports a local connection) | Control from outside the home, cloud-based voice assistants, push notifications, clock synchronisation |
| Wi-Fi router | Keypads, scenes, schedules and sensor automations — they run between the gateway and the Zigbee devices | All app control, voice and notifications |
| Mains power, inverter on | Everything on the inverter circuit, if the gateway and router are on it too | Loads deliberately left off the inverter, such as heavy appliances |
| Mains power, no backup | Nothing electrical — but on restore, devices return to their configured power-on state and the gateway rejoins the network on its own | Everything, briefly; a good system needs no one to "re-set" it afterwards |
| The gateway itself | The lights, curtains and other loads are unaffected and stay in their current state; what else still works depends on the system's design | Scenes, schedules, sensor automations, app and voice — until the gateway is restarted or replaced from backup |
The last row is the one to ask about specifically. A gateway on backed-up power, in a ventilated spot, rarely fails; but if it does, you want to know in advance what the family can still do from the wall, and how long a replacement and restore takes. Do smart homes work during power cuts and internet outages? walks through the wider reliability picture.
Backups, updates, security and growth
Configuration backups
Months of commissioning live on the gateway: every device, every room, every keypad mapping, every scene, schedule and automation. A Zigbee network's identity — its channel, network ID and security key — is held by the coordinator too. Without a backup, replacing the gateway can mean re-pairing every device in the home. Ask whether the configuration is backed up, where, and who can restore it.
Firmware updates
Gateways and devices receive firmware updates that fix bugs and add features. Updates are good, but an update should be applied deliberately, not in the middle of a Saturday evening party; ask how updates are handled and whether the installer checks the system afterwards.
Security
- Zigbee traffic in the home is encrypted with the network key held by the gateway; new devices can only join while pairing is deliberately opened.
- The weakest link is usually the account, not the radio. The owner — not the installer's personal phone — should hold the main account, with family members added as users.
- Use a strong Wi-Fi password and keep the router's firmware current. Where the router supports it, a separate network for smart devices limits what a compromised gadget elsewhere can reach.
Growth: how many devices, and when to add a second gateway
Zigbee as a standard can address far more devices than any home will ever use; the practical limit is the gateway's capacity and the health of the mesh. For most flats and villas a single gateway runs the whole home. What matters more than raw device count is that the mesh has enough mains-powered devices spread evenly so that every battery sensor and far-corner keypad has a strong route back. Separate buildings — an outhouse, a farmhouse cottage — or very large homes are where a second gateway or a dedicated repeater is considered, and that is a design decision, not something to discover after the fact.
Eight questions to ask an installer about the gateway
- Where will the gateway be installed, and is that location on the electrical drawing with its own backed-up socket?
- Do scenes, schedules and sensor automations run on the gateway in my home, or in a cloud server?
- Can you unplug the internet during the demo and show me the keypads, a schedule and a sensor still working?
- If the gateway itself fails, what can my family still do from the wall, and how quickly can you replace and restore it?
- Is my configuration backed up, and who holds that backup?
- Whose account owns the system, and how do I add or remove family members?
- How do firmware updates happen, and do you check the system afterwards?
- If I add a room or a floor in two years, does the same gateway handle it, and how is the mesh extended?
These questions sit alongside the wider checklist in best home automation companies in Hyderabad, which covers how to compare installers on design, service and support.
How Pert delivers it — a designed solution, not a DIY kit
Pert's keypads, tunable and dimmable lighting, motorised curtains and sensors and security devices work together as one Zigbee system through the Pert gateway. Because we design and install the whole system rather than selling a kit, the gateway is planned like any other part of the home: its location and backed-up socket are marked on the electrical drawing, it is placed in the open away from metal and the Wi-Fi router, and it is connected to the router with a reserved address. During commissioning our team pairs devices in a planned order, names every device by room, checks the mesh at the far rooms and outdoor areas, builds the scenes, schedules and automations on the gateway, and then tests the house with the internet disconnected. At handover the main account is in the owner's name, and after handover we look after updates, changes and additions with you — so the box on the shelf is something you never have to think about.
Planning home automation for a Hyderabad flat or villa? We will design the whole system — gateway, mesh, keypads, lighting, curtains and security — around how your family actually lives, and show you it working with the internet unplugged. Request a consultation →
Frequently asked questions
Is a smart home gateway the same as my Wi-Fi router?
No. The router connects your phones, laptops and TV to the internet. The gateway runs the automation: in a Zigbee system it forms and manages the network the keypads, light controllers, curtain motors and sensors use, stores the scenes, schedules and automations, and runs them locally. The gateway usually connects to the router so the app, remote access and voice assistants can reach it, but the automation should not depend on the router to switch a light.
Does home automation stop working if the internet goes down?
Not in a well-designed local system. When scenes, schedules and sensor automations run on the gateway in the home, they keep working through an internet outage. You lose control from outside the home, cloud-based voice assistants and push notifications until the connection returns. Systems that run their logic in a cloud server can stop altogether, so ask any installer to demonstrate with the internet unplugged.
Where should the smart home gateway be placed?
Centrally, in the open rather than in a metal enclosure, and on backed-up power. In a flat that usually means a ventilated shelf or niche near the middle of the home, connected to the router, with both on the inverter or UPS. Avoid metal distribution boards, closed metal racks and the space right beside the Wi-Fi router or a USB 3 drive. In a multi-floor villa the gateway goes on a middle floor, and mains-powered devices carry the mesh to the other floors.
What happens if the gateway itself fails?
It depends on the system's design, so ask before you buy. The gateway coordinates the network and runs scenes, schedules and automations, so those pause while it is offline; the lights, curtains and other loads are unaffected. A good installer keeps a backup of the configuration, can replace a gateway quickly, and tells you plainly which controls still work in the meantime. Backed-up power and a cool, ventilated location prevent most failures in the first place.