Sounds like a plan. Feel free to get back once the issue is fixed.
I’m seeing issues with mDNS on rp2040s. I haven’t been able to pull any relevant logs however about half my devices are no longer registering .local addresses anymore (checked using avahi browser). The units report into HA but the builder shows them as offline and without an address can’t update them.
edit 2: This seems more like a general network stability issue with pico. Sending data to HA seems fine but firmware updates, mdns, etc seem to be hit or miss. I only have one esp32 device but it doesn’t seem to be affected after the update.
edit - not sure if this might be related.
Compiling .pioenvs/pico-display/src/esphome/components/mdns/mdns_rp2040.cpp.o
In file included from /data/cache/platformio/packages/framework-arduinopico/libraries/LEAmDNS/src/LEAmDNS.h:120,
from /data/cache/platformio/packages/framework-arduinopico/libraries/LEAmDNS/src/ESP8266mDNS.h:47,
from src/esphome/components/mdns/mdns_rp2040.cpp:10:
/data/cache/platformio/packages/framework-arduinopico/cores/rp2040/PolledTimeout.h:27: warning: "IRAM_ATTR" redefined
27 | #define IRAM_ATTR
|
In file included from src/esphome/core/application.h:9,
from src/esphome/components/mdns/mdns_rp2040.cpp:6:
src/esphome/core/hal.h:29: note: this is the location of the previous definition
29 | #define IRAM_ATTR __attribute__((noinline, long_call, section(".time_critical")))
|
3 Likes
@Duckshousemacservice There is a clean all option in the very top right menu of the ESPHome Builder. Try that
That worked! thanks jesse
Same issue here, 3 devices total and 2 give a compile error. Clean didn’t help. The two devices are both a co2 sensor (scd30). You have a link to the issue on github.com?
Found something: esphome 2025.11.0 and CO2 sensor SCD30 compilation error · Issue #12028 · esphome/esphome · GitHub
Lots of errors trying to update a Mitsubishi heatpump. I found a page on changes related to Mitsubishi climate so I will try to figure out what needs to be updated in my YAML. If anyone else using Mitsubishi climate has already figured this out please let me know 
I’m seeing the exact same issue here. All my Picos go offline like you describe it within a minute after being powered up or reset. None of my ESP-based devices exhibit this behaviour, and there is nothing in my wifi config that differs between the ESP:s and the Picos. They all worked before the update.
1 Like
I had a lot of esp devices go offline. What I had to do in install them again one by one plugging them directly into my NUC running home assistant. I then used the installed method Plug into the computer running ESPHome Device Builder. Once I did that I could move them back into their place and then I can once again update wirelessy. 
PS: Clean build wirelessy did not work. Had to plug them in directly. Some were okay and some were not.
Blacky 
1 Like
Please keep us posted on this “going off line” issue. I’m especially curious whether this means totally not available on the network, or just from the builder add-on? Can you connect directly to the IP address? Is it randomly assigned by DHCP or reserved/static?
I’d like to know what to watch/test for when I start updating devices to this version.
I’m getting tearing of lvgl objects since the update on my waveshare esp32-s3-touch-lcd-7B. Every few seconds there will be a flicker of tearing in one object on the screen. I’m using this driver and this yaml for setting up the screen. I’ve reverted to esphome 2025.10.5 and the tearing goes away. Any help getting the new esphome version to work would be helpful.
Like every other esphome version update, it didn’t take long to get some validation and compile errors. In my case the esp32 cameras I’ve been using for years now won’t even validate.
In some other post it was suggested to add the “psram:” which indeed fixed the validation issue and made it compile. Now I’ll have to wait and see if the “test”- camera is working as expected. When it does, I’ve got a dozen or so of them awaiting the same fate.
After the last update, almost none of my ESP devices would compile anymore, and it took me several hours (partly due to introducing secondary errors while making changes) to get everything working again. I think the breaking changes that occur during an update could be communicated better, perhaps summarized in a list.
Sure, with the help of the forum and/or half an hour of searching, you can find the “PSRAM:” solution for ESP-CAMs. But I also had to replace all ESPColor with Color and add “min_auth_mode:”. I already dedicate a fair amount of my free time to Home Assistant and ESP Home. How do people who only rarely check the forum manage it?
You mean something like this?
1 Like
I’ve logged RP2040 mDNS loses IP address, or stops completely · Issue #12060 · esphome/esphome · GitHub with as much information as I can gather at the moment. Its not much to go on i’m afraid.
Thanks, I’ll be keeping an eye on that issue.
I suspect I’ll be OK, since I use static IP addresses (with reservations on the DNS server) for all my ESP devices.
They only update when it’s necessary…
1 Like
Hi All,
Same issue.
I have just added manual IPs to the configs until this is resolved.
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
manual_ip:
static_ip: 192.168.1.xxx
gateway: 192.168.1.1
subnet: 255.255.255.0
That fixes the update issue.
It’s not bad idea even if resolved…
2 Likes
Static IP addresses on your ESP devices… 
I generally prefer to let my router (UniFi Dream Machine) assign static IPs instead of setting them directly on the ESP32 devices.
After updating to 2025.11.0, some of my devices compiled and uploaded fine, but a few got stuck trying to reconnect and stayed offline. The only way I was able to recover them was by plugging each device into my Home Assistant hub and using the “Plug into the computer running ESPHome Device Builder” flashing method.
Once re-flashed that way, I could move them back to their normal location, and wireless updates worked again.
Also, when updating some devices, I had to adjust the code, but the ESPHome logs clearly showed what the issue was and how to fix it.
Blacky
I am also having the issue. It is able to pull sensor data from the Pico, but it shows offline and I can not get to the logs or install a new config without powerfailing it.
1 Like