Add Grid status sensor to Tesla Fleet

[Bre77]

Proposed change

Add Grid status sensor to Tesla Fleet

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).
  • I've opened up a PR to add logos and icons in Brands repository.
• 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: Add Tesla Fleet grid status core#126438
• 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

• New Features
  • Introduced a new sensor entity, "Grid status," to the Tesla Fleet integration documentation, indicating its availability.

[coderabbitai]

Walkthrough

Walkthrough

The pull request introduces a new sensor entity, "Grid status," to the Tesla Fleet integration documentation. This addition clarifies that the "Grid status" sensor is now available, marked with a "Yes" designation for its availability. The existing entities in the documentation remain unchanged, and the new sensor is incorporated into the list of available sensors.

Changes

File	Change Summary
source/_integrations/tesla_fleet.markdown	Added new sensor entity: `

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant TeslaFleetIntegration
    participant Documentation

    User->>TeslaFleetIntegration: Request sensor information
    TeslaFleetIntegration->>Documentation: Retrieve available sensors
    Documentation-->>TeslaFleetIntegration: Return list of sensors including "Grid status"
    TeslaFleetIntegration-->>User: Provide sensor information

Loading

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[netlify]

✅ Deploy Preview for home-assistant-docs ready!

Name	Link
🔨 Latest commit	35c0c73
🔍 Latest deploy log	https://app.netlify.com/sites/home-assistant-docs/deploys/66f353f817796300085271a1
😎 Deploy Preview	https://deploy-preview-34911--home-assistant-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[coderabbitai]

Actionable comments posted: 0

Outside diff range and nitpick comments (1)

source/_integrations/tesla_fleet.markdown (1)

191-191: LGTM! Consider adding a brief description.

The addition of the "Grid status" sensor to the Energy sites section is appropriate and follows the existing format. It's a relevant addition that aligns with the PR objectives.

Consider adding a brief description of what the "Grid status" sensor represents, either in this table or in a separate section, to provide users with more context about its functionality and importance.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 0e8e10f and 35c0c73.

Files selected for processing (1)

• source/_integrations/tesla_fleet.markdown (1 hunks)

[c0ffeeca7]

Thank you, @Bre77 👍