Add Supervisor discovery metadata

This commit is contained in:
2026-09-04 12:57:32 +02:00
parent a26c37dee0
commit 632b0b294e
2 changed files with 8 additions and 0 deletions
+5
View File
@@ -5,3 +5,8 @@ Configure the local controller address and the installation-specific credentials
For local certificates, `fingerprint` mode requires the expected SHA-256 certificate fingerprint. A certificate change is rejected. `system_ca` uses the standard trust store, while `custom_ca` is reserved for a separately provided local certificate authority. For local certificates, `fingerprint` mode requires the expected SHA-256 certificate fingerprint. A certificate change is rejected. `system_ca` uses the standard trust store, while `custom_ca` is reserved for a separately provided local certificate authority.
The bridge API is intended for the internal Home Assistant network and is not exposed on a host port by default. The bridge API is intended for the internal Home Assistant network and is not exposed on a host port by default.
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.
+3
View File
@@ -10,6 +10,9 @@ arch:
- amd64 - amd64
- aarch64 - aarch64
image: git.bahmcloud.de/bahmcloud/mb-secure-bridge image: git.bahmcloud.de/bahmcloud/mb-secure-bridge
hassio_api: true
discovery:
- mb_secure
ports: {} ports: {}
ports_description: {} ports_description: {}
options: options: