From 632b0b294e109e41adb0e978bb9888667608b8af Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ren=C3=A9=20Bachmann?= Date: Fri, 4 Sep 2026 12:57:32 +0200 Subject: [PATCH] Add Supervisor discovery metadata --- mb_secure_bridge/DOCS.md | 5 +++++ mb_secure_bridge/config.yaml | 3 +++ 2 files changed, 8 insertions(+) diff --git a/mb_secure_bridge/DOCS.md b/mb_secure_bridge/DOCS.md index 6627b72..e747d52 100644 --- a/mb_secure_bridge/DOCS.md +++ b/mb_secure_bridge/DOCS.md @@ -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. 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. diff --git a/mb_secure_bridge/config.yaml b/mb_secure_bridge/config.yaml index 3f452d6..7bfa66b 100644 --- a/mb_secure_bridge/config.yaml +++ b/mb_secure_bridge/config.yaml @@ -10,6 +10,9 @@ arch: - amd64 - aarch64 image: git.bahmcloud.de/bahmcloud/mb-secure-bridge +hassio_api: true +discovery: + - mb_secure ports: {} ports_description: {} options: