Revert "Added starline run sensor (#35726)"

[Anonym-tsk]

This reverts commit 0244173.

Proposed change

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: Revert "Add starline run sensor (#130444)" core#133566
• 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
  • Updated the description of binary sensors for the starline integration, removing "running state" from the list of available sensors.

[netlify]

✅ Deploy Preview for home-assistant-docs ready!

Name	Link
🔨 Latest commit	e9b7081
🔍 Latest deploy log	https://app.netlify.com/sites/home-assistant-docs/deploys/6764145af4343300088ebba2
😎 Deploy Preview	https://deploy-preview-36432--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]

📝 Walkthrough

Walkthrough

The pull request modifies the documentation for the Starline integration in Home Assistant, specifically updating the description of available binary sensors. The change involves removing the "running state" sensor from the list of binary sensors, resulting in a revised list that includes hand brake, hood, trunk, alarm status, doors lock state, handsfree, neutral, and moving ban status. The overall documentation structure remains unchanged, maintaining the integration's core functionality.

Changes

File	Change Summary
source/_integrations/starline.markdown	Updated binary sensors list by removing "running state" sensor

The changes are purely documentation-related, with no modifications to the actual integration's code or functionality. The documentation now reflects a slightly reduced set of binary sensor options for the Starline integration.

---

📜 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 c96ae08 and e9b7081.

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

source/_integrations/starline.markdown (1)

32-32: LGTM! Verify complete removal of "running state" references

The binary sensors list modification is clean and maintains proper formatting.

Let's verify that all references to "running state" have been properly removed:

✅ Verification successful

Revert of "running state" is complete and consistent

The verification shows that:

1. There are no remaining references to "running state" in the starline integration documentation or code
2. The only starline-related file containing binary sensor information is the documentation file being modified
3. The removal is clean and doesn't affect other integrations that use different running state concepts

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any remaining references to "running state" in the codebase
# that might need to be updated for consistency

# Search for "running state" in documentation and integration code
rg -i "running state" --type yaml --type markdown --type python

Length of output: 96

---

Script:

#!/bin/bash
# Let's try a more comprehensive search without file type restrictions
rg -i "running state"

# Also search for potential variations
rg -i "running.*status"

Length of output: 2959

---

Script:

#!/bin/bash
# Let's check the actual starline integration code to verify the binary sensors
fd starline --type f --exec rg -l "binary_sensor"

# Also check for any references to running in the starline integration
fd starline --type f --exec rg -l "running"

Length of output: 134

---

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.