Support for HLK-LD2410 in latest Tasmota (missing the documentation)

[mmatesic01]

Hello,
There is a support for HLK-LD2410 sensor in Tasmota 12.3.1 through serial inteface, but there is no explanation which BIN file supports it, how to connect the sensor and how to setup the Tamota.
Can anyone help?
Thank you.

[sfromis]

You need your own build to enable this optional feature, USE_LD2410. Once you have that, the gpio configuration gets specific tx/rx pins for LD2410, and of course connect them to the board.

[dkebler]

#17555 (comment)

[mmatesic01]

Hi, I did my own build, connected TX and RX wires to RX and TX on WEMOS, but get no values. Are GPIO1 and GPIO3 OK or do I have to choose some other GPIO?  

[levanLuongnt]

I don't know how to use it, can you give me file bin?

[Derek-K]

I just tried. Under "4. Custom parameters" Add this

#ifdef USE_LD2410
 #undef USE_LD2410
#endif
#define USE_LD2410

[barbudor]

Why make it complicated when it can be simpler ?

#ifndef USE_LD2410
 #define USE_LD2410
#endif

Or just use the #define and forget about the warning if there's one

#define USE_LD2410

[Derek-K]

That is playing by the standard build practice outline in the document.

[sfromis]

The standard practice does have the advantage of also working when the #define is of a value, not merely a binary.

[barbudor]

Try swapping the wires. Sometime there is ambiguity if TX/RX are meant from the ESP or the sensor point of view

[mmatesic01]

Swapped the wires now it works.
Thank you.

[levanLuongnt]

Can you give me file bin?

[miaszh]

Hi, can you share your compiled bin?
Thanks

[sfromis]

As already posted earlier, it is pretty easy to do a custom build, using a simple browser-based tool.

[ozett]

as as replacment for compiling maybe the all-sensors.bin includes this new sensor?

the webinstaller has the allsensor.bin
#9568 (comment)

[sfromis]

No, LD2410 is not included there

[ozett]

good to know... maybe someone can put this in the next build of all-sensors?

[sfromis]

tasmota-allsensors is an unofficial experimental build which is far from having all sensors. I'm not involved in considerations about which ones are included, but it may be a bit random, for the purpose of having some test builds.

[Jajola]

It's definitely in the tasmota-allsensors build as of me trying it today

Program Version	14.2.0.4 (6650dee-allsensors)
2024-09-09T08:51:26

I just had to configure the Tx & Rx pins to LD2410 Tx & Rx respectively & all good!

[sfromis]

Then things changed since 1½ years ago. Maybe they'll change again some day, as those "special" builds do not have the same expectations of a stable mix of features, like with the regular builds.

[S-A-M-J]

I did add the
#ifdef USE_LD2410
#undef USE_LD2410
#endif
#define USE_LD2410
in a custom build. I then used platform io as vsc extension to build in the tasmota32c3 enviroment.
The build worked and the ld2410 now shows up under the configure module dropdown. However once i hit save and the chip reboots the configuration for the ld2410 is gone. This happens only for the ld2410, a config of an io as button will be saved.
Furthermore i noticed that under module type i now have esp32c3 (0) and esp32c3 (1) which have the same config though.
Any idea what i'm doing wrong?

edit: i know i'm not supposed to change any env apart from tasmota and tasmota32 but i can't get platformio to use the right board when im using these enviroments

[sfromis]

Since you got the gpios available for config, the build is likely ok. The esp32c3 (0) entry is selecting the template you can configure, instead of doing it all in configure module, but both ways can work.

One possible cause is that something causes Tasmota to fail when booting, then Tasmota may "scale back" features until able to boot without crashing. As the LD2410 needs more than a little bit of power, it might be due to the board not getting the power it needs.

[S-A-M-J]

ok i checked by powering it from a lab bench power supply but there is no change in behaviour.
Do you maybe have any other ideas. Or what lead to the boot to fail?

[S-A-M-J]

ok rebuild and reflashed and it fixed itself. Thank you

[guysnraw]

Hi, any idea how to use those distance values in rules?

[sfromis]

Just like any other JSON values, triggers like on LD2410#Distance[1] do var1 %value% endon for the first one.

[guysnraw]

Thank you

[4139GGN]

I already did my build and have it configured. But the values are always 0.
Last night, I don't know exactly when I took a value. But he stood there frozen.
Are you connected:
Pin1:-
Pin2: RX (Wemos D1)
Pin3:-
Pin4: GND
Pin5: +5v

[sfromis]

You still have the same wiring issue as in your first image. What's off there is that the yellow/green colors at the LD2410 are wrong, meaning that your wiring looked right when using those labels, but swapped when using the real pinout of the LD2410. The tx/rx connections need to be crossed, while you wired them as straight instead.

As I suggested, to match my image:

TX from the LD2410 to a Tasmota gpio configured as LD2410 Rx and RX to a LD2410 Tx pin.

[4139GGN]

It seems to be a feeding problem.
There was another device on that Wemos that was feeding off of it.
I left it just on the USB-powered wemos of the MacBook and it started working fine, I think. At least it gave values.
Now I have placed it in another place powered by a Samsung USB power supply from the drawer. And the value stays at 0.
I also saw the error in the GPIO configuration

[sfromis]

You need a good power supply situation for stable operation with LD2410. Many D1 Mini clones are not good for that, as they have a much weaker LDO than the original, 150 mA instead of 500 mA of 3.3V. And your USB power source is also a risk factor.

[4139GGN]

Seems that if. That the whole problem came from food.
Now I have a doubt:
I have 3 motion sensor values and 2 energy ones.
Is there a rule to make a value that is "presence detector: Yes/No"?

[4139GGN]

I'm checking:
When I connect the wemos to USB the analog output of the LD2410 works.
I can see how the wemos LED lights up when 10 seconds pass and there is no movement. There is no record on the console when the LED is turned on or off.
It is configured as a button on GPIO4 (D2).
If I disconnect and connect the LD2410, maintaining the power of the wemos, in the console I start to see records with the movement within the angle of the sensor.
But now the wemos LED is always off.
There are two "ons" on the LD2410?

[dali-dbr]

Hi.

Today I built a custom firmware using the line below:

#ifndef USE_LD2410 // Human Presence detector
#define USE_LD2410
#endif

It all works, it will send the distance values to MQTT. But it will not send null (0.0) values to MQTT. So when I leave the room the Tasmota GUI will show 0.0 cm, but 0.0 will not be sent to MQTT. MQTT keeps the earlier value until the 5-min refresh state cycle hits.

Any suggestions?

Thank you

[sfromis]

Well, sensor data is only published at TelePeriod, not when changes in readings occur. Default telemetry period is 5 minutes, nothing gets published in between. You can shorten the period, and/or you can setup rules to react to changes, and trigger additional publishes.

[dali-dbr]

Thanks for your reply.

I don't think so.

All other values are instantly sent to MQTT as seen in Tasmota GUI.

values differ because I could not get both screenshots at the same time.

But when values reset to 0.0, MQTT payload does not update with null values

Br

[dali-dbr]

Yes, you are correct.

It seems I have to set up a rule that whenever the value changes it should publish an MQTT topic. Will look into it.

Thank you

Br,
Dali

[giulianosrebuli]

Hi, if anyone could help. I tried using the tasmocompiler on gitpod to make my custom build, using an ESP-WROOM-32, so on boards i selected ESP32 Generic. On step 4 i added the following

#ifdef USE_LD2410
 #undef USE_LD2410
#endif
#define USE_LD2410

as suggested earlier.
I managed to build and flash the firmware, but it doesn't seem to be creating it's own access point so i can configure the module. I already tried all the options below

#ifndef USE_LD2410 // Human Presence detector
#define USE_LD2410
#endif

#define USE_LD2410

but nothing seems to work. I am using the Tasmota Web Flasher to flash the custom firmware, and it goes well, it erases and fully install the firmware.
Am I doing something wrong? Can anyone please give some advice?

[barbudor]

With the web installer, are you using the 'factory.bin' firmware ?
For serial flashing you must use the 'factory.bin'
Simple '.bin' is for OTA upgrade once you already have Tasmota flashed

[giulianosrebuli]

Oh, i didn't know that, thanks. By factory.bin you mean one of the pre-compiled firmwares? or is it something else?

[barbudor]

No
When compiling, 2 binaries are created:

• tasmota32.bin is strictly for OTA upgrades
• tasmota32.factory.bin is strictly for serial flashing

[giulianosrebuli]

Ah, i see now! It worked here, thanks so much for your time!

[ferbulous]

Hi, since distance detection 0 (no presence) doesn’t get published instantly. I noticed it took almost 4-5 minutes
Can anyone help with creating rule that publish only when 3 conditions are met? Specifically when detection distance 0, 1 & 2 are all 0

[mcnguyen33r]

Dear All,
Can someone help me? I have no experience and I am not I coder/ developer.
I am composing my own tasmota,bin file with ld2410 support (having solution above already) and some presettings such as

Module: Generic 18
GPIO1 = LD2410 Tx
GPIO3 = LD2410 Rx
GPIO4 = IRsend
GPIO14 = IRrcv

So, how can I put these in the step 4 (I am using TasmoCompiler)
Thank you
Minh Chau

[sfromis]

The general way of doing pin config is to not use "Configure Module", but instead "Configure Template". After that, you can get the template as a string, which you can then use when doing a custom build, setting the value with a #define USER_TEMPLATE (you need to escape each " as \", and then have " around the string. To also have the template activated, also #define MODULE USER_MODULE.

[mcnguyen33r]

Thank sfromis,
Actually, I have no experience on this, I am using ChatGPT helping me and here's my "Custom parameters"
`#ifndef USER_CONFIG_OVERRIDE_H
#define USER_CONFIG_OVERRIDE_H

#ifndef USE_LD2410
#define USE_LD2410
#endif

#ifdef MQTT_HOST
#undef MQTT_HOST
#endif
#define MQTT_HOST "192.168.1.102"

#ifdef MQTT_PORT
#undef MQTT_PORT
#endif
#define MQTT_PORT 1883

#ifdef MQTT_USER
#undef MQTT_USER
#endif
#define MQTT_USER "home"

#ifdef MQTT_PASS
#undef MQTT_PASS
#endif
#define MQTT_PASS "home1234"

#define TEMPLATE_NAME "Điều khiển điều hòa"
#define TEMPLATE "{"NAME":"Điều khiển điều hòa","GPIO":[1,9248,1,9280,1056,1,1,1,1,1,1088,1,1,1],"FLAG":0,"BASE":18}"

#ifdef MQTT_TOPIC
#undef MQTT_TOPIC
#endif
#define MQTT_TOPIC "tasmota_ir"

#endif // USER_CONFIG_OVERRIDE_H`
Gipod creaated a bin file and I flashed but nothing saved as template.
I do not know why
Can you help me?
Thank you

[ferbulous]

Add this line in step 4 & compile

#define USE_LD2410

Go to template setting and assign tx & rx pin for LD2410 Tx & LD2410 Rx respectively

Then you can add this rule in the console

rule2
on LD2410#Distance[0] do var1 %value% endon 
on var2#State=detected do publish detected endon
on var2#State=nobody backlog delay 5; do publish nobody endon
rule2 1

rule3
on var1#State>=10 do var2 detected endon
on var1#State==0 do var2 nobody endon
rule3 1
rule3 5

I'm pretty sure others have a better way of implementing the rules or thru berry/script (which I'm not familiar with)

You can remove backlog delay 5 if you need instant no presence detection. I added that because sometimes it turns to 0 quite briefly when I'm still in the room

on var2#State=nobody do publish nobody endon

[sfromis]

Don't use ChatGPT for such specific details, unless you want bad advice.

Those #define for TEMPLATE and TEMPLATE_Name are invalid, I specifically said to have USER_TEMPLATE (and no separate one with the name).

[mcnguyen33r]

Thank you very much.
As I said before, I had no expreriences and no knowledge on this,
I'll try to find out gain
Best Regards
Minh Chau

[jkwim]

I am trying to get a LD2410B working with no luck:

https://vi.aliexpress.com/item/1005007139061447.html?

Is the following wiring and configuration correct?

[jkwim]

It seems that the board that I have been using has an issue with Tx/Rx.

I tried a brand new D1 Mini Clone and it works with the same custom compiled binary.

13:03:10.029 RSL: SENSOR = {"Time":"2024-08-14T13:03:10","LD2410":{"Distance":[133.0,130.0,114.0],"Energy":[100,100]}}
13:03:11.028 RSL: SENSOR = {"Time":"2024-08-14T13:03:11","LD2410":{"Distance":[89.0,97.0,104.0],"Energy":[100,100]}}
13:03:12.028 RSL: SENSOR = {"Time":"2024-08-14T13:03:12","LD2410":{"Distance":[91.0,103.0,89.0],"Energy":[100,100]}}
13:03:13.028 RSL: SENSOR = {"Time":"2024-08-14T13:03:13","LD2410":{"Distance":[75.0,83.0,69.0],"Energy":[100,100]}}
13:03:14.027 RSL: SENSOR = {"Time":"2024-08-14T13:03:14","LD2410":{"Distance":[85.0,81.0,64.0],"Energy":[100,100]}}
13:03:15.028 RSL: SENSOR = {"Time":"2024-08-14T13:03:15","LD2410":{"Distance":[70.0,73.0,57.0],"Energy":[100,100]}}
13:04:22.427 CMD: baudrate
13:04:22.431 RSL: RESULT = {"Baudrate":255900}

00:00:00.001 HDW: ESP8266EX
00:00:00.016 UFS: FlashFS mounted with 1992 kB free
00:00:00.069 CFG: Loaded from File, Count 22
00:00:00.078 SCR: ufilesystem found
00:00:00.088 Project tasmota - Tasmota Version 14.1.0.3(LD2410-scr-udsp-4M-trim)-2_7_7(2024-08-04T16:26:16)
00:00:00.089 SNS: Hardware Serial
00:00:01.001 WIF: Connecting to AP1 xxx SLT Channel 4 BSSIdxxx in mode 11n as tasmota-xxx..
00:00:01.650 LD2: Firmware version V2.04.23022511
00:00:03.791 WIF: Connected

Sensor:
LD2: Firmware version V2.04.23022511

[sfromis]

What you do with the Baudrate command is irrelevant when using a driver already taking care of the details. With a working LD2410, I have the default {"Baudrate":115200}
And at boot, I get 00:00:03.012 LD2: Firmware version V1.07.22082218

The log you posted earlier shows that you did not try to use the standard Tasmota driver, but for a test case there you typically need to talk to the sensor.

[jkwim]

I compared the two boards:
Both have CH340C and there are two 470 Ohm resistors connected between Tx/Rx pins and CH340C in both.

I reset the configuration of the development board that I used and configured only Tx/Rx GPIO's.

Used the same 5V power (a power bank),

Dev board has AMS1117 popular LDO Regulator whereas the D1 Mini Clone has a dubious unmarked LDO Regulator (which is supposed to be of lower capacity than the AMS1117 as per discussions in the internet).

Anyway 5V is fed from the source so in that sense the power supplied will be identical.

Still the driver does not seem to get loaded for some reason (I used the same custom binary on both).

My Dev Board

00:00:00.001 HDW: ESP8266EX
00:00:00.038 UFS: FlashFS mounted with 1840 kB free
00:00:00.083 CFG: Loaded from File, Count 11
00:00:00.089 QPC: Count 1                                            <<<<<<<<<<<<<<<<
00:00:00.094 SCR: ufilesystem found
00:00:00.117 Project tasmota - Tasmota Version 14.1.0.3(LD2410-scr-udsp-4M-trim)-2_7_7(2024-08-04T16:26:16)
00:00:00.128 SNS: Hardware Serial
00:00:01.919 WIF: Connecting to AP1 ...
00:00:04.433 WIF: Connected

There is a QPC: Count 1 message. No idea about it.

D1 Mini Clone

00:00:00.002 HDW: ESP8266EX
00:00:00.022 UFS: FlashFS mounted with 1992 kB free
00:00:00.076 CFG: Loaded from File, Count 29
00:00:00.084 SCR: ufilesystem found
00:00:00.096 Project tasmota - Tasmota Version 14.1.0.3(LD2410-scr-udsp-4M-trim)-2_7_7(2024-08-04T16:26:16)
00:00:00.097 SNS: Hardware Serial
00:00:01.001 WIF: Connecting to AP1 ........
00:00:01.652 LD2: Firmware version V2.04.23022511 <<<<<<<<<<<<<<<<<<<
00:00:03.792 WIF: Connected

Status 4 output is identical:

07:24:09.795 RSL:              STATUS4 = {"StatusMEM":{"ProgramSize":730,"Free":1316,"Heap":15,"ProgramFlashSize":4096,"FlashSize":4096,"FlashChipId":"16405E","FlashFrequency":40,"FlashMode":"DOUT","Features":["0809","07AA858E","042A02A1","000000C3","00000000","C0009901","000000A4","00200000","04000000","00000400","00000000"],"Drivers":"1,2,!4,!5,!8,9,10,12,13,!18,!19,!22,!24,!27,29,!30,!35,!37,38,50,62,!68","Sensors":"1,2,4,5,6,102","I2CDriver":"3,5,47"}}
11:55:00.040 MQT: stat/tasmota/STATUS4 = {"StatusMEM":{"ProgramSize":730,"Free":1316,"Heap":15,"ProgramFlashSize":4096,"FlashSize":4096,"FlashChipId":"1640EF","FlashFrequency":40,"FlashMode":"DOUT","Features":["0809","07AA858E","042A02A1","000000C3","00000000","C0009901","000000A4","00200000","04000000","00000400","00000000"],"Drivers":"1,2,!4,!5,!8,9,10,12,13,!18,!19,!22,!24,!27,29,!30,!35,!37,38,50,62,!68","Sensors":"1,2,4,5,6,102","I2CDriver":"3,5,47"}}

Simply a big puzzle!

[sfromis]

Those logs do not show the most important details, how the wiring and active configuration is.
Backlog Template; Module; GPIO 255
Of course, you need to have the pins configured correctly, for a build including the feature.

Your image with green/orange colors for wires appears to be swapped. It is "not uncommon" that boards may be labeled with what to connect instead of what the function is. Hence, "try swapping" is a common good advice.

With ESP8266, you also have alternate hardware serial with TX on gpio 15 and RX on gpio 13. I've tested it to work with pin 2 from a LD2410 to gpio 15 configured as LD2410 Tx and pin3 to gpio 12, unsurprisingly configured as LD2410 Rx.

And you need to make sure to have good power available, which also might be influencing the wiring/connections. As LD2410 expects 5V, what your LDO can deliver should not be much of a factor. but saying "power bank" is no indication of how well it delivers.

Whether you get a QPC: Count number reported depends on whether Tasmota is counting your restarts against the threshold for a quick power cycle.

[jkwim]

With ESP8266, you also have alternate hardware serial with TX on gpio 15 and RX on gpio 13. I've tested it to work with pin 2 from a LD2410 to gpio 15 configured as LD2410 Tx and pin3 to gpio 12, unsurprisingly configured as LD2410 Rx.

Tried this but did not work.

BTW since I have a TFT display also connected to this board I duplicated the complete GPIO configuration including the display on to the D1 Mini and connected the LD2410 as before (GPIO1 LD2410 Tx - UART Rx, GPIO3 LD2410 Rx - UART Tx) and the sensor works on D1 Mini no matter what.

It simply does not work on my Development Board.

I did compare outputs of GPIO 255, Template, Module commands based on your suggestion.

Changed the set of jumper cables also to see whether there was a problem with wires.

I am going to park this here and try connecting the sensor the GeekMagic Unit and see whether it will work there.

Only issue is that the sensor can be mounted only on a side.and don't know with two layers of plastic how the detection will be.

[jkwim]

I thought of adding the following also in to the discussion if somebody might find it useful.

My first unit of LD2410B became faulty due to a mistake by me and had to wait until newly ordered units arrived.

I have setup a ESP-01 based prototype for my further testing. I am looking for a small enclosure to fit this in.|

Basically I have used following to quickly build the prototype.

1. ESP-01
2. MicroUSB Breakout board
3. AMS1117 3.3v LDO Regulator Module
4. A 2.54mm to 1.27mm conversion PCB and a 1.27mm pin header for easy plugging in/out the LD2410 module
5. Reset switch
6. WS2812 RGB LED - thought that I will be able to show detection status/values during testing/fine tuning by changing colors

ESP-01 has only 4 x GPIO's exposed and were connected as follows:

1. GPIO0 - out to WS2812
2. GPIO1 - LD2410 Tx
3. GPIO2 - Digital OUT from LD2410
4. GPIO3 - LD2410 Rx

Since I have pin headers to connect GPIO0 & GPIO2, instead of the LED a buzzer module can also be plugged in here.

Also we can use the SerialSend5 command as follows to interact with the LD2410 module.

For example to retrieve the firmware version:

WebLog 4

02:02:11.534 CMD: Serialsend5 0xFDFCFBFA0200A00004030201
02:02:11.536 SRC: WebConsole from 192.168.1.119
02:02:11.539 CMD: Grp 0, Cmd 'SERIALSEND', Idx 5, Len 26, Pld 2147483647, Data '0xFDFCFBFA0200A00004030201'
02:02:11.544 MQT: stat/tasmota/RESULT = {"SerialSend":"Done"}
02:02:11.618 LD2: Rcvd FDFCFBFA0C00A0010000000104021125022304030201
02:02:11.621 LD2: Firmware version V2.04.23022511

I have tried few other commands and the responses get displayed when in Weblog 4 level.

The last line which shows the Firmware version in human readable form comes from the driver itself when the response is received.

[jkwim]

Got some hints from this post:
https://community.home-assistant.io/t/ld2410-esphome-tips/477058/339

[jkwim]

Engineering mode can be enabled by issuing three commands:

Serialsend5 0xFDFCFBFA0400FF00010004030201 Enable Configuration
Serialsend5 0xFDFCFBFA0200620004030201 Enable Engineering Mode
Serialsend5 0xFDFCFBFA0200FE0004030201 Close Configuration

When you enable engineering mode, the actual values from each Distance Gate also get reported by the sensor. However these data do not get displayed by the driver.

Without engineering mode enabled data gets reported as:
11:47:32.983 LD2: Rcvd F4F3F2F10D0002AA033100641E006400005500F8F7F6F5
With engineering mode enabled additional data gets reported:
11:48:16.258 LD2: Rcvd F4F3F2F1230001AA031E00643300640000080864646412150A070B04000064645B38222C2756015500F8F7F6F5

Engineering mode can be turned off by:

Serialsend5 0xFDFCFBFA0400FF00010004030201 Enable Configuration
Serialsend5 0xFDFCFBFA0200630004030201 Disable Engineering Mode
Serialsend5 0xFDFCFBFA0200FE0004030201 Close Configuration

Similarly, the threshold values can be set/read with commands.

What this means is that using a script we should be able to plot a graph in real time (at this moment I have no experience in plotting graphs in Tasmota GUI). If anybody knows, some hints will be really appreciated.

This is the manufacturer provided Desktop Configuration GUI accessible by directly connected USB/TTL converter to the sensor.

Using a script we should be able to do similar actions via Tasmota GUI.

[sfromis]

I'd really not recommend to base such builds on the crappy ESP-01. And while ESP8266 dev boards are better, by now I'd always base such builds on an ESP32 variant, which in addition to some extra hardware features also enables the Berry language embedded with Tasmota, providing greatly enhanced options for local processing, like coding drivers for LD2410.

[jkwim]

Here is a summary of what I have done to get the output like this ie. the sensitivity setting vs actual detected levels at each distance point

1. Added following features in to custom compile apart from what is required for scripting.

        // For Scripts
        #ifndef USE_SCRIPT
          #define USE_SCRIPT
        #endif
 
        // When you activate Scripts Rules should be disabled
        #ifdef USE_RULES
          #undef USE_RULES
        #endif
 

        #define MAXSVARS 4
        // Max Variable size in SCRIPTS
        #define SCRIPT_MAXSSIZE 128
 
        #define USE_SCRIPT_WEB_DISPLAY
        #define USE_SCRIPT_JSON_EXPORT
 
 
        // To be able to parse WEBSEND received data
        // WEBSEND is a Tasmota Console Command
	    #ifdef USE_WEBSEND_RESPONSE
          #undef USE_WEBSEND_RESPONSE
        #endif
        #define USE_WEBSEND_RESPONSE

        
        // Google Charts
        #ifndef USE_GOOGLE_CHARTS
          #define USE_GOOGLE_CHARTS
        #endif 

        // Long JSON Data
        #ifndef USE_SCRIPT_FULL_JSON_PARSER
          #define USE_SCRIPT_FULL_JSON_PARSER
        #endif

2. Modified the 2410 driver to append Engineering Data to SENSOR MQTT message
   xsns_102_ld2410.ino: Modification for reading Engineering Mode Data #22097

3. Script

>D 40
tvar=0
tstr=""
m:men=0 8
m:mse=0 8
m:sen=0 8
m:sse=0 8
cnt=0

Activate the Engineering Mode by issuing commands (this can be done manually also)

>S
if upsecs==10 {
;Enable Configuration
=>Serialsend5 0xFDFCFBFA0400FF00010004030201
}
if upsecs==12 {
;Enable Engineering Mode
=>Serialsend5 0xFDFCFBFA0200620004030201
}
if upsecs==14 {
;Close Configuration
=>Serialsend5 0xFDFCFBFA0200FE0004030201
}

Periodically issue the command to capture the sensitivity settings

if upsecs%60==0 {
=>LD2410MovingSens
}

Grab the data from E section:

>E
mse[1]=LD2410#Moving#Sensitivity[1]
mse[2]=LD2410#Moving#Sensitivity[2]
mse[3]=LD2410#Moving#Sensitivity[3]
mse[4]=LD2410#Moving#Sensitivity[4]
mse[5]=LD2410#Moving#Sensitivity[5]
mse[6]=LD2410#Moving#Sensitivity[6]
mse[7]=LD2410#Moving#Sensitivity[7]
mse[8]=LD2410#Moving#Sensitivity[8]

sse[1]=LD2410#Static#Sensitivity[1]
sse[2]=LD2410#Static#Sensitivity[2]
sse[3]=LD2410#Static#Sensitivity[3]
sse[4]=LD2410#Static#Sensitivity[4]
sse[5]=LD2410#Static#Sensitivity[5]
sse[6]=LD2410#Static#Sensitivity[6]
sse[7]=LD2410#Static#Sensitivity[7]
sse[8]=LD2410#Static#Sensitivity[8]

men[1]=LD2410#MEnergy[1]
men[2]=LD2410#MEnergy[2]
men[3]=LD2410#MEnergy[3]
men[4]=LD2410#MEnergy[4]
men[5]=LD2410#MEnergy[5]
men[6]=LD2410#MEnergy[6]
men[7]=LD2410#MEnergy[7]
men[8]=LD2410#MEnergy[8]

sen[1]=LD2410#SEnergy[1]
sen[2]=LD2410#SEnergy[2]
sen[3]=LD2410#SEnergy[3]
sen[4]=LD2410#SEnergy[4]
sen[5]=LD2410#SEnergy[5]
sen[6]=LD2410#SEnergy[6]
sen[7]=LD2410#SEnergy[7]
sen[8]=LD2410#SEnergy[8]

for cnt 1 sse[-1] 1
  tvar=cnt*0.75
  print E: %tvar%m men[%0cnt%] %men[cnt]% mse[%0cnt%] %mse[cnt]% sen[%0cnt%] %sen[cnt]% sse[%0cnt%] %sse[cnt]%
next

Draw the Google Chart in the W section

>W
Free Heap {m}%heap%
$<div id="chart1" style="width:640px;height:300px;margin:0 auto"></div>
$gc(lt men mse "Distance" "MEnergy" "MThresh" "0.75|1.5|2.25|3.0|3.75|4.5|5.25|6.0")
$var options = {
$vAxis:{viewWindow:{min:0,max:100},title: 'Energy \%'},
$hAxis: {title: 'Distance'},
$title:'Moving Human Energy Levels at Distance Gate'
$};
$gc(e)
$<br>
$<div id="chart2" style="width:640px;height:300px;margin:0 auto"></div>
$gc(lt sen sse "Distance" "SEnergy" "SThresh" "0.75|1.5|2.25|3.0|3.75|4.5|5.25|6.0")
$var options = {
$vAxis:{viewWindow:{min:0,max:100},title: 'Energy \%'},
$hAxis: {title: 'Distance'},
$title:'Static Human Energy Levels at Distance Gate'
$};
$gc(e)
#

Console output:

17:09:23.032 MQT: tele/tasmota/SENSOR = {"Time":"2024-09-08T17:09:23","Switch1":"ON","LD2410":{"Distance":[30.0,68.0,31.0],"Energy":[100,100], "MEnergy":[100,100,73,18,11,10,9,10], "SEnergy":[7,0,0,100,100,100,82,78]}}
17:09:23.036 E:
17:09:23.039 E: Energy1 100.00
17:09:23.042 E: Energy2 0.00
17:09:23.062 E: 0.75m men[1] 100.00 mse[1] 50.00 sen[1] 0.00 sse[1] 0.00
17:09:23.065 E: 1.50m men[2] 73.00 mse[2] 40.00 sen[2] 0.00 sse[2] 40.00
17:09:23.069 E: 2.25m men[3] 18.00 mse[3] 30.00 sen[3] 100.00 sse[3] 40.00
17:09:23.072 E: 3.00m men[4] 11.00 mse[4] 20.00 sen[4] 100.00 sse[4] 30.00
17:09:23.075 E: 3.75m men[5] 10.00 mse[5] 15.00 sen[5] 100.00 sse[5] 30.00
17:09:23.078 E: 4.50m men[6] 9.00 mse[6] 15.00 sen[6] 82.00 sse[6] 20.00
17:09:23.082 E: 5.25m men[7] 10.00 mse[7] 15.00 sen[7] 78.00 sse[7] 20.00
17:09:23.085 E: 6.00m men[8] 0.00 mse[8] 15.00 sen[8] 0.00 sse[8] 20.00

[jkwim]

NOTE:
Above outputs have a mistake. I have picked up JSON array values from 1...8 whereas it should have been 0...7. Once that change is made values are correctly read by the script

[CancunManny]

Like many others I can't seem to get my LD2410 working.

I compiled 3 different bins, first one using these settings
#ifdef USE_LD2410
#undef USE_LD2410
#endif
#define USE_LD2410

2nd with these settings
#ifndef USE_LD2410
#define USE_LD2410
#endif

3rd with these settings
#define USE_LD2410

(I copied code just as above, with some lines indented in once place)

I am putting these settings in user_config_override.h file

I am guessing the compiling did work since when I flashed the bins when I go to configure the module I can select LD2410rx/tx for my pins.

I set Tx pin as LD2410tx and Rx pin as LD2410rx

When I restart the tasmota on top I get this

Tasmota
LD2410 Moving Distance 0.0 cm
LD2410 Static Distance 0.0 cm
LD2410 Detect Distance 0.0 cm

I then went back to configure module, and I swapped the pins, so the TX pin got LD2410 Rx and Rx pin got LD2410 Tx, rebooted tasmota and got same result as above.

Somewhere someone mentioned that power might be the issue as some china d1 minis (what I use) don't have enough power. I do have the HLK app that connects via bluetooth to the sensor, and I confirmed senor itself is working fine as I am able to access it via bluetooth and the readings are good.

Tomorrow I plan to set up another d1 mini and another sensor, to see if the issue is with one of the hardwares, but I am leaning towards it not being the case. I did make sure there is continuity between the jumper cables.

What else could I try? Or what am I missing?

[CancunManny]

So I figured it out! In the process I found an interesting glitch as well.

Turns out that to switch the cables around, you have to change the actual cables, you can't just switch them on the configuration module. On tasmota you HAVE TO set the Tx pin to LD2410 Tx and the Rx pin to LD2410 Rx. Then you connect the Rx pin of the sensor to the Tx pin of tasmota, and the Tx pin of the sensor to the Rx pin of tasmota (d1 mini)

In my previous tests, I always had Rx to Rx and Tx to Tx. I had assumed that if just switched the pins via configuration module it would do the same thing as my physically swapping the wires, that is not the case.

Here is the interesting glitch. I had physical wire connected between rx and rx and tx with tx. Then on configuration module I set Tx to be LD2410 Rx, and the Rx to be LD2410 Tx. When I went back to the main screen it would show all zeros. I then would get into the sensor via the bluetooth app, confirm sensor was working, well when I backed out to the main screen of the app, a couple seconds later the sensor would sortha work. At times it would update distance every couple of seconds, at times it would take 10 to 15 seconds. If I rebooted the device I would go back to all zeros, and it would stay like that until I got onto the sensor via the bt app, then got out of it.

I love this sensor! At some point I had 3 of them integrated into home assistant using a bluetooth proxy, but it was glitchy. For those 3 sensors I figured using the output pin was enough (using as motion sensor in 2 bathrooms and a hallway), but for my next build I do need to trigger actions based on distance. Glad I finally figured it out!

[sfromis]

Well, you can't expect it to work configuring "wrong" tx/rx in Tasmota, as you need to match hardware tx/rx on the ESP8266. Software serial cannot cope with the speed needed.

[CancunManny]

Thanks for confirming. So basically only ONE LD2410 can be used at a time with a single D1 mini correct? Only pins on D1 Mini that can be used are tx and rx correct? And Tx and Rx are not like the SDA and SCL where you can connect multiple devices to the same two pins correct?

[sfromis]

Mostly correct, but I'd expect the other hardware serial to work too, gpio15/13 vs gpio 1/3, but you can only have multiple of the same component type when a dropdown appears to the right when selecting it. Not the case for serial in general. However, you could have different serial-based sensors on different pin pairs, as long as software serial is workable.

In principle, you could have multiple devices on one serial bus, but only if they all are designed for this, including some addressing scheme for which to talk to. That's "quite uncommon"; hence the general answer is that it is not how serial works. OTOH, a characteristic of I2C is such a device address scheme.

[dkebler]

Just mentioning that (at least for 2410s I have) they have an "out" pin. If all you need is to detect presence (not the LD values) or not and the default settings of the chip are good for you then you don't need a special build (nor hook up the tx/rx pins). Just connect that out pin to a gpio and set it as a switch. From my experience it is about 7 secs from when that pin goes high (on detecting) and when it goes low (no longer detecting). For my application that is fine.

Just adding that I downloaded the high link app from Play store as Cancun Manny suggested and it's great. Without messing with the serial connection you can set important stuff like the sensitivity and distance to trigger. Which was all I needed

[erix22]

Thank you for you all for theses informations about voltages

[bigfacevn]

Just mentioning that (at least for 2410s I have) they have an "out" pin. If all you need is to detect presence (not the LD values) or not and the default settings of the chip are good for you then you don't need a special build (nor hook up the tx/rx pins). Just connect that out pin to a gpio and set it as a switch. From my experience it is about 7 secs from when that pin goes high (on detecting) and when it goes low (no longer detecting). For my application that is fine.

Just adding that I downloaded the high link app from Play store as Cancun Manny suggested and it's great. Without messing with the serial connection you can set important stuff like the sensitivity and distance to trigger. Which was all I needed

I built my firmware for ESP32S2. I connected the LD2410C's OUT pin to GPIO16 and configured it as Switch1. Could you help me write a rule to turn on Power when the OUT pin becomes active?

[sfromis]

You need no rules for that, as coupling a Switch input with a Relay output is default behavior in Tasmota. Do make sure to select a SwitchMode to match the behavior you want.

In case of wanting to keep output power on for an interval after last movement detected, setting PulseTime may be useful.

[bigfacevn]

Always Switch1 OFF even though I'm next to it

[sfromis]

I answered to your question about switching power when OUT becomes active. But until you configure the sensitivity data in the LD2410 itself, don't expect it to "magically" know your use case about when OUT "should" become active.

To be clear, it could be possible to make rules reacting the the more detailed data, instead of the OUT pin, as long as you understand how those numbers work in your use case.