Gas Boiler KNX Integration: Viessmann Vitodens and Vaillant ecoTEC Modbus Setup
Integrating gas and condensing boilers into a KNX building automation system provides a single interface for zone heating setpoints, fault alerting, gas energy sub-metering and EN 15232-1 Class A adaptive heating control — without replacing the boiler's own controls.
Why integrate a boiler with KNX
Modern condensing boilers expose a Modbus TCP or OpenTherm interface that allows a KNX system to write flow temperature setpoints, read operating status, retrieve gas consumption counters and receive fault codes. This integration delivers four measurable benefits.
Single interface for zone setpoints
KNX room thermostats send heating demand directly to the boiler setpoint via Modbus — eliminating separate boiler programmer and zone valve controllers. One ETS6 time schedule controls all zones and the boiler simultaneously.
Fault alerting to BMS
Boiler fault codes appear in KNX group addresses within the Modbus poll cycle. ARISTO BewO sends email or SMS when fault GA changes to 1 — facilities engineers receive immediate notification with fault code included in the message body.
Gas energy sub-metering
The boiler's internal gas energy meter (Modbus register, kWh) feeds into KNX energy monitoring. Monthly gas consumption reports per zone or per boiler support ISO 50001 energy management and BREEAM Ene 02 sub-metering credits.
EN 15232-1 Class A/B compliance
Adaptive heating control — weather compensation, room-by-room PI setpoint control and optimum start — requires digital integration between the boiler and room temperature sensors. KNX/Modbus integration enables Class A energy classification for BREEAM Man credits.
Viessmann Vitodens 200-W Modbus TCP setup
The Vitodens 200-W uses the ViCARE ModBus module — a DIN-rail mounted gateway that provides RS-485 or Ethernet Modbus TCP (port 502) access to the boiler's internal registers. The module clips onto the boiler PCB bus connector and requires a separate 24V supply from the panel.
Vitodens 200-W key Modbus holding registers
Register Description Type Notes
1 Flow temperature setpoint (°C×10) Read/Write Write to control heating
3 Actual flow temperature (°C×10) Read-only Measured at boiler outlet
5 Return temperature (°C×10) Read-only Measured at boiler return
7 Boiler status Read-only 0=Standby, 1=Heating,
2=DHW, 3=Fault
100 Fault code Read-only 0=No fault; non-zero=fault
200 Gas energy meter (uint32, kWh) Read-only Cumulative gas consumption
Protocol: Modbus TCP, port 502
Gateway: ViCARE ModBus module (DIN-rail, connects to X4 boiler bus)
Poll interval: 30 seconds recommendedConnect the Vitodens Modbus TCP interface to a KNX/Modbus gateway such as the Intesis IN701KNX. In the MAPS configuration tool, map each register to a KNX group address with the appropriate DPT.
KNX group address mapping
Register 1 → DPT 9.001 (°C, 2-byte float) → GA 8/0/0 Flow setpoint (write) Register 7 → DPT 5.010 (uint8) → GA 8/0/1 Boiler status (read) Register 200→ DPT 12.001 (uint32, kWh) → GA 8/0/2 Gas energy meter (read) Register 100→ DPT 5.010 (uint8) → GA 8/0/4 Fault code (read) Write GA 8/0/0 value 21.0°C → Modbus register 1 value 210 Read GA 8/0/1: 0=standby, 1=heating, 2=DHW, 3=fault
Vaillant ecoTEC integration options
Vaillant uses eBUS (a proprietary 2-wire serial bus) on older ecoTEC plus and pro models. Direct KNX/eBUS gateways are not commercially available, making direct Modbus integration impossible on these variants. Three integration paths are available depending on the ecoTEC model and project requirements.
Option 1: VR900 cloud API (ecoTEC plus/pro)
The Vaillant VR900 internet gateway provides a cloud REST API (myVaillant or Vaillant ERelax). Use a Home Assistant instance with the Vaillant ERelax integration to bridge cloud data to KNX via the HA KNX integration. Limitation: 5-minute update interval — not suitable for real-time setpoint control. Use for status monitoring and energy logging only.
Option 2: VR33 OpenTherm interface (ecoTEC plus/pro)
The Vaillant VR33 adapter enables OpenTherm protocol on eBUS models. A third-party KNX/OpenTherm gateway (Remeha iSense or Nibe Uplink OpenTherm bridge) converts OpenTherm to KNX group objects: flow setpoint, room temperature demand, modulation level. OpenTherm provides real-time setpoint control unlike the cloud API.
Option 3: ecoTEC pure with VR940 Modbus TCP (recommended for new projects)
The Vaillant ecoTEC pure (current generation) supports Modbus TCP directly via the VR940F Ethernet module. Register map is similar to Viessmann — flow setpoint, return temperature, status and fault code registers. Specify ecoTEC pure at design stage for projects requiring direct KNX/Modbus integration without eBUS conversion.
Cascade boiler control via KNX
Commercial buildings with 2–4 boilers in a cascade configuration use lead/lag control to match heating output to demand while extending equipment life. KNX logic in the MDT Logic Module SCN-LOGM.01 manages the cascade sequence.
Cascade lead/lag logic — ETS6 MDT Logic Module
Total heating demand GA (sum of zone thermostat outputs) → MDT Logic
If demand > 0%: → Write setpoint to Lead Boiler (GA 8/0/0)
If demand > 50%: → Enable Lag Boiler 2 via KNX relay output
(relay NO → boiler 2 enable terminal)
Sequence rotation (extends boiler life):
ETS6 weekly time module → rotate lead boiler each Monday
Week 1: Boiler 1 lead, Boiler 2 lag
Week 2: Boiler 2 lead, Boiler 1 lag
Setpoint scaling:
Zone demand 0–100% DPT 5.001 → proportional setpoint
20°C (min) to 80°C (max) → write to lead boiler GA 8/0/0Cascade interlock:always include a boiler enable/disable relay output in the cascade wiring. Do not rely solely on Modbus setpoint writes to shut down a lag boiler — a failed gateway or network issue should fall back to the boiler's own controls rather than leaving a lag boiler running at full output.
Condensing boiler return temperature monitoring
Condensing boilers achieve maximum efficiency (above 108% net calorific value) only when the return water temperature falls below 55°C — the condensing onset point. KNX monitoring of return temperature is therefore a commissioning KPI, not just a diagnostic tool.
Return temperature group address — Intesis MAPS signal
Modbus register 5 (return temperature, °C×10)
→ DPT 9.001 (°C, 2-byte float, divide by 10)
→ GA 8/0/3 (Boiler Return Temperature)
ARISTO trend graph: plot GA 8/0/3 vs time
Daily minimum return temperature report (06:00)
Alert threshold: if daily minimum return > 60°C:
→ ARISTO alarm "Hydraulic imbalance: check mixing
valve or buffer tank — boiler not condensing"
Commissioning KPI: return temperature < 45°C for
>80% of heating season operating hoursA consistently high return temperature (above 60°C) indicates hydraulic imbalance — either the mixing valve is set too high, the buffer tank is undersized, or the secondary circuit lacks sufficient flow. Visualise return temperature against outdoor temperature in ARISTO to identify the heating curve adjustment needed.
DHW domestic hot water integration
The boiler's DHW (domestic hot water) setpoint is accessible via a separate Modbus register. KNX time scheduling provides automatic legionella prevention and solar thermal priority without a separate programmer.
DHW schedule — MDT Logic Module time events
Modbus register 10: DHW setpoint (°C×10, read/write) → DPT 9.001 → GA 8/0/5 (DHW Setpoint, write) ETS6 time schedule (MDT SCN-LOGM.01): 05:00 → GA 8/0/5 = 60°C (legionella, EN ISO 15154) 06:00 → GA 8/0/5 = 50°C (normal hot water) 22:00 → GA 8/0/5 = 0°C (DHW off — setpoint 0 = off) Solar thermal priority logic: If GA 9/0/3 (solar yield kW) > 2kW → GA 8/0/5 = 40°C (solar covers remainder) Frost protection: If GA 8/1/0 (outdoor temp) < 2°C → KNX relay output → DHW circulation pump ON
Boiler fault alerting
Boiler fault detection uses two Modbus registers: register 7 (status = 3 means fault) and register 100 (fault code, non-zero means fault). The KNX fault GA triggers ARISTO BewO email and SMS alerting with the fault code included in the message.
ARISTO BewO fault alert configuration
Trigger: GA 8/0/4 (Boiler Fault) = 1
(Set when register 7 = 3 OR register 100 ≠ 0)
ARISTO BewO rule:
IF GA("8/0/4") = 1
THEN ALARM "Boiler Fault Code " + GA("8/0/4") + " at " + TIME
TO EMAIL facilities@building.com
VIA SMTP → email-to-SMS gateway (for on-call engineer)
Response SLA (commercial):
Boiler fault → facilities engineer on-site: 4 hours
Critical (loss of heating below 5°C outdoor): 1 hour
Logging: all fault events with timestamp stored in ARISTO
database for warranty documentation and maintenance recordsInclude fault code in alert: Viessmann fault code 0x10 (sensor failure) requires a different response than 0x21 (ignition failure). Including the raw fault code in the alert email allows the engineer to order the correct part before arriving on-site, reducing downtime for building occupants.
Viessmann ViCare cloud API for energy reporting
In addition to local Modbus TCP control, the Viessmann ViCare REST API (api.viessmann.com) provides historical gas consumption data at 5-minute intervals. This cloud API complements local Modbus — use Modbus for real-time setpoint control and the ViCare API for long-term energy reporting.
ViCare API capabilities
- Daily gas consumption (kWh) — historical series
- Seasonal efficiency (SCOP) — calculated by boiler
- DHW energy consumption separate from heating
- OAuth2 authentication (Viessmann account required)
- 5-minute update interval — not real-time
Do not use for setpoint control
The ViCare cloud API has 5-minute latency and depends on internet connectivity. Always use local Modbus TCP for flow setpoint writes and fault detection. Use the cloud API only for daily energy reporting and seasonal efficiency trending in IP-Symcon or ARISTO BewO.
Commissioning verification procedure
After ETS6 download and Modbus gateway configuration, perform a four-step commissioning test before handing over the installation. Document all results in the commissioning certificate.
| Step | Action | Expected result |
|---|---|---|
| 1 | Send GA 8/0/0 = 21°C from ETS6 Group Monitor | Boiler display shows 21°C flow setpoint within 30 seconds |
| 2 | Read GA 8/0/1 (status) and compare to boiler display mode indicator | GA value 0/1/2/3 matches standby/heating/DHW/fault on boiler display |
| 3 | Note register 200 (kWh), run boiler 30 minutes, re-read | kWh counter has incremented — gas consumption measured |
| 4 | Disconnect boiler sensor briefly → verify GA 8/0/4 = 1 and email received | Fault GA triggers within 60 seconds; alert email arrives with fault code |
Need boiler KNX integration engineered and commissioned?
We configure Modbus TCP gateways, map boiler registers to KNX group addresses and commission fault alerting — delivered with full ETS6 project documentation and commissioning certificates.
Request a quote →