Versions the M5 Atom Echo dedicated Bluetooth proxy ESPHome config (source of truth + README) that lends its BLE radio to shelly-manager's ble-agent for provisioning WiFi-less Shellys over mOS RPC-over-BLE.
esphome/shelly-ble-proxy.yaml — board: m5stack-atom, esp-idf, bluetooth_proxy: active, API encryption. Lean/no-voice (bluetooth_proxy + voice boot-loops the ESP32-PICO). The api.encryption.key is the handoff to the ble-agent (BLE_PROXY_NOISE_PSK).
Built/flashed via the in-cluster ESPHome Device Builder (esphome.home.renner.uno, PR #156). The dashboard reads from its PVC, not git, so these files are the reviewed/backed-up copy kept in sync by hand.
## What
Versions the M5 Atom Echo dedicated **Bluetooth proxy** ESPHome config (source of truth + README) that lends its BLE radio to shelly-manager's ble-agent for provisioning WiFi-less Shellys over mOS RPC-over-BLE.
- `esphome/shelly-ble-proxy.yaml` — `board: m5stack-atom`, `esp-idf`, `bluetooth_proxy: active`, API encryption. Lean/no-voice (bluetooth_proxy + voice boot-loops the ESP32-PICO). The `api.encryption.key` is the handoff to the ble-agent (`BLE_PROXY_NOISE_PSK`).
- `esphome/README.md` — device index, required secrets, flashing flow.
Built/flashed via the in-cluster ESPHome Device Builder (`esphome.home.renner.uno`, PR #156). The dashboard reads from its PVC, not git, so these files are the reviewed/backed-up copy kept in sync by hand.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Source-of-truth YAML (+ README) for the M5 Atom Echo dedicated Bluetooth proxy
that lends its BLE radio to shelly-manager's ble-agent for provisioning WiFi-less
Shellys over mOS RPC-over-BLE. Built/flashed via the in-cluster ESPHome Device
Builder (esphome.home.renner.uno).
Lean, dedicated config (no voice — bluetooth_proxy + voice boot-loops the
ESP32-PICO), esp-idf framework, bluetooth_proxy active. The api encryption key is
the handoff to the ble-agent (its BLE_PROXY_NOISE_PSK). The dashboard reads from
its PVC, not git, so these files are the reviewed/backed-up copy kept in sync by
hand.
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.
What
Versions the M5 Atom Echo dedicated Bluetooth proxy ESPHome config (source of truth + README) that lends its BLE radio to shelly-manager's ble-agent for provisioning WiFi-less Shellys over mOS RPC-over-BLE.
esphome/shelly-ble-proxy.yaml—board: m5stack-atom,esp-idf,bluetooth_proxy: active, API encryption. Lean/no-voice (bluetooth_proxy + voice boot-loops the ESP32-PICO). Theapi.encryption.keyis the handoff to the ble-agent (BLE_PROXY_NOISE_PSK).esphome/README.md— device index, required secrets, flashing flow.Built/flashed via the in-cluster ESPHome Device Builder (
esphome.home.renner.uno, PR #156). The dashboard reads from its PVC, not git, so these files are the reviewed/backed-up copy kept in sync by hand.🤖 Generated with Claude Code