Inside a No-Cloud KNX Villa: A 640 m² Abu Dhabi Smart Home Build

The brief was quiet — quieter than most smart home briefs we hear. A 640 m² hillside villa, owned by a family that had lived there since 2009 and wanted automation that felt like their house, not a tech demo of it. Two floors, seven lighting scenes, a single intercom tile by the front door, and "nothing that beeps."

The constraint they didn't quite say out loud, but turned out to be the single hardest design decision: no new cloud accounts. They had lived through one smart home platform's discontinuation already and didn't trust adding more dependencies they couldn't shut off.

The house was already wired — for 2009

The villa was wired for traditional circuits in 2009: every room on a switch, every load on a circuit, neutrals at every backbox because the original electrician was rigorous. That gave us a choice: rip and replace with new KNX cabling, or use the existing infrastructure and drop KNX intelligence in behind every faceplate.

We chose the second path. The owners kept every faceplate. Only the mechanism behind it changed.

The wire we did and didn't pull

• KNX TP1 bus: two new lines pulled through the existing conduit, 64 devices on line A (living areas), 48 on line B (sleeping areas).
• DALI-2 broadcast: per floor, re-terminating the luminaires onto a single 16-bit address space for tunable white 2700-6500 K control.
• Zigbee mesh: for battery sensors only — door contacts, motion, leak, CO₂. No primary control on wireless. Every actuator is wired.
• IP intercom: a single PoE doorstation at the front door, SIP-bridged to the owner's iPhone.

Seven scenes the family actually uses

We started with twelve scenes during scoping. The owner ruthlessly cut them to seven. Three weeks after handover, six were still in active use. That's the rule we now apply to every scene-design conversation: fewer scenes that get used beats more scenes that sit.

1. Morning: 2700 K at 20% ramping to 4000 K at 60% over 8 minutes, on the alarm time the owner already sets in their phone.
2. Cooking: CRI-90 pendants at 90%, ambient at 40%, shades half-up. One button on the kitchen panel.
3. Cinema: shades down, bias light at 1%, amplifier on zone B, family-room lights to 5%.
4. Evening: warm pools of light around seating, hallway path at 10%, bedrooms at 30%.
5. Sleep: bedrooms off, hallways at 2% (nightlight level), kitchen at 0, garage door confirms locked.
6. Absent: randomised presence (lights cycle as if someone's home), CO₂ > 1000 ppm triggers an alert, HVAC setback.
7. Welcome: the path scene that runs when the front-door intercom recognises the owner's car arriving.

The no-cloud architecture

This is the part we get asked about most. How do you build a full smart home without a cloud account anywhere in the chain?

The short answer: KNX and DALI run entirely on local protocols. They don't need the internet to function. The longer answer is about everything that seems like it needs cloud:

• Mobile app control: a Life Smart central runs locally on the home network, with a VPN tunnel back to the owner's phone for remote access. No vendor cloud in between.
• Voice control: intentionally not deployed. The owner uses physical keypads + the mobile app. We offered Alexa/HomeKit; they declined.
• Intercom video: SIP over the owner's existing data plan. The doorstation pushes video directly to the iPhone via local network when at home, via the VPN when away.
• Software updates: the KNX devices don't push firmware. They just work. We update the Life Smart central manually, every 6 months, after testing in our workshop.

What the family notices and what they don't

The morning scene is the feature they mention most often — the slow ramp wakes them up without an alarm. The cinema scene gets used three times a week. The CO₂ alert in the absent scene has triggered twice (once when the cleaning team forgot to ventilate). They've never used the touch panel during a power-quality event, because everything has a wired override.

What they don't notice — and this is the goal — is the KNX system itself. The owner once mentioned, six months after handover, that the system had been "perfectly invisible." That's the brief they wrote at the start.

The cost picture

This was a substantial retrofit. The full project came in at AED 240,000, across KNX devices (~AED 95,000), DALI drivers and re-termination (~AED 35,000), the IP intercom (~AED 14,000), structured cabling and conduit pulls (~AED 28,000), and commissioning + ETS programming (~AED 68,000). Annual support runs ~AED 18,000.

Comparable wireless-only retrofits run AED 60,000 - AED 100,000. The 2.5× premium for KNX buys 15-25 years of operation versus 5-8 for wireless mesh. For a family that already lived through one platform discontinuation, that's the calculus that mattered.

If you're scoping a villa retrofit and want a frank conversation about whether KNX or wireless is right for your home, reach out.