Summary of "So einfacht geht's 2026 - KNX Heizungssteuerung in Home Assistant"

Short summary — what the video covers

Topic: Creating KNX Climate entities in Home Assistant via the (January 2026) UI update and practical configuration examples for KNX heating control.
Main point: Home Assistant now lets you create Climate entities (and many other entity types) from the KNX integration UI (KNX tab → Entities → Add). Correct KNX Data Point Types (DPTs) and understanding where controller logic runs (room controller vs heating actuator) are critical for a working setup.

Main takeaway

Home Assistant’s KNX UI can now create Climate entities directly. You must bind the right KNX group addresses with appropriate DPTs and know whether the controller lives in the room device or the actuator to ensure proper behavior.

Key technological concepts and product features

Home Assistant (HA) KNX UI

The KNX integration GUI is located in the KNX tab in the sidebar.
You can create Climate entities and many other entity types via the GUI.
Default state update behavior:
- HA reads device state after restart.
- If no update occurs within 60 minutes, HA re-reads the device.
- The 60-minute timer restarts on any feedback from the device.

KNX heating control basics

Two main control styles:
- Relative setpoint shift (offset from a base setpoint).
- Absolute setpoint specification (explicit target temperature).
Controller location affects what addresses/DPTs you must bind:
- Controller can be the wall thermostat (room controller), inside the heating actuator, or elsewhere.

KNX Data Point Types (DPTs) and limitations

Use correct DPTs when importing an ETS project into HA.
- Example issue: a temperature encoded with a floating-point DPT (DPT 9 variant mismatch) prevented automatic mapping.
Home Assistant does NOT support 1-bit “setpoint shift via key press” style objects.
- You need a numeric setpoint-shift object (2-byte or absolute value).

Operating mode and objects

Combined operating mode objects (one object representing modes like comfort/eco/standby) are typically easier to map than multiple single-bit mode objects.
Some controllers lack an “automatic” mode or “off” in a combined object — check your device features.
Heating vs cooling support exists (important for heat pumps).

Useful KNX objects to map for a Climate entity

Current temperature (DPT 9 / temperature)
Current humidity (optional)
Target temperature (absolute) or:
- Setpoint shift + Setpoint status (numeric)
Operating mode (combined object preferred)
Operating mode status
Activity / valve position (percentage)
On/Off (if available)
Heating/Cooling mode and their statuses

Step-by-step highlights shown in the video (examples)

Import KNX project / group addresses into Home Assistant
- Recommended: ensure correct DPTs in ETS before importing.
Add Entity → Climate
- Choose the current temperature object (or enter manually if DPT mismatch).
Setpoint shift example (Kitchen)
- Use setpoint shift transmitter and setpoint status.
- Choose appropriate DPT (2-byte setpoint shift shown). HA requires a numeric object (not 1-bit).
- Configure min/max offsets (example: -5 to +5 K) and step (example: 0.5 K).
- Add activity (valve %), operating mode and operating mode status (combined object), etc.
- Test: HA sends setpoint shift (e.g., +3 K) and actuator feedback shows target temp and valve %.
Absolute setpoint example (Living room)
- Bind target temperature and status addresses (example min/max: 5–37 °C, step 0.5 K).
- Ensure current temperature is DPT 9001 (temperature); otherwise fix in ETS or enter manually (HA will warn).
- Map operating mode, heating/cooling status, on/off as available.
- Test: HA sends exact temperature values (e.g., 29 °C) rather than offsets.
Testing and debugging
- Use ETS bus monitor / diagnostics to watch what HA sends and what the actuator responds with.
- If HA cannot auto-map items, check group address DPTs in ETS and correct them.
Naming and entity IDs
- Give entities clear names during creation to avoid automatic fallback errors.
- You can rename the display name without changing the entity_id to avoid breaking automations — edit the entity’s settings.

Common pitfalls and tips

Ensure the KNX project uses correct Data Point Types (e.g., DPT 9001 for temperature) before importing — saves manual fixes.
HA does not support 1-bit setpoint shifting; require numeric (2-byte or absolute) objects.
If controllers don’t provide a status address, you can sometimes reuse the same group address for status — but verify device behavior first.
Default HA read interval is 60 minutes; HA restarts the timer on each feedback.
Prefer combined operating mode objects over multiple single-bit mode objects unless your controller uses individual bits.
When creating entities, name them properly to avoid duplicates and breaking existing automations or dashboards.

Extras / channel resources mentioned

Presenter promotes a KNX + Home Assistant course on Udemy (referred to as “Judemi” in subtitles).
“Insider” membership level with device-specific playlists and deeper tutorials.
Links to earlier videos and a playlist on KNX heating control and Home Assistant for foundational knowledge.

Main speakers / sources referenced

Video presenter / channel author (unnamed in subtitles) — walkthrough and demonstrations.
Home Assistant (KNX integration; January 2026 update).
ETS (KNX programming/diagnostics tool) and KNX actuators/room controllers (examples: heating actuator, Mini‑Touch).
KNX protocol and Data Point Types (DPTs).
Udemy course (presenter’s KNX + Home Assistant course) — optional paid resource.