Build errors after upgrade to 2025.8.0 on Pi 5/16GB?

mprowe · August 21, 2025, 8:34am

Following the prompt to switch the framework: from aurduino to esp-idf, which I have done successfully on x86 Home Assistant server, it is not going so well on a Raspberry Pi 5?
This is the start of the build output:

INFO ESPHome 2025.8.0
INFO Reading configuration /config/esphome/victron-reader.yaml...
INFO Generating C++ source...
INFO Compiling app...
Processing victron-reader (board: lolin_s2_mini; framework: espidf; platform: https://github.com/pioarduino/platform-espressif32/releases/download/54.03.21-2/platform-espressif32.zip)
--------------------------------------------------------------------------------
ERROR idf_tools.py installation failed
INFO Package configuration completed successfully
Library Manager: Installing bblanchon/ArduinoJson @ 7.4.2
INFO Installing bblanchon/ArduinoJson @ 7.4.2
Unpacking  [####################################]  100%
Library Manager: [email protected] has been installed!
INFO [email protected] has been installed!
ERROR idf_tools.py installation failed
INFO Package configuration completed successfully
idf_tools.py installation failed
HARDWARE: ESP32S2 240MHz, 320KB RAM, 4MB Flash
 - framework-espidf @ 3.50402.0 (5.4.2) 
 - tool-cmake @ 3.30.2 
 - tool-esp-rom-elfs @ 2024.10.11 
 - tool-esptoolpy @ 5.0.2 
 - tool-mklittlefs @ 3.2.0 
 - tool-ninja @ 1.13.1 
 - tool-scons @ 4.40801.0 (4.8.1) 
 - toolchain-esp32ulp @ 2.35.0-20220830 
 - toolchain-xtensa-esp-elf @ 14.2.0+20241119
Reading CMake configuration...
FileNotFoundError: [Errno 2] No such file or directory: '/data/cache/platformio/packages/tool-cmake/bin/cmake':
  File "/usr/local/lib/python3.12/site-packages/platformio/builder/main.py", line 173:
    env.SConscript("$BUILD_SCRIPT")
  File "/data/cache/platformio/packages/tool-scons/scons-local-4.8.1/SCons/Script/SConscript.py", line 620:
    return _SConscript(self.fs, *files, **subst_kw)

It looks (to me) as if the idf_tools.py has a problem? Any thoughts?

Regards, Martin

zoogara · August 21, 2025, 8:42am

Have a look at this:

github.com/esphome/esphome

Update to 2025.8.0 fails

opened 02:36PM - 20 Aug 25 UTC

cristianstoica

### The problem Update to 2025.8.0 from 2025.7.5 fails on HAOS with ESPHome Add…on. Tried: - usual installation (via GUI) - from ESPHome Builder (Wirelessly, Plug into computer etc) - cleaned build files - removing caches (ALL PlatformIO caches) - reinstalled the add-on Nothing worked. Usually getting errors "-- git rev-parse returned 'fatal: not a git repository (or any parent up to mount point /)", "xtensa-esp32-elf-* is not a full path and was not found in the PATH." Firstly, when reinstalling the addon. I got "TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType:" but when retrying it just got vack to first errors" ### Which version of ESPHome has the issue? 2025.8.0 ### What type of installation are you using? Home Assistant Add-on ### What platform are you using? ESP32 ### Component causing the issue _No response_ ### YAML Config ```yaml ``` ### Anything in the logs that might be useful for us? ```txt INFO ESPHome 2025.8.0 INFO Reading configuration /config/esphome/esp32-bluetooth-proxy-088e90.yaml... INFO Generating C++ source... INFO Compiling app... Processing esp32-bluetooth-proxy-088e90 (board: esp32dev; framework: espidf; platform: https://github.com/pioarduino/platform-espressif32/releases/download/54.03.21-2/platform-espressif32.zip) -------------------------------------------------------------------------------- INFO Package configuration completed successfully INFO Package configuration completed successfully HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash - framework-espidf @ 3.50402.0 (5.4.2) - tool-cmake @ 3.30.2 - tool-esp-rom-elfs @ 2024.10.11 - tool-esptoolpy @ 5.0.2 - tool-mklittlefs @ 3.2.0 - tool-ninja @ 1.13.1 - tool-scons @ 4.40801.0 (4.8.1) - toolchain-esp32ulp @ 2.35.0-20220830 - toolchain-xtensa-esp-elf @ 14.2.0+20241119 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).' -- The C compiler identification is unknown -- The CXX compiler identification is unknown -- The ASM compiler identification is unknown -- Found assembler: xtensa-esp32-elf-gcc -- Warning: Did not find file Compiler/-ASM -- 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/project.cmake:571 (__project): The CMAKE_C_COMPILER: xtensa-esp32-elf-gcc is not a full path and was not found in the PATH. Tell CMake where to find the compiler by setting either the environment variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH. Call Stack (most recent call first): CMakeLists.txt:3 (project) CMake Error at /data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:571 (__project): The CMAKE_CXX_COMPILER: xtensa-esp32-elf-g++ is not a full path and was not found in the PATH. Tell CMake where to find the compiler by setting either the environment variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH. Call Stack (most recent call first): CMakeLists.txt:3 (project) CMake Error at /data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:571 (__project): The CMAKE_ASM_COMPILER: xtensa-esp32-elf-gcc is not a full path and was not found in the PATH. Tell CMake where to find the compiler by setting either the environment variable "ASM" or the CMake cache entry CMAKE_ASM_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH. Call Stack (most recent call first): CMakeLists.txt:3 (project) ========================== [FAILED] Took 5.99 seconds ========================== ``` ### Additional information INFO ESPHome 2025.8.0 INFO Reading configuration /config/esphome/esp32-bluetooth-proxy-088e90.yaml... INFO Starting log output from 192.168.8.19 using esphome API INFO Successfully resolved esp32-bluetooth-proxy-088e90 @ 192.168.8.19 in 0.000s INFO Successfully connected to esp32-bluetooth-proxy-088e90 @ 192.168.8.19 in 0.005s INFO Successful handshake with esp32-bluetooth-proxy-088e90 @ 192.168.8.19 in 0.072s [17:35:45][I][app:149]: ESPHome version 2025.7.5 compiled on Aug 6 2025, 08:44:17 [17:35:45][C][wifi:613]: WiFi: [17:35:45][C][wifi:434]: Local MAC: F4:65:0B:08:8E:90 [17:35:45][C][wifi:439]: SSID: [redacted] [17:35:45][C][wifi:442]: IP Address: 192.168.8.19 [17:35:45][C][wifi:446]: BSSID: [redacted] [17:35:45][C][wifi:446]: Hostname: 'esp32-bluetooth-proxy-088e90' [17:35:45][C][wifi:446]: Signal strength: -53 dB ▂▄▆█ [17:35:45][C][wifi:455]: Channel: 11 [17:35:45][C][wifi:455]: Subnet: 255.255.255.0 [17:35:45][C][wifi:455]: Gateway: 192.168.8.1 [17:35:45][C][wifi:455]: DNS1: 45.90.28.130 [17:35:45][C][wifi:455]: DNS2: 45.90.30.130 [17:35:45][C][logger:246]: Logger: [17:35:45][C][logger:246]: Max Level: DEBUG [17:35:45][C][logger:246]: Initial Level: DEBUG [17:35:45][C][logger:252]: Log Baud Rate: 115200 [17:35:45][C][logger:252]: Hardware UART: UART0 [17:35:45][C][logger:259]: Task Log Buffer Size: 768 [17:35:45][C][bluetooth_proxy:158]: Bluetooth Proxy: [17:35:45][C][bluetooth_proxy:159]: Active: YES [17:35:45][C][bluetooth_proxy:159]: Connections: 3 [17:35:45][C][bluetooth_proxy:159]: Raw advertisements: YES [17:35:45][C][safe_mode.button:024]: Safe Mode Button 'Safe Mode Boot' [17:35:45][C][safe_mode.button:024]: Icon: 'mdi:restart-alert' [17:35:45][C][factory_reset.button:011]: Factory Reset Button 'Factory reset' [17:35:45][C][factory_reset.button:011]: Icon: 'mdi:restart-alert' [17:35:45][C][esp32_ble:518]: BLE: [17:35:45][C][esp32_ble:518]: MAC address: F4:65:0B:08:8E:92 [17:35:45][C][esp32_ble:518]: IO Capability: none [17:35:45][C][esp32_ble_tracker:763]: BLE Tracker: [17:35:45][C][esp32_ble_tracker:764]: Scan Duration: 300 s [17:35:45][C][esp32_ble_tracker:764]: Scan Interval: 320.0 ms [17:35:45][C][esp32_ble_tracker:764]: Scan Window: 30.0 ms [17:35:45][C][esp32_ble_tracker:764]: Scan Type: ACTIVE [17:35:45][C][esp32_ble_tracker:764]: Continuous Scanning: YES [17:35:45][C][esp32_ble_tracker:780]: Scanner State: RUNNING [17:35:45][C][esp32_ble_tracker:792]: Connecting: 0, discovered: 0, searching: 0, disconnecting: 0 [17:35:45][C][bluetooth_proxy.connection:017]: BLE Connection: [17:35:45][C][esp32_ble_client:063]: Address: [17:35:45][C][esp32_ble_client:063]: Auto-Connect: FALSE [17:35:45][C][esp32_ble_client:100]: State: IDLE [17:35:45][C][bluetooth_proxy.connection:017]: BLE Connection: [17:35:45][C][esp32_ble_client:063]: Address: [17:35:45][C][esp32_ble_client:063]: Auto-Connect: FALSE [17:35:45][C][esp32_ble_client:100]: State: IDLE [17:35:45][C][bluetooth_proxy.connection:017]: BLE Connection: [17:35:45][C][esp32_ble_client:063]: Address: [17:35:45][C][esp32_ble_client:063]: Auto-Connect: FALSE [17:35:45][C][esp32_ble_client:100]: State: IDLE [17:35:45][C][esphome.ota:073]: Over-The-Air updates: [17:35:45][C][esphome.ota:073]: Address: esp32-bluetooth-proxy-088e90.local:3232 [17:35:45][C][esphome.ota:073]: Version: 2 [17:35:45][C][safe_mode:018]: Safe Mode: [17:35:45][C][safe_mode:019]: Boot considered successful after 60 seconds [17:35:45][C][safe_mode:019]: Invoke after 10 boot attempts [17:35:45][C][safe_mode:019]: Remain for 300 seconds [17:35:45][C][api:207]: API Server: [17:35:45][C][api:207]: Address: esp32-bluetooth-proxy-088e90.local:6053 [17:35:45][C][api:212]: Using noise encryption: YES [17:35:45][C][mdns:122]: mDNS: [17:35:45][C][mdns:122]: Hostname: esp32-bluetooth-proxy-088e90

Seems to be a common issue

zoogara · August 21, 2025, 8:43am

Workaround is at this post:

github.com/esphome/esphome

Update to 2025.8.0 fails

opened 02:36PM - 20 Aug 25 UTC

cristianstoica

### The problem Update to 2025.8.0 from 2025.7.5 fails on HAOS with ESPHome Add…on. Tried: - usual installation (via GUI) - from ESPHome Builder (Wirelessly, Plug into computer etc) - cleaned build files - removing caches (ALL PlatformIO caches) - reinstalled the add-on Nothing worked. Usually getting errors "-- git rev-parse returned 'fatal: not a git repository (or any parent up to mount point /)", "xtensa-esp32-elf-* is not a full path and was not found in the PATH." Firstly, when reinstalling the addon. I got "TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType:" but when retrying it just got vack to first errors" ### Which version of ESPHome has the issue? 2025.8.0 ### What type of installation are you using? Home Assistant Add-on ### What platform are you using? ESP32 ### Component causing the issue _No response_ ### YAML Config ```yaml ``` ### Anything in the logs that might be useful for us? ```txt INFO ESPHome 2025.8.0 INFO Reading configuration /config/esphome/esp32-bluetooth-proxy-088e90.yaml... INFO Generating C++ source... INFO Compiling app... Processing esp32-bluetooth-proxy-088e90 (board: esp32dev; framework: espidf; platform: https://github.com/pioarduino/platform-espressif32/releases/download/54.03.21-2/platform-espressif32.zip) -------------------------------------------------------------------------------- INFO Package configuration completed successfully INFO Package configuration completed successfully HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash - framework-espidf @ 3.50402.0 (5.4.2) - tool-cmake @ 3.30.2 - tool-esp-rom-elfs @ 2024.10.11 - tool-esptoolpy @ 5.0.2 - tool-mklittlefs @ 3.2.0 - tool-ninja @ 1.13.1 - tool-scons @ 4.40801.0 (4.8.1) - toolchain-esp32ulp @ 2.35.0-20220830 - toolchain-xtensa-esp-elf @ 14.2.0+20241119 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).' -- The C compiler identification is unknown -- The CXX compiler identification is unknown -- The ASM compiler identification is unknown -- Found assembler: xtensa-esp32-elf-gcc -- Warning: Did not find file Compiler/-ASM -- 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/project.cmake:571 (__project): The CMAKE_C_COMPILER: xtensa-esp32-elf-gcc is not a full path and was not found in the PATH. Tell CMake where to find the compiler by setting either the environment variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH. Call Stack (most recent call first): CMakeLists.txt:3 (project) CMake Error at /data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:571 (__project): The CMAKE_CXX_COMPILER: xtensa-esp32-elf-g++ is not a full path and was not found in the PATH. Tell CMake where to find the compiler by setting either the environment variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH. Call Stack (most recent call first): CMakeLists.txt:3 (project) CMake Error at /data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:571 (__project): The CMAKE_ASM_COMPILER: xtensa-esp32-elf-gcc is not a full path and was not found in the PATH. Tell CMake where to find the compiler by setting either the environment variable "ASM" or the CMake cache entry CMAKE_ASM_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH. Call Stack (most recent call first): CMakeLists.txt:3 (project) ========================== [FAILED] Took 5.99 seconds ========================== ``` ### Additional information INFO ESPHome 2025.8.0 INFO Reading configuration /config/esphome/esp32-bluetooth-proxy-088e90.yaml... INFO Starting log output from 192.168.8.19 using esphome API INFO Successfully resolved esp32-bluetooth-proxy-088e90 @ 192.168.8.19 in 0.000s INFO Successfully connected to esp32-bluetooth-proxy-088e90 @ 192.168.8.19 in 0.005s INFO Successful handshake with esp32-bluetooth-proxy-088e90 @ 192.168.8.19 in 0.072s [17:35:45][I][app:149]: ESPHome version 2025.7.5 compiled on Aug 6 2025, 08:44:17 [17:35:45][C][wifi:613]: WiFi: [17:35:45][C][wifi:434]: Local MAC: F4:65:0B:08:8E:90 [17:35:45][C][wifi:439]: SSID: [redacted] [17:35:45][C][wifi:442]: IP Address: 192.168.8.19 [17:35:45][C][wifi:446]: BSSID: [redacted] [17:35:45][C][wifi:446]: Hostname: 'esp32-bluetooth-proxy-088e90' [17:35:45][C][wifi:446]: Signal strength: -53 dB ▂▄▆█ [17:35:45][C][wifi:455]: Channel: 11 [17:35:45][C][wifi:455]: Subnet: 255.255.255.0 [17:35:45][C][wifi:455]: Gateway: 192.168.8.1 [17:35:45][C][wifi:455]: DNS1: 45.90.28.130 [17:35:45][C][wifi:455]: DNS2: 45.90.30.130 [17:35:45][C][logger:246]: Logger: [17:35:45][C][logger:246]: Max Level: DEBUG [17:35:45][C][logger:246]: Initial Level: DEBUG [17:35:45][C][logger:252]: Log Baud Rate: 115200 [17:35:45][C][logger:252]: Hardware UART: UART0 [17:35:45][C][logger:259]: Task Log Buffer Size: 768 [17:35:45][C][bluetooth_proxy:158]: Bluetooth Proxy: [17:35:45][C][bluetooth_proxy:159]: Active: YES [17:35:45][C][bluetooth_proxy:159]: Connections: 3 [17:35:45][C][bluetooth_proxy:159]: Raw advertisements: YES [17:35:45][C][safe_mode.button:024]: Safe Mode Button 'Safe Mode Boot' [17:35:45][C][safe_mode.button:024]: Icon: 'mdi:restart-alert' [17:35:45][C][factory_reset.button:011]: Factory Reset Button 'Factory reset' [17:35:45][C][factory_reset.button:011]: Icon: 'mdi:restart-alert' [17:35:45][C][esp32_ble:518]: BLE: [17:35:45][C][esp32_ble:518]: MAC address: F4:65:0B:08:8E:92 [17:35:45][C][esp32_ble:518]: IO Capability: none [17:35:45][C][esp32_ble_tracker:763]: BLE Tracker: [17:35:45][C][esp32_ble_tracker:764]: Scan Duration: 300 s [17:35:45][C][esp32_ble_tracker:764]: Scan Interval: 320.0 ms [17:35:45][C][esp32_ble_tracker:764]: Scan Window: 30.0 ms [17:35:45][C][esp32_ble_tracker:764]: Scan Type: ACTIVE [17:35:45][C][esp32_ble_tracker:764]: Continuous Scanning: YES [17:35:45][C][esp32_ble_tracker:780]: Scanner State: RUNNING [17:35:45][C][esp32_ble_tracker:792]: Connecting: 0, discovered: 0, searching: 0, disconnecting: 0 [17:35:45][C][bluetooth_proxy.connection:017]: BLE Connection: [17:35:45][C][esp32_ble_client:063]: Address: [17:35:45][C][esp32_ble_client:063]: Auto-Connect: FALSE [17:35:45][C][esp32_ble_client:100]: State: IDLE [17:35:45][C][bluetooth_proxy.connection:017]: BLE Connection: [17:35:45][C][esp32_ble_client:063]: Address: [17:35:45][C][esp32_ble_client:063]: Auto-Connect: FALSE [17:35:45][C][esp32_ble_client:100]: State: IDLE [17:35:45][C][bluetooth_proxy.connection:017]: BLE Connection: [17:35:45][C][esp32_ble_client:063]: Address: [17:35:45][C][esp32_ble_client:063]: Auto-Connect: FALSE [17:35:45][C][esp32_ble_client:100]: State: IDLE [17:35:45][C][esphome.ota:073]: Over-The-Air updates: [17:35:45][C][esphome.ota:073]: Address: esp32-bluetooth-proxy-088e90.local:3232 [17:35:45][C][esphome.ota:073]: Version: 2 [17:35:45][C][safe_mode:018]: Safe Mode: [17:35:45][C][safe_mode:019]: Boot considered successful after 60 seconds [17:35:45][C][safe_mode:019]: Invoke after 10 boot attempts [17:35:45][C][safe_mode:019]: Remain for 300 seconds [17:35:45][C][api:207]: API Server: [17:35:45][C][api:207]: Address: esp32-bluetooth-proxy-088e90.local:6053 [17:35:45][C][api:212]: Using noise encryption: YES [17:35:45][C][mdns:122]: mDNS: [17:35:45][C][mdns:122]: Hostname: esp32-bluetooth-proxy-088e90

olimexsmart · September 16, 2025, 9:01pm

For me the problem was just using the Git Bash terminal in windows. Exectuing directly the affected Python script gave me this error:

olli@myPS MINGW64 ~/.platformio/packages/tool-esp_install/tools
$ python idf_tools.py
ERROR: MSys/Mingw is not supported. Please follow the getting started guide of the documentation to set up a supported environment

switched to PowerShell and everything went well