Voice Control for KNX
"Alexa, turn off the living room" — connecting voice assistants to a KNX installation without sacrificing reliability or local control.
How voice control reaches KNX
Voice assistants (Alexa, Google Home, Siri) are cloud services. KNX is a local bus. Bridging them always involves at least one intermediate layer — and that layer determines reliability, latency, and what happens when the internet is down.
Recommended path
Best practiceKNX TP → KNX IP Router → Home Assistant → Nabu Casa → Alexa/Google/HomeKit
✅ Local control, one integration layer, HA handles all three voice platforms
⚠️ Nabu Casa subscription (€6.50/mo) or own reverse proxy setup
Gira ecosystem path
Vendor lock-inKNX TP → Gira X1 / HomeServer → Gira S1 → Alexa skill
✅ Fully supported by Gira, stable, no HA needed
⚠️ Gira-only devices, Gira S1 subscription required, less flexible
Specialist bridge
CommercialKNX TP → MDT IP Router → dedicated KNX-Alexa bridge (Intellihouse, iRidium)
✅ Purpose-built, no general smart home platform needed
⚠️ Commercial licences, limited device ecosystem
Matter future path
EmergingKNX TP → Thread/Matter bridge → Matter controller → HomeKit
✅ Matter-native, works with HomePod mini, no cloud subscription
⚠️ Experimental in 2025, limited KNX↔Matter bridges available
Platform comparison
| Feature | Amazon Alexa | Google Home | Apple HomeKit/Siri |
|---|---|---|---|
| KNX via HA | ✅ Home Assistant Alexa skill | ✅ HA Google Assistant | ✅ HA HomeKit bridge |
| Local processing | ❌ Always cloud | ❌ Always cloud | ✅ HomePod processes locally |
| Privacy | Low (Amazon cloud) | Low (Google cloud) | High (on-device/HomePod) |
| Wake word | Alexa | Hey Google / OK Google | Hey Siri |
| EU hardware | Echo Dot, Echo Show | Nest Mini, Nest Hub | HomePod mini, HomePod 2 |
| Device limit in HA | No hard limit | No hard limit | 150 per Home (Apple limit) |
| Scene recall | ✅ "Alexa, movie mode" | ✅ "Hey Google, bedtime" | ✅ via Shortcuts |
| Blind/shutter control | ✅ | ✅ | ✅ (HomeKit cover entity) |
| Thermostat control | ✅ | ✅ | ✅ |
| Status queries | ✅ "Alexa, is the door locked?" | ✅ | ✅ |
Home Assistant HomeKit Bridge — setup guide
HA's built-in HomeKit Bridge integration creates a virtual HomeKit hub that makes HA entities available to Apple Home and Siri. Local — no Nabu Casa subscription needed for HomeKit.
Setup steps:
- 1. In HA: Settings → Integrations → Add → HomeKit Bridge
- 2. Configure included domains:
light, switch, cover, climate, sensor, binary_sensor, lock - 3. Filter by entity area or label if you have non-HomeKit-ready entities
- 4. Scan QR code in Apple Home app → "Add Accessory" → enter 8-digit code
- 5. Name entities logically: "Living room main" not "KNX_1_0_5" — voice uses entity names
- 6. Create Rooms in Apple Home matching physical rooms
- 7. Test: "Hey Siri, turn off the kitchen lights"
⚠️ Entity naming matters
Voice assistants match spoken commands to entity names. Name your KNX-linked HA entities as the user will speak them: "Living room ceiling", "Bedroom reading light", "Kitchen under-cabinet". Avoid technical KNX group address names in HA.
Reliability architecture — what works when internet is down
✅ Always works (local):
- • KNX pushbuttons → KNX TP → actuators
- • DALI scenes triggered from KNX
- • KNX time programs and logic
- • Home Assistant automations (local)
- • HomeKit with HomePod as hub (local processing)
- • EnOcean / Casambi / Z-Wave (local)
❌ Fails without internet:
- • Alexa voice commands
- • Google Assistant voice commands
- • Nabu Casa remote access
- • Gira S1 cloud bridge
- • Remote app access (HA Cloud)
- • Any cloud-only integration
The correct architecture: KNX handles all critical control locally. Voice assistants are a convenience layer only — if Alexa goes down, guests still have physical KNX switches. This is the approach we implement in all residential projects.
Voice-ready KNX system from day one
We pre-configure Home Assistant with your KNX group addresses, set up HomeKit/Alexa integration, and test every voice command before handover.
Request a quote →