Replaces the static Ble__Proxies__0__{Name,Host,Port} env — which addressed the proxy by shelly-ble-proxy-1.iot.renner.uno, poisoned over IPv6 by the *.renner.uno wildcard — with a single shared fleet Noise key as Ble__Discovery__Key, from the same shelly-ble-proxy-key secret. Discovery finds the proxy on the IoT VLAN via mDNS (_esphomelib._tcp) over the existing net1 macvlan and dials its real link IP; the key lets the native-API Noise handshake complete.
Sequencing: merge after#14's image is live, so discovery is present when the static entry is removed. (Before then the running image simply has no static proxy for a short window.)
Companion to k.renner/shelly-manager#14 (mDNS auto-discovery of esphome BLE proxies).
Replaces the static `Ble__Proxies__0__{Name,Host,Port}` env — which addressed the proxy by `shelly-ble-proxy-1.iot.renner.uno`, poisoned over IPv6 by the `*.renner.uno` wildcard — with a single shared **fleet Noise key** as `Ble__Discovery__Key`, from the same `shelly-ble-proxy-key` secret. Discovery finds the proxy on the IoT VLAN via mDNS (`_esphomelib._tcp`) over the existing net1 macvlan and dials its real link IP; the key lets the native-API Noise handshake complete.
**Sequencing:** merge *after* #14's image is live, so discovery is present when the static entry is removed. (Before then the running image simply has no static proxy for a short window.)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
shelly-manager now auto-discovers esphome bluetooth_proxy nodes on the IoT
VLAN via mDNS (_esphomelib._tcp) — see k.renner/shelly-manager#14. Replace
the static Ble__Proxies__0__{Name,Host,Port} env (which addressed the proxy
by shelly-ble-proxy-1.iot.renner.uno — poisoned over IPv6 by the
*.renner.uno wildcard) with a single shared fleet Noise key exposed as
Ble__Discovery__Key, from the same shelly-ble-proxy-key secret.
Merge after #14's image is live so discovery is present when the static
entry goes away.
Co-Authored-By: Claude Bot <claude-bot@renner.uno>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Companion to k.renner/shelly-manager#14 (mDNS auto-discovery of esphome BLE proxies).
Replaces the static
Ble__Proxies__0__{Name,Host,Port}env — which addressed the proxy byshelly-ble-proxy-1.iot.renner.uno, poisoned over IPv6 by the*.renner.unowildcard — with a single shared fleet Noise key asBle__Discovery__Key, from the sameshelly-ble-proxy-keysecret. Discovery finds the proxy on the IoT VLAN via mDNS (_esphomelib._tcp) over the existing net1 macvlan and dials its real link IP; the key lets the native-API Noise handshake complete.Sequencing: merge after #14's image is live, so discovery is present when the static entry is removed. (Before then the running image simply has no static proxy for a short window.)
🤖 Generated with Claude Code
shelly-manager now auto-discovers esphome bluetooth_proxy nodes on the IoT VLAN via mDNS (_esphomelib._tcp) — see k.renner/shelly-manager#14. Replace the static Ble__Proxies__0__{Name,Host,Port} env (which addressed the proxy by shelly-ble-proxy-1.iot.renner.uno — poisoned over IPv6 by the *.renner.uno wildcard) with a single shared fleet Noise key exposed as Ble__Discovery__Key, from the same shelly-ble-proxy-key secret. Merge after #14's image is live so discovery is present when the static entry goes away. Co-Authored-By: Claude Bot <claude-bot@renner.uno>