Skip to content

Support KNX scene entity configuration from UI #42664

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
joostlek merged 1 commit into from
Dec 23, 2025
Merged

Support KNX scene entity configuration from UI #42664

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions source/_integrations/knx.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1823,6 +1823,10 @@ entity_category:

The KNX scene platform allows you to activate KNX scenes and updates scene entities when the corresponding scene number is received on the KNX bus.

Scene entities can be created from the frontend in the KNX panel or via YAML.

{% details "Configuration of KNX scene entities via YAML" %}

```yaml
# Example configuration.yaml entry
knx:
Expand Down Expand Up @@ -1852,6 +1856,8 @@ entity_category:
default: None
{% endconfiguration %}

{% enddetails %}

## Select

The KNX select platform allows the user to define a list of values that can be selected via the frontend and can be used within conditions of automation. When a user selects a new item, the assigned generic raw payload is sent to the KNX bus. A received telegram updates the state of the select entity. It can optionally respond to read requests from the KNX bus.
Expand Down