Just in case anyone struggles with a DFRobot SEN0557 (ld2410), I had to set the baud rate to 57000 and it started working. It is specified on their data site - 24GHz Human Presence Sensing Module Wiki - DFRobot
For your information, I have read the documentation. All my other gates, except gate 0 and gate 1, works fine, hence the question. Pls don’t answer if you don’t want to, I am not forcing you. Just don’t be rude about it.
Muchas gracias por esta información, ahora he eliminado de la tarjeta toda la info numérica y la he cambiado por estas 2 gráficas. Ahora puedo prescindir hasta de configurar el LD2410 por bluetooth ya que con la misma tarjeta se hace muy fácil hacerlo, es hasta más cómodo.
Thank you very much for this information, I have now removed all the numerical information from the card and replaced it with these 2 graphics. Now I can even do without having to configure the LD2410 via Bluetooth, since it is very easy to do so with the same card, it is even more comfortable.
hi. Is this code for 2 LD2410C sensors still working for you? I have similar code, but the second uart_1 does not work. The only difference I see is the board type. I set it to
Hi, thanks for this
Couldn’t figure why my previous bars keep going outside the box but yours work fine.
I changed it slightly to show the threshold value instead of the name (g1/g2 etc)
Is it possible to still label both gates number & thrsehold value?
type: custom:config-template-card
variables:
g0MT: states['number.wemos_esp12_mmwave_g0_still_threshold'].state
g1MT: states['number.wemos_esp12_mmwave_g1_still_threshold'].state
g2MT: states['number.wemos_esp12_mmwave_g2_still_threshold'].state
g3MT: states['number.wemos_esp12_mmwave_g3_still_threshold'].state
g4MT: states['number.wemos_esp12_mmwave_g4_still_threshold'].state
g5MT: states['number.wemos_esp12_mmwave_g5_still_threshold'].state
g6MT: states['number.wemos_esp12_mmwave_g6_still_threshold'].state
g7MT: states['number.wemos_esp12_mmwave_g7_still_threshold'].state
g8MT: states['number.wemos_esp12_mmwave_g8_still_threshold'].state
entities:
- sensor.wemos_esp12_mmwave_g0_still_energy
- sensor.wemos_esp12_mmwave_g1_still_energy
- sensor.wemos_esp12_mmwave_g2_still_energy
- sensor.wemos_esp12_mmwave_g3_still_energy
- sensor.wemos_esp12_mmwave_g4_still_energy
- sensor.wemos_esp12_mmwave_g5_still_energy
- sensor.wemos_esp12_mmwave_g6_still_energy
- sensor.wemos_esp12_mmwave_g7_still_energy
- sensor.wemos_esp12_mmwave_g8_still_energy
card:
type: custom:bar-card
title: Still Energy Test
direction: up
columns: 9
height: 150px
width: 100%
positions:
icon: "off"
indicator: "off"
value: inside
entities:
- entity: sensor.wemos_esp12_mmwave_g0_still_energy
target: ${g0MT}
limit_value: true
name: ${g0MT}
severity:
- color: Red
from: ${g0MT}
to: 100
- entity: sensor.wemos_esp12_mmwave_g1_still_energy
target: ${g1MT}
limit_value: true
name: ${g1MT}
severity:
- color: Red
from: ${g1MT}
to: 100
- entity: sensor.wemos_esp12_mmwave_g2_still_energy
target: ${g2MT}
limit_value: true
name: ${g2MT}
severity:
- color: Red
from: ${g2MT}
to: 100
- entity: sensor.wemos_esp12_mmwave_g3_still_energy
target: ${g3MT}
limit_value: true
name: ${g3MT}
severity:
- color: Red
from: ${g3MT}
to: 100
- entity: sensor.wemos_esp12_mmwave_g4_still_energy
target: ${g4MT}
limit_value: true
name: ${g4MT}
severity:
- color: Red
from: ${g4MT}
to: 100
- entity: sensor.wemos_esp12_mmwave_g5_still_energy
target: ${g5MT}
limit_value: true
name: ${g5MT}
severity:
- color: Red
from: ${g5MT}
to: 100
- entity: sensor.wemos_esp12_mmwave_g6_still_energy
target: ${g6MT}
limit_value: true
name: ${g6MT}
severity:
- color: Red
from: ${g6MT}
to: 100
- entity: sensor.wemos_esp12_mmwave_g7_still_energy
target: ${g7MT}
limit_value: true
name: ${g7MT}
severity:
- color: Red
from: ${g7MT}
to: 100
- entity: sensor.wemos_esp12_mmwave_g8_still_energy
target: ${g8MT}
limit_value: true
name: ${g8MT}
severity:
- color: Red
from: ${g8MT}
to: 100
Strangely, when I installed it (turned it on) for the first time (new) and then changed it to 0.2m Still Energy was still normal, not long after that it got stuck at 100%.
This has been happening for a long time, even though I have replaced the ESP32 and/or LD2410 with another one, but the results are still the same.
Now it has been several months, although it does not affect its performance, it still feels like there is something bothering me.
Hi to everyone,
I’m a starter in home automation ad i wanted to ask here for some help with the ld2410 (bluetooth version).
I managed to configure the sensor both ways, via bluetooth and via wifi with an esp32 wroom ad it works well either way (i have good wifi and a bluetooth proxy right next to it).
My only problem is the responsive time: i use the ld2410 to turn on the lights in the kitchen with WLED and home assistant. The fact is that it takes quite a few seconds to turn on the lights (4/5s in bluetooth, 2/3s in wifi).
Is there something i can do to improve this or its something that can be resolved with a combo: ld2410 + zigbee pir sensor?
Thanks
I’d start with looking at your thresholds. I have a few that pick up motion instantly and a few that are a little lazier because of having the thresholds higher for the range that covers the point of entry into the room.
I just installed LD2410 on my hallway. I didn’t work with them for a while, so when i updated hlk radar tool i see that now app has “auto” mode, where sensor calibrates itself to it’s best situation. Then only small corrections are needed (fw update was also necesarry since sensors were sitting a copulle of years in my drawer).
But, i install my LD’s so that light is controlled with ld’s out pin, not with esp. This way i ensure that light will go on even if esp is broken. So i only ise HA monitoring, settings and eventual additional automations.
comes on in time 
thanks a lot.
