Skip to content
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

Add ld2454 #4606

Closed
wants to merge 3 commits into from
Closed

Add ld2454 #4606

wants to merge 3 commits into from

Conversation

rickbronson
Copy link

Description:

Add documentation for the HILINK LD2454 vehicle speed detector radar,
the code for this will follow soon.
Related issue (if applicable): fixes

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

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.

Copy link
Contributor

coderabbitai bot commented Jan 24, 2025

Walkthrough

This pull request introduces comprehensive documentation for the LD2454 sensor component in ESPHome. The documentation covers the sensor's capabilities, including vehicle and pedestrian detection up to 100 meters, Bluetooth connectivity, and UART configuration. It provides detailed YAML configuration examples for various components such as sensor, switch, number, button, text sensor, and select. The documentation also includes an automation section for setting Bluetooth passwords and integrating with Home Assistant.

Changes

File Change Summary
components/sensor/ld2454.rst Added comprehensive documentation for LD2454 sensor, including configuration variables, component settings, and integration examples
index.rst Added LD2454 sensor entries in "Motion" and "Presence Detection" sections with brief descriptions

Possibly related PRs

Suggested reviewers

  • nagyrobi
  • jesserockz

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 5

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 92bfa9d and 1ad8473.

⛔ Files ignored due to path filters (1)
  • images/ld2454.png is excluded by !**/*.png
📒 Files selected for processing (2)
  • components/sensor/ld2454.rst (1 hunks)
  • index.rst (2 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
index.rst (1)

Pattern **: - Do not generate or add any sequence diagrams

components/sensor/ld2454.rst (1)

Pattern **: - Do not generate or add any sequence diagrams

🪛 GitHub Actions: Lint
components/sensor/ld2454.rst

[error] 17-17: Image file 'components/sensor/images/ld2454.png' is not readable

🔇 Additional comments (2)
components/sensor/ld2454.rst (1)

247-247: Verify source of inspiration reference.

The source of inspiration links to the LD2410 implementation. Please verify if this is intentional or if it should reference an LD2454-specific implementation.

index.rst (1)

606-606: LGTM!

The LD2454 entries are correctly added to both the Motion and Presence Detection sections, following the existing format and accurately reflecting the component's capabilities.

Also applies to: 710-710

Comment on lines +13 to +17
.. figure:: images/ld2454.png
:align: center
:width: 50.0%

LD2454 vehicle speed and presence sensor
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Add the missing image file.

The pipeline is failing because the image file components/sensor/images/ld2454.png is missing. Please add the image file to the correct location.

🧰 Tools
🪛 GitHub Actions: Lint

[error] 17-17: Image file 'components/sensor/images/ld2454.png' is not readable

Comment on lines +70 to +71
- **target_snr** (*Optional*, int): Target signal to noise ration.
Value between ``0`` and ``255`` inclusive.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix typo in SNR description.

There's a typo in "ration" - it should be "ratio".

-- **target_snr** (*Optional*, int): Target signal to noise ration.
++ **target_snr** (*Optional*, int): Target signal to noise ratio.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- **target_snr** (*Optional*, int): Target signal to noise ration.
Value between ``0`` and ``255`` inclusive.
- **target_snr** (*Optional*, int): Target signal to noise ratio.
Value between ``0`` and ``255`` inclusive.

target_speed:
name: "Speed (km/h)"
target_snr:
name: "Speed (km/h)"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix copy-paste error in sensor name.

The name for target_snr is incorrectly showing "Speed (km/h)" which appears to be copied from the target_speed sensor above.

-          name: "Speed (km/h)"
+          name: "Signal to Noise Ratio"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
name: "Speed (km/h)"
name: "Signal to Noise Ratio"

Comment on lines +123 to +135
All options from :ref:`Sensor <config-sensor>`.
- **snr_threshold_level** (*Optional*, int): The larger the value, the lower the sensitivity and the more difficult it is to detect the target.
Value between ``3`` and ``8`` inclusive.
All options from :ref:`Sensor <config-sensor>`.
- **max_detect_distance** (*Optional*, int): Maximum detection distance (meters)
Value between ``10`` and ``255`` inclusive.
All options from :ref:`Sensor <config-sensor>`.
- **min_speed** (*Optional*, int): Minimum movement speed (km/h)
Value between ``0`` and ``120`` inclusive.
All options from :ref:`Sensor <config-sensor>`.
- **no_target_timeout** (*Optional*, int): No target delay time setting (seconds). If target is detected, it will delay notification (retriggerable).
Value between ``0`` and ``255`` inclusive.
All options from :ref:`Sensor <config-sensor>`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix incorrect configuration references.

The configuration options are referencing "Sensor" configuration instead of "Number" configuration in multiple places.

-  All options from :ref:`Sensor <config-sensor>`.
+  All options from :ref:`Number <config-number>`.

This change needs to be applied to all configuration variables in the Number section (effective_trigger_time, snr_threshold_level, max_detect_distance, min_speed, no_target_timeout).

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
All options from :ref:`Sensor <config-sensor>`.
- **snr_threshold_level** (*Optional*, int): The larger the value, the lower the sensitivity and the more difficult it is to detect the target.
Value between ``3`` and ``8`` inclusive.
All options from :ref:`Sensor <config-sensor>`.
- **max_detect_distance** (*Optional*, int): Maximum detection distance (meters)
Value between ``10`` and ``255`` inclusive.
All options from :ref:`Sensor <config-sensor>`.
- **min_speed** (*Optional*, int): Minimum movement speed (km/h)
Value between ``0`` and ``120`` inclusive.
All options from :ref:`Sensor <config-sensor>`.
- **no_target_timeout** (*Optional*, int): No target delay time setting (seconds). If target is detected, it will delay notification (retriggerable).
Value between ``0`` and ``255`` inclusive.
All options from :ref:`Sensor <config-sensor>`.
All options from :ref:`Number <config-number>`.
- **snr_threshold_level** (*Optional*, int): The larger the value, the lower the sensitivity and the more difficult it is to detect the target.
Value between ``3`` and ``8`` inclusive.
All options from :ref:`Number <config-number>`.
- **max_detect_distance** (*Optional*, int): Maximum detection distance (meters)
Value between ``10`` and ``255`` inclusive.
All options from :ref:`Number <config-number>`.
- **min_speed** (*Optional*, int): Minimum movement speed (km/h)
Value between ``0`` and ``120`` inclusive.
All options from :ref:`Number <config-number>`.
- **no_target_timeout** (*Optional*, int): No target delay time setting (seconds). If target is detected, it will delay notification (retriggerable).
Value between ``0`` and ``255`` inclusive.
All options from :ref:`Number <config-number>`.


- **move_direction** (*Optional*, int): Movement direction setting (0: Only detect away, 1: Only detect approach, 2: All detected)
Value between ``0`` and ``2`` inclusive.
All options from :ref:`Sensor <config-sensor>`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix incorrect configuration reference.

The configuration option is referencing "Sensor" configuration instead of "Select" configuration.

-  All options from :ref:`Sensor <config-sensor>`.
+  All options from :ref:`Select <config-select>`.

Committable suggestion skipped: line range outside the PR's diff.

Copy link

netlify bot commented Jan 24, 2025

Deploy Preview for esphome ready!

Name Link
🔨 Latest commit c231278
🔍 Latest deploy log https://app.netlify.com/sites/esphome/deploys/6793c8f072044900089cd140
😎 Deploy Preview https://deploy-preview-4606--esphome.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.

@github-actions github-actions bot locked and limited conversation to collaborators Jan 26, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant