Attempting to update with ESPHome 2025.4.1

Smart Home Integrations Home Assistant
1

@nate Getting the following error when attempting recent ESPHome 2025.4.1 update:
Any advice would be greatly appreciated.

Compiling .pioenvs/garage-door-6f65e9/src/esphome/components/mdns/mdns_component.cpp.o
Compiling .pioenvs/garage-door-6f65e9/src/esphome/components/web_server/web_server_v1.cpp.o
Compiling .pioenvs/garage-door-6f65e9/src/esphome/components/web_server_base/web_server_base.cpp.o
Compiling .pioenvs/garage-door-6f65e9/src/esphome/components/wifi/wifi_component.cpp.o
src/esphome/components/mdns/mdns_component.cpp: In member function ‘void esphome::mdns::MDNSComponent::compile_records_()’:
src/esphome/components/mdns/mdns_component.cpp:65:50: error: ‘using element_type = class esphome::api::APINoiseContext’ {aka ‘class esphome::api::APINoiseContext’} has no member named ‘has_psk’
65 | if (api::global_api_server->get_noise_ctx()->has_psk()) {
| ^~~~~~~
*** [.pioenvs/garage-door-6f65e9/src/esphome/components/mdns/mdns_component.cpp.o] Error 1
========================== [FAILED] Took 9.59 seconds ==========================

Screenshot from 2025-04-30 17-13-40
Screenshot from 2025-04-30 17-13-401235×458 67.1 KB

1 Like
2

See: 2025.4.0 Error: mdns_component.cpp.o] Error 1; {aka 'class esphome::api::APINoiseContext'} has no member named 'has_psk' · Issue #80 · konnected-io/konnected-esphome · GitHub

Long story short, some updates to MDNS component that I made are conflicting with some other unrelated updates added around the same time. All will be resolved in the next ESPHome release, so the simple thing to do is just wait a couple weeks for ESPHome 2025.5.

1 Like
3

@nate Thank you for your quick response. Will await an update, no worries.

1 Like
4

Thank you. I will hang tight as well.

I haven’t been able to update my Alarm Pro beyond 2025.4.0 and my GDOBlaq devices beyond 2025.3.0.

5

I’m running into update problems here as well but I’m not sure it’s the same issue. I’m trying to update the ESPHome (2025.4.0) with FW to 1.2.1.4. Update fails. Fast flashing blue LED. Have to manually re-flash from PC to restart. Same issue?

6

@Ron_Smith Not the same issue. The OP issue is a firmware compilation issue. Sounds like you have compiled and flashed an updated firmware, but something is not working right.

The most common cause of the rapid blue blinking LED is choosing the wrong Ethernet adapter type for your hardware. Make sure you check the hardware version number (printed on the front of the board) and select the correct Ethernet adapter in the firmware settings on the Network > Ethernet screen.

7

Thanks Nate. I was wondering about this. The Pro is Enet v1.6. I have selected that version for FW. The FW loads OK. However, then I go to the Alarm Panel Pro Setting page, it says ethernet V1.8 and newer. The page also says Firmware Update is Ready and if I hit that button, it hangs. Please advise.

8

That’s your problem. The Ethernet setting for v1.8 and newer won’t work on a v1.6 board. Select the other option for v1.7 and older.

9

Nate, I hate taking up your time with this one. Sorry. I have attempted the FW reload about 6 or 7 times now and have been very very very careful to select the correct version for Ethernet v1.6. It keeps loading the wrong version. Please advise.

10

I opened a support ticket on this one since it’s not related to the original community post.

11

2025.4.2 is out now and we still cant update.

12

@greg9 The code that fixes it will be in 2025.5

1 Like