Gives shelly-manager the api.encryption.key so its native ESPHome-API client (k.renner/shelly-manager#12) can do the real Noise_NNpsk0 handshake to the Atom Echo bluetooth_proxy.
shelly-ble-proxy-key.sops.yaml — SOPS Secret (api-key), same value as the ESPHome dashboard's shelly_ble_proxy_api_key (44-char base64 / 32-byte PSK), encrypted to the cluster age recipient.
shelly-manager-deployment — inject it as Ble__Proxies__0__Key via secretKeyRef.
Effect:/ble-radios upgrades from the bare TCP :6053 check to a real handshake + DeviceInfo (shows the proxy's name/version) — which also validates the Noise/frame stack on live hardware before the BLE scan/GATT provisioning slices build on it.
Adding the env changes the pod template, so the Recreate strategy rolls a new pod that picks up the secret.
Gives shelly-manager the `api.encryption.key` so its native ESPHome-API client (k.renner/shelly-manager#12) can do the **real Noise_NNpsk0 handshake** to the Atom Echo `bluetooth_proxy`.
- **`shelly-ble-proxy-key.sops.yaml`** — SOPS Secret (`api-key`), same value as the ESPHome dashboard's `shelly_ble_proxy_api_key` (44-char base64 / 32-byte PSK), encrypted to the cluster age recipient.
- **`shelly-manager-deployment`** — inject it as `Ble__Proxies__0__Key` via `secretKeyRef`.
**Effect:** `/ble-radios` upgrades from the bare TCP `:6053` check to a real handshake + `DeviceInfo` (shows the proxy's name/version) — which also validates the Noise/frame stack on **live hardware** before the BLE scan/GATT provisioning slices build on it.
Adding the env changes the pod template, so the Recreate strategy rolls a new pod that picks up the secret.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
shelly-manager's native ESPHome-API client (PR k.renner/shelly-manager#12)
does the real Noise_NNpsk0 handshake to the Atom Echo bluetooth_proxy when
it has the api.encryption.key. Provide it:
* shelly-ble-proxy-key.sops.yaml — SOPS Secret holding api-key, the same
value as the ESPHome dashboard's shelly_ble_proxy_api_key.
* shelly-manager-deployment: inject it as Ble__Proxies__0__Key via
secretKeyRef.
Effect: /ble-radios upgrades from a bare TCP :6053 check to a real
handshake + DeviceInfo (device name/version), which also validates the
Noise/frame stack on live hardware ahead of the BLE scan/GATT work.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Gives shelly-manager the
api.encryption.keyso its native ESPHome-API client (k.renner/shelly-manager#12) can do the real Noise_NNpsk0 handshake to the Atom Echobluetooth_proxy.shelly-ble-proxy-key.sops.yaml— SOPS Secret (api-key), same value as the ESPHome dashboard'sshelly_ble_proxy_api_key(44-char base64 / 32-byte PSK), encrypted to the cluster age recipient.shelly-manager-deployment— inject it asBle__Proxies__0__KeyviasecretKeyRef.Effect:
/ble-radiosupgrades from the bare TCP:6053check to a real handshake +DeviceInfo(shows the proxy's name/version) — which also validates the Noise/frame stack on live hardware before the BLE scan/GATT provisioning slices build on it.Adding the env changes the pod template, so the Recreate strategy rolls a new pod that picks up the secret.
🤖 Generated with Claude Code