A KNX push button interface is a device that connects physical push buttons or switches to a KNX bus installation, translating button presses into KNX telegrams that control lighting, blinds, HVAC, and other building functions. It acts as a bridge between a conventional switch and the KNX system, making it possible to use standard push buttons without replacing them with dedicated KNX keypads. The sections below walk through how these interfaces work, what types exist, and how they fit into a modern smart home setup.
What does a KNX push button interface actually do?
A KNX push button interface reads the physical state of connected push buttons or binary inputs and converts those signals into KNX telegrams sent across the bus. When a user presses a button, the interface detects the contact closure, packages it as a standardized KNX data point, and broadcasts it to the bus so that actuators such as dimmers, shutters, or switching actuators can respond.
Beyond simple on/off switching, most interfaces support more nuanced input types. A single button can be programmed to send different telegrams depending on whether it is pressed briefly or held down, enabling dimming ramp-up, blind movement, or scene recall from the same physical button. Some interfaces also monitor potential-free contacts from third-party devices such as doorbells, window contacts, or alarm outputs, making them versatile input nodes in a broader automation scheme.
How does a KNX push button interface communicate on the bus?
A KNX push button interface communicates by sending KNX telegrams over the twisted-pair bus (TP) using the standard KNX/EIB protocol. Each telegram carries a group address that links the interface to one or more actuators, so pressing a button triggers only the devices assigned to that group address in ETS.
The interface draws its operating power directly from the bus line, typically 21 to 30 V DC supplied by the KNX power supply unit, so no separate power wiring is needed for the interface itself. The connected push buttons are low-voltage, potential-free contacts wired to the interface’s input terminals. When a contact closes, the interface generates a telegram with a defined data type, for example a 1-bit switching command or a 4-bit dimming command, and places it on the bus within milliseconds. All other bus devices receive the telegram simultaneously, and only those programmed with the matching group address act on it.
What types of KNX push button interfaces are available?
KNX push button interfaces are available in several form factors and input counts, typically ranging from 2-channel to 16-channel devices, and they differ in mounting style, input type support, and additional features. You can explore KNX compatible products and solutions to find the right fit for your installation.
- DIN rail interfaces: Mounted inside the distribution board, these are the most common choice for new builds and renovations where the push buttons are wired back to a central cabinet.
- Flush-mounted interfaces: Installed in a standard wall box behind a conventional switch plate, these suit situations where wiring cannot be routed to a central cabinet.
- Interfaces with temperature or scene inputs: Some models add analogue inputs for room temperature sensors or scene controllers alongside binary push button inputs.
- Multi-function binary inputs: Higher-end models accept not just push buttons but also pulse meters, motion detector contacts, or window handle positions on the same terminals.
Choosing between them depends on the installation topology, the number of buttons to be connected, and whether additional sensor inputs are needed in the same location.
What’s the difference between a KNX push button interface and a KNX sensor?
The key distinction is that a KNX push button interface is a passive input device that converts external contact signals into bus telegrams, while a KNX sensor actively measures a physical quantity such as temperature, brightness, or motion and sends that measured value onto the bus.
A push button interface relies entirely on an external mechanical action. It has no measuring capability of its own. A KNX room temperature sensor, by contrast, continuously monitors the ambient temperature and sends updates to a heating actuator or controller without any human input. In practice, many modern KNX devices combine both functions: a room controller unit might include binary inputs for push buttons as well as an integrated temperature sensor, but these are technically two distinct functional blocks on the same hardware. Understanding the difference matters when planning group addresses and logic in ETS, because button inputs typically send switching or scene telegrams while sensor values drive setpoint or threshold comparisons in automation rules.
How is a KNX push button interface configured in ETS?
A KNX push button interface is configured in ETS (Engineering Tool Software) by importing the device’s product database entry, setting the operating mode for each input channel, assigning group addresses, and downloading the configuration to the device over the KNX bus.
The process follows a consistent pattern regardless of manufacturer. First, the installer adds the device to the ETS project and opens its parameter page. For each channel, the operating mode is selected: switching, dimming, blind control, value sending, or scene recall. The short and long press behavior can be defined separately, so a short press might toggle a light while a long press starts dimming. Once parameters are set, group addresses are linked to the channel’s communication objects. For example, the “switch” communication object on channel 1 is linked to the same group address as the switch actuator output controlling a lighting circuit. After all assignments are complete, the configuration is programmed into the device via the KNX programming interface, and the device responds immediately to button presses according to its new settings.
Can a KNX push button interface work with smart home apps and voice control?
Yes. A KNX push button interface works seamlessly with smart home apps and voice control when a KNX controller or bridge is present in the installation. The interface itself remains a local input device, but the functions it controls through the bus can also be operated and automated remotely via compatible platforms.
For example, a lighting circuit triggered by a push button interface can equally be switched from a smartphone app or through a voice assistant, because all control happens at the group address level on the KNX bus. Any device with the right group address can send a command, whether that is a physical button, an app, or a voice platform. This is exactly the architecture that makes KNX installations future-proof: the physical layer and the logical layer are separate, so adding app control or voice control does not require rewiring or replacing the push button interface.
How xxter Helps Professionals Get the Most from KNX Push Button Interfaces
xxter is built specifically for KNX installations, and its controller sits at the center of the system, connecting the physical KNX bus to the digital world of apps, voice assistants, and smart energy management. For professionals working with push button interfaces, xxter adds a layer of control and automation that goes well beyond what ETS programming alone can achieve.
- Remote and app control: Any group address controlled by a push button interface is instantly accessible through the xxter app on iOS, Android, Windows, and Apple Watch, with no subscription fees.
- Voice control via Pairot: The Pairot bridge makes KNX functions available through Apple HomeKit, Amazon Alexa, and Google Assistant, so clients can control the same circuits their push buttons operate using only their voice.
- Scene and planning logic: xxter’s scene module and planner let professionals build time-based or trigger-based automations on top of existing push button configurations without modifying the ETS project.
- Smart energy integration: The xxter Smart Energy Manager can act on the same KNX group addresses used by push button interfaces to optimize energy use automatically based on dynamic pricing and weather data.
Whether you are commissioning a new KNX project or upgrading an existing installation, xxter gives you the tools to deliver a smarter, more connected result for your clients. Get in touch with xxter to find out how the platform fits your next project.
This content was generated with the help of AI — it may contain mistakes