Fix ESPHome dev build: use on_value trigger variable instead of Select .state

[TrevorSchirmer]

Version: 26.7.7.1

What does this implement/fix?

Fixes the CI dev-channel build failure:

'class esphome::template_::TemplateSelect<...>' has no member named 'state'

ESPHome removed the deprecated std::string state member from select entities on the dev branch (deprecated in 2026.1.0, removed for 2026.7.0). The on_value condition lambdas of the firmware_selector select in TEMP_PRO-1_W.yaml and TEMP_PRO-1_ETH.yaml read id(firmware_selector).state, which no longer compiles against dev.

Since these lambdas run inside the select's own on_value trigger, the newly selected option is already available as the trigger variable x. Comparing x == "Ethernet" works on every ESPHome version back to this config's min_version: 2025.2.0 (x is std::string on older releases and StringRef on dev — both compare against string literals), so stable, beta, and dev all compile without raising the minimum version. Runtime behavior is unchanged.

Also bumps the firmware version to 26.7.7.1 per convention.

Types of changes

• Bugfix (fixed change that fixes an issue)
• New feature (thanks!)
• Breaking change (repair/feature that breaks existing functionality)
• Dependency Update - Does not publish
• Other - Does not publish
• Website of github readme file update - Does not publish
• Github workflows - Does not publish

Checklist / Checklijst:

• The code change has been tested and works locally
• The code change has not yet been tested

If user-visible functionality or configuration variables are added/modified:

• Added/updated documentation for the web page

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@TrevorSchirmer, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 04bbffb6-0178-4780-b854-b699b34c874d

📥 Commits

Reviewing files that changed from the base of the PR and between 7b6df83 and 4d4aee0.

📒 Files selected for processing (3)

• Integrations/ESPHome/Core.yaml
• Integrations/ESPHome/TEMP_PRO-1_ETH.yaml
• Integrations/ESPHome/TEMP_PRO-1_W.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/select-state-dev-compat

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}