Loxone vs. KNX – What Are the Differences?

With KNX, the logic sits in the devices themselves. A push button knows which group address it sends to, an actuator knows which one it listens to, and neither needs a third party for this. The standard specifies it this way: KNX has been standardised in EN 50090 since 1994 and internationally as ISO/IEC 14543-3, and the standard explicitly describes a system without a central control component.

With Loxone, the logic sits in the Miniserver. It is the central control unit; the Extensions connect to it via the Link interface, and Tree and Air devices connect to those in turn. A push button reports there, the Miniserver decides, and it sends the switching command back to the actuator.

This sounds like a detail of the wiring, but it is the junction at which almost every other difference is decided: who does the programming, what a failure means, how long the system can be extended, and how easily the manufacturer can be changed.

With KNX, what fails is what is broken, and nothing else. If an actuator fails, its circuit stays dark; every other push button and actuator carries on, because neither depends on a third device. If a power supply fails, the line it feeds goes down and the remaining lines keep running.

With a centralised architecture, the failure of the central unit affects the whole building, because that is where the link between push button and actuator lives. Loxone offers coupling several Miniservers via gateway and client for critical installations, but that is a decision made during planning and it costs money; it is not a property of the system.

In practice this does not mean one is safe and the other is not. It means the question never has to be asked with KNX, and needs an answer with a centralised architecture before the first channel is assigned.

KNX is a standard, not a product. More than 500 member companies stand behind it, and there are over 8,000 certified products. In Germany alone there are 150 manufacturers and 23,000 partners from the trades and system integration (knx.de, as of September 2026). Anyone who needs a switching actuator can choose between dozens, and they work together in the same project without a gateway in between.

Loxone is a manufacturer. Miniserver, Extensions, Tree devices, software and app come from one source and are matched to each other. That is both the advantage and the tie: it fits together because it was developed together, and there is no second supplier from whom the same component could be bought.

For a building in use for twenty years or more, this is a commercial question rather than a technical one. Anyone replacing a defective actuator in fifteen years needs any suitable one from the market with KNX, and precisely that manufacturer with a vendor-tied system.

KNX is commissioned with the ETS. ETS6 Professional costs 1,000 euros net, and ETS6 Lite, limited to 20 devices, costs 200 euros net (as of September 2026, prices from the KNX Association). The software is manufacturer-independent: one project contains devices from different manufacturers, and their product databases are loaded into the same project.

Loxone Config is free, runs on Windows and has no licence fee. Programming is done with logic blocks via drag and drop; no programming language is needed. Access to the shop and partner terms, on the other hand, runs through the partner programme.

The thousand euro difference is noticeable for a single family home and a footnote for a commercial property. More important than the amount is that the ETS is a tool for the standard, while Loxone Config is a tool for one manufacturer's products.

The decision is not an either-or. Loxone offers a KNX Extension through which up to 500 KNX group addresses can be integrated, sending and receiving, with various data point types. This allows an existing KNX installation to continue under a Miniserver, or a KNX system to be supplemented with Loxone functions.

The limit of this bridge is the number itself. 500 group addresses are ample for a single family home and quickly tight for a larger property, and whatever runs through the Extension then depends on the Miniserver again.

Anyone mixing the systems should therefore decide beforehand which one leads. Two systems both trying to switch the same luminaire is not added comfort, it is a fault hunt.

KNX argues for itself when: the building will be in use for a long time, devices from several manufacturers are to work together, the failure of a central unit would be unacceptable, a tender requires a standardised system, or it is a commercial building. Changing the contractor is also easier, because any KNX partner can open an existing project in the ETS.

Loxone argues for itself when: the installation should be up quickly and without licence costs for the software, complex logic and visualisation matter more than manufacturer independence, everything should come from one source, or the budget for planning and commissioning is tight.

What never holds up is deciding by the price of the first component. Over their service life, both systems cost considerably more in planning, commissioning and extension than in the hardware of day one.