ESPHome latest update seems to break update to devices

ESPHome
1

Compiling .pioenvs/konnected-870515/src/esphome/components/mdns/mdns_component.cpp.o
Compiling .pioenvs/konnected-870515/src/esphome/components/sensor/filter.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()) {
| ^~~~~~~
Compiling .pioenvs/konnected-870515/src/esphome/components/sensor/sensor.cpp.o
*** [.pioenvs/konnected-870515/src/esphome/components/mdns/mdns_component.cpp.o] Error 1
========================== [FAILED] Took 7.57 seconds ==========================
====== [ERROR] /config/esphome/konnected-870515.yaml ======

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/konnected-9baeac/src/esphome/components/mdns/mdns_component.cpp.o] Error 1
========================== [FAILED] Took 5.75 seconds ==========================
====== [ERROR] /config/esphome/konnected-9baeac.yaml ======

======================== [SUMMARY] ========================

  • /config/esphome/konnected-870515.yaml: FAILED
  • /config/esphome/konnected-9baeac.yaml: FAILED
2

Apparently this is a known bug in ESPHome. There is a GitHub ticket about it in Konnected’s GitHub. Here is the comment from the ticket:

I see. I was able to reproduce the error, which only shows up if API encryption is enabled.

The problem is that that particular line of code that’s erroring is dependent on other changes in esphome/esphome#7296 which has been approved and merged but not released yet. Presumably this change will be included in ESPHome 2025.5.x.

My recommendation is to just wait until ESPHome 2025.5.x is released, and then this error should go away. There’s nothing groundbreaking in this firmware update that needs to be immediately updated.

5 Likes
3

Thank you for spotting that.

4

Still an issue in ESPHome 2025.5.2

5

Latest release is 2025.4.2
If I recall correctly, release of .0 is always on the 3rd Wednesday

6

You are of course correct, glasses incoming! :slight_smile: