Systems

Apple Home vs KNX: you don't have to choose

9 min read6 August 2026Felix, Orchard
Entrance hall and staircase in a contemporary Mallorca villa with concealed lighting

Short answer: KNX is the engine, Apple Home is the steering wheel, and asking which is better is like asking whether an engine is better than a steering wheel. In a properly built villa you have both — and almost every argument I hear on this subject comes from someone selling one of them.

They're not the same category of thing

The comparison gets made constantly, usually by an installer who deals in one and not the other, and it muddles two entirely separate layers of a system.

KNX is a wired control bus. A green twisted-pair cable runs around your house alongside the mains, connecting actuators in the distribution board to switches, sensors and thermostats on the wall. When you press a switch, a telegram goes down the bus and an actuator closes a relay. It is a field bus standard, conceptually closer to industrial building control than to consumer electronics, and it has existed in one form or another since 1990.

Apple Home is a user interface and an automation layer. It doesn't switch anything itself. It presents accessories, groups them into rooms, runs scenes and automations, and gives you a consistent way to reach all of it from an iPhone, a Watch, an iPad or by speaking to a HomePod.

So the honest framing isn't "which one" — it's "what runs the loads, and what does the family touch."

What KNX is actually good at

Reliability at density. A large villa might have eighty or a hundred lighting circuits, twenty shading motors and a dozen climate zones. Wireless protocols degrade badly at that scale, particularly through the stone construction typical here. A wired bus doesn't care. It carries on working at circuit two hundred exactly as it did at circuit two.

Longevity and independence. This is the argument that actually matters. KNX is an open standard with certified devices from dozens of manufacturers. A KNX actuator bought in 2011 still works. More importantly, any KNX engineer anywhere can open your project file in ETS and take over your system. You are not dependent on one company continuing to exist, continuing to like you, or continuing to answer the phone.

It runs without anything else. No internet, no server, no cloud, no subscription. If every clever layer above it fails, the switches on your walls still turn on your lights. That is a genuinely underrated property.

Ask for your ETS project file. If a KNX installer won't give you the project file for the system in your own house, that's a serious problem, and it's more common than it should be. Without it, the next engineer has to reverse-engineer everything, which is expensive. Get it in writing before work starts.

What Apple Home is actually good at

It's already on every device you own. This is not a small thing — it's most of the value. There is no app to download, no account to create, no manual, no training session that everyone forgets. Your teenage son can dim the terrace lights and so can your mother-in-law, on a phone she already knows how to use, without anyone showing her.

The interface is genuinely well made. Rooms, scenes, favourites, and a widget on the lock screen. Whatever you think of Apple, they have spent more on making this comprehensible than any home automation manufacturer has ever spent on anything.

Guest access is properly designed. You can share a home with someone, revoke it instantly, and give a housekeeper or property manager access to some things and not others without setting up an account on a proprietary system.

Voice actually works. A HomePod in the kitchen is faster than any wall panel ever installed, and it costs a fraction as much.

How they work together

The bridge is usually Home Assistant, running on a small server in your plant room. It speaks KNX natively, reads every group address on the bus, and exposes each one to Apple Home as a native accessory. The KNX side is untouched — it doesn't know or care that anything has been added.

In practice the layers end up like this:

LayerWhat it does
KNXSwitches and dims circuits, drives shading motors, runs climate zones. Works standalone.
Home AssistantTranslates between systems, runs complex logic locally, handles anything KNX finds awkward.
Apple HomeWhat the household actually touches. Scenes, rooms, voice, remote access, guest sharing.
Physical switchesStill work. Always. This matters more than people expect.

Everything above runs on site. Losing your internet connection costs you remote access from off the island; it does not cost you your lights.

When each one is the wrong answer

KNX is wrong for an apartment, for a house you're not renovating, and for anyone unwilling to spend on first-fix cabling. Its cost sits in the wiring and the commissioning, not the hardware, so retrofitting it into a finished house is usually indefensible. Below roughly forty circuits, a well-designed system on Thread and Matter with retrofit modules will do the job for a fraction of the money.

Apple Home is wrong as your only layer in a large villa. It has no concept of a wired bus, its automation engine is deliberately simple, and it will not gracefully handle a hundred circuits, complex conditional logic, or anything requiring proper scheduling. It is an interface. Asked to be an engine, it disappoints — which is where most of the "HomeKit isn't good enough for serious houses" complaints come from. Those people are right, and they're arguing against a claim nobody sensible is making.

The Mallorca-specific bit

Two things make this island different from the UK or Germany.

The first is construction. Traditional Mallorcan building is stone and thick — often a metre or more — and much of it is under heritage protection that rules out chasing walls. That pushes older properties away from KNX and toward wireless, and it makes the network design far more important than it is in a British new-build.

The second is installer churn. Companies here appear and disappear with the market. I have surveyed several houses where the original installer is simply gone, the system is undocumented, and the proprietary controller running it has no local interface at all. Everything in it is stranded. That's the real argument for open standards and for insisting on documentation you own — not an abstract principle, a practical one.

Most houses I see don't need a new system. They need the good one they already have made usable. That's what an Apple Home migration is.

Not sure which layer your problem is in?

That's what the survey answers. Half a day at the house, €450 fixed, and a written report on what you have, what's wrong with it and what putting it right would cost. Yours to keep whether or not you use me.

Book a survey

Questions

Quick answers.

Is KNX better than Apple Home?

They do different jobs, so the comparison doesn't really hold. KNX is a wired control bus that switches and dims circuits and drives climate and shading. Apple Home is a user interface. In a well-built villa you use both.

Can KNX be controlled from Apple Home?

Yes. The usual route is a small local server running Home Assistant with the KNX integration, which reads the bus and presents each circuit to Apple Home as a native accessory. No cloud service involved, and the bus itself is unchanged.

Do I still need KNX if I have Apple Home?

For a small apartment, no. For a villa with more than roughly forty lighting circuits, motorised shading and multi-zone climate, yes — wireless becomes unreliable at that density and Apple Home has no equivalent to a wired bus for switching real loads.

Is KNX outdated?

No, and its conservatism is the point. It's an open standard maintained since 1990, so a device bought today still works in fifteen years and any KNX engineer can take over your system. That matters on an island where installers come and go.