Upgrade to esphome 2026.7.0 (+ component fixes)#29
Merged
Conversation
2026.7.0 removed network::get_use_address() (→ get_use_address_to) and a select's public .state (→ current_option()), breaking three devices. Fixes: - hot-tub: point iq2020 at a temporary fork with the get_use_address_to fix (jbunting/ESP-IQ2020@e9c441f) until upstream PR Ylianst/ESP-IQ2020#111 lands. - zigbee: bump tube0013/esphome-components 85dda63 → 9c64319 (upstream fix for stream_server), and switch the vendored MGM24 baud lambdas from select .state → .current_option(). - zwave: migrate to TubesZB's native `zwave_proxy` config (vendored) — drops the external oxan stream_server entirely. NOTE: Z-Wave now integrates via HA's ESPHome/Z-Wave path, not the old tcp://:6638 stream_server socket. - requirements.txt: esphome 2026.6.4 → 2026.7.0. All five devices verified compiling on 2026.7.0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Supersedes Renovate's raw bump (#25), which alone breaks three devices. 2026.7.0 removed two APIs used by our external components:
network::get_use_address()→get_use_address_to(buf).state→current_option()Fixes
get_use_address(). Repointed to a temporary fork with the fix (jbunting/ESP-IQ2020@e9c441f) until upstream lands: Fix build on esphome 2026.7.0 (get_use_address removed) Ylianst/ESP-IQ2020#111.tube0013/esphome-components85dda63 → 9c64319(upstream fixed stream_server), and updated the vendored MGM24 baud lambdasselect .state → .current_option().zwave_proxyconfig (vendoreddevices/vendor/tubeszb-zw.yaml), dropping the external oxan stream_server entirely.2026.6.4 → 2026.7.0.zwave now uses ESPHome's native
zwave_proxyinstead of the oldstream_server(rawtcp://:6638). Z-Wave JS must be reconfigured in HA to use the ESPHome Z-Wave proxy instead of the TCP socket.Verified
All five devices compile locally on esphome 2026.7.0 (hot-tub, zwave, zigbee, plus bluetooth-proxy & garage-door). CI
validate-deviceswill re-confirm.Follow-ups
🤖 Generated with Claude Code