Most smart home articles are shopping lists. This guide looks at a smart home the way an ELV engineer looks at any low-current system: what the parts are, how they talk to each other, how they are powered and wired, what the network has to carry, how the system is secured, and how it fits together with CCTV, access control and the rest of the building. Whether you are fitting out an apartment yourself or specifying automation for a villa project, the same questions decide whether the system still works well five years after handover.
1. The building blocks of a smart home system
Every smart home, from a few smart plugs to a fully wired villa, is made of the same four layers. Thinking in layers makes it much easier to choose products and to find faults later.
- Field devices: switches, dimmers, relays, curtain motors, thermostats and AC interfaces, sensors (motion, door/window, temperature, humidity, water leak, smoke alerts), smart locks, cameras and video door stations.
- Communication: the protocol the devices use to talk, either a radio mesh (Zigbee, Z-Wave, Thread), Wi-Fi, or a wired bus (KNX, Modbus, DALI for lighting, RS-485 in some systems).
- Controller or hub: the device that holds the logic (scenes, schedules, rules) and bridges protocols. It may be a dedicated hub, a smart speaker with a built-in radio, a home server running software such as Home Assistant, or a KNX/BMS controller in larger projects.
- User interface and cloud: mobile apps, wall touch panels, voice assistants and, often, a cloud service for remote access and notifications.
A good design answers one question for every function: where does the logic run? If a light only switches because a cloud server tells it to, an internet outage or a vendor shutting down a service can leave a wall switch that no longer works. Wherever possible, keep basic functions (lights, curtains, heating and cooling) working locally on the hub or the device itself, and use the cloud only for remote access and notifications.
2. Choosing the protocol: Zigbee, Z-Wave, Thread/Matter, Wi-Fi or KNX
The protocol decision matters more than the brand. It decides range, battery life, how many devices the network can carry, whether you need a hub, and how easy it is to mix brands later.
| Protocol | Medium | Typical devices | Strengths | Things to watch |
|---|---|---|---|---|
| Zigbee | 2.4 GHz radio mesh | Sensors, bulbs, switches, plugs | Low power, large mesh, wide product choice | Needs a coordinator (hub); shares 2.4 GHz with Wi-Fi, so plan channels |
| Z-Wave | Sub-GHz radio mesh | Locks, sensors, relays | Better wall penetration, less interference with Wi-Fi | Frequency is regional; buy the variant approved for your country |
| Thread + Matter | 2.4 GHz IP mesh (Thread); Matter is the application layer over Thread or Wi-Fi | Newer sensors, plugs, locks, bulbs | Designed to work across ecosystems; local control | Needs a Thread border router; check which device types and features your controller supports |
| Wi-Fi | Home Wi-Fi network | Cameras, plugs, displays, appliances | No hub, high bandwidth | Higher power use; dozens of devices can overload a basic router; often cloud-dependent |
| KNX | Dedicated twisted-pair bus (also IP and RF variants) | Lighting, blinds, HVAC, scenes in villas and buildings | Very reliable, decentralised, open standard with many manufacturers | Must be planned before first-fix wiring; programmed by a trained integrator |
A practical rule: for a retrofit or rented apartment, use one radio ecosystem (Zigbee, or Thread/Matter for new products) with Wi-Fi only for cameras and high-bandwidth devices. For a new villa or full renovation, a wired backbone such as KNX for lighting, blinds and HVAC is worth considering, with radio devices only where cables cannot reach. Mixing four apps and four protocols with no single controller is the most common reason a smart home becomes frustrating.
How a radio mesh behaves
In Zigbee, Z-Wave and Thread, mains-powered devices (switches, plugs, relays) usually act as routers and pass messages on, while battery sensors are “sleepy” end devices that only talk to a nearby router. So build the mesh from the hub outwards: install and pair mains-powered devices first, then the battery sensors. A villa with concrete walls and slabs may need extra mains-powered routers on each floor, exactly as it needs extra Wi-Fi access points. Keep the hub away from metal cabinets, distribution boards and the back of a TV.
3. Electrical side: wiring and installation
Most failures in smart switching come from the electrical side, not the app. Check these points before ordering any wall device.
- Neutral at the switch. Many smart switches and dimmers need a neutral conductor in the switch box to power their electronics. Older installations often bring only the live and switched live to the switch. Either choose a no-neutral model that is rated for your load, fit a relay module at the light point instead, or run a neutral during renovation.
- Back box depth. Smart modules are deeper than ordinary switches. Measure the back box and the space behind the plate; a squeezed module overheats and is hard to service.
- Load type and rating. Check the device rating against the real load, especially LED drivers (inrush current), motors (curtains, pumps), heaters and water heaters. Dimmers must match the LED driver’s dimming method (leading edge, trailing edge, 0-10 V or DALI).
- Supply. Confirm the voltage and frequency for your country (for example 230 V, 60 Hz in Saudi Arabia) and any local approval marks for mains devices.
- Low-voltage cabling. In new builds, run Cat6 to every room, to ceiling points for access points and cameras, to the main door, and to the technical cabinet. Add spare conduits to curtain pockets, AC units and the gate. Cables are cheap during first fix and very expensive afterwards.
- Technical cabinet. Plan a ventilated cabinet or rack for the router, switch, hub, NVR and KNX power supply, fed from a dedicated circuit and a small UPS.
Isolate and test before touching any switch, label the wires before removing an old device, and leave mains work to a qualified electrician working to the local wiring regulations.
4. Network design for smart devices
A smart home is an IP network with many small, low-security devices on it. Treat it like any other ELV network:
- Coverage first. Survey Wi-Fi signal where devices will sit, not just in the living room. Use wired access points or a mesh system with wired backhaul in multi-storey villas.
- Segmentation. Put smart devices and cameras on their own SSID and VLAN, separate from laptops and phones. Allow only the traffic the controller and apps need. If the router cannot do VLANs, at least use its guest or IoT network feature.
- Addressing. Reserve DHCP addresses for hubs, controllers, NVRs and KNX/IP interfaces so integrations do not break when an address changes.
- Bandwidth. Cameras are the heavy users. Size the uplink for remote viewing and any cloud recording; sensors and switches use almost nothing.
- Power resilience. Put the router, switch, hub and NVR on a UPS so automations, cameras and the door station keep working during short power cuts.
5. Security and privacy
- Change every default password and use a separate, strong password for each hub, camera and NVR.
- Enable two-factor authentication on the main smart home and camera accounts.
- Update firmware during commissioning, then on a schedule. Prefer brands that publish security updates for several years.
- Avoid opening ports on the router for remote access. Use the vendor’s secure remote access or a VPN into the home network.
- Disable features you do not use (UPnP, unused cloud integrations, open RTSP streams).
- Point cameras at your own property and follow local privacy rules on recording neighbours, shared corridors and audio.
6. Integration with CCTV, access control and intercom
The real value of a smart home appears when systems work together. Typical integrations an ELV engineer is asked for:
- CCTV. A motion or door event turns on outdoor lights and shows the relevant camera on a touch panel or TV. Most NVRs and cameras offer ONVIF or RTSP streams that a controller can display; event integration usually needs the NVR’s API, an alarm output relay, or a supported integration in the controller.
- Access control and smart locks. Unlocking the main door with a card, PIN or app can switch the house to “home” mode, disarm the alarm and turn on hallway lights. In buildings, the apartment’s smart lock or intercom may need to work alongside the building’s access control and lift control system, so agree interfaces with the building operator early.
- Video intercom. An IP door station can ring the app and touch panels and release the door or gate through a relay. Keep a local release that works without the internet.
- Intruder alarm. Door and motion sensors can serve both the alarm and automations, but a monitored alarm system should keep its own certified panel and communicator.
- HVAC and energy. AC interfaces, thermostats and energy meters allow “away” setbacks and alerts for unusual consumption.
One firm limit: smart smoke or heat alerts do not replace a fire alarm system where the building regulations require one. Do not let an automation interfere with fire alarm functions, emergency door release or emergency lighting. In apartment buildings these are part of the building’s life-safety systems and are subject to the local Civil Defence or other authority.
7. Worked example: three-bedroom apartment retrofit
A typical brief: lights, AC and curtains from the phone, a leak alert in the kitchen, a camera and smart lock at the front door, no rewiring of walls.
| Area | Devices | Automation |
|---|---|---|
| Entrance | Smart lock, door contact, Wi-Fi or PoE camera | Alert if the door opens while the home is in “away” mode; hallway light on when unlocked at night |
| Living room | Zigbee wall switches (neutral confirmed), motion sensor, IR or Wi-Fi AC interface, curtain motor | Lights on at sunset; AC off after 30 minutes without motion |
| Kitchen | Water leak sensor, smart plug for the water heater | Phone alert on leak; water heater on a schedule |
| Bedrooms | Zigbee switches, temperature and humidity sensor | “Good night” scene turns off lights and sets AC |
| Cabinet | Router with IoT network, Zigbee hub, small UPS | Hub runs scenes locally; cloud only for remote access |
This comes to roughly 15 to 20 devices. Because the switches are mains-powered Zigbee routers, the battery sensors have a strong mesh to join, and Wi-Fi carries only the camera, the AC interface and the phones.
8. Worked example: new villa with a wired backbone
For a new two-storey villa, the design starts on the drawings, before first-fix wiring. Lighting circuits, blinds and AC are controlled by KNX actuators in the distribution boards, with KNX push buttons in each room. A Cat6 star from the technical cabinet feeds ceiling access points, PoE cameras, the IP door station and touch panels. A KNX/IP interface lets a visualisation server or app control the house, and a Zigbee or Thread network covers battery sensors where cables were not planned. The CCTV NVR, door station and alarm panel are on their own VLANs, with defined integration points (camera pop-up on door ring, lights on alarm). Everything in the cabinet runs from a UPS sized for at least the router, switch and door station.
9. Commissioning and handover checklist
- Name every device by floor, room and function (for example “GF Kitchen Ceiling Light”).
- Test each scene and automation, including what happens when the internet is down and when the power returns after a cut.
- Check mesh health or bus diagnostics; add routers where the signal is weak.
- Update firmware, change default passwords and record admin credentials in a secure handover document.
- Back up the controller configuration (or the KNX project file) and give the client a copy.
- Provide a one-page user guide: how to use the main scenes, how to switch lights manually, and who to call.
10. Common mistakes
- Buying devices from several ecosystems with no single controller.
- Ordering smart switches before checking for a neutral and the back box depth.
- Relying on the cloud for basic functions such as lights and curtains.
- Leaving cameras and hubs on the same flat network as personal devices, with default passwords.
- Treating consumer smoke alerts as a substitute for a required fire alarm system.
- Leaving the low-voltage cabling plan until after plastering.
Frequently asked questions
Do I need a hub?
Wi-Fi devices work without one, but Zigbee and Z-Wave need a coordinator, and Thread needs a border router. In practice a local hub or controller also lets automations run without the internet, which is worth having.
Is Matter the answer to compatibility?
Matter makes it easier for devices to work with several ecosystems and supports local control, but support differs by device type and controller. Check that both the device and your controller support the functions you need before buying.
KNX or wireless?
KNX suits new builds and full renovations where cables can be planned; it is very reliable and not tied to one manufacturer. Wireless suits retrofits and rented homes. Many projects use both: KNX for the fixed backbone and wireless for battery sensors.
Can a smart home system control my building’s access control or lifts?
Only through an interface agreed with the building operator, usually a relay, an API or a vendor integration. Lift and building access systems belong to the building and often have security and life-safety roles, so they should not be modified from an apartment system.
Related guides and tools
- Access control system components explained
- SOYAL access control: setup, lift control and troubleshooting
- VLAN for CCTV systems and CCTV cybersecurity
- Integrated security: CCTV, access control and alarm
- IP subnet & VLAN planner and PoE budget calculator

