bahmcloud/HA-KNX-Bridge
1
0
Fork 0
mirror of https://github.com/bahmcloud/HA-KNX-Bridge.git synced 2026-04-06 12:11:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Track project prompt and state files

Browse Source
This commit is contained in:
René Bachmann
2026-02-13 12:14:45 +01:00
parent b733f9d62d
commit 127fa98471
3 changed files with 77 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.gitignore vendored
View File

@@ -1,4 +1,6 @@
.idea/
!.idea/START_PROMPT.md
!.idea/PROJECT_STATE.md
.DS_Store
__pycache__/
*.pyc

55
.idea/PROJECT_STATE.md generated Normal file
View File

@@ -0,0 +1,55 @@
# Project State: HA KNX Bridge
## Project Description
HA KNX Bridge is a Home Assistant custom integration that mirrors Home Assistant entities
to KNX group addresses and accepts KNX actions to control Home Assistant entities.
It is installed via HACS and configured through the Home Assistant UI (config flow).
The integration should:
- Reuse an existing Home Assistant KNX integration entry when available.
- Allow users to add "Ports" that bind a single HA entity to KNX group addresses.
- Auto-select appropriate KNX DPTs and request only the group addresses needed.
- Ignore missing/empty group addresses without errors.
Target compatibility: Home Assistant 2025.12 with forward compatibility to 2026.2.
Project rules:
- Keep `README.md` updated for user-relevant changes after each new version.
- Maintain `CHANGELOG.md` with newest entries at the top.
- Releases are created only when explicitly requested.
- Version number must match everywhere it is referenced (manifest, changelog, README, HACS if used).
## Current State (as of 2026-02-13)
Completed:
- Repo initialized with `main` branch and pushed to GitHub.
- HACS metadata (`hacs.json`) and base integration scaffold created.
- Config flow created with subentries ("Ports") for:
- Binary Sensor
- Cover
- KNX group address validation and normalization in subentry flows.
- Options flow skeleton added (no options yet).
- `bcs.yaml` metadata file added for BCS store listing.
- Bridge manager implements:
- Binary sensor state -> KNX send (DPT 1)
- Cover KNX incoming commands -> HA services
- Cover HA state -> KNX percent updates (DPT 5.001)
- README includes initial DPT mapping and roadmap.
- Project version set to 0.0.2 and `CHANGELOG.md` maintained.
Files created:
- `custom_components/ha_knx_bridge/__init__.py`
- `custom_components/ha_knx_bridge/bridge.py`
- `custom_components/ha_knx_bridge/config_flow.py`
- `custom_components/ha_knx_bridge/const.py`
- `custom_components/ha_knx_bridge/manifest.json`
- `custom_components/ha_knx_bridge/strings.json`
- `hacs.json`
- `README.md`
- `CHANGELOG.md`
- `.gitignore`
Open items / next steps:
- Validate and format KNX group address inputs in config flow.
- Add optional option flow for future settings.
- Expand entity coverage (light, switch, sensor, climate).
- Add tests (config flow, KNX mapping).
- Improve DPT auto-selection logic per entity features.

20
.idea/START_PROMPT.md generated Normal file
View File

@@ -0,0 +1,20 @@
# Start Prompt (Use for Every New Chat)
You are working on the `HA-KNX-Bridge` project.
Required steps at the start of every new chat:
1. Read `.idea/PROJECT_STATE.md` to understand the goal and current status.
2. Scan the repository for recent code changes relevant to the request.
3. If you make changes, update `.idea/PROJECT_STATE.md` to reflect the new state and date.
Constraints:
- Keep the project description and state accurate and concise.
- Always write an explicit date (YYYY-MM-DD) when updating the Current State section.
- Do not invent progress; only record what is verified in the repo.
- After any user-relevant change and version bump, update `README.md`.
- Maintain `CHANGELOG.md` with newest entries at the top, format:
- Version number
- Date (YYYY-MM-DD)
- Bullet list of changes
- Create releases only when explicitly requested.
- Keep the version number consistent in all files where it appears.