Adding HLK-LD2415H Documentation

[cptskippy]

Description:

Adding documentation for the Hi-Link HLK-LD2415H speed sensor.

Related issue (if applicable): n/a

Pull request in esphome with YAML changes (if applicable): esphome/esphome#6813

Checklist:

• I am merging into next because this is new documentation that has a matching pull-request in esphome as linked above.
  or

• I am merging into current because this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.

• Link added in /index.rst when creating new documents for new components or cookbook.

Summary by CodeRabbit

• Documentation
  • Added setup instructions for the LD2415H 24Ghz mmWave Radar Sensor with ESPHome.
  • Included configuration examples and detailed sensor usage information.

[netlify]

✅ Deploy Preview for esphome ready!

Name	Link
🔨 Latest commit	c112034
🔍 Latest deploy log	https://app.netlify.com/sites/esphome/deploys/6737a4af85d7f8000836269a
😎 Deploy Preview	https://deploy-preview-3874--esphome.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

The new ld2415h.rst file introduces comprehensive instructions for integrating the LD2415H 24Ghz mmWave Radar Sensor with ESPHome. It details the setup process, configuration options, and usage examples, enabling users to track object velocity effectively. No changes were made to any exported or public entities.

Changes

File	Change Summary
components/sensor/ld2415h.rst	Added instructions for setting up and configuring the LD2415H 24Ghz mmWave Radar Sensor with ESPHome.

In fields where waves and sensors meet,
The LD2415H is quite the feat.
With radar eyes, it tracks the flow,
Of objects moving to and fro.
ESPHome now speaks its tongue,
A new chapter has begun.
🎉🚀

---

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

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between bc91bdd and d8d03b3.

Files ignored due to path filters (5)

• components/sensor/images/ld2415h.back.png is excluded by !**/*.png
• components/sensor/images/ld2415h.configuration.ui.png is excluded by !**/*.png
• components/sensor/images/ld2415h.front.png is excluded by !**/*.png
• components/sensor/images/ld2415h.sensor.ui.png is excluded by !**/*.png
• images/ld2415h.png is excluded by !**/*.png

Files selected for processing (1)

• components/sensor/ld2415h.rst (1 hunks)

Files skipped from review due to trivial changes (1)

• components/sensor/ld2415h.rst

[cptskippy]

@jesserockz I've changed the base branch to "next", my apologies for messing that up.