Implement bridge-backed Home Assistant integration
This commit is contained in:
@@ -3,3 +3,25 @@
|
||||
Unofficial local Home Assistant integration for MB-Secure through the vendor-neutral MB-Secure Bridge API.
|
||||
|
||||
This public integration never connects directly to the controller and never stores controller credentials. The implementation is currently being developed against a neutral mock bridge.
|
||||
|
||||
The current development core includes UI and Supervisor app discovery flows,
|
||||
local bearer-token authentication, periodic snapshot reconciliation, a
|
||||
server-sent event listener with reconnect handling, and sanitized diagnostics.
|
||||
|
||||
Entities are created only for capabilities reported by the bridge. Controllers,
|
||||
areas, and modules are registered as devices with a stable hierarchy; points and
|
||||
outputs are attached to their normalized parent device. Snapshot reconciliation
|
||||
adds and removes runtime entities when the topology changes.
|
||||
|
||||
## Development
|
||||
|
||||
Use Python 3.14 and install the pinned test toolchain in an isolated environment:
|
||||
|
||||
```shell
|
||||
python -m venv .venv
|
||||
.venv/bin/python -m pip install -r requirements_test.txt
|
||||
.venv/bin/ruff check .
|
||||
.venv/bin/ruff format --check .
|
||||
.venv/bin/mypy custom_components/mb_secure
|
||||
.venv/bin/pytest
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user