ESPHome 2025.6 issues with online_image: and system hangs

I have a quite complex in-progress project that is working well on ESPHome 2025.5.2. After upgrade to 2025.6.0 I have had several reliability issues (to the point where I have having problems capturing logs).

Has anyone else who uses online_image:, http_request: etc upgraded to 2025.6? Did you experience any issues?

Two main problems:

  1. online_image: behaviour seems to have changed - I saw there was a couple of updates to code in the changelog but they don’t look that drastic. On_download and on_error don’t look like they act the same anymore, with download retrying immediately after failure rather than running the on_error block and exiting.
  2. Random hangs - I think when trying to connect to the api

I will have to do a usb log capture later if I want to log an issue on Github - meanwhile any others having problems with this release?

Project is back to 2025.5.2 and working fine now.

I can confirm. Since 2026.0 I cannot access the logs of one device I have updated since. The wireless logs stop with:
INFO Successful handshake with ecodan @ 192.168.178.89 in 0.072s

The device properly reports values to Home Assistant.

I’m having similar problems with two of my ESP8266 projects. They’re very software-heavy and have issues with available RAM. With every update, I hope it doesn’t require even more memory and cause my ESP to crash.
Lack of memory manifests itself at my projects in problems with OTA flashing, Wi-Fi connection issues, and an increasing frequency of crashes. In the worst case, the D1 Mini boards won’t let me flash them via OTA at all, and I have to flash an older version via cable. In one case, I’m now considering replacing the ESP8266 with an ESP32.

Yeah I think something in 2025.6 uses significantly more memory that previous versions. I can reproduce the symptoms in earlier versions but only by adding some larger images.

I am getting this on an ESP32 immediately after an update to 2025.6

Mine is an api issue. Data being received in the broswer app.

Update:
I had to add username and password lines to the mqtt:
section of the ESPHome yaml.
Now all is good.