Configuring heating and cooling changeover in KNX is one of those tasks that looks straightforward on paper but quickly reveals its complexity in real buildings. Mixed-mode HVAC systems, where the same zones or fan coil units can switch between heating and cooling depending on the season or even the time of day, demand precise logic in ETS and careful planning of group addresses. Get it wrong, and you end up with zones fighting each other, valves opening in the wrong direction, or thermostats that simply do not know what mode they are in. This guide walks through the full process: from understanding how KNX handles changeover logic, to configuring it step by step, to catching the mistakes that trip up even experienced integrators.
How mixed-mode HVAC systems behave in KNX
A mixed-mode building uses the same hydronic or air-based distribution infrastructure for both heating and cooling. The central plant switches between hot and chilled water supply depending on demand, season, or occupancy patterns. From a KNX perspective, the critical challenge is that the building automation system must always know the current operating mode and communicate that state to every relevant actuator and thermostat in the installation.
KNX thermostats and HVAC actuators typically support both heating and cooling setpoints, but they rely on an external mode signal to determine which setpoint is active and which valve direction is correct. Without a reliable changeover signal on the bus, a thermostat may command a valve to open for heating while the system is actually delivering chilled water, causing discomfort and wasted energy. The KNX heating/cooling changeover is therefore not just a comfort feature; it is a fundamental control requirement for mixed-mode buildings.
Mapping the changeover logic to KNX group addresses
Before opening ETS, it helps to map out the logic clearly. The changeover state is typically represented as a 1-bit datapoint: 1 = cooling, 0 = heating (following the KNX standard DPT 1.100). This single bit needs to reach every thermostat, actuator, and controller object that depends on the operating mode.
A clean group address structure separates the changeover signal into a dedicated functional block. A common approach uses a main group for HVAC control, a middle group for system-level signals, and individual group addresses for the changeover bit per zone or globally. If the changeover is building-wide, a single group address broadcast to all relevant objects is sufficient. If different wings or floors switch independently, each zone needs its own changeover group address linked to the appropriate source, typically a KNX logic module or central controller output.
Configuring the changeover in ETS step by step
The ETS configuration process for KNX heating/cooling changeover follows a clear sequence. Starting from the thermostat or HVAC controller device in ETS, locate the communication object for heating/cooling mode. This is usually labeled “H/C changeover” or “Mode” and carries DPT 1.100.
- Link the H/C changeover object on each thermostat to the designated changeover group address
- Connect the changeover output from the central controller or logic module to the same group address
- Verify that the datapoint type matches on both sending and receiving objects
- Set the thermostat’s parameter for “changeover source” to “via bus” rather than manual or fixed
After downloading the configuration, test by sending the changeover bit manually from ETS diagnostics. The thermostat display should update its active setpoint and mode indication immediately. If it does not respond, check whether the object is flagged for both write and update, a common oversight that prevents the object from receiving bus telegrams.
Handling zones with different changeover timing
In larger buildings, not all zones switch at the same moment. An interior zone may call for cooling while a north-facing perimeter zone still needs heating. This is where the KNX mixed-mode building configuration becomes more nuanced, and where a logic module or a capable central controller becomes essential.
The solution is to avoid a single global changeover bit and instead implement zone-level changeover logic. Each zone’s thermostat receives its own changeover signal, generated by a logic function that evaluates local conditions: room temperature, setpoint deviation, valve position feedback, or a combination of these. A KNX logic module or a gateway with scripting capability can calculate this per zone and write the appropriate bit to each zone’s changeover group address independently.
Timing delays also matter. When the central plant switches from heating to chilled water supply, there is a lag before the distribution pipework reaches the correct temperature. Configuring a delay in the changeover logic, typically several minutes, prevents thermostats from opening valves before the system is ready, avoiding energy waste and temperature overshoot.
Common changeover configuration mistakes and how to fix them
Even experienced KNX installers run into predictable problems when configuring HVAC changeover. Recognizing these early saves significant commissioning time on site.
One of the most frequent issues is a datapoint type mismatch. If the sending object uses DPT 1.001 (a generic 1-bit on/off) and the receiving thermostat expects DPT 1.100 (heating/cooling), ETS may allow the link, but the thermostat interprets the value incorrectly. Always confirm DPT alignment before downloading. A second common mistake is forgetting to set the changeover object’s communication flags correctly: the object on the thermostat must have the Write and Update flags enabled, while the sending object needs the Transmit flag active.
Another issue arises when integrators use a fixed parameter in ETS to set the thermostat permanently to heating or cooling mode, then later try to override it via bus. If the parameter overrides the bus object, the thermostat will ignore incoming changeover telegrams entirely. The fix is to set the operating mode parameter to “determined by bus object” and ensure the controller sends an initialization telegram on startup so thermostats always have a valid mode on power-up. You can log in to your xxter account to manage initialization settings and monitor device status remotely.
How xxter supports KNX HVAC professionals
xxter’s platform is built with exactly these integration challenges in mind. The xxter controller provides the central logic layer that mixed-mode buildings need: it can generate and distribute changeover signals across all zones, apply timing delays, and respond dynamically to building conditions, all without requiring additional third-party logic hardware.
- Zone-level changeover logic configurable through the xxter interface, without complex ETS programming
- Script and trigger functionality to automate mode switching based on schedules, temperatures, or external signals
- Integration with the Smart Energy Manager to align HVAC changeover with dynamic energy pricing and solar production
- Full KNX compatibility with standard DPT objects, ensuring seamless communication with any compliant thermostat or actuator
For professionals working on mixed-mode buildings, xxter removes the guesswork from changeover configuration and gives you a reliable, auditable control layer that clients can actually use. Explore the xxter controller HVAC product information on the xxter website, or contact the xxter team directly to discuss your project requirements.
Ofte stillede spørgsmål
What is the best way to test the heating/cooling changeover signal after configuring it in ETS?
The most reliable method is to use ETS diagnostics to manually send the changeover bit (0 for heating, 1 for cooling) to the group address and observe the thermostat’s display response in real time. You should verify that the active setpoint, mode indication, and valve direction all update correctly. If you have physical access to the installation, cross-check with a clamp meter or actuator feedback to confirm that valve behavior matches the commanded mode.
Can a KNX thermostat operate in mixed-mode without receiving a changeover signal from the bus?
Technically yes, but it is not recommended for real-world mixed-mode buildings. Most thermostats allow you to fix the operating mode via an ETS parameter, but this means the device will always assume heating or always assume cooling regardless of what the central plant is actually delivering. In a mixed-mode system, this almost always leads to valves opening in the wrong direction, causing discomfort and energy waste. Always configure the thermostat to receive its mode via bus and ensure an initialization telegram is sent on startup.
How do I handle a situation where some thermostats respond to the changeover signal and others do not?
Start by checking the communication flags on the non-responding thermostats — the most common cause is a missing Write or Update flag on the H/C changeover object. Next, verify that the group address is correctly linked to both the sending and receiving objects in ETS, and that the datapoint type (DPT 1.100) matches on all sides. If flags and DPTs are correct, use ETS Group Monitor to confirm that the telegram is actually reaching the bus and that no addressing conflict exists.
How long should the timing delay be when switching from heating to cooling mode, and how do I configure it?
The appropriate delay depends on the length and thermal mass of your distribution pipework, but a range of 5 to 15 minutes is typical for most hydronic systems. The goal is to ensure the water in the pipes has reached the correct temperature before thermostats are allowed to open valves. This delay is best configured in a logic module or central controller — such as the xxter controller — as a timed trigger that holds the changeover bit from being distributed to zone thermostats until after the plant transition period has elapsed.
Is it possible to implement zone-level changeover logic without a dedicated logic module or central controller?
It is possible in small installations using advanced thermostat parameters or actuator logic, but it becomes difficult to maintain and troubleshoot as the number of zones grows. Without a central logic layer, you would need to replicate changeover conditions independently for each zone, which increases ETS complexity and commissioning time significantly. For any installation with more than two or three independently switching zones, a dedicated logic module or a controller with scripting capability is strongly recommended for reliability and auditability.
What should I do if the thermostat ignores the changeover telegram even after setting the correct flags and DPT?
First, confirm in the ETS device parameters that the operating mode source is set to ‘determined by bus object’ rather than a fixed parameter — a fixed parameter will silently override any incoming telegram. Second, check whether the device requires an ETS download after flag changes, as some devices cache their configuration. Finally, verify the device firmware version, as some older thermostat firmware versions have known bugs with DPT 1.100 handling that were resolved in later releases; consult the manufacturer’s release notes if the issue persists.
Can the KNX heating/cooling changeover signal be integrated with energy management or building scheduling systems?
Yes, and this is increasingly common in energy-conscious buildings. By linking the changeover logic to a Smart Energy Manager or building scheduler, you can align HVAC mode switching with factors like dynamic electricity tariffs, solar production peaks, or occupancy schedules — reducing operating costs without sacrificing comfort. Platforms like xxter support this natively by combining KNX changeover control with energy data inputs, allowing the system to automatically favor heating or cooling modes during the most cost-effective energy windows.