To configure a KNX push button interface in ETS, open the device in your ETS project, set the operating mode and function parameters for each channel, assign group addresses to the relevant communication objects, and download the configuration to the device via the KNX bus. The process is straightforward but requires attention to datapoint types and channel settings to ensure reliable operation. The questions below walk through each step in detail.
What parameters do you need to set in ETS for a push button interface?
In ETS, the core parameters for a KNX push button interface are the operating mode per channel (switch, dimming, blind/shutter, value, or scene), the button function (toggle, always on, always off), and any timing settings such as short/long press detection. These parameters define how each button channel behaves on the KNX bus and what type of telegram it sends.
Most push button interfaces present their settings under a general tab and individual channel tabs within the ETS device properties panel. Start with the general parameters, where you typically configure the bus voltage recovery behavior and communication timing. Then move to each channel and set the operating mode that matches the load it will control. A channel controlling a light needs switch or dimming mode; a channel controlling a blind needs the shutter/blind operating mode.
Long press and short press detection is particularly important. If you want a single button to toggle a light on a short press and activate a scene on a long press, you need to enable dual-function mode and set the long press delay, usually between 400 and 800 milliseconds depending on the manufacturer’s parameter set. Always consult the device’s ETS product database documentation for the exact parameter names, since terminology varies between manufacturers.
How do you assign group addresses to a KNX push button in ETS?
To assign group addresses to a KNX push button interface in ETS, navigate to the device’s communication objects tab, locate the relevant object for each channel (such as “Switch object” or “Dim object”), and drag or link the appropriate group address to it. Each communication object that needs to interact with another device must share at least one group address with that device’s corresponding object.
A common approach is to use a three-level group address structure: main group for the system area (for example, lighting), middle group for the room, and sub-group for the specific function. For a push button controlling a living room ceiling light, you might assign the group address 1/1/1 to both the button’s switch output object and the actuator’s switch input object. This shared address is how the button telegram reaches the actuator.
If the push button also needs to receive status feedback, for example to drive an LED indicator, you assign a second group address to the status communication object and link it to the actuator’s status output. Keep group address assignments consistent across your project to avoid conflicts and simplify troubleshooting later.
What are the correct datapoint types for push button communication objects?
The correct datapoint type (DPT) for a standard KNX push button switch object is DPT 1.001 (1-bit, switch). For dimming control, the step/stop object uses DPT 3.007 (4-bit, dimming control) and the value object uses DPT 5.001 (8-bit, percentage). Scene objects use DPT 18.001 (1-byte scene control). Using the wrong DPT causes communication errors or silent failures on the bus.
ETS assigns datapoint types automatically based on the operating mode you select in the device parameters, but it is worth verifying them manually, especially when linking objects across different manufacturers’ devices. A mismatch between a button’s output DPT and an actuator’s input DPT means the telegram will either be ignored or misinterpreted.
- DPT 1.001 for on/off switch objects
- DPT 3.007 for relative dimming (step/stop)
- DPT 5.001 for absolute brightness value (0 to 100%)
- DPT 18.001 for scene activation and storage
When working with blind and shutter objects, the move object uses DPT 1.008 (up/down) and the step object uses DPT 1.007 (step/stop). Always cross-check the DPTs in both the sending and receiving device to confirm they match before downloading the configuration.
How do you download and test the configuration on the KNX bus?
To download the configuration to a KNX push button interface, connect your ETS computer to the KNX bus via an IP or USB interface, select the device in your ETS project, and use the “Download” function to program the application, parameters, and group addresses. After the download completes, test each button by pressing it and observing the bus traffic in the ETS group monitor.
Before downloading, ensure the device is powered and reachable on the bus. ETS will first write the physical address if it has not been set, which requires pressing the programming button on the device. Once the address is confirmed, the full application download takes anywhere from a few seconds to a minute depending on the device and connection type.
The ETS group monitor is your most valuable testing tool. Open it during the test phase and press each button. You should see the outgoing telegram appear on the correct group address with the expected datapoint value. If a telegram appears but the actuator does not respond, the issue is likely a group address mismatch or a DPT conflict on the actuator side rather than a problem with the push button configuration itself.
Why is the push button not responding after ETS programming?
If a KNX push button interface is not responding after ETS programming, the most common causes are an incomplete application download, a mismatched group address between the button and the actuator, an incorrect datapoint type, or missing bus voltage at the device. Checking each of these systematically will identify the problem in most cases.
Start by confirming the download completed without errors in ETS. A partial download can leave the device in an undefined state. If in doubt, perform a full download including the application program rather than a partial parameter-only update. Next, open the group monitor and press the button to check whether any telegram appears on the bus at all. If no telegram is visible, the device may not be receiving bus power or the application has not loaded correctly.
If a telegram does appear but the actuator ignores it, compare the group addresses on both devices and verify the DPTs match. Also check that the actuator’s communication object is set to receive (write flag enabled) and that the button’s object is set to transmit (transmit flag enabled). These flags are sometimes disabled by default in certain device profiles and must be enabled manually in ETS.
How xxter Supports Professionals Working with KNX
Configuring a KNX push button interface in ETS is a precise task, and having the right platform to manage and extend that configuration is what separates a functional installation from a truly smart one. xxter builds on top of a properly programmed KNX installation to add a layer of control, automation, and usability that professionals and end users both benefit from.
- Centralised control: The xxter controller connects to your KNX bus and makes every group address accessible through the free xxter app on smartphones, tablets, and computers, without subscription fees.
- Scenes and automation: xxter’s scene module, planner, and scripting tools let you build logic on top of your KNX push button programming without touching ETS again.
- Voice control integration: With Pairot, your KNX installation becomes compatible with Apple HomeKit, Amazon Alexa, and Google Assistant, giving clients voice control over every button function you have programmed.
Whether you are commissioning a residential project or a larger building installation, xxter gives you a professional-grade platform that complements your ETS work and delivers a seamless experience to the end user. Explore the xxter controller and compatible KNX products and discover how it extends what you build in ETS into a complete smart home solution. For questions about your specific project, get in touch with the xxter team to discuss how xxter can support your installation.