37 lines
1.6 KiB
Markdown
37 lines
1.6 KiB
Markdown
# MB-Secure for Home Assistant
|
|
|
|
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
|
|
```
|
|
|
|
## Manual installation for testing
|
|
|
|
1. Copy `custom_components/mb_secure` into `/config/custom_components/mb_secure` on the Home Assistant system.
|
|
2. Restart Home Assistant.
|
|
3. Install and start the MB-Secure Bridge app.
|
|
4. Confirm the discovered **MB-Secure** integration in **Settings > Devices & services**.
|
|
|
|
Validate connectivity, topology, and read-only state updates before testing area or output commands on a live installation.
|