Studio Matrx Monthly · Volume 1 · Issue 2 · July 2026
Amogh N P
 In loving memory of Amogh N P — Architect · Designer · Visionary 
Smart Home Design for Architects & Designers (India)
Smart Home

Smart Home Design for Architects & Designers (India)

The smart layer is an architectural system, not an accessory bought after handover. Here is how to design it at concept and schematic stage, coordinate with your MEP consultant and integrator, and produce drawings that a contractor can actually build.

22 min readAmogh N P5 July 2026Last verified July 2026
An architect's floor plan overlaid with lighting zones, camera positions and a network rack location, marked in coloured pens on tracing over the base drawing

Most Indian smart homes are designed twice. The architect designs the building, the walls close, the client moves in — and then a system integrator is called to bolt automation onto a finished shell. The result is surface conduit in casing-capping, switch modules that do not sit flush, a rack shoved into a shoe cupboard, and cameras cabled through drilled-through walls that leak during monsoon. None of this is the integrator's fault. It is a design-stage omission. The smart layer is a building service on the same footing as plumbing, HVAC and power, and it must be drawn, coordinated and specified before rough-in, not after paint.

This guide is written for the architect and the interior designer who is responsible for the drawing set — the person the client trusts to make sure nothing is forgotten. It covers when to introduce the smart layer, how to coordinate with the MEP or electrical consultant and the integrator, what to provision in the walls, where devices sit on the plan, how lighting automation and HVAC change your reflected ceiling plan, the drawings you must produce, the wired-versus-wireless decision as a design call, and the mistakes that recur on almost every project. For the homeowner-facing companion to this, see the smart home planning guide; for the physical build, the smart home installation guide.

Automation is not a product the client buys later. It is a layer you draw now — and every wall you close without it is a decision to spend ten times more, or to accept second-best forever.

Introduce the smart layer at concept, not tender

The single biggest lever an architect controls is timing. Decisions about the smart layer cascade from the earliest sketches, and each one that is deferred narrows the options and raises the cost.

At concept stage you are already making three automation-relevant decisions whether you notice them or not: where the incoming services enter, where the electrical distribution board and any low-voltage rack will live, and the broad zoning of the home into public, private and service areas. The rack location in particular is an architectural decision — it needs a ventilated, dust-controlled, accessible cupboard of roughly 600 by 600 mm footprint with power and drainage-free positioning, and if you do not reserve it at concept you will lose it to joinery later.

At schematic stage you fix the lighting design intent, the HVAC strategy and the security approach. These are the three systems automation touches most, so this is where you must decide, at least in principle, whether the home is wired (KNX or a structured bus), wireless (Zigbee, Z-Wave, Matter over Thread and Wi-Fi), or hybrid. That single decision governs conduit routing, switch-box depth and the neutral requirement for the entire project.

At tender and GFC the drawings must already carry the smart layer as coordinated information, because the electrical contractor is pricing conduit runs, box types and cable pulls off your set. If it is not on the drawing, it is not in the price, and it will arrive as a variation.

Design stageSmart-layer decision to lockCost of deferring
ConceptRack / server cupboard location, service entry, DB positionLose the space to joinery; surface-mount later
SchematicWired vs wireless, lighting zones, HVAC strategyWrong conduit and box depth throughout
Design developmentDevice points, RCP coordination, load scheduleMissing points added as site variations
Tender / GFCFully coordinated LV drawings, specificationsEverything becomes a chargeable extra
Rough-in on siteNothing new — only executionChasing finished walls at premium rates

Coordinate: architect, MEP consultant, integrator

Smart-home design fails at the seams between disciplines. The architect owns the space and the drawing set; the MEP or electrical consultant owns loads, circuits and compliance under IS 732; the integrator owns the automation logic, the bus topology and the commissioning. When these three work in sequence rather than in parallel, gaps open exactly where responsibilities meet.

The workflow below is the one that works: the architect convenes the integrator early — at schematic, not at fit-out — so that device points and the wired-versus-wireless decision inform the MEP consultant's circuit design, not the other way round.

Who does what, and when Architect Space, RCP, drawing set MEP consultant Loads, circuits, IS 732 Integrator Bus, logic, commissioning Schematic Design dev Rough-in Integrator joins at schematic so points inform circuit design

Fix the responsibility for three things in writing, because these are where projects break: who provides the load schedule (MEP, but the integrator must state the automation loads), who owns the conduit and box schedule (architect coordinates, MEP details, integrator confirms bus routing), and who is liable for the network backbone (usually the integrator, but the architect must reserve the pathways). A short responsibility matrix in the tender documents prevents the classic finger-pointing when a camera point is missing.

Provision the walls: conduit, deep boxes, neutral

Whatever automation logic you choose later, the physical provisioning is decided now. Three items must appear on your electrical drawings for every project, and they are cheap while the walls are open.

Neutral at every switch box. Traditional Indian switch wiring loops only the live through the switch and takes the neutral straight to the load. Almost every smart switch and smart dimmer needs a neutral at the switch box to power its own electronics. Instruct the MEP consultant to specify a neutral pulled to every switch position, not only where automation is currently planned — it costs a few rupees of extra wire and saves a rewire.

Deep switch boxes. Smart modules are deeper than conventional plates. Specify 65 mm deep GI or PVC back-boxes as standard for all switch and control positions, against the 45 mm boxes commonly used. This one line in the specification prevents modules that will not seat flush.

Conduit as pathways, not just circuits. Run generous conduit with pull-strings and reserve at least one spare conduit from the rack to each floor and to key rooms. A 25 mm spare conduit costed at rough-in is worth more than any device. This is where the wired versus wireless decision shows up physically: a wired KNX home needs a continuous bus conduit routed to every control point in a topology-appropriate pattern, while a wireless home still needs the network and camera backbone.

Provisioning itemStandard practiceSmart-ready specification
Switch-box depth45 mm65 mm deep back-box, all positions
Neutral wiringLive-only loop at switchNeutral pulled to every switch box
Switch conduitSized to circuitSpare capacity + pull-string
Rack pathwaysNot provided25 mm+ spare conduit to each floor / key room
Camera / sensor dropsAd hocMarked points with Cat6 home-run to rack

Put the devices on the drawing

Automation is a set of physical points that must be located on your plans and reflected ceiling plans, or the contractor cannot build them. The figure below shows where the smart layer sits on a typical floor plan.

Smart points on the floor plan Living Bedroom Kitchen Utility / rack RACK Camera Camera (gate view) Control panel Wi-Fi AP Motion / gas sensor Occupancy sensor Every camera and AP is a Cat6 home-run to the rack; sensors and panels ride the bus or conduit.

Work through the plan room by room and mark: camera positions (with field-of-view arrows and a Cat6 home-run to the rack, cabled inside conduit so the run is replaceable), video door phone and smart lock at the entry, Wi-Fi access-point locations on the RCP with a structured cable to each, occupancy and motion sensors at ceiling or high-level with their coverage cones, gas and water-leak sensors in kitchen and utility, and control-panel or keypad positions at entry and master bedroom. For the network side, coordinate the smart home networking backbone so access points, rack and camera runs are a single structured-cabling design rather than three afterthoughts.

Lighting automation zones and scene planning

Lighting is where automation most changes an architect's drawings. A conventional RCP shows fixtures and one-to-one switching. An automated RCP shows zones — groups of fixtures that are controlled and dimmed together to make a scene — and this changes the circuit design that the MEP consultant produces.

Design the zones from the experience backwards: a living room might carry an ambient zone, a feature or art zone, a task zone and a cove or perimeter zone, each separately dimmable so scenes like Evening, Movie, Bright and Off can be composed. Decide dimming method early — trailing-edge dimming for LED drivers, DALI for larger or commercial-grade jobs, or a KNX dimming actuator in a wired home. Record the intended scenes at design stage; the detailed logic is built by the integrator, but the zoning and the fixture grouping are architectural, and they must be on the drawing before the electrician wires the circuits. See smart home scenes and automations for how the zones become usable routines, and choosing smart lighting for the control-method trade-offs.

HVAC integration and other systems

For air-conditioning, decide whether control is at the infrastructure level (a VRF or ducted system exposing a bus interface such as Modbus or a manufacturer gateway that the automation reads) or at the appliance level (individual split units controlled through IR blasters or smart controllers). Infrastructure-level control must be specified with the HVAC consultant and the equipment order; appliance-level control can be added later but gives coarser results. Thermostat and controller positions, and any gateway that must sit near the rack, belong on the coordinated drawings — cover the detail in smart HVAC and climate. Motorised curtains and blinds need a concealed power point and, for wired systems, a control cable at each window head — an easy point to forget at the RCP stage. Water and energy management similarly need meter and valve positions reserved.

Documentation the architect must produce

The smart layer only exists if it is drawn and specified. Your set should carry, at minimum:

  • A low-voltage / automation layout over the electrical plan, showing every device point, camera, sensor, panel and access point with a legend.
  • An RCP with lighting zones identified and dimming method noted.
  • A rack / server-cupboard detail with size, ventilation, power and cable-entry.
  • A conduit and back-box schedule noting 65 mm boxes, neutral requirement and spare pathways.
  • A structured-cabling / network schematic from rack to each drop.
  • A technical specification — make, model, rating and standard for each item — which becomes the basis for the smart home BOQ and specification.

Feed these into a costed smart home BOQ generator and sanity-check the client's budget against the smart home cost calculator before tender.

The wired-versus-wireless decision, as a design call

For the architect this is not a gadget preference — it is a routing and coordination decision. A wired KNX home gives the most robust, latency-free, decade-stable control and is the right call for large villas, multi-storey homes and clients who want reliability over flexibility; it demands bus conduit to every control point, disciplined topology, deep boxes and a competent integrator, and it must be committed at schematic. A wireless home (Zigbee, Z-Wave, Matter over Thread and Wi-Fi) is faster to deploy, easier to change and better for retrofit or phased fit-out, at the cost of battery maintenance and radio-environment dependence. Many Indian projects land on a hybrid — wired backbone for lighting and critical loads, wireless for sensors and convenience devices. Work through the trade-off in wired versus wireless home automation and the broader home automation guide, and make the call before the conduit is drawn.

Common architect mistakes

MistakeConsequenceFix
Automation left to fit-out stageSurface conduit, no neutralsDraw the LV layer at schematic
No rack location reservedRack in a cupboard, overheatsReserve a ventilated 600 mm cupboard at concept
45 mm boxes specifiedModules will not sit flushSpecify 65 mm deep boxes throughout
Integrator engaged too lateCircuit design does not match logicBring integrator in at schematic
Cameras cabled without conduitRuns not replaceable, monsoon ingressCat6 in conduit, sealed entries
No responsibility matrixGaps at discipline seamsWritten matrix in tender documents

A plan-stage checklist

Before you issue GFC drawings, confirm: rack/server cupboard located and detailed; wired-versus-wireless decided; neutral specified at every switch box; 65 mm deep boxes specified; spare conduit and pull-strings to each floor and key room; every camera, sensor, panel and access point on the LV layout; lighting zones on the RCP with dimming method; HVAC control level agreed with the HVAC consultant; structured-cabling schematic from rack to drops; technical specification written for the BOQ; responsibility matrix agreed between architect, MEP and integrator. If every box is ticked, the smart home will be built once, not twice.

References

Export this guide