KNX ETS software handles group address configuration for energy endpoints by allowing engineers to create structured group address tables that link the communication objects of energy meters and sensors to logical addresses, enabling data exchange across the KNX bus. Each energy endpoint, whether a power meter, heat meter, or pulse counter, exposes communication objects that must be manually assigned to group addresses within ETS before any monitoring or control is possible. The sections below walk through the key questions professionals encounter when configuring energy endpoints in KNX ETS software.
What types of group addresses are used for energy endpoints in KNX?
Energy endpoints in KNX use group addresses that correspond to distinct measurement values: active power, reactive power, energy consumption totals, voltage, current, and pulse counts. Each measurable quantity requires its own dedicated group address. A single three-phase energy meter, for example, will typically need separate group addresses for each phase’s power reading, each phase’s voltage, and the cumulative energy total.
Group addresses for energy endpoints fall into two broad categories. Cyclic or event-driven status group addresses carry live measurement data that the meter sends automatically at defined intervals or on value changes. Reset or command group addresses allow the KNX controller or a logic module to trigger a meter reset or request an immediate value update. Keeping these two categories clearly separated in your group address structure prevents accidental resets and makes troubleshooting far simpler.
In larger installations, energy group addresses are often organized using a three-level hierarchy in ETS: the main group represents the building system (for instance, energy monitoring), the middle group represents the zone or floor, and the sub-group identifies the specific measurement point. This structure keeps the address table readable and maintainable over time.
How does ETS assign and structure group addresses for energy metering?
ETS does not assign group addresses automatically. The engineer creates group addresses manually within the group address editor, then drags or links them to the relevant communication objects of each energy device. ETS provides a free-form address space of up to 65,535 group addresses, organized in whatever hierarchy the engineer defines.
For energy metering projects, a consistent naming convention is essential. A practical approach is to prefix every energy-related group address with a recognizable label such as “EN” followed by the meter location and the measured quantity. ETS supports long descriptive names, so there is no reason to use cryptic shorthand that creates confusion during maintenance or handover.
ETS also allows group addresses to be exported and imported as CSV files, which is useful when a project involves many energy endpoints across a large building. Engineers can prepare the address list in a spreadsheet, import it into ETS, and then proceed with linking communication objects, which significantly reduces manual entry errors.
What datapoint types does ETS require for energy monitoring group addresses?
Every group address used for energy monitoring must be assigned a matching datapoint type (DPT) that defines the data format and unit of measurement. The most common DPTs for energy endpoints are DPT 9.x (two-byte floating point) for live power values in watts or kilowatts, DPT 13.x (four-byte signed integer) for energy totals in watt-hours, and DPT 14.x (four-byte floating point) for high-precision measurements such as voltage and current.
Choosing the wrong DPT is one of the most frequent configuration mistakes in energy metering projects. If a receiving device or visualization system expects DPT 14.056 for active power but the meter sends DPT 9.024, the received value will be misinterpreted and display nonsense figures. ETS flags DPT mismatches with a warning, but it does not prevent commissioning, so the engineer must verify DPT compatibility manually before testing.
Pulse counters used for gas or water metering typically use DPT 5.010 (one-byte unsigned integer) or DPT 12.001 (four-byte unsigned integer) depending on the counter range. Always check the device documentation to confirm which DPT the manufacturer has implemented before creating the group address.
How do you link energy meter communication objects to group addresses in ETS?
Linking communication objects to group addresses in ETS is done within the device properties panel. After adding an energy meter to the ETS project and loading its product database entry, you navigate to the device’s communication objects tab, locate the relevant object (for example, “Active Power Total”), and drag the target group address onto it. Alternatively, you can right-click the object and select the group address from a list.
One communication object can be linked to multiple group addresses if the same value needs to be received by more than one device, such as both a KNX controller and a display panel. However, only one device should have the send flag enabled for any given group address to avoid bus conflicts. In energy metering, the meter itself holds the send flag, while the controller and visualization devices hold the receive flag.
After linking, always verify the communication object flags in ETS. For energy status values, the correct flag combination is typically: Transmit enabled, Read enabled, and Communication enabled on the meter side; Receive enabled and Communication enabled on the controller side. Missing or incorrect flags are a common cause of data not appearing in the visualization after commissioning.
Why do energy group addresses sometimes fail to transmit data correctly in KNX?
Energy group addresses fail to transmit data correctly for several reasons: DPT mismatches between sender and receiver, incorrect communication object flags, bus load issues caused by meters sending too frequently, or addressing conflicts where two devices share the same group address with send flags both active.
Cyclic transmission intervals are a particularly common source of problems in energy monitoring installations. If ten meters each send power readings every second, the combined bus load can exceed recommended levels, causing telegrams to be lost or delayed. The solution is to increase the cyclic send interval to a value appropriate for the monitoring granularity needed, typically between 30 seconds and 5 minutes for most energy dashboards.
Another frequent issue is that some energy meters only send a value when it changes by a defined threshold. If the threshold is set too high, small but meaningful changes in consumption will never be transmitted. Reviewing the device parameters in ETS and adjusting the minimum send delta resolves this. Always use the ETS diagnostic view or a KNX bus monitor tool to observe actual telegram traffic when troubleshooting silent group addresses.
How does a KNX controller use group address data from energy endpoints?
A KNX controller receives energy measurement values from group addresses and uses them to drive automation logic, visualization dashboards, and energy management decisions. The controller subscribes to the relevant group addresses, stores the incoming values, and makes them available to scenes, scripts, and external integrations in real time.
In practice, a controller can use incoming power readings to trigger load-shedding scenes when consumption exceeds a threshold, or to activate a heat pump only when solar production is sufficient. This closes the loop between measurement and action, turning passive monitoring into active energy management.
How Xxter Helps Professionals Manage KNX Energy Data
Once group addresses for energy endpoints are correctly configured in KNX ETS software, the xxter controller takes over as the central hub that collects, processes, and acts on that data. Xxter is designed specifically for professional KNX installations and bridges the gap between raw group address values and meaningful, actionable energy insights.
- The xxter controller reads energy group addresses directly from the KNX bus and presents live and historical consumption data through the free xxter app on any smartphone, tablet, or computer.
- The Smart Energy Manager (SEM) uses incoming energy data alongside weather forecasts and dynamic pricing to automatically minimize grid consumption and reduce energy costs.
- Scripts and triggers in xxter allow professionals to build automation logic based on energy thresholds, turning ETS-configured group addresses into real-time control actions without additional programming environments.
There are no license fees or subscription costs involved. Xxter works with any properly commissioned KNX energy installation, making it a straightforward addition to projects where ETS group address configuration is already complete. If you are setting up energy monitoring for a KNX project and want a controller built for KNX energy installations, making full use of your group address data, get in touch with the xxter team to discuss your installation.