Skip to content

Add supported functionality to ESPHome #38614

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Apr 18, 2025
Merged

Add supported functionality to ESPHome #38614

merged 4 commits into from
Apr 18, 2025

Conversation

bdraco
Copy link
Member

@bdraco bdraco commented Apr 18, 2025

Proposed change

Add supported functionality to ESPHome
Required as part of docs-supported-functions for Gold

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

  • Link to parent pull request in the codebase:
  • Link to parent pull request in the Brands repository:
  • This PR fixes or closes issue: fixes #

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

Summary by CodeRabbit

  • Documentation
    • Expanded and restructured the ESPHome integration documentation for improved clarity.
    • Added detailed descriptions of supported functionality, including entity types, event firing, Home Assistant Actions, entity state retrieval, and tag scanning support.
    • Clarified options for enabling device capabilities via the options flow.

Required as part of `docs-supported-functions` for Gold
@home-assistant home-assistant bot added the current This PR goes into the current branch label Apr 18, 2025
Copy link
Contributor

coderabbitai bot commented Apr 18, 2025

📝 Walkthrough

Walkthrough

The ESPHome integration documentation was expanded and restructured to provide a more detailed and organized overview of its supported functionality. The previous brief mention of Home Assistant actions was replaced with a comprehensive "Supported Functionality" section, which now includes detailed descriptions of entity exposure, event firing, action definitions, entity state retrieval, and tag scanning. The documentation also clarifies the capability for ESPHome devices to call any Home Assistant Action, noting its default disabled status and per-device enablement. The options flow include directive was repositioned for improved clarity.

Changes

File(s) Change Summary
source/_integrations/esphome.markdown Expanded and restructured documentation: replaced brief actions mention with detailed "Supported Functionality" section, added subsections on entity exposure, event firing, action definitions, entity state retrieval, tag scanning, and clarified action-calling capability; repositioned options flow include directive.

Sequence Diagram(s)

sequenceDiagram
    participant ESPHome Device
    participant Home Assistant

    ESPHome Device->>Home Assistant: Expose entities via Native API
    ESPHome Device->>Home Assistant: Fire events on event bus
    Home Assistant->>ESPHome Device: Define actions based on device config
    ESPHome Device->>Home Assistant: Retrieve entity states via user-defined actions
    ESPHome Device->>Home Assistant: (Optional) Call any Home Assistant Action (if enabled)
    ESPHome Device->>Home Assistant: Send tag scanning events
Loading

📜 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 576bd7e and 94ac7be.

📒 Files selected for processing (1)
  • source/_integrations/esphome.markdown (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • source/_integrations/esphome.markdown

🪧 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.
  • @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 or @coderabbitai title 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.

Copy link

netlify bot commented Apr 18, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 94ac7be
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/68020cbcae3fd50008921806
😎 Deploy Preview https://deploy-preview-38614--home-assistant-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

jesserockz
jesserockz previously approved these changes Apr 18, 2025
@bdraco
Copy link
Member Author

bdraco commented Apr 18, 2025

thanks

@bdraco bdraco merged commit 839e28e into current Apr 18, 2025
9 checks passed
@bdraco bdraco deleted the bdraco-patch-12 branch April 18, 2025 08:30
@github-actions github-actions bot locked and limited conversation to collaborators Apr 19, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
current This PR goes into the current branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants