claude-botandClaude Opus 4.8
fdddbe7e78
Per how it's actually run: drop OTA and the fallback AP/captive_portal — this is a fixed, low-value proxy, so updates and any WiFi recovery are done by re-flashing over USB. Secrets shrink to iot_wifi_ssid / iot_wifi_password / shelly_ble_proxy_api_key (the api encryption key stays; it's the ble-agent handoff). README secrets list + flashing note updated to match. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1.4 KiB
ESPHome device configs
Source-of-truth YAML for ESPHome devices in the homelab. These are built and
flashed through the ESPHome Device Builder running in-cluster at
https://esphome.home.renner.uno (see kubernetes/apps/home-assistant/esphome-*
and the esphome-gate Authentik blueprint).
The dashboard reads configs from its own /config on the esphome-data PVC — it
does not sync from git. So the flow is: edit here → paste/copy into the
dashboard → compile + flash. Keep the two in sync manually; git is the reviewed,
backed-up copy.
Devices
| File | Device | Role |
|---|---|---|
shelly-ble-proxy.yaml |
M5 Atom Echo (ESP32-PICO) | Dedicated Bluetooth proxy that lends its BLE radio to shelly-manager's ble-agent for provisioning WiFi-less Shellys over mOS RPC-over-BLE. |
Secrets
The dashboard's secrets.yaml (on the PVC — not in git) must define:
iot_wifi_ssid: "<IoT SSID>"
iot_wifi_password: "<...>"
# 32-byte base64 — dashboard "Generate", or: openssl rand -base64 32
# This value is the handoff to the ble-agent (its BLE_PROXY_NOISE_PSK).
shelly_ble_proxy_api_key: "<...>"
Flashing
USB only — the config has no OTA and no recovery AP by design. Flash (and any later update or WiFi-recovery) is browser-side over USB (ESP Web Tools / Web Serial, Chrome/Edge): plug the Atom Echo into your computer, open the dashboard, Install → Plug into this computer.