Here we try to explain some generalities, what we know, and what will happen
- Usage
- Supply voltage requirements?
- What is the maximum detection distance?
- What is the left and right detection width of the radar in meters?
- What is the detection angle of the radar?
- Installation method?
- Schematic representation of the radar's detection range?
- What are the installation requirements?
- Bought a few mmwave sensors suggested by this forum in the past but they all keep getting triggered by fans.Has the LD2450 improved?
- What are the possible sources of interference in 2A?
- 2A, for example, wind affects radar judgment. How do you deal with that?
- I've set up the A2 in Home Assistant and I've flashed the Aug 1 beta firmware.The sensor works somewhat okay when I'm moving, but a couple of seconds after sitting down, it'll easily drift both the X and Y axis several meters, sometimes for just a second.I've got a small zone set up at my computer to trigger the lights, but as I was laying in bed several two meters away, it would trigger periodically.But when I was actually moving in and out of the zone, it would trigger pretty reliably.Additionally, it seems to think there are two people in room frequently, even if it's just me. Moving sometimes fixes this, but not always.（MrHaxx1@reddit）
- my fans and ac are detected by the sensor, I’m guessing this is the part where I have to adjust x & y distance for exclusion?
- The target disappears when you sit still in front of the sensor.
- Hilink APP
- When you guys say update the firmware, do you mean the LD2450 firmware?
- When I open the HLKRadarTool APP, it just prompts me to update, but no changes after the update, is this normal?
- Why does the HLKRadarTool APP not offer parameter adjustment?
- How do I update the firmware on the LD2450 module itself?
- What are some of the features of the current firmware version?
- Will the LD2450 offer the same parameter adjustment as the LD2410 in the future?
- If I accidentally update to beta v1.23, can I downgrade back?
- Updated the sensor to the latest july build. Is it normal that it still shows the july ota ready for upgrade if I connect to the app again?
Usage
Supply voltage requirements?
You need to ensure 5V 500ma or above, and choose a more reliable USB power supply to avoid interference from signal ripple.
What is the maximum detection distance?
Up to 6 meters.
What is the left and right detection width of the radar in meters?
- In our tests, the maximum range extends about 3m left and right with the radar as the center. But limited by the testing environment, this is a data of ours for reference only.
- This is basically the same as the test data provided in the hilink documentation
What is the detection angle of the radar?
The azimuth is 60 degrees on either side, adding up to 120 degrees. 35 degrees up and down, adding up to 70 degrees.
Installation method?
Hilink's LD2450 documentation is quoted as follows:
Typical mounting method of D2450 is wall mounting, as shown in the figure, the longest positioning and tracking distance is 6 m. Wall mounting needs to take into account the obstruction in the application scenario and the interfering objects on the top of the wall, and the recommended mounting height is 1.5~2 m. The installation height is 1.5~2 m. The installation height is 1.5~2 m.
Schematic representation of the radar's detection range?
We still use Hilink's module documentation for the schematic diagram (the picture is slightly adjusted):
The figure shows the tracking range of the module at a wall height of 1.5m, and the tester is 1.75m tall with a medium build. The detection angle range is ±60° centered on the radar antenna plane.
What are the installation requirements?
According to the documentation of hilink, it points out the following characteristics:
Bought a few mmwave sensors suggested by this forum in the past but they all keep getting triggered by fans.Has the LD2450 improved?
(question by (ferbulous@ha forum)
Some advanced radars are able to avoid signals like fans, they differentiate between information like the frequency of the target. The LD2450 looks to be a little better radar. We’re still testing some newer signals like the LD1125H and hope to share them with you sometime.
What are the possible sources of interference in 2A?
This is a collection of possible sources of 2A interference that we have gathered so far:
- Windblown clothing interference from balconies
- Wind disturbance outdoors
- Exhaust fan interference in the kitchen
- Ceiling fan interference in the living room
- Ghostly shadows in certain special cases They dart in and out of energy range and then disappear.
- Cats on the table A few times they are seen as humans.
We will continue to try to refine this list.
2A, for example, wind affects radar judgment. How do you deal with that?
Some errors can not be ruled out, only to change the installation location, not suitable for balcony.
I've set up the A2 in Home Assistant and I've flashed the Aug 1 beta firmware.The sensor works somewhat okay when I'm moving, but a couple of seconds after sitting down, it'll easily drift both the X and Y axis several meters, sometimes for just a second.I've got a small zone set up at my computer to trigger the lights, but as I was laying in bed several two meters away, it would trigger periodically.But when I was actually moving in and out of the zone, it would trigger pretty reliably.Additionally, it seems to think there are two people in room frequently, even if it's just me. Moving sometimes fixes this, but not always.（MrHaxx1@reddit）
We sent the question back to the developers at hilink and got some responses, "Well, there is a static error, I compared the same type of product and it has the same problem, I'll ask the original manufacturer. See if we can optimize it.” In our own experience, detecting while sleeping is very difficult to succeed. When sitting, it seems to be ok. The height of the mounting needs to be about where the seated head would be. For multiple people, this may also be an interference trigger too, in the current ld2450 firmware, v1.23 beta seems to be more sensitive. But we'll hopefully see how it goes in mid-August after the Hilink APP is improved to switch to a better multiplayer mode.
my fans and ac are detected by the sensor, I’m guessing this is the part where I have to adjust x & y distance for exclusion?
(question by ferbulous@home-assistant commuinity)
It’s a ceiling fan, and the sensor is not positioned towards it, I did try leaning the sensor a bit to the floor. I’m not sure if this helps since it still detects my ac when it’s turned on
I don't know if I mentioned it, but one of hilink's visions for the way to fix interference in general is to make a way to exclude an area of interference in the same way that you can draw a picture.
It sounds wonderful, but we don't know how long it will take to realize it, and we're still waiting for the multiplayer mode firmware to be developed. But the last we heard from hilink is that they've been very busy lately trying to customize some products for their customers.
Sometimes hilink can still be amazingly efficient though, at least their excellent planning to make the ld2410 so popular is an amazing thing. As far as I can tell they are also trying to evaluate how to make the ld2450 easier to use.
I reverted back to firmware 1.22 but it’s not doing any better Looking forward for the next update if that improves this
This is close to our test results, and v1.23, the beta version, seems to have overly sensitive issues.
The target disappears when you sit still in front of the sensor.
(question by Vladi2023@Reddit)
Hello Is there any way to adjust the mmWave detection and maintaining sensitivities? I am literally siting in front of sensor and if I am not moving, "any presence" is cleared and Target going to "0". So basically, Human Sensor 2A works like PIR motion sensor (which is obviously not the purpose of this mmWave sensor)
We just spoke with the hilink folks while we tested the complete immobilization and indeed the target disappeared.
From the hilink developers we got a simple answer:
ld2450 does not support stationary detection.
In our tests at the same time we found that detections continue to be captured as long as they move slightly.
This may be a limitation of the LD2450 and may be difficult to be solved perfectly.
Regarding the further exploration of stationary detection of the 24G radar, on the LD2410, tests also revealed that almost complete stationarity leads to a smaller energy amplitude as well. We went on to consult with the developers at Hi-LInk and got some new answers:
Stationary 2410 is possible, and there is a limit to how far the 2410 can detect stationary, about 1.5 to 2 meters. (The future 2450 is unlikely to increase the stationary detection) this demand we will evaluate the discussion, to detect stationary will require more antennas and algorithms to optimize, the cost will certainly have increased. For example, it may require two or more chips, more antennas, and algorithm optimization. Of course, you can also increase the frequency, but many applications require cost-effective solutions, so there are trade-offs.
From this information, in some specific areas, you can use the static function of the 2410 to supplement may be good, for example, in the sofa and other areas, you can use a ld2410 radar to lock the detection distance of roughly 2m, and only use its static function to help ld2450 to determine.
Of course Rock-Lee also mentions using PIR to trigger a faster response to human activity.
We have research in these areas unfolding in human detection:
- We are testing some of the more expensive 24G radars, including radars such as the CEM5460, LD1125H, etc., which seem to be able to be smarter than the LD2410 in determining respiratory radar in human activity.
- We're testing some 60G sleep radars as well as fall radars. Sleep radars have been in the works for a while, and they hang above the bed and are able to detect a person's breathing, heartbeat, and rolling over. It's like specializing in stationary activity
- We're in the preliminary stages of evaluating and studying some TMOS solutions (STHS34PF80 chip), which is a new generation of PIRs designed by ST, and it's interesting to see how they can discriminate ambient noise and detect stationary features.
Hilink APP
When you guys say update the firmware, do you mean the LD2450 firmware?
When we say update firmware in our general context it is the firmware for the esp32, which is the firmware for the esphome part. This does not require the involvement of the HLKRadrTool APP.
When I open the HLKRadarTool APP, it just prompts me to update, but no changes after the update, is this normal?
Currently (as of August 3, 23) the APP's functionality is limited to firmware updates, and the firmware we have pre-installed is v1.22 which is the current latest stable version. There is only an internal beta version of V1.23, hilink calls it the Taster version, we don't recommend normal users to use the beta version.
So if the radar is working fine, please don't try the LD2450 firmware.
Why does the HLKRadarTool APP not offer parameter adjustment?
According to what we've gotten from the hilink developers so far, the relevant app features will be opened up gradually, with a target tracking demo feature at the earliest possible time, as well as a multiplayer mode tracking toggle. This cycle could be in mid-August.
How do I update the firmware on the LD2450 module itself?
Currently the HLKRadarTool APP offers OTA functionality, and firmware switching can be done in it.
What are some of the features of the current firmware version?
As of today, August 3, 23, there is a stable firmware V1.22 and a tasting firmware V1.23 (i.e. test firmware). All of our current 2A radars are sent out with firmware V1.22. Firmware V1.23, in our testing, seems to be more overly sensitive and can cause active 3D printers to be seen as human targets. We have brought this issue back to hilink personnel. It seems that the V1.23 firmware adds a version display (in the update screen), but in this regard, it is not possible to say for sure.
Will the LD2450 offer the same parameter adjustment as the LD2410 in the future?
According to Hilink's technical staff, the LD2450's parameters are much more complex, so it won't provide that kind of direct parameter adjustment. However, they will consider providing a region exclusion function similar to fp2, which can exclude interference sources in a fixed region. This sounds exciting.
If I accidentally update to beta v1.23, can I downgrade back?
In our testing, yes, it is still possible to downgrade back to v1.22
Updated the sensor to the latest july build. Is it normal that it still shows the july ota ready for upgrade if I connect to the app again?
(question by ferbulous@ha community)
At this point in time (2023-8-22), the app functionality of the ld2450 remains rather rudimentary, with one of the more puzzling aspects being the fact that it still may alert for updates after updating the ota.
The beta version of v1.23 seems to recognize a portion of the version number, but adjusts the sensitivity too high to easily recognize the fan.
One explanation we got from hilink is that if you refirm a firmware of the same version, there will be an error in the validation and it won't update once again. So, this strange logic is sometimes that not being able to update successfully means you are already on this firmware.
Really strange? But when you think about radar modules that don't have bluetooth to update the firmware, then it seems to be a bit lucky again.