Not sure if these belongs here or the ESPHome discord... trying to rebuild an ESPHome configuration on another board type (esp32c3 to esp32c6), aand the build fails because the sdkconfig doesn't match the new target. I've cleaned the build files but the error remains. Is there a way to get into the esphome volume to manually clear the build cache? Running HAOS on Yellow.
#Clear sdkconfig in esphome builder
zenith pivot
Build output:
INFO ESPHome 2025.7.5
INFO Reading configuration /config/esphome/sump-alert.yaml...
INFO Generating C++ source...
INFO Compiling app...
Processing sump-alert (board: esp32-c6-devkitc-1; framework: espidf; platform: https://github.com/pioarduino/platform-espressif32/releases/download/53.03.13/platform-espressif32.zip)
--------------------------------------------------------------------------------
HARDWARE: ESP32C6 160MHz, 320KB RAM, 8MB 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.10.2
- 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...
-- Configuring incomplete, errors occurred!
CMake Error at /data/cache/platformio/packages/framework-espidf/tools/cmake/targets.cmake:108 (message):
Target 'esp32c3' in sdkconfig '/data/build/sump-alert/sdkconfig.sump-alert' does not match currently selected IDF_TARGET 'esp32c6'. To change the target, clear the build directory and sdkconfig file, and build the project again.
Call Stack (most recent call first):
/data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:24 (__target_init)
CMakeLists.txt:2 (include)
========================== [FAILED] Took 3.96 seconds ==========================
rigid zephyr
Not sure if these belongs here or the ESPHome discord... trying to rebuild an ES...
its probably more at home on the ESPHome discord.
zenith pivot
Asked there too, but I thought I'd check in here as well since it's more about how to access the volume of a running add-on as opposed to the add-on itself.