A KNX push button interface and a binary input module are both KNX input devices, but they serve different purposes. A push button interface is designed specifically to connect conventional wall-mounted push buttons or switches, converting their signals into KNX telegrams. A binary input module is a more general-purpose device that reads potential-free contact signals from a wider range of sources, such as door contacts, window sensors, or motion detectors. Understanding which one fits your project depends on what you want to connect and where.
What does each KNX input type actually do?
A KNX push button interface converts the physical press of a conventional push button or rocker switch into a KNX telegram that the bus can act on. A binary input module reads the open or closed state of any potential-free contact and translates that state change into a KNX group address action. Both devices act as translators between the physical world and the KNX bus, but they are optimized for different signal sources and installation contexts.
Push button interfaces are typically designed with the user experience in mind. They often support short press, long press, and double-click detection, which gives you fine-grained control over what action each button triggers. You can dim lights with a long press, toggle them with a short press, and call up a scene with a double tap, all from a single physical button.
Binary input modules, by contrast, are less focused on nuanced button behavior and more focused on state detection. They report whether a contact is open or closed, which makes them ideal for monitoring sensors and devices that simply switch between two states. Some binary input modules also support pulse counting, making them useful for reading energy meters or flow sensors.
What kinds of devices connect to each module?
A KNX push button interface connects conventional push buttons, rocker switches, and similar manual input devices. A binary input module connects any device that produces a potential-free contact signal, including reed contacts in windows and doors, PIR motion detectors with relay outputs, alarm contacts, and even simple manual switches when advanced button behavior is not needed.
In practice, the devices you connect to each module look like this:
- Push button interface: wall-mounted push buttons, rocker switches, glass touch panels without built-in KNX logic
- Binary input module: window contacts, door contacts, motion detectors, water leak sensors, alarm system outputs, manual switches used purely for on/off signaling
The key distinction is that push button interfaces are optimized for human interaction, while binary input modules are optimized for sensor and system integration. If a device needs to detect a human gesture with timing sensitivity, a push button interface is the right choice. If a device simply needs to report a state, a binary input module handles that job cleanly.
Can a binary input module replace a push button interface?
A binary input module can replace a push button interface for basic switching tasks, but it is not a full substitute. Binary input modules detect contact state changes and can trigger KNX actions on a rising or falling edge, which covers simple on/off switching. However, they typically cannot distinguish between a short press and a long press, which means you lose the ability to control dimming or call up multiple functions from a single button.
For straightforward lighting control where a button only needs to toggle a circuit on or off, a binary input module works perfectly well and is often the more economical choice. But for any installation where users expect to dim lights, adjust blinds with a long press, or trigger scenes through button combinations, a dedicated push button interface delivers the functionality that binary input modules cannot match.
The practical rule is this: if the physical input is a human pressing a button and you want responsive, gesture-aware control, use a push button interface. If the input is a sensor or system reporting a state, use a binary input module.
Where are binary input modules typically installed?
Binary input modules are most commonly installed in distribution boards or cable ducts, close to the sensors or contacts they monitor. Because they are not designed for wall mounting or user interaction, they are usually placed in technical spaces such as meter cupboards, electrical panels, or false ceilings where wiring runs are accessible but aesthetics are not a concern.
Typical installation scenarios include connecting window and door contacts throughout a building so the KNX system can respond automatically when a window is opened, or integrating alarm system outputs so the smart home reacts to security events. Binary input modules are also used in energy monitoring setups, where pulse outputs from utility meters feed into the KNX bus for consumption tracking.
Because they sit in technical spaces rather than living areas, binary input modules are usually DIN rail mounted and selected for the number of inputs they offer, often ranging from four to eight channels per device, making them efficient for monitoring multiple sensors from a single location.
Which KNX input type is right for a new smart home build?
For a new smart home build, you will almost certainly need both types. Use a KNX push button interface wherever residents will physically interact with the system through wall buttons, and use binary input modules wherever sensors, contacts, or external systems feed information into the KNX bus. The two device types complement each other rather than compete.
In a typical residential project, push button interfaces handle the living room, bedroom, and hallway switches where users expect responsive, multi-function control. Binary input modules handle window sensors, door contacts, and any third-party system outputs that the automation logic needs to monitor. Designing the input layer this way keeps the installation clean, cost-effective, and easy to maintain.
If your build includes energy monitoring, window automation based on weather conditions, or integration with an alarm system, binary input modules become especially important. They are the backbone of sensor-driven automation, while push button interfaces remain the primary tool for user-driven control.
How xxter Helps Professionals Design the Right KNX Input Layer
Choosing between a KNX push button interface and a binary input module is a design decision that shapes how intuitive and reliable a smart home installation becomes. xxter supports professional installers and system integrators in making those decisions correctly from the start. The xxter controller sits at the center of any KNX installation and works seamlessly with both input types, translating their signals into automated actions, scenes, and schedules through the xxter app.
- Full KNX compatibility means push button interfaces and binary input modules both integrate without configuration workarounds
- The xxter app gives end users clear, visual control over every input-driven function from any device
- Features like the scene module, planner, and triggers let you build sophisticated logic on top of simple input signals
- No license fees or subscription costs, so the value of a well-designed input layer is never eroded by ongoing charges
Whether you are designing a new build or expanding an existing KNX system, xxter gives you the tools to build an installation that is reliable, scalable, and genuinely easy to use. Explore the xxter controller and compatible KNX products and discover how it brings every input type together in one smart, connected system. To discuss your specific project requirements, get in touch with the xxter team for professional guidance.