ESPHome 2026.5.1 released on 24-05-2026
ESPHome 2026.5.1 is out now. It delivers a clutch of ESP-IDF and toolchain fixes plus runtime and peripheral stability improvements for ESP32 and ESP8266, aimed at reducing noisy build output and improving hardware compatibility.
See the ESPHome GitHub release notes or the project pages for the full changelog and details of each fix.
What’s in this release
- ESP-IDF and toolchain fixes: suppress noisy “git rev-parse” errors when .git is stripped; fix tarfile extraction crashing on Python 3.11; write version.txt after extraction so the bootloader shows the real version; backport a ninja linux-arm64 entry for aarch64 hosts; default to remote HEAD when cg.add_library URL lacks a #ref; honour dict shorthand for library.json dependencies; and change IDF warnings handling (demote/deactivate -Werror behaviour and replace per-class demotes with a blanket -Wno-error).
- ESP32 / ESP8266 runtime and peripheral fixes: defer wrapping of esp_panic_handler to avoid affecting the arduino-esp32 IDF component; demote IDF #warning deprecations under the ESP-IDF toolchain; use an os_timer-based esp_delay() on ESP8266; wake the main loop on ESP8266 software-serial RX; assert NSS before wait_busy on sx126x so commands wake the chip from sleep; fix LN882H IRAM_ATTR injection point for libretiny; and restore a null guard for the tuya status_pin.
- Core, API, dashboard and config workflow stability and dependency bumps: persist and restore CORE.toolchain via StorageJSON; refresh the compiled-config cache after upload/logs fallback; break an include cycle between api_connection and api_server; a dashboard test fix for Windows CI; and dependency bumps (zeroconf updated through 0.149.16 and sendspin-cpp to v0.6.1).
Upgrade notes
- Build behaviour for ESP-IDF warnings has changed: -Werror handling has been demoted and replaced with a blanket -Wno-error. If your builds depend on warnings being treated as errors, review your toolchain flags or pin a specific ESP-IDF/toolchain version before upgrading.
- If you need to revert, roll back to the previous release tag on the project’s GitHub repository.
Please share comments on your experience with 2026.5.1 on the project’s GitHub issues or discussion pages.
