LD2410 esphome tips

aruffell · May 16, 2023, 11:54pm

@soubhik - I am using the PR version and did not have to merge anything. All I did was add the dev version of ESPHome to my install (it can coexist with the regular one) and then used the example YAML which pulls the needed code to program the ESP32.

The code that tells it where to get the integration that hasn’t been merged yet is:

external_components:
  source: github://regevbr/esphome@ld2410
  components: [ld2410]

Once it is merged into the released channel, I believe all that you need to do is remove the code above and re-upload the firmware.

Protoncek · May 17, 2023, 7:53am

Doesn anyone knows why this is not included in esphome yet? Today esphome 2023.5.0 is up, but this is still not included…?

koying · May 17, 2023, 8:45am

Because the PR has not been merged.

Protoncek · May 17, 2023, 8:56am

That’s what i was asking… (why it was not included → why it was not merged yet, if it works…?)

mihaichrapan · May 17, 2023, 10:42am

I understand that only one can be controlled and set its parameters which is connected to rx tx to ld2410 respectively rx tx from esp 8266 and the rest just read clered or detected which are connected to the out pin from ld2410 and one gpio pin from esp8266?

athua · May 22, 2023, 11:33am

I managed to get a LD2410C working with a Wemos D1 Mini Compatible ESP32 board and also got it to light up the internal blue LED when motion is detected. The LD2410C is connected using the UART pins (the pins marked TX and RX on the D1 Mini ESP32 board didn’t work and I had to use GPIO16 and GPIO17). Also the Bluetooth Proxy has been enabled for Home Assistant.

If it will help anyone, here is my config which got the LED working:

substitutions:
  name: "esp32-motion-sensor"

esphome:
  name: ${name}
  name_add_mac_suffix: false

api:
ota:

logger:
  level: INFO
  baud_rate: 0

esp32:
  board: esp32dev
  framework:
    type: esp-idf

esp32_ble_tracker:
  scan_parameters:
    interval: 1100ms
    window: 1100ms
    active: true

bluetooth_proxy:
  active: true
  cache_services: false

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

uart:
  id: ld2410_uart
  tx_pin: GPIO17
  rx_pin: GPIO16
  baud_rate: 256000
  parity: NONE
  stop_bits: 1

ld2410:
  uart_id: ld2410_uart

binary_sensor:
  - platform: ld2410
    has_target:
      name: Presence
    has_moving_target:
      name: Moving Target
      on_press:
        then:
          - light.turn_on: led
      on_release:
        then:
          - light.turn_off: led
    has_still_target:
      name: Still Target

output:
  - platform: ledc
    id: onboard_led
    pin:
      number: GPIO2
      inverted: false

light:
 - platform: monochromatic
   name: "Onboard LED"
   output: onboard_led
   id: led

formatBCE · May 23, 2023, 3:10am

On ESP32, you may use almost any pins for UART. However, hardware UART pins are recommended for faster speed.

Also, you don’t need to switch serial logging off - ESP32 has 3 UARTs, so you’re good having both sensor and logger. Nevertheless, i had problems with using all 3 UARTs on some ESP32 Mini boards, but on other they work fine, all 3.

P.S. I don’t see that you use UART at all - just binary sensor, which is working without UART anyways.

athua · May 23, 2023, 3:33am

Thanks for the feedback. I used GPIO16 and GPIO17 as the pinouts for my board seems to match the following diagram and it corresponds with UART2.

I also did have the distance and energy level sensors working but I removed them as they were creating lots of chatter to Home Assistant with the distance and energy levels constantly updating while I was in the room.

sensor:
  - platform: ld2410
    moving_distance:
      name : Moving Distance
    still_distance:
      name: Still Distance
    moving_energy:
      name: Move Energy
    still_energy:
      name: Still Energy
    detection_distance:
      name: Detection Distance

formatBCE · May 23, 2023, 3:46am

Yes, you did it right. IO16/17 are good. But if you don’t plan to use that energy stuff and fine-tuning gate thresholds, you don’t need UART.

athua · May 23, 2023, 4:06am

As I have the LD2410C with bluetooth, I found it much easier to use the Android app and connect to it directly via bluetooth to fine tune the gate thresholds and settings rather than setting them in the yaml and having to upload it to the ESP32 board each time.
Wouldn’t I still need to use the UART to get the data for Move Target and Still Target binary sensors?

formatBCE · May 23, 2023, 4:21am

Yeah you need it, sorry to be unclear. I meant, there’s 5th pin on sensor, and it provides simple binary sensor of presence (without moving/still, joined one). In that case you can use it directly, without UART.

screek-workshop · May 23, 2023, 11:22pm

Using gpio binary pins seems to be a good idea and works well in many places. But one also needs to be aware that the delayed off time in the parameter settings can become bothersome.

athua · May 24, 2023, 12:05am

Very true. The delayed off time for presense (combined move and static) can be configured on the LD2410. I have connected it to an ESP32 using the UART as that way I can directly access the move target sensor which responds very quickly.

CalcU · May 28, 2023, 3:16pm

I can read at least 2 persons writing that the android app is in English, but I can’t locate / convert it to English.

Any help on this?
Thanks

Protoncek · May 28, 2023, 3:36pm

App is (automatically) in english only if device (phone) language is set to english.

CalcU · May 28, 2023, 4:07pm

Thanks!, i just found it.

I will now try to understand the values…

I attached the LD2410 to a door, and i want to detect the movement through this door. let’s see if i can xD

PatrikPatrik · May 28, 2023, 6:14pm

I got it to work with an ESP32 with one LD2410 over UART, now I would like to connect two or three LD2410 over UART to one ESP32 - how do I configure that in ESPhome (if it is possible)?

jpravetz · June 3, 2023, 9:13pm

I’d agree that the LD2410B doesn’t play well with fans, even if the fan is outside the documented 60˚ cone of detection.

I have an LD2410B on the ceiling, with fan blades as close as 0.8m away and at the same height. The sensor shows an almost continuous moving target peaking at about 4m away, and a strong static target across the full range of 1.5m to 6m. I see no way to filter that out.

I’d guess fans, wind, curtain movement, and the like are problems for many home settings. I’d love to hear if anyone is able to effectively use these devices when dealing with such factors.

walberjunior · June 4, 2023, 5:56pm

Have you tested with the code from this link?

github.com/esphome/esphome

Add configuration flow abilites to the ld2410 component

esphome:dev ← regevbr:ld2410

opened 01:04AM - 14 Feb 23 UTC

regevbr

+1661 -313

# What does this implement/fix? Currently, in order to easily calibrate we ne…ed to download the radar app and do it over Bluetooth. To support the calibration process you can now: 1. enable engineering mode 1. monitor the gates values 1. change the gates thresholds and repeat step 2 if necessary (without reflashing esp) 1. disable engineering mode In the updated docs I added a suggestion of a custom HA card that will make this process super easy, same as the app :-) ## Types of changes - [ ] Bugfix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [x] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Other **Related issue or feature (if applicable):** fixes <link to issue> https://github.com/esphome/feature-requests/issues/2107 **Pull request in [esphome-docs](https://github.com/esphome/esphome-docs) with documentation (if applicable):** https://github.com/esphome/esphome-docs/pull/2680 https://deploy-preview-2680--esphome.netlify.app/components/sensor/ld2410 ## Test Environment - [x] ESP32 - [ ] ESP32 IDF - [ ] ESP8266 - [ ] RP2040 ## Example entry for `config.yaml`: (must be on latest dev branch) ```yaml external_components: source: github://regevbr/esphome@ld2410 components: [ld2410] api: services: - service: set_ld2410_bluetooth_password variables: password: string then: - bluetooth_password.set: id: ld2410_comp password: !lambda 'return password;' uart: id: ld2410_uart tx_pin: GPIO17 // Your pin rx_pin: GPIO16 // Your pin baud_rate: 256000 parity: NONE stop_bits: 1 ld2410: uart_id: ld2410_uart throttle: 1500ms id: ld2410_comp select: - platform: ld2410 distance_resolution: name: distance resolution baud_rate: name: baud rate light_function: name: light function out_pin_level: name: out pin level button: - platform: ld2410 factory_reset: name: "factory reset" restart: name: "restart" query_params: name: query params number: - platform: ld2410 timeout: name: timeout max_move_distance_gate: name: max move distance gate max_still_distance_gate: name: max still distance gate g0_move_threshold: name: g0 move threshold g0_still_threshold: name: g0 still threshold g1_move_threshold: name: g1 move threshold g1_still_threshold: name: g1 still threshold g2_move_threshold: name: g2 move threshold g2_still_threshold: name: g2 still threshold g3_move_threshold: name: g3 move threshold g3_still_threshold: name: g3 still threshold g4_move_threshold: name: g4 move threshold g4_still_threshold: name: g4 still threshold g5_move_threshold: name: g5 move threshold g5_still_threshold: name: g5 still threshold g6_move_threshold: name: g6 move threshold g6_still_threshold: name: g6 still threshold g7_move_threshold: name: g7 move threshold g7_still_threshold: name: g7 still threshold g8_move_threshold: name: g8 move threshold g8_still_threshold: name: g8 still threshold light_threshold: name: light threshold text_sensor: - platform: ld2410 version: name: "presenece sensor version" mac_address: name: "presenece sensor mac address" switch: - platform: ld2410 engineering_mode: name: "engineering mode" bluetooth: name: control Bluetooth binary_sensor: - platform: ld2410 has_target: name: "presence" has_moving_target: name: "movement" has_still_target: name: "still" out_pin_presence_status: name: out pin presence status - platform: gpio pin: GPIO13 // Your pin name: gpio out pin presence device_class: presence sensor: - platform: ld2410 moving_distance: name: "Moving distance (cm)" still_distance: name: "Still Distance (cm)" moving_energy: name: "Move Energy (%)" still_energy: name: "Still Energy (%)" detection_distance: name: "Distance Detection (cm)" g0_move_energy: name: g0 move energy g0_still_energy: name: g0 still energy g1_move_energy: name: g1 move energy g1_still_energy: name: g1 still energy g2_move_energy: name: g2 move energy g2_still_energy: name: g2 still energy g3_move_energy: name: g3 move energy g3_still_energy: name: g3 still energy g4_move_energy: name: g4 move energy g4_still_energy: name: g4 still energy g5_move_energy: name: g5 move energy g5_still_energy: name: g5 still energy g6_move_energy: name: g6 move energy g6_still_energy: name: g6 still energy g7_move_energy: name: g7 move energy g7_still_energy: name: g7 still energy g8_move_energy: name: g8 move energy g8_still_energy: name: g8 still energy light: name: light ``` ## Checklist: - [x] The code change is tested and works locally. - [x] Tests have been added to verify that the new code works (under `tests/` folder). If user exposed functionality or configuration variables are added/changed: - [x] Documentation added/updated in [esphome-docs](https://github.com/esphome/esphome-docs). Features done: - added engineering mode switch + sensors to show the energy values - added bluetooth switch - added factory reset, restart and query parameters buttons - added version and mac address text sensors - added ability to see and control all configurations directly from HA using number elements - Added nice default icons to all enetites - Cleaned up some of the code - added option to control the throttling of the data rate - added option to control the distance resolution - added option to change the bluetooth password - added option to change baud rate - added option to control the light sensor functionality Please note that this is a breaking change to the current configuration

Install the dev version of esphome.
You will see which gate is having the most interference from the fan.

jpravetz · June 4, 2023, 8:30pm

I have not. I’ve only looked at it via the HiLink phone app + bluetooth. I’m currently using it with HA via Bluetooth and a bluetooth proxy (with all it’s reconnect problems). I only became aware yesterday that connected (via wires), LD2410 support has significant updates that are not released yet.