top of page

Most "Smart Homes" Are Just Remote Controls. Here's What Actually Makes One Automated.


A client told me last month his house was "fully automated" because he could turn every light off from his phone before bed. I didn't argue with him at the time, but I want to argue with the word here, because that habit, phone out, app open, tap the button, is the opposite of automation. It's a remote control with better range.

Real automation means the house did that on its own. No app, no tap, no voice command. A condition was met, a rule fired, something happened. If a human still has to notice the condition and act on it, you haven't automated anything. You've just moved the light switch onto a screen.

What automation actually requires

Automation is a loop: a sensor detects a condition, logic decides what that condition means, an actuator carries out the response. All three parts have to exist and talk to each other for anything to happen without a person in the middle. Miss one and you get something else instead.

Miss the sensor and you get a scene you have to trigger yourself, which is scheduling at best, remote control at worst.

Miss the logic and you get raw switches with no rules behind them, smart in name only.

Miss the actuator and you get a system that knows exactly what it wants to happen and no way to make it happen.

Most of what gets sold as a "smart home" is one or two of these three, dressed up with an app. That's not a knock on the gadgets themselves, some of them are genuinely well made. It's that a bulb you can dim from your phone and a bulb that dims itself when the room's occupied and the light outside drops below a threshold are different products solving different problems, even though they look identical in the box.

The gear, layer by layer

Sensors

Presence detectors (PIR for basic on/off, mmWave where you need to catch someone sitting still), light-level sensors, temperature and humidity, CO2, door and window contacts, a weather station for wind and rain. This is the layer that tells the system what's actually happening in the building right now. Skip this layer and every automation you build is really just a timer with extra steps, it fires on a clock instead of on reality.

The bus

In a KNX installation this is a dedicated twisted-pair cable running to every switch, sensor and actuator, carrying nothing but KNX telegrams. It's not on your Wi-Fi, it doesn't need a router to be working, and it doesn't care if your fibre is down. This is the part people underspend on because it's invisible once the walls close, and it's the part that determines whether the rest of the system still works during a power cut or an ISP outage.

Actuators

Relays for switching, dimming actuators for lighting, blind and shutter actuators for shading, valve actuators for HVAC zones. This is the layer that does the physical work: opens, closes, dims, switches. Everything upstream of this is just information until an actuator turns it into something that happened in the real world.

Logic

This is the part most DIY setups skip entirely, and it's the actual brain of the operation. In a KNX system this can live in the devices themselves through logic function blocks programmed in ETS, or it can be handed off to something like Home Assistant when the rule needs to weigh several things at once, time of day, presence, weather, a calendar entry, before deciding what to do. Either way, this is where "if this, then that" actually gets written down and enforced, every time, not just when someone remembers.

Interface

Keypads, wall panels, and gateways like 1Home for voice control through Apple Home, Google Home or Alexa. Worth being honest about what this layer is for: it's the human override, not the automation. A beautiful interface on top of a system with no logic is still just a very expensive remote control.

Where this shows up in a real house

A blind that closes because someone opened an app at 6pm is manual control with a nice UI. A blind that closes because a light sensor and a temperature reading crossed a threshold, at 6pm or 4:30pm on an overcast winter day, whichever the conditions actually call for, is automation. Same motor, same actuator, completely different system behind it.

It also shows up during a power cut. A system built on cloud-dependent bulbs and a Wi-Fi hub loses its logic the moment the router goes down, because the "brain" was never in the house to begin with. A KNX system with local logic keeps making decisions on its own bus regardless of what the internet is doing, because the sensor, the logic and the actuator are all sitting on the same wire in the same building.

What this means at the brief stage

If you're specifying a project, don't just count switches and outlets. Count sensors per room, work out where the logic runs, and check that every actuator you're speccing has something upstream of it deciding when to fire, not just a person with an app. That's the difference between a house full of smart devices and a house that's actually automated.

Happy to walk through what that looks like room by room for a specific project. No pressure either way.

Wayne. wayne@knxlogic.co.za | 082 564 3982 | www.knxlogic.co.za

Comments


bottom of page