Add ESPHome Version sensor

[edwardtfn]

And renames the TX Firmware, which resolves #66

Summary by CodeRabbit

• New Features

  • Introduced a new text sensor to display the ESPHome version.

• Improvements

  • Updated the name of the existing firmware version sensor for clarity.

[coderabbitai]

Walkthrough

The pull request modifies the ESPHome/TX-Ultimate-Easy-ESPHome_core.yaml configuration file by introducing a new text sensor esphome_fw_version to display the ESPHome firmware version. Simultaneously, the existing tx_fw_version text sensor has been renamed from "Firmware version" to "TX Ultimate Easy Firmware Version". These changes aim to provide more detailed firmware version information within the ESPHome configuration.

Changes

File	Change Summary
ESPHome/TX-Ultimate-Easy-ESPHome_core.yaml	- Added new text sensor esphome_fw_version with platform version and name "ESPHome Version" - Renamed tx_fw_version sensor name to "TX Ultimate Easy Firmware Version"

Assessment against linked issues

Objective	Addressed	Explanation
Firmware check availability [#66]	✅

Possibly related PRs

• Testing new versioning #40: Modifies the same configuration file with focus on version management.
• Fix relay on display as light mode #55: Affects related ESPHome configuration file structure.
• Fix relay toggle when button action is set to none #60: Modifies relay control logic in similar configuration file.
• New LED mapping for US 3&4-Gang #68: Updates LED-related configuration file.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 695cca0 and 37b2e93.

📒 Files selected for processing (1)

• ESPHome/TX-Ultimate-Easy-ESPHome_core.yaml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• ESPHome/TX-Ultimate-Easy-ESPHome_core.yaml

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

ESPHome/TX-Ultimate-Easy-ESPHome_core.yaml (1)

170-173: Consider adding entity category for consistency.

For consistency with the tx_fw_version sensor, consider adding the entity_category: diagnostic attribute to the ESPHome version sensor as well, since both are diagnostic version information.

  - id: esphome_fw_version
    platform: version
    name: "ESPHome Version"
+   entity_category: diagnostic

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f258b8f and 695cca0.

📒 Files selected for processing (1)

• ESPHome/TX-Ultimate-Easy-ESPHome_core.yaml (1 hunks)

🔇 Additional comments (2)

ESPHome/TX-Ultimate-Easy-ESPHome_core.yaml (2)

170-173: LGTM! Well-implemented ESPHome version sensor.

The implementation correctly uses the built-in version platform to expose the ESPHome version information. The naming is clear and follows good practices.

---

175-175: LGTM! Clear and descriptive firmware version naming.

The rename from "Firmware version" to "TX Ultimate Easy Firmware Version" improves clarity by explicitly distinguishing it from the ESPHome version. This change aligns well with issue #66.