Compile Issues with ESP32-C3 and espidf

ESPHome
1

Hi
It seems like this is an issue which occasional recurs, but for me, after upgrading to 2025.7.4 yesterday, I can no longer compile code for my ESP32-C3. I am trying to create a BT proxy, so my yaml is:

esphome:
  name: bt-proxy-wr
  friendly_name: Bluetooth Proxy WR2
  min_version: 2024.12.0
  name_add_mac_suffix: true

esp32:
  board: esp32-c3-devkitm-1
  framework:
    type: esp-idf
    sdkconfig_options:
      CONFIG_BT_BLE_42_FEATURES_SUPPORTED: y
      CONFIG_BT_BLE_50_FEATURES_SUPPORTED: n
# Enable logging
logger:
  level: VERBOSE

# Enable Home Assistant API
api:
  encryption:
    key: "blah"

ota:
  - platform: esphome
    password: "blah blah"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Bt-Proxy-Wr Fallback Hotspot"
    password: "blah blah blah"

#captive_portal:
esp32_ble_tracker:
  scan_parameters:
    # We currently use the defaults to ensure Bluetooth
    # can co-exist with WiFi In the future we may be able to
    # enable the built-in coexistence logic in ESP-IDF
    active: true

bluetooth_proxy:
  active: true

button:
  - platform: safe_mode
    id: button_safe_mode
    name: Safe Mode Boot

  - platform: factory_reset
    id: factory_reset_btn
    name: Factory reset

and I consistently get the error, logged as follows:

INFO ESPHome 2025.7.4
INFO Reading configuration /config/esphome/bt-proxy-wr.yaml…
INFO Generating C++ source…
INFO Compiling app…
Processing bt-proxy-wr (board: esp32-c3-devkitm-1; framework: espidf; platform: https://github.com/pioarduino/platform-espressif32/releases/download/53.03.13/platform-espressif32.zip)

HARDWARE: ESP32C3 160MHz, 320KB RAM, 4MB Flash

  • framework-espidf @ 3.50302.0 (5.3.2)
  • tool-cmake @ 3.30.2
  • tool-esptoolpy @ 4.8.6
  • tool-mklittlefs @ 3.2.0
  • tool-ninja @ 1.7.1
  • tool-riscv32-esp-elf-gdb @ 14.2.0+20240403
  • tool-xtensa-esp-elf-gdb @ 14.2.0+20240403
  • toolchain-esp32ulp @ 2.35.0-20220830
  • toolchain-riscv32-esp @ 13.2.0+20240530
    Reading CMake configuration…
    – git rev-parse returned ‘fatal: not a git repository (or any parent up to mount point /)
    Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).’
    – Building ESP-IDF components for target esp32c3
    – Configuring incomplete, errors occurred!

fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
CMake Error at /data/cache/platformio/packages/framework-espidf/tools/cmake/build.cmake:552 (message):
/root/.platformio/penv/.espidf-5.3.2/bin/python: Error while finding module
specification for ‘idf_component_manager.prepare_components’
(ModuleNotFoundError: No module named ‘idf_component_manager’)

Call Stack (most recent call first):
/data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:710 (idf_build_process)
CMakeLists.txt:3 (project)

========================== [FAILED] Took 3.77 seconds ==========================

Any ideas on how to fix it? I have tried doing a Clean Build Files (no change), and also tried reverting to an earlier version (it never finished downloading).
Thanks
Alex

2

Did you try with arduino framework?
Or to install manually idf_component_manager

3

Are you using ESPHome Builder add-on? There is nothing wrong with your yaml, I suggest you uninstall and re-install the ESPHome add-on.

4

I thought I had read that the Arduino framework wasn’t good for a BT proxy using WiFi. If I got that wrong, please tell me and I will give it a go.
If you could point me at info on how to manually install idf_component_manager, that would be useful. I will Google too.

5

Yes, I am using the ESPHome Builder add-on. I will uninstall and reinstall it.

6

Thanks, I had the same problem and reinstalling ESPHome (2025.7) fixed my problem.

Just in case anybody else is wondering, it was pretty painless: it kept my devices and their config files, and I just had to wait for it to re-download and re-compile the dependencies (which is no big deal).