Unusable custom firmware with latest ESPHome version (2025.7.3)

[amarok45]

I'm running Home Assistant, which proposed to update ESPHome to 2025.7.3 but this version is no longer compatible with ESP-IDF 4.4.8 (it uses instead 5.3.2) which prevents your firmware from being installed on my ESP32-S3-Box-3.

Is there a way to make it work? Do I have to modify some data in the yaml file?

Thank you for your answer.

[BigBobbas]

can you try one of the versions in the dev branch. Either s3b.yaml if you have sensor dock etc or s3b_n0_sensors.yaml if you don't.

thanks
Rob

[amarok45]

Thank you for your quick answer.

In the s3b.yaml file of the dev branch, in line 169, there is a parameter "wifi_qr". I don't know what value to write? Can you explain? Thank you

[BigBobbas]

you can add the following to your secrets.yaml file

wifi_qr: "WIFI:T:WPA;S:YOUR_SSID;P:YOUR_PASSWORD;;"

change YOUR_SSID and YOUR_PASSWORD - to whatever credentials you want the QR code to connect to. The QR code is displayed on the screen when the 'wifi' icon is tapped on the home screen

[amarok45]

Thank you again.

Now, when trying to install the configuration, compiling fails and I get this error message:

xtensa-esp-elf-g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
*** [.pioenvs/esp32-s3box-3/src/main.cpp.o] Error 1

Sorry for so many problems, but whereas my device worked fine before upgrading HA, now it's a nightmare...

Best regards

[BigBobbas]

this will because the machine you are compiling on is low in ram.

[FirstRulez]

Thank you again.

Now, when trying to install the configuration, compiling fails and I get this error message:

xtensa-esp-elf-g++: fatal error: Killed signal terminated program cc1plus compilation terminated. *** [.pioenvs/esp32-s3box-3/src/main.cpp.o] Error 1

Sorry for so many problems, but whereas my device worked fine before upgrading HA, now it's a nightmare...

Best regards

I also had this issue building many esphome devices, and found that sometimes if you restart esphome add-on just before doing the compile it will work (assuming you are not able to make more RAM available to the build machine. I thankfully upgraded recently so resolved by allocating more ram to my virtual HASS machine.

[amarok45]

Thank you for your help, now it works like a charm (I had to increase the allocated RAM for my virtual machine to 8 GB).

Best regards, thank you for your work!

[JyskMakerDK]

Hey
Get this when i try to compile the s3b.yaml from the dev sectien.

Dependency Graph
|-- qr-code-generator-library @ 1.7.0
|-- ESPMicroSpeechFeatures @ 1.1.0
|-- esp-audio-libs @ 1.1.4
Compiling .pioenvs/esp32-s3box-3/src/main.cpp.o
In file included from src/esphome/components/adc/adc_sensor.h:9,
                 from src/esphome.h:3,
                 from src/main.cpp:3:
/data/cache/platformio/packages/framework-espidf/components/esp_adc/deprecated/include/esp_adc_cal.h:17:2: warning: #warning "legacy adc calibration driver is deprecated, please migrate to use esp_adc/adc_cali.h and esp_adc/adc_cali_scheme.h" [-Wcpp]
   17 | #warning "legacy adc calibration driver is deprecated, please migrate to use esp_adc/adc_cali.h and esp_adc/adc_cali_scheme.h"
      |  ^~~~~~~
In file included from src/esphome/components/adc/adc_sensor.h:10:
/data/cache/platformio/packages/framework-espidf/components/driver/deprecated/driver/adc.h:19:2: warning: #warning "legacy adc driver is deprecated, please migrate to use esp_adc/adc_oneshot.h and esp_adc/adc_continuous.h for oneshot mode and continuous mode drivers respectively" [-Wcpp]
   19 | #warning "legacy adc driver is deprecated, please migrate to use esp_adc/adc_oneshot.h and esp_adc/adc_continuous.h for oneshot mode and continuous mode drivers respectively"
      |  ^~~~~~~

And after it uploads, and se the log wireless. is says this in the start..

INFO ESPHome 2025.7.4
INFO Reading configuration /config/esphome/esp32-s3-box-3-52c12c.yaml...
INFO Updating https://github.com/esphome/esphome.git@pull/9100/head
INFO Detected timezone 'Europe/Copenhagen'
WARNING The 'publish_initial_state' option has been replaced by 'trigger_on_initial_state' and will be removed in a future release
INFO Starting log output from 192.168.1.132 using esphome API
INFO Successfully resolved esp32-s3box-3 @ 192.168.1.132 in 0.000s
INFO Successfully connected to esp32-s3box-3 @ 192.168.1.132 in 0.058s
INFO Successful handshake with esp32-s3box-3 @ 192.168.1.132 in 0.096s

[BigBobbas]

@JyskMakerDK they are warnings and nothing to be concerned about. These will be fixed at some point in the future but currently do not cause any issues.