Update of esphome device fails after update

ESPHome
1

Hi,

I’m running Home Assistant in a Proxmox VM.
I have an esphome ble-proxy up and running. Updating it fails since upgrading to a newer version. I had this issue with 2025.10.1 and 2025.10.2.
I tried uninstall and re-install of the esphome add-on. I’ve also performed a “Clean all” before installing the config.

My config is:

esphome:
  name: ble-proxy-esp32
  friendly_name: BLE Proxy ESP32
  platformio_options:
    platform: espressif32
    board_build.flash_mode: dio

esp32:
  board: esp32dev
  framework:
    type: esp-idf

logger:
# Enable Home Assistant API

api:
  encryption:
    key: "..."

ota:
  - platform: esphome
    password: "..."

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  ap:
    ssid: "BLE-Proxy Fallback"
    password: "fallback_pw"

captive_portal:


# Aktiviert den BLE Proxy
esp32_ble_tracker:

# Aktiviert Bluetooth-Proxy-Funktion für Home Assistant
bluetooth_proxy:
  active: true
light:
  - platform: esp32_rmt_led_strip
    id: rgb_led
    name: "RGB Status LED"
    pin: GPIO27
    num_leds: 1
    rgb_order: GRB
    chipset: ws2812
    restore_mode: ALWAYS_OFF
    effects: []

Validation of the config is successful.
The log output of the install process is:

INFO ESPHome 2025.10.2
INFO Reading configuration /config/esphome/bt-extender.yaml...
INFO Generating C++ source...
INFO Compiling app...
Processing ble-proxy-esp32 (board: esp32dev; framework: espidf; platform: espressif32)
--------------------------------------------------------------------------------
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
 - framework-espidf @ 3.50402.0 (5.4.2) 
 - tool-cmake @ 3.30.2 
 - tool-esp-rom-elfs @ 0.0.1+20241011 
 - tool-ninja @ 1.7.1 
 - tool-riscv32-esp-elf-gdb @ 12.1.0+20221002 
 - tool-xtensa-esp-elf-gdb @ 12.1.0+20221002 
 - toolchain-xtensa-esp-elf @ 14.2.0+20241119
Reading CMake configuration...
Dependency Graph
|-- noise-c @ 0.1.10
RAM:   [==        ]  17.3% (used 56744 bytes from 327680 bytes)
Flash: [=======   ]  73.5% (used 1349242 bytes from 1835008 bytes)
Building .pioenvs/ble-proxy-esp32/firmware.bin
Creating esp32 image...
Successfully created esp32 image.
merge_factory_bin([".pioenvs/ble-proxy-esp32/firmware.bin"], [".pioenvs/ble-proxy-esp32/firmware.elf"])
Info: bootloader.bin not found - skipping
Info: partition-table.bin not found - skipping
Info: ota_data_initial.bin not found - skipping
Info: ble-proxy-esp32.bin not found - skipping
Using FLASH_EXTRA_IMAGES from PlatformIO environment
Merging binaries into /data/build/ble-proxy-esp32/.pioenvs/ble-proxy-esp32/firmware.factory.bin
*** [.pioenvs/ble-proxy-esp32/firmware.bin] TypeError : sequence item 10: expected str instance, int found
Traceback (most recent call last):
  File "/data/cache/platformio/packages/tool-scons/scons-local-4.8.1/SCons/Action.py", line 1441, in execute
    result = self.execfunction(target=target, source=rsources, env=env)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/ble-proxy-esp32/post_build.py", line 107, in merge_factory_bin
    env.VerboseAction(" ".join(cmd), "Merging binaries with esptool")
                      ^^^^^^^^^^^^^
TypeError: sequence item 10: expected str instance, int found
========================== [FAILED] Took 8.40 seconds ==========================

I am looking for any help to get this working again. Thank you in advance!

2

At some point it was expecting a string (text or words), but found an integer (number) instead.
As someone not familiar with C++ programming and all the ESPHome code, I find these error messages rather unhelpful.

Is that all of your YAML code ? The only numeric value I see is num_leds which should be an integer.

3

Thank you for your response. I’ve removed the light block but the error persists.