Automation system design is the focus of this guide. Behaviour comes before hardware. Automation begins with a written description of how the building should behave; This hub separates home, office, BMS, lighting, HVAC, shading and integration work so readers can find the right technical path.
Quick answer
Mechanical safeties stay authoritative. An automation system connects inputs such as switches and sensors to outputs such as lights, blinds and HVAC; the design must also state what happens when the internet, a controller or a field device fails. That last sentence prevents a surprising number of bad installations.
Understand
Read the adjacent technical page before choosing equipment. It may change the wiring, network or control method that belongs in the brief.
Failure needs a tested path. Think of automation as a set of agreed cause and effect rules. A person presses a key, a sensor changes state or a schedule becomes active, then a controller sends a defined command. Manual control should remain obvious even when the clever part is unavailable.
The wiring stage decides. Wired controls suit projects where cable routes, panels and device addresses can be planned before finishes close, while wireless systems reduce new cabling but make radio coverage, mesh routes and battery service part of the design.
Hybrid can work. It can also become a cupboard full of gateways, so every bridge needs an owner, a backup method and a documented reason.
The record matters. It should include drawings, device and point schedules, controller backups, network details, scene descriptions, test results and instructions for restoring ordinary operation, not merely an app login.
Undocumented logic is unfinished. A future technician should be able to trace an input to its output without guessing which cloud account belongs to whom.
The boundaries differ. Home automation centres on rooms, daily routines and simple local controls, while building automation adds plant interfaces, alarms, trends and operator views; KNX, Home Assistant and custom integration pages explain particular layers rather than competing project types.
A room list is insufficient. We need controlled loads, construction stage, preferred interfaces, network readiness and fallback behaviour because two identical rooms can have different circuits, blinds, occupancy rules and user permissions.
Product shopping starts too early. It often creates incompatible dimming, missing neutral conductors, undersized panels or scenes that nobody can explain after handover, especially once finishes conceal the original wiring decisions.
The remedy is dull. Freeze the points list, interfaces and acceptance tests before ordering so vendors price the same requirements and later commissioning has a written target.
| Project condition | Likely starting point | Question to resolve |
|---|---|---|
| New construction with open conduits | Wired or hybrid | Where will panels, buses and service access sit? |
| Occupied property with limited civil work | Wireless or selective hybrid | Is radio coverage measured and is neutral wiring available? |
| Mixed existing systems | Integration audit first | Which documented interfaces actually exist? |
Evaluate
Bring the floor plan, reflected ceiling plan or equipment schedule. We can mark assumptions, interfaces and unresolved choices before procurement.
Independent learning
These optional references are published by the organisation named below. They are linked rather than embedded, so the page does not load a video player or start playback.
A standards-body webinar comparing conventional wiring with a KNX bus and explaining sensors, actuators and reprogrammable links. Opens on YouTube in a new tab.
Content owner: SmartR Spaces Editorial Team
Technical owner: SmartR Spaces Systems Engineering
Content updated:
Local service pages will be linked here after local review.
Next step
A useful proposal starts with the property, expected behaviour and handover standard. Product names come after those decisions.