Add the Apollo Firmware Version entity

[bharvey88]

Version: 26.8.26.1 (unchanged, see below)

What does this implement/fix?

H-3 had no entity reporting which firmware it is running, and its ESPHome Version was disabled_by_default: true so nobody saw that either. CAST-1, AIR-1, MSR-2 and PLT-1 all already carry both.

Adds Apollo Firmware Version and brings ESPHome Version in line with the rest of the fleet:

  - platform: version
    name: "ESPHome Version"
    id: esphome_version
    hide_timestamp: true
    entity_category: "diagnostic"
  - platform: template
    name: "Apollo Firmware Version"
    id: apollo_firmware_version
    update_interval: never
    entity_category: "diagnostic"

Published from on_boot priority 500, the same way CAST-1 does it:

    - priority: 500
      then:
        - text_sensor.template.publish:
            id: apollo_firmware_version
            state: "${version}"

Both live in H-3.yaml rather than Core.yaml, which is where the fleet keeps them. H-3D has no api:, no web_server and logger: baud_rate: 0, so text sensors there have nowhere to surface and would only cost flash. H-3 already kept its ESPHome Version in the variant file for the same reason.

The block comment above the wifi_info group said "Diagnostics, all disabled by default", which stops being true once these two are visible, so it is now scoped to the Wi-Fi sensors it still describes.

No version bump. This rides the bump in the All Lights PR rather than incrementing twice in one day for a product that has not shipped. The two branches touch different parts of H-3.yaml and merge cleanly in either order.

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

esphome config passes on both H-3.yaml and H-3D.yaml, and Apollo Firmware Version renders in the merged H-3 config. Not yet tested on hardware.

🤖 Generated with Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 7ffdedcf-729d-4233-b5e5-e26d2c0aac63

---

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.}