23 lines
1.6 KiB
Markdown
23 lines
1.6 KiB
Markdown
# Configuration
|
|
|
|
## Test installation
|
|
|
|
Add `https://git.bahmcloud.de/bahmcloud/home-assistant-addons` as a custom repository in the Home Assistant app store, refresh the store, and install **MB-Secure Bridge**.
|
|
|
|
Install the MB-Secure custom integration before starting the app so that Supervisor discovery can offer the integration automatically.
|
|
|
|
Configure the local controller address and the installation-specific credentials supplied for your system. Credentials stay inside the app and are never passed to the Home Assistant integration.
|
|
|
|
For local certificates, `fingerprint` mode requires the expected SHA-256 certificate fingerprint. A certificate change is rejected. `system_ca` uses the standard trust store. For `custom_ca`, place the PEM certificate at the configured path inside the app configuration directory.
|
|
|
|
The bridge also requires the installation-specific object catalog at the configured path. Place the exported catalog in the app configuration directory as `objects.csv`, or update `object_catalog_path`. The app mounts this directory read-only and does not copy its contents into diagnostics or logs.
|
|
|
|
The bridge API is intended for the internal Home Assistant network and is not exposed on a host port by default.
|
|
|
|
For the first live test, verify connectivity, discovered topology, and read-only state updates before operating areas or outputs.
|
|
|
|
When running under Home Assistant Supervisor, the app advertises and registers
|
|
the local Bridge API through Supervisor discovery. The runtime-provided internal
|
|
host name and the dedicated local bridge token are sent only to Supervisor. The
|
|
integration asks for confirmation before creating a config entry.
|