KNX, wireless or conventional: what suits your home?
Compare the tasks and long-term support first. A simple installation can be as appropriate as comprehensive building automation. What matters is which functions you actually need.
PLAN2X · Editorial review: 17 October 2026
Requirements before product names
Describe everyday situations: getting up, leaving home and welcoming guests. Which functions must remain usable without a phone or internet connection? Keep these requirements the same for every supplier. This makes quotations using different technologies meaningfully comparable.
Systems, connections and apps are different layers
KNX is a building automation standard. Matter describes how supported smart home devices work together; Thread is an IP-based wireless network technology. An app or controller adds interfaces and automations. Sharing a wireless network alone does not make devices functionally compatible.
Thread Group: Matter & Thread FAQComparing installation and connectivity approaches
| Approach | Strengths | Limitations and effort | Questions before deciding |
|---|---|---|---|
| Conventional electrical installation | Direct, familiar controls; a targeted scope without a connected platform is possible. | Coordinated scenes and later changes may require extra components or wiring. | Which functions are sufficient today, and which cable provisions will you need later? |
| KNX with wired and optional wireless devices | A standard with products from multiple manufacturers; building services can be coordinated. | Planning and ETS expertise are required; cable routes and setup add project work. | Who supplies the ETS project, documentation and support? Which functions remain available without a server? |
| Vendor-specific building automation | A coordinated portfolio can simplify selection and operation. | Device choice, extensions and configuration depend more closely on the particular ecosystem. | Which third-party devices, data exports and service partners are available? |
| Wireless and hub solutions, such as Zigbee | Devices can often be added without installing a new control cable. | Wireless coverage, power supplies, the hub and specific device compatibility must align. | Does this exact hub support your chosen devices and automations? |
| Matter over Thread, Wi-Fi or Ethernet | A shared application standard for supported devices and platforms; local communication is provided for. | Device types, platforms and functions still matter; Thread requires a suitable border router. | Which functions are certified and usable in practice? Which controllers and optional cloud services are needed? |
A combination can also make sense
A planned core installation can be extended with connected devices. DALI, for example, focuses on lighting control and can form part of a wider design through suitable gateways. Check the available functions, maintenance and outage behaviour of every connection.
DALI Alliance: Key featuresConsider costs throughout use
Compare the same scope, including design, devices, wiring, setup and documentation. Also ask about subscriptions, battery replacement, updates and future changes. Blanket claims such as “wireless is always cheaper” or “KNX only pays off above a certain house size” tell you little about your particular project.
Distinguish device lifespan from system lifespan
An actuator may still work electrically after its app, hub or cloud service loses support. Conversely, a single device can fail without requiring the entire installation to be replaced. Hardware factors include suitable loads, switching frequency, temperature and build quality. Neither “KNX”, “wireless” nor price alone establishes a fixed lifespan.
KNX: backward compatibility helps continued operation
KNX Association describes backward compatibility as a core principle of ETS. The multi-vendor standard broadens the choice when replacing a device later. A replacement must still suit the functions, loads, mounting location and configuration; reconfiguration is often necessary. Keep the ETS project, product data and documentation. This helps long-term maintainability; it does not guarantee the lifespan of an individual actuator.
KNX Association: The evolution of ETSLow-cost and proprietary actuators: plan for replacement
A low purchase price can make sense for a limited use case. Still check the support period, an accessible supplier, technical documentation, local operation and replacement options. If a proprietary hub or service disappears, working hardware can also lose its usefulness. The risk depends on the product and its dependencies, not its country of manufacture. Include fault finding, travel, installation and setup in replacement costs.
BSI: Setting up a smart home securelyQuestions to help you decide
- What must keep working during an internet, hub or server outage?
- Can different people use the home without instruction?
- Who has access to configurations and backups?
- How long are updates promised, and what works after support ends?
- Can an individual actuator be replaced with a suitable device from another supplier?
- What does a failure cost, including labour and setup?