LD2402 Command confusion

[pkkrusty]

Playing with LD2402, and having trouble understanding the command list in the driver. If @protectivedad can comment a bit to explain, would be helpful.

1. LD2402_SetMotion n,n1..n16 - set motion threshold values (16)

Can you provide an example of a complete command? Unclear what a complete command looks like. What is the range for the threshold values?

2. LD2402_AutoUpdate 3.0,2.0,3.0 - start autoupdate trigger,keep,micro magnification factor

In the code (line 741, the range is from 1 to 20, but the ESPHome code from Mc-Joung indicates a limited subset of values:
Trigger Multiplier Controls initial motion detection 2.0-5.0 (higher = less sensitive)
Hold Multiplier Controls presence retention 2.0-4.0 (higher = shorter retention)
Micromotion Multiplier Controls small motion sensitivity 3.0-6.0 (higher = less sensitive)
Why the difference?

3. LD2402_Follow command is quite useful for initial calibration, similar to shortening webrefresh to 1000 to see how the device is responding without having to calibrate with the official application. I think it's helpful to keep in.

4. Engineering mode is used how? When I activate it, all I see on the main page is LD2402 Initialized

[protectivedad]

1. If you do a ld2402_status 3 command the output will show you the current numbers. You can copy and paste the numbers in the command line and change them as you see fit for example:

ld2402_status 3
08:19:30.470 MQT: stat/tasmota/RESULT = {"LD2402":{"MaximumDistance":85,"DisappearenceDelay":30,"MotionThresholds":[49.50,47.00,38.00,34.00,33.00,33.00,33.00,33.00,33.00,33.00,33.00,33.00,33.00,33.00,33.00,33.00],"MicroThresholds":[52.00,48.00,40.00,35.00,35.00,34.00,33.00,32.00,32.00,32.00,32.00,32.00,32.00,32.00,32.00,32.00]}}

ld2402_SetMotion 49.50,47.00,38.00,34.00,33.00,33.00,33.00,33.00,33.00,33.00,33.00,33.00,33.00,33.00,33.00,33.00
08:22:34.701 MQT: stat/tasmota/RESULT = {"LD2402_SetMotion":"Accepted... Allow 2 seconds to write to device."}

Same with the micro threshold values.

Running ld2402_setmotion gives:

08:46:28.329 MQT: stat/tasmota_65FB60/RESULT = {"LD2402_SetMotion":"Requires 1,2,..16 (values are dB <= 95.00"}

So the range is from 0 to <= 95.00.

2. The HLK-LD2402 user manual I used has the parameter range as 0x000A~0x00C8

3. Thanks for the feedback.

4. After the ld2402_mode 1 command the ld2402_status 1 command should give you:

08:32:19.984 MQT: stat/tasmota/RESULT = {"LD2402SNS":{"Distance":153,"Motion":true,"Occupancy":true,"PowerInterference":1,"MotionEnergies":[0.00,0.00,45.09,39.59,35.37,34.53,31.39,31.45,30.66,29.08,27.63,27.92,26.38,26.85,25.16,25.74],"MicroEnergies":[0.00,0.00,46.52,40.60,34.88,33.70,30.52,29.22,29.29,30.83,25.61,26.73,22.74,25.65,22.38,25.47]}}

as opposed to ld2402_mode 0 which gives:

08:34:58.464 MQT: stat/tasmota/RESULT = {"LD2402SNS":{"Distance":231}}

You can compile Tasmota with the sensor debug on and set weblog 4 to get details of what is going on. If normal mode works and engineering doesn't then I would make sure my connections are solid and maybe try it with a different esp module. Which one are you using?