Judging by this scheme
I found an analog to the hexagon, this is SY8120B1ABC, Step down type SOT236 DC DC Converters ROHS. I would like to clarify with you whether such an analogue is suitable?
1 Like
have you contacted hilink about the problem with the app?
Hi, this looks really great, do you have github page for that?
I don’t have a github page but I based my code here on the following from Screek Workshop and the link to their github page can be found in the post below:
I know, but their code is not easily applicable to other ESP devices. Your code is awesome and it would be great if noobs like me could just create yaml configuration which would be automatically updated from GitHub as development progresses.
P. S. I have noticed that this sensor is quite slow in detecting presence, is that normal?
Hope you don’t mind sharing this code along with the LD2450 esphome example in my repo.
I changed it a bit to grab automatically all the active LD2450 targets and put them in seperate cards with the area_name of each device as title (one card per active device).
It only works with the code from the example in the repo above, but feel free to change it for the example of the Screek commercial products.
1 Like
Hi, i want to block a fan around this area but looks like 6000 is the limit.
How can I bypass that?
Btw, I’ve already changed the range to 7000 mm for this graph
If you are using the YAML based on the Screek code, you just need to update the max value for each of the Y values from 6000 to something like 7500:
- platform: template
name: "Zone1 Y-Begin ${friendly_name}"
id: zone1_y_begin
mode: box
min_value: 0
max_value: 7500
I had already updated my code to use 7500 in my earlier post of my YAML code:
1 Like
It looks like the default distance goes up to 7 meters, we will fix this code issue and release new firmware.
Nice approach. Thank you.
1 Like
The original code for the Plotly graphs were mine and I’m happy for you to share it in your repo.
3 Likes
Hello everyone, I wrote an external component for an LD2450 sensor. All the configuration mentioned in the PDF documentation is available. I also added the ability to rotate the output coordinates so that when the sensor is placed in the corner of the room, the coordinates are relative to the walls.
The project is here:
5 Likes
Wonderful work! Thank you very much!
Time to abandon my project…
I think we should now concentrate to build a python library and an integration like LD2410, and let them directly communicate via Bluetooth in HA without the need of an ESP.
Wouldn’t be much of a work for someone who knows what to do since the communication protocol for LD2450 and LD2410 isn’t much different
Someone here that could do that?
Hello,
Implementation in esp home is on going:Add LD2450 component by hareeshmu · Pull Request #5674 · esphome/esphome · GitHub 
1 Like
Thanks, had some problem earlier where the target keeps missing and the bt was unreliable (keeps disconnecting from the app every few seconds).
Turns out the usb extension cord was the issue, used a 3m one since I needed to position on the corner of the room.
Nice, would I need to exclude a zone with the hlkradar app?
You can enable zone ignoring in both the hlkradar application and the external component.
I seem to have figured out how I could disable J5EDH. The multimeter worked in automatic mode. To measure the throttle, it turns out that the multimeter had to be switched to the resistance measurement mode, but since I am not strong in electronics and circuit design, I prefer to use auto mode and the multimeter itself determines which measurement mode to use. That’s why I bought a smart multimeter. Before measuring the throttle, the LD2450 radar had to be de-energized, which I did not do. I did all the measurements on the LD2450 radar under a voltage of +5v. So, the LD2450 radar was under voltage +5v, when I touched the ends of the winding with the probes, the multimeter tried to determine what we were measuring and thereby closed the throttle through the internal circuit of the smart multimeter. Step-down DC/DC converter J5EDH fails and burns out
The same throttle that I measured with a multimeter and because of what the J5EDH burned down
1 Like
Thanks, testing it now. I can see the ignore zone in the hlkradar app after making the change on esphome
Just a few questions:
- What is ‘single target’ for?
- Can I display the exclusion zone using plotly graph in ha?
- For the regions type dropdown option, does this mean I can only assign either exclusion zone or detect zone but not both?
- This is the mode of the sensor in which it detects only one target, it is difficult to say for what purpose this was done by the developers of the sensor.
- I don’t see a problem with this.
- Yes, the sensor protocol does not allow simultaneous ignoring and detecting zones.
1 Like