---
title: "KNX"
description: "KNX is a built-in integration for Home Assistant. It has 8.9k installs sharing analytics and works locally."
canonical: "https://vulpo.app/integrations/core/knx"
url: "https://vulpo.app/integrations/core/knx.md"
last-updated: "2026-10-22"
version: "1.4"
---

# KNX

> KNX is a built-in integration for Home Assistant. It has 8.9k installs sharing analytics and works locally.

KNX is a built-in Home Assistant integration that connects to a KNX bus over IP and works locally. It supports tunneling and routing connections, including KNX IP Secure and Data Secure with a keyring file exported from ETS. It provides entity platforms such as lights, climate, covers, sensors, switches, fans, weather and several others. Actions can send data to the bus, read group addresses, expose values to the bus, register addresses for event triggering, and reload the integration. Diagnostic sensors report connection status, connection type, individual address and telegram traffic, and a telegram device trigger can start automations. Options cover rate limiting, state reading behavior and telegram history storage, including a PostgreSQL backend, and setup is done in the UI.

Automatic summary of Home Assistant's source code. Something wrong? [Get in touch](https://vulpo.app/contact)

[Open in My Home Assistant](https://my.home-assistant.io/redirect/config_flow_start/?domain=knx)

## Supports

- **Works locally**: Talks to your devices on your own network. No vendor cloud in between.
- **Set up in the UI**: Add it in Settings, Devices and services. Nothing to download.
- **Device triggers**: Its devices can start automations directly.
- **Change settings later**: Its connection settings can change without removing it.
- **Platinum quality**: Home Assistant's own rating of its code and setup experience.
- **Updated with Home Assistant**: Ships and updates with every Home Assistant release.

## Setting it up

It is added under Settings, Devices and services, with Add integration.

### KNX connection

- **KNX connection type**: Please select the connection type you want to use for your KNX connection.

### Tunnel endpoint

- **Select the tunnel endpoint used for the connection.**: 'Automatic' selects a free tunnel endpoint for you when connecting. If you're unsure, this is the best option.

Also asked when at the tunnel endpoint step.

### Tunnel settings

- **Host**: IP address or hostname of the KNX/IP tunneling device.
- **Local IP interface**: Local IP or interface name used for the connection from Home Assistant. Leave blank to use auto-discovery.
- **Port**: Port used by the KNX/IP tunneling device.
- **Route back / NAT mode**: Enable if your KNXnet/IP tunneling server is behind NAT. Only applies for UDP connections.
- **KNX tunneling type**: Select the tunneling type of your KNX/IP tunneling device. Older interfaces may only support UDP.

### Routing

- **Individual address**: KNX address to be used by Home Assistant, e.g. 0.0.4
- **Local IP interface**: Local IP or interface name used for the connection from Home Assistant. Leave blank to use auto-discovery.
- **Multicast group**: Multicast group used by your installation. Default is 224.0.23.12
- **Multicast port**: Multicast port used by your installation. Default is 3671
- **KNX IP Secure Routing**: Select if your installation uses encrypted communication according to the KNX IP Secure standard. This setting requires compatible devices and configuration. You'll be prompted for credentials in the next step.

### Import KNX Keyring

- **Keyring file**: Select a .knxkeys file. This can be exported from ETS.
- **Keyring password**: The password to open the .knxkeys file was set when exporting.

### Secure routing

- **Backbone key**: Can be seen in the 'Security' report of your ETS project. Eg. 00112233445566778899AABBCCDDEEFF
- **Network latency tolerance**: Should be equal to the backbone configuration of your ETS project. Default is 1000

### Secure tunneling

- **Device authentication password**: This is set in the 'IP' panel of the interface in ETS.
- **User ID**: This usually is tunnel number +1. So first tunnel in the list presented in ETS would have User-ID 2.
- **User password**: Password for the specific tunnel connection set in the 'Properties' panel of the tunnel in ETS.

### After setup

- **Rate limit**: Maximum outgoing telegrams per second. 0 to disable limit. Recommended: 0 or between 20 and 40
- **State updater**: Sets the default behavior for reading state addresses from the KNX Bus. When enabled, Home Assistant will monitor each group address and read it from the bus if no value has been received for one hour. When disabled, state addresses will only be read once after a bus connection is established. This behavior can be overridden for individual entities using the sync\_state option.
- **Telegram storage backend**: Select where to store KNX telegram history.
- **Group monitor history**: Number of hours of telegram history to load when the group monitor is opened.
- **Retention period**: Number of days to keep telegram history. Older telegrams are automatically deleted nightly at 3 AM. Set to 0 to delete all telegram history on every nightly run.
- **Database name**: Name of the database to store telegrams in.
- **Host**: Hostname or IP address of the PostgreSQL server.
- **Password**: Password for the PostgreSQL user. Leave blank to keep the current password.
- **Port**: Port the PostgreSQL server is listening on.
- **Use TLS**: Encrypt the connection to the PostgreSQL server (sslmode=require). Note that the server certificate is not verified.
- **Username**: Username to authenticate with the PostgreSQL server.

Texts from Home Assistant's source code, [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0).

## Entities

- **Sensors**: Connection established, Connection type, Individual address, Telegrams, Undecodable Data Secure telegrams, Incoming telegrams, Incoming telegram errors, Outgoing telegrams, Outgoing telegram errors

## Actions

- **Register knx\_event**: Adds or removes group addresses to knx\_event filter for triggering knx\_events. Only addresses added with this action can be removed.
  Fields: Group address, Remove event registration, Value type
- **Expose to KNX bus**: Adds or removes exposures to KNX bus. Only exposures added with this action can be removed.
  Fields: Group address, Entity attribute, Default value, Entity, Remove exposure, Value type
- **Read from KNX bus**: Sends GroupValueRead requests to the KNX bus. Response can be used from knx\_event and will be processed in KNX entities. When response data is requested, waits for the answer to a single group address and returns it.
  Fields: Group address
- **Reload**: Reloads the KNX integration.
- **Send to KNX bus**: Sends arbitrary data directly to the KNX bus.
  Fields: Group address, Payload, Send as Response, Value type

## Troubleshooting

- **Diagnostics**: Downloads a diagnostics file to attach to a bug report.
- **Repair notices**: Notices it can show in Settings, Repairs:
  KNX Data Secure telegrams can't be decrypted, Invalid KNX entity configuration, KNX telegram storage error

## At a glance

- Kind: Built-in integration
- Category: [Hubs and protocols](https://vulpo.app/integrations/category/hubs-and-protocols.md), Building automation
- Brand: [KNX](https://vulpo.app/integrations/knx.md)
- Number: 8.9k installs sharing analytics
- Connection: Works locally
- Upkeep: Part of Home Assistant
- Needs: Built into Home Assistant
- Quality scale: Platinum quality scale
- Domain: `knx`
- Source: <https://www.home-assistant.io/integrations/knx/>

In Vulpo: Light card, Quick Toggle card, Cover card, Climate card, Lumen sky (Pro), Apple Watch, Control Center, Climate Live Activity (Pro)

[Widgets & Live Activities in Vulpo](https://vulpo.app/features/widgets-and-live-activities)

## Other ways in for KNX

| Name | Kind | Installs or stars | Connection | Upkeep |
| --- | --- | --- | --- | --- |
| [KNX User Forum Icon Set](https://github.com/mampfes/ha-knx-uf-iconset) | Dashboard card | 13 GitHub stars | Connection not stated | No update in 6 to 18 months |

Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about)

Last updated 2026-10-22. Source: https://vulpo.app/integrations/core/knx

---

- HTML version of this page: https://vulpo.app/integrations/core/knx
- Site index for agents: https://vulpo.app/llms.txt
- Everything in one document: https://vulpo.app/llms-full.txt
- All pages: https://vulpo.app/sitemap.xml
