feat(esphome): enable OTA + BLE debug logging on the shelly proxy #181

2026-07-14T07:20:00Z

claude-bot commented

2026-07-14 07:20:00 +00:00

Unblocks the provisioning debug loop. The Shelly-over-BLE provision fails at the GATT connect, and the cause is inside the ESP's BLE stack — invisible from shelly-manager's side. The current INFO-level, no-OTA firmware means every ESP change needs a physical USB flash, which isn't sustainable.

ota: (esphome platform) so future config changes push over WiFi from the in-cluster ESPHome Device Builder. Set shelly_ble_proxy_ota_password in the dashboard secrets first.
logger DEBUG with esp32_ble_client=VERBOSE / esp32_ble_tracker,bluetooth_proxy=DEBUG so a connect attempt logs its progress and the actual failure reason (connect failed, reason=0x…).

One USB flash to bootstrap (unavoidable — current firmware has no OTA); after that every ESP iteration is a remote OTA push. Then I watch the DEBUG logs during a provision and we finally see why the BLE connect never completes.

🤖 Generated with Claude Code

Unblocks the provisioning debug loop. The Shelly-over-BLE provision fails at the GATT connect, and the cause is inside the ESP's BLE stack — invisible from shelly-manager's side. The current INFO-level, no-OTA firmware means every ESP change needs a physical USB flash, which isn't sustainable. - **`ota:`** (esphome platform) so future config changes push over WiFi from the in-cluster ESPHome Device Builder. Set `shelly_ble_proxy_ota_password` in the dashboard secrets first. - **logger DEBUG** with `esp32_ble_client=VERBOSE` / `esp32_ble_tracker,bluetooth_proxy=DEBUG` so a connect attempt logs its progress and the actual failure reason (`connect failed, reason=0x…`). **One USB flash to bootstrap** (unavoidable — current firmware has no OTA); after that every ESP iteration is a remote OTA push. Then I watch the DEBUG logs during a provision and we finally see why the BLE connect never completes. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

claude-bot added 1 commit 2026-07-14 07:20:00 +00:00

feat(esphome): enable OTA + BLE debug logging on the shelly proxy 2990f6e425

Provisioning a Shelly over BLE fails at the GATT connect and the cause is
inside the ESP's BLE stack — invisible from shelly-manager's side. To
diagnose and iterate without a USB re-flash per change:

  * ota: (esphome platform) so future config changes push over WiFi from the
    ESPHome Device Builder. Bootstrapping costs one USB flash; set
    shelly_ble_proxy_ota_password in the dashboard secrets first.
  * logger DEBUG with esp32_ble_client=VERBOSE / esp32_ble_tracker,
    bluetooth_proxy=DEBUG, so a connect attempt logs its progress and the
    failure reason.

Takes effect on the (one) USB re-flash; thereafter iterate remotely.

Co-Authored-By: Claude Bot <claude-bot@renner.uno>

k.renner merged commit 5306c47600 into master

2026-07-14 07:39:21 +00:00

k.renner referenced this issue from a commit

2026-07-14 07:39:22 +00:00

Merge pull request 'feat(esphome): enable OTA + BLE debug logging on the shelly proxy' (#181) from feat/esphome-proxy-ota into master

claude-bot referenced this pull request

2026-07-14 07:46:49 +00:00

fix(esphome): valid logger levels on the shelly proxy (global VERBOSE) #182

claude-bot referenced this issue from a commit

2026-07-14 07:46:49 +00:00

fix(esphome): valid logger levels on the shelly proxy (global VERBOSE)

Sign in to join this conversation.