Skip to content

Conversation

@farmio
Copy link
Contributor

@farmio farmio commented Dec 20, 2025

Proposed change

Support KNX text entity configuration from UI

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

Checklist

  • I understand the code I am submitting and can explain how it works.
  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

@home-assistant
Copy link

Hey there @Julius2342, @marvin-w, mind taking a look at this pull request as it has been labeled with an integration (knx) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of knx can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign knx Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds support for configuring KNX text entities through the Home Assistant UI (in addition to the existing YAML configuration). This brings the text platform in line with other KNX platforms that already support UI configuration.

Key changes:

  • Refactored text entity classes to support both YAML and UI configuration sources
  • Added UI schema validation and websocket API support for text entities
  • Implemented comprehensive test coverage for UI-created and UI-loaded text entities

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
homeassistant/components/knx/text.py Refactored entity classes: split into base _KnxText, KnxYamlText for YAML config, and new KnxUiText for UI config; updated setup to handle both config sources
homeassistant/components/knx/storage/entity_store_schema.py Added TEXT_KNX_SCHEMA validation schema for UI configuration with group address, mode, respond_to_read, and sync_state fields
homeassistant/components/knx/storage/const.py Added CONF_GA_TEXT constant for text group address configuration key
homeassistant/components/knx/const.py Added Platform.TEXT to SUPPORTED_PLATFORMS_UI to enable UI configuration
homeassistant/components/knx/strings.json Added translation strings for text platform UI configuration including descriptions and labels
tests/components/knx/test_text.py Added test_text_ui_create and test_text_ui_load tests to verify UI configuration creation and storage loading
tests/components/knx/snapshots/test_websocket.ambr Added snapshot for text platform schema returned by websocket API
tests/components/knx/fixtures/config_store_text.json Added test fixture with sample stored text entity configuration

Co-authored-by: Copilot <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants