Voice assistants on a KNX system: choices and trade-offs

Customers expect to walk into a smart home and talk to it. The question is which voice assistant and which integration path. Three paths are common, and each has clear trade-offs.

Vendor cloud bridges. Most major KNX integrators (Gira, Jung, Busch-Jaeger, ABB, Schneider) offer their own cloud service that connects a customer account to a voice assistant. Setup is straightforward: pair the visualization to the cloud, link the cloud to Alexa or Google, and devices appear in the assistant. Latency is moderate (1 to 3 seconds), and the cloud sits in the middle of every command. Privacy-conscious customers may push back on this.

Local-first via Home Assistant. Home Assistant runs on a small Raspberry Pi or NUC inside the house and connects to KNX over IP. The HomeKit integration in Home Assistant exposes everything to Siri without any external cloud. The Alexa and Google integrations still need an internet hop, but the path stays inside the customer's account rather than transiting a vendor cloud. Latency is excellent (under one second).

Native KNX-HomeKit gateways. A few hardware vendors offer dedicated boxes that bridge KNX to HomeKit only. They are simpler than Home Assistant but less flexible. If the customer is fully in the Apple ecosystem, this is the lowest-friction option.

For any path, scope what voice control will and will not do before the customer says yes. Voice works well for binary commands (turn on, turn off) and presets (movie scene, goodnight). It is awkward for fine-grained dim control or anything that requires confirmation feedback, because voice assistants do not always know whether the command succeeded. Set expectations early.