Hubs & protocols
KNX
knx
Built inLocal pushPlatinum
The KNX integration connects Home Assistant to your KNX installation, allowing you to control KNX devices, act on telegrams and forward state changes from other integrations entities to your KNX bus.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
light | Light | |
switch | Switch or outlet | |
cover | Blind, garage door, window or door | |
climate | Thermostat | |
fan | Fan | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
button | Button (as a switch) | |
scene | Scene (as a switch) | |
select | Mode picker (as switches) |
11 reports below say how a device from this integration behaves in the Home app.
What people report
KNX is local and generic: lights, covers, fans, climate and weather stations are configured by group address. Climate entities from KNX have mapped poorly to HomeKit and Alexa modes.
- Works6
- Partly works9
- Not working1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| KNX climate with swing | Works Local | Swing support added to KNX climate entitiesSaved copyProposed change Added support for swing in knx climate devices ## Type of change - [ ] Dependency upgrade - [ ] Bugfix (non-breaking change which fixes an issue) - [ ] New integration (thank you!) - [x] New feature (which adds functionality to an existing inte Excerpt saved from GitHub on 2026-10-23. | PR #136752 · 2025-01 | |
| KNX covers (shutters and blinds) | Works Local | Cover support tested with MDT roller shutter actuatorsSaved copyAdds support for KNX covers (roller shutters, window blinds) ## Description: Related feature request: https://community.home-assistant.io/t/support-for-knx-shutters-position-stop/14142 ### Notes 1. Tested with MDT roller shutter. This hardware uses 0 as open and 100 as closed, which is the opposite of the base cover implementation. This problem is mentioned here, which appeared to suggest that the polymer frontend would automatically reverse the definition of open/closed based on the device class so I also added optional support for the "device_class" setting. When I tested that locally it … Excerpt saved from GitHub on 2026-10-23. | PR #7997 · 2017-06 | |
| KNX fan with switch address | Works Local | Fans supporting only on/off or on/off plus speed supportedSaved copyProposed change This adds support for knx fan entities that either only support switching (on/off binary) or support switching in addition to setting a speed. The actuators default turn-on speed will be respected then. - [x] requires a release of `xknx` with https://github.com/XKNX/xknx/pull/1775 this is added to HA here https://github.com/home-assistant/core/pull/159371 ## Type of change <!-- What type of change does you Excerpt saved from GitHub on 2026-10-23. | PR #159367 · 2025-12 | |
| KNX lights (colour, HS, colour temperature) | Works Local | RGB, HS and DPT 9 colour temperature lights supportedSaved copyProposed change Update xknx to 2.11.0 https://github.com/XKNX/xknx/releases/tag/2.11.0 - Add support for DPT 9 color temperature in lights. - This version paves the way for HA Time and Date entity support. ## Type of change <!-- What type of change does your PR introduce to Home Assistant? NOTE: Please, check only 1! box! If your PR requires multiple boxes to be checked, you'll most likely need to split it into Excerpt saved from GitHub on 2026-10-23. | PR #95213 · 2023-06 | |
| KNX switch | Works | Broken in Home Shows 'not supported' in Home app after bridge setup | Fixed in 0.66 by HomeKit rewriteSaved copy… .homekit.state without resolving. If I change the order of devices in configurarion.yaml, the previously unsupported device returns to work and another switch stop working in homekit. My config: https://pastebin.com/uc7pUKac The device not working now is: - platform: knx name: Specchio bagno ingresso address: '3/1/0' (line 214 in the config) https://imgur.com/YskDLzg screen of the issue. Excerpt saved from GitHub on 2026-10-23. | Issue #13241 · 2018-03 |
| KNX weather station | Works Local | Dedicated weather station entity addedSaved copyProposed change This PR adds support for a dedicated KNX weather station. Detail View: Default view: If `expose_sensors` is used it will additionally publish all values as dedicate Excerpt saved from GitHub on 2026-10-23. | PR #39476 · 2020-08 | |
| KNX climate / thinka gateway | Partly works | Partly in Home Thermostat only shows set temperature; mode errors | Missing hvac_modes in KNX climate; KNX unmaintainedSaved copy… Assistant release (if known): n/a Operating environment (Hass.io/Docker/Windows/etc.): Hass.io Integration: https://www.home-assistant.io/integrations/climate.knx/ Description of problem: With HomeKit all works fine, but with alexa, if configured as below won't work. only works with "on_off_address\state_address" or with "controller_mode_address\mode_state_address" configured. This happen because Alexa NEED the "hot" or "cold" mode. My thermostat only have to set the temperature, not have a manual on\off or controller_mode, when it feel the right temperature activate valves. If i set the … Excerpt saved from GitHub on 2026-10-23. | Issue #30204 · 2019-12 |
| KNX climate without on/off address | Partly works Local | Partly in Home Works in HomeKit; thermostat shows only temperature set point | Only works for Alexa with on_off or controller address configuredSaved copy… Assistant release (if known): n/a Operating environment (Hass.io/Docker/Windows/etc.): Hass.io Integration: https://www.home-assistant.io/integrations/climate.knx/ Description of problem: With HomeKit all works fine, but with alexa, if configured as below won't work. only works with "on_off_address\state_address" or with "controller_mode_address\mode_state_address" configured. This happen because Alexa NEED the "hot" or "cold" mode. My thermostat only have to set the temperature, not have a manual on\off or controller_mode, when it feel the right temperature activate valves. If i set the … Excerpt saved from GitHub on 2026-10-23. | Issue #30204 · 2019-12 |
| KNX climate/cover devices | Partly works Local | Partly in Home Climate without on/off state not shown properly in HomeKit | Workaround config used for HomeKit state; unique_id neededSaved copy> Feature list is only for media players > > Ah, too bad. I didn't see that. Maybe the HomeKit integration will add this function for climate entities too - you could ask them. > > > problem is not homekit integration but how works the knx climate > > This is where I disagree. KNX provides a HA entity - this is fine. HomeKit doesn't support to change the temperature when the HA climate entity is set "OFF". This has nothing to do with KNX - if it was any other integration it would behave the same way. > So why not fix this problem at the cause instead of adding support for workarounds in … Excerpt saved from GitHub on 2026-10-23. | Issue #49088 · 2021-04 |
| KNX cover with tilt | Partly works Local | Partly in Home Closing via icon or Siri leaves tilt unchanged | Home only controls primary service; limitation of HomeKitSaved copy… problem I have already reported this in #48555 which was fixed. Unfortunately the same issue is still happening, maybe the bug was misinterpreted. I have a cover (KNX) with position and tilt_position. Controlling the cover with HomeKit works fine for both position and tilt. The problem I have is with fully closing the cover via HomeKit. If I close it by just tapping the icon or with Siri (hey siri, close cover xyz), the tilt position is not changed. Example: Cover is at 50% position, 50% tilt "Hey siri, close cover" HomeKit sets the position to 0: 2021-03-31 19:38:24 DEBUG (MainThread) … Excerpt saved from GitHub on 2026-10-23. | Issue #56400 · 2021-09 |
| KNX cover with tilt | Partly works Local | Partly in Home Close from Home app or Siri leaves tilt unchanged | Position and tilt work separately; full close ignores tiltSaved copyThe problem I have a cover (KNX) with position and tilt_position. Controlling the cover with HomeKit works fine for both position and tilt. The problem I have is with fully closing the cover via HomeKit. If I close it by just tapping the icon or with Siri (hey siri, close cover xyz), the tilt position is not changed. Example: Cover is at 50% position, 50% tilt "Hey siri, close cover" HomeKit sets the position to 0: `2021-03-31 19:38:24 DEBUG (MainThread) [homeassistant.components.homekit.type_covers] cover.buro_raff_1: Set position to 0` The tilt position is still at 50% When closing the … Excerpt saved from GitHub on 2026-10-23. | Issue #48555 · 2021-03 |
| KNX covers | Partly works Local | Partly in Home Movement progress percentage no longer shown while opening or closing | Position state correct in HA; HomeKit lacks target positionSaved copyThe problem Hi, I am facing a strange situation with HomeKit reading the state of my KNX covers. Before 2022.8 Home Assistant update, HomeKit was showing the progress of my covers while they were opening or closing (progress in percentage). After 2022.8 Home Assistant update, HomeKit doesn’t show anymore the progress. I only have the final state, i.e., either closed or open or 47% or 95% etc… But nothing is showing the progress in % while the covers are moving up or down. I haven’t changed anything to my config files… All is the same as before. I must say that I still have the 2022.7.7 Home … Excerpt saved from GitHub on 2026-10-23. | Issue #87461 · 2023-02 |
| KNX external blinds | Partly works Local | Partly in Home Blinds tilt back open after closing from Home | Works in HA UI; Home forces last tilt angle after movementSaved copyThe problem Hi. When I lower the blinds through HomeKit UI and they come to the closed position, they automatically tilt back up (to an open angle) after a couple of seconds. If I then manually adjust the tilt in HomeKit UI to a closed angle, a similar thing happens when most open: when they reach the top position, they get automatically lowered by a couple of centimetres. It feels like HomeKit is forcing last set slat angle to whatever position of the blinds. When I control my same blinds through HA UI it all works well: lowering them also sets slat angle to closed, opening also sets angle … Excerpt saved from GitHub on 2026-10-23. | Issue #60079 · 2021-11 |
| KNX room controller / climate (HVAC modes mapped to presets) | Partly works Local | Broken in Home Target mode set from Home app causes mapping error | HVAC modes map to presets so HomeKit cannot set target modeSaved copyI have the very same issue with KNX room controllers, on boot every controller throws following error: [code] Each entity exposes following attributes: [code] So, actual modes are mapped to the `preset_mode`. Excerpt saved from GitHub on 2026-10-23. | Issue #36342 · 2020-06 |
| KNX room controller thermostat | Partly works Local | Partly in Home Setting HVAC mode from Home app errors because modes map to preset_mode | Error on boot for every controllerSaved copyI have the very same issue with KNX room controllers, on boot every controller throws following error: [code] Each entity exposes following attributes: [code] So, actual modes are mapped to the `preset_mode`. Excerpt saved from GitHub on 2026-10-23. | Issue #36342 · 2020-06 |
| KNX climate with operation mode | Not working | Broken in Home TargetHeatingCoolingState invalid value errors in log | Errors persisted after upgrade from 0.103.0Saved copyHome Assistant release with the issue: 0.103.0 Last working Home Assistant release (if known): 0.102.3 Operating environment (Hass.io/Docker/Windows/etc.): Hass.io on Debian on NUC Integration: https://www.home-assistant.io/integrations/climate.knx https://www.home-assistant.io/integrations/homekit/ Description of problem: Continuous errors, looks like an issue with converting the HVAC operation mode from the KNX integration to HomeKit. Started after upgrading to 0.103.0. Error goes away when removing "operation_mode_address:" and "operation_mode_state_address:" from config, but that causes … Excerpt saved from GitHub on 2026-10-23. | Issue #29916 · 2019-12 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local push
Talks to the device on your network, and the device tells Home Assistant the moment something changes.
Details
| Installs (analytics) | 8,883 (1.25%) |
|---|---|
| Quality scale | Platinum |
| Added in | Home Assistant 0.24 |
| Set up in the UI | Yes |
| Maintainers | @Julius2342, @farmio, @marvin-w |
Limitations from the docs
- The integration aims to be compatible with a wide variety of KNX devices from different manufacturers and eras. However, there are some devices that use non-standard DPT or use telegrams in a proprietary way. In these cases, you might not be able to configure entities directly through this integration. However, you …
- The KNX tools for AI conversation agents return at most 1000 entries per call. An agent can page through the rest, but a question that would need the entire project or the full telegram history in a single answer may not be answered completely.
- The KNX tools work on raw KNX data: group addresses, individual addresses, and DPTs. They do not know about the Home Assistant entities you created from those group addresses. To let an agent control those entities as well, keep the built-in Assist API selected alongside the KNX API.
- USB bus interfaces are not directly supported by the underlying xknx library. However, you could try to run a software KNX router such as Calimero or knxd alongside Home Assistant to serve as a USB to IP bridge. For best reliability, using a certified KNX IP interface or router is recommended.
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
