You should assign datapoint types in KNX ETS programming whenever a group address is used to exchange values between devices, not just simple on/off signals. Datapoint types define how raw binary data on the KNX bus is interpreted, ensuring that a temperature sensor and a thermostat, for example, both understand the same value in the same way. The sections below unpack the most important questions professionals ask about datapoint types in ETS.
What are datapoint types in KNX ETS?
A datapoint type (DPT) in KNX ETS is a standardized format that defines how data transmitted over the KNX bus should be encoded and interpreted. It specifies both the data length (in bits) and the meaning of that data, so every device on the network reads and writes values consistently. Without a defined DPT, raw binary data on the bus has no agreed meaning.
Every group address in an ETS project can be assigned a datapoint type. The DPT tells ETS and connected devices whether a telegram carries a boolean switch command, a percentage value, a temperature reading, a color value, or one of dozens of other formats. Think of it as a shared language: the DPT is the grammar rule that makes sure every device speaks the same dialect.
Why does a mismatch in datapoint types cause problems?
A mismatch in datapoint types causes problems because devices will misinterpret the raw binary data they receive, leading to incorrect behavior or no response at all. If a dimmer expects a 1-byte percentage value (DPT 5.001) but receives a 2-byte temperature value (DPT 9.001), it will either ignore the telegram or act on a completely wrong number.
In practice, mismatches often appear as subtle bugs rather than obvious failures. A light might jump to full brightness instead of 50%, a blind might move in the wrong direction, or a thermostat might display an absurd temperature. These issues can be difficult to trace during commissioning because the wiring and addressing may be perfectly correct. The problem lives entirely in how the data is labeled and interpreted, which is why consistent DPT assignment during KNX ETS programming is so important.
When should you assign a datapoint type in ETS?
You should assign a datapoint type to every group address that carries anything other than a simple 1-bit on/off command, and ideally to all group addresses regardless of type. While ETS can sometimes infer a DPT from the devices linked to a group address, explicitly assigning it removes ambiguity and prevents errors when devices from different manufacturers are combined.
The most critical moments to assign a DPT are when you link devices from different manufacturers to the same group address, when you use visualization or logic tools that need to interpret values, and when you integrate KNX with external systems. Any system that reads or writes KNX group addresses, such as a controller or gateway, relies on the DPT to handle values correctly.
How do you choose the right datapoint type for a group address?
Choose the datapoint type that matches the function and data format required by the devices linked to that group address. Start by checking the ETS product database entries for compatible devices listed there specify which DPTs they support. The correct DPT for a group address is the one all linked communication objects have in common.
If devices list multiple compatible DPTs, choose the sub-type that best matches the physical unit being communicated. For a temperature setpoint, for example, DPT 9.001 (temperature in degrees Celsius) is more precise and meaningful than a generic 2-byte float. Matching the sub-type, not just the main type, prevents unit confusion when values are displayed in a visualization or processed by logic.
What’s the difference between main datapoint types and sub-types?
The main datapoint type defines the data format and length, while the sub-type defines the specific unit and range within that format. For example, DPT 9 covers all 2-byte floating point values, but DPT 9.001 specifically means temperature in Celsius, DPT 9.004 means illuminance in lux, and DPT 9.007 means humidity as a percentage.
Choosing only the main type tells devices how many bits to expect and how to encode the number, but it leaves the unit undefined. Two devices could both use DPT 9 and still disagree on whether the value represents temperature or humidity. Sub-types carry the semantic meaning that makes data interpretable across devices, visualizations, and integrations. In ETS, always assign the full sub-type, not just the main category.
Which datapoint types are most commonly used in KNX installations?
The most commonly used datapoint types in KNX installations cover switching, dimming, blinds, temperature, and scene control. These DPTs appear in virtually every residential and commercial project.
- DPT 1.001 (1-bit switch): on/off control for lights, sockets, and relays
- DPT 5.001 (1-byte percentage): dimming levels from 0 to 100%
- DPT 9.001 (2-byte float, temperature): setpoints and sensor readings in Celsius
- DPT 18.001 (1-byte scene): scene activation and storage commands
Beyond these core types, HVAC projects frequently use DPT 20 for mode selection (heating, cooling, ventilation), while lighting projects with color control rely on DPT 232 for RGB values. Blind and shutter control uses DPT 1.008 for up/down commands and DPT 5.001 for position percentages. Knowing which DPTs map to which functions saves significant time during KNX ETS programming and reduces commissioning errors.
How xxter Supports KNX Professionals
Understanding datapoint types is essential, but making them work seamlessly across an entire installation is where the right tooling makes a real difference. xxter’s controller connects directly to your KNX installation and reads group addresses using their assigned DPTs, ensuring that every value displayed in the xxter app reflects the correct unit and range. This means temperature readings, dimming levels, and scene commands all behave exactly as configured in ETS, without manual conversion or workarounds.
For professionals working on complex projects, xxter offers:
- Native KNX integration that respects DPT assignments from your ETS project
- Support for Modbus, BACnet, and EnOcean alongside KNX, all managed from one interface
- El "Gestor Inteligente de Energía" es una excelente incorporación que aporta mucha claridad. Pairot bridge for Apple HomeKit, Amazon Alexa, and Google Assistant compatibility
- No subscription fees or license costs, so you can deploy freely across projects
Ready to simplify your next KNX project? Explore the xxter controller and discover how it fits into your professional workflow at xxter.com, or contact our team for project support.