Decide in this order
- 1. Scenes and daily operation — what the family or facility team actually does, hour by hour.
- 2. Control surfaces — keypad, app, voice, panel, or scheduled logic. Voice is never the primary surface.
- 3. Topology — wired backbone with wireless only at the leaves.
- 4. Cabling and containment — the only irreversible decision on the list.
- 5. Protocols and platform.
- 6. Products.
- Most projects run this list backwards, starting with a brand, and then discover the cabling will not support it.
Protocol trade-offs
| Protocol | Strength | Watch out for |
|---|---|---|
| KNX | Open, wired, decades of device support, no cloud dependency | Needs a trained integrator and ETS discipline |
| DALI-2 | The right answer for serious lighting control and tunable white | Bus power supplies and addressing must be planned, not improvised |
| BACnet/IP | Standard for HVAC and building services integration | Point naming discipline decides whether analytics is possible later |
| Zigbee / Thread / Matter | Good for retrofit and leaf devices | Mesh reliability depends on mains-powered node density |
| Proprietary ecosystems | Fast, polished user experience | Platform risk — verify local control survives an internet outage |
Cabling and containment benchmarks
- Home-run Cat6A to every control point, keypad and sensor location — wireless is a fallback, not a plan.
- A dedicated, ventilated equipment room or rack with a spare 30% U-space and 30% spare breaker capacity.
- Separate containment for control bus and mains, with 20% spare conduit fill for the second phase.
- Two structured cabling drops behind every display, not one.
- Neutral wire at every switch box — the most common retrofit blocker in Indian residences.
- Labelled, tested and certified links with a printed test report as a payment milestone.
Reliability rules
- Every automated function must have a manual override that works with the internet down.
- Local processing for anything safety- or comfort-critical; cloud only for remote access and updates.
- One time source, one authentication directory, one logging destination.
- UPS the controllers, the network core and the gateway — not just the rack.
- No single-vendor lock on the network layer; keep switching and Wi-Fi independently serviceable.
Commissioning and handover pack
- As-built schematics, panel schedules and IP address plan.
- Full device inventory with firmware versions and licence expiry dates.
- Scene documentation in plain language, one page per room.
- Admin credentials handed to the owner in writing — not retained solely by the integrator.
- Recorded walkthrough for the household staff or facility team.
- A defined AMC scope: response times, firmware policy, and who owns the programming files.
Failure patterns worth avoiding
- Automation specified after electrical drawings are frozen.
- Wireless-first design in a concrete-and-steel structure.
- Programming files held hostage by the integrator.
- Scenes designed for a showroom demo rather than for a Tuesday morning.
- No documented rollback when a firmware update breaks a driver.
Frequently asked
- When should automation be designed into a project?
- At architectural and MEP stage, before electrical layouts are frozen. Cabling, containment, panel space and the equipment room are the decisions that cannot be retrofitted cheaply; product selection can wait.
- Is wired or wireless automation better?
- Wired backbone, wireless leaves. In Indian concrete-and-steel construction a wireless-first design tends to degrade as the home fills with furniture, appliances and neighbouring networks.
- Who should own the programming files?
- The client. Programming files, admin credentials and licence records belong in the handover pack. If an integrator retains them, the owner cannot change service partners without rebuilding the system.
- Does Matter remove the need for a wired backbone?
- No. Matter improves interoperability at the device layer; it does not change the physics of signal propagation, the need for local control during outages, or the value of home-run cabling.
Cite this reference
Arif Khan, “The Smart Automation Playbook”, arifkhanglobal.com, 2026.
Free to quote and republish in part with a link to arifkhanglobal.com/resources/smart-automation-playbook.