KNX UI
This is the KNX panel for the KNX core integration in Home Assistant. It provides a user interface for interacting with the KNX integration.
Development
If you check out this repository for the first time please run the following command to init the submodules:
$ nvm use
$ script/bootstrap
...
Development build (watcher)
$ script/develop
...
Production build
$ script/build
...
Update the home assistant frontend
Get the latest release tag.
$ script/upgrade-frontend
...
Or get a specific tag or sha.
$ script/upgrade-frontend <tag-or-sha>
...
Testing the panel
First of all we recommend to follow the instructions for preparing a home assistant development environment.
You can test the panel by symlinking the build result directory knx_frontend
into your Home Assistant configuration directory.
Assuming:
- The
knx-frontendrepository is located at<knx-frontend-dir>path - The
home-assistant-corerepository is located at<hass-dir>path (Remark: per default the Home Assistant configuration directory will be created within<hass-dir>/config)
$ ln -s <knx-frontend-dir>/knx_frontend <hass-dir>/config/deps/lib/python3.xx/site-packages/
$ hass -c config
...
Or on a venv-install
$ cd <hass-dir>
$ script/setup
# Next step might be optional
$ source .venv/bin/activate
$ export PYTHONPATH=<knx-frontend-dir>
$ hass
...
Now hass (Home Assistant Core) should run on your machine and the knx panel is
accessible at http://localhost:8123/knx.
On Home Assistant OS you might use https://github.com/home-assistant/addons-development/tree/master/custom_deps
AI Agent Support
This repository ships a set of instructions for AI coding agents.
-
GitHub Copilot comes pre-configured — its guidance lives in
.github/copilot-instructions.md. -
For other agents, you can easy symlink the Copilot instructions with:
yarn agent:claude # Creates CLAUDE.md yarn agent:gemini # Creates GEMINI.md yarn agent:codex # Creates AGENTS.md
3 maintainers
Metadata
3 maintainers
Release files for knx-frontend 2026.7.8.100603
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| knx_frontend-2026.7.8.100603.tar.gz | 45.5 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| knx_frontend-2026.7.8.100603-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 91.2 MB
Release files / knx_frontend-2026.7.8.100603.tar.gz
| Download URL | knx_frontend-2026.7.8.100603.tar.gz |
|---|---|
| Size | 45.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f34c9e0d9f1af160dffcd1178c54a471fa60969f724e79a0fb872c15b81d1693
|
|
BLAKE2b-256 checksum How to use checksums |
3d684a952bf0a0fb7ad04acad63c2ac89879d17e41fe728a07238403edbc9aa0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.6
|
Release files / knx_frontend-2026.7.8.100603-py3-none-any.whl
| Download URL | knx_frontend-2026.7.8.100603-py3-none-any.whl |
|---|---|
| Size | 45.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
79685431bc37f57997a6dceeeea14ee37c5e0a2ed7f1d2c2708217be9ee72e23
|
|
BLAKE2b-256 checksum How to use checksums |
b17e4d839a7f4f4b06ccf108c13f7a44b4414f374bccd1a6274ed8cf7b4bd851
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.6
|
Security for knx-frontend 2026.7.8.100603
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
