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 ld2450 document #3327

Merged
merged 11 commits into from
Feb 20, 2025
Merged

Add ld2450 document #3327

merged 11 commits into from
Feb 20, 2025

Conversation

hareeshmu
Copy link
Contributor

@hareeshmu hareeshmu commented Nov 4, 2023

Description:

Add ld2450 documentation

Related issue (if applicable): fixes

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

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

netlify bot commented Nov 4, 2023

Deploy Preview for esphome ready!

Name Link
🔨 Latest commit ff5e0ac
🔍 Latest deploy log https://app.netlify.com/sites/esphome/deploys/67b6f19d926fed0008aeff23
😎 Deploy Preview https://deploy-preview-3327--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.

@hareeshmu hareeshmu changed the title Add initial ld2450 document Add ld2450 document Nov 6, 2023
@hareeshmu hareeshmu force-pushed the ld2450 branch 3 times, most recently from f8604a1 to 13f31ab Compare November 14, 2023 04:19
@hareeshmu hareeshmu force-pushed the ld2450 branch 2 times, most recently from 8685970 to 37b651f Compare November 27, 2023 04:17
@hareeshmu hareeshmu force-pushed the ld2450 branch 2 times, most recently from edbee03 to 471eaa6 Compare December 14, 2023 07:17
Copy link

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@github-actions github-actions bot added the stale label Feb 13, 2024
Copy link

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@github-actions github-actions bot added the stale label Apr 14, 2024
@github-actions github-actions bot closed this Apr 22, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Apr 24, 2024
@kbx81 kbx81 reopened this Feb 10, 2025
@esphome esphome unlocked this conversation Feb 10, 2025
@esphome esphome bot marked this pull request as draft February 10, 2025 05:19
@esphome
Copy link

esphome bot commented Feb 10, 2025

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@kbx81 kbx81 marked this pull request as ready for review February 10, 2025 05:57
@esphome esphome bot requested a review from kbx81 February 10, 2025 05:57
@github-actions github-actions bot removed the stale label Feb 11, 2025
using multiple components.
- **bluetooth** (*Optional*): Turn on/off the bluetooth adapter. Defaults to ``true``. All options from
:ref:`Switch <config-switch>`.
- **multi_target** (*Optional*): Turn on/off the Multi Target Tracking option. All options from
Copy link

@WiebKastanje WiebKastanje Feb 18, 2025

Choose a reason for hiding this comment

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

multi_target defaults to false

Copy link
Member

Choose a reason for hiding this comment

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

Nope, it's read from the device at start-up so its state will depend on how it's set on the LD2450. IIRC, the LD2450's factory default has it set to "on", but the state is stored so it will be recalled after each reset or power-cycle.

Copy link

@WiebKastanje WiebKastanje Feb 19, 2025

Choose a reason for hiding this comment

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

Yes, you are correct. Apologies for not fully understanding the LD2450 specs.
However: this integration does not show (after factory reset) status: multi-target ON.
This happens (after factory reset, change in status multi-target to ON) after activating the mobile app connection to the sensor.
Is this perhaps a glitch in the integration code?

Copy link
Member

Choose a reason for hiding this comment

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

Hmm, on the bottom of page 9 it's indicated that multi-tracking is enabled by default.

Copy link

@WiebKastanje WiebKastanje Feb 19, 2025

Choose a reason for hiding this comment

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

After Factory Reset, not only multi-target does not report back to default ON.
Also zone details like Zone Type (disabled) and Zone X and Y values (0 mm) do not report these default settings.

A Restart after Factory Reset does not report default settings either.
Also powercycle of the sensor does not solve this.

These values are updated correctly to default settings when:
-powercycle the ESP32 or
-the mobile app connects to the sensor.

Hope this testinformation provide some insights.

Copy link
Member

Choose a reason for hiding this comment

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

Hmm, that's not my experience at all, @WiebKastanje. When I factory reset the LD2450, the settings revert to the radar's defaults as documented.

Are you factory resetting the ESP or the LD2450? These are different things.

Factory resetting the ESP does not impact the radar settings, as they are stored on the radar module itself and retrieved from it when the ESP boots. That would explain why you are not seeing the settings revert to their defaults.

When you factory reset the radar module--whether via Bluetooth using the app or using the method provided in the ESPHome component--the settings will not be reflected in ESPHome/HA until the ESP is rebooted, as it only queries the module at startup and settings are not sent from the module to the ESP immediately following a factory reset. This is expected behavior and there's not a way to change this -- it's just how the LD2450 radar module works.

@kbx81 kbx81 merged commit eb5b6d1 into esphome:next Feb 20, 2025
3 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Feb 22, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants