That ‘denied by Referer ACL’ message means it’s looking at the HTTP REFERER header.
The referrer (misspelled in the www spec as “referer”) is the website you came from.
If you click the link, your browser sends this site’s URL in the referer header and you get a 403 (not sure why their firewall has that rule but it’s still set that way).
If you instead copy the link and open it in a new tab, then there’s no referring site. Apparently that makes their firewall happy, so the it doesn’t block you and you can see the doc.
That’s the trick if anyone else wants to look at the (Chinese) hardware spec sheet from the link.
Hi,
I’m also trying to connect the D1mini to LD2450.
RX–>TX
TX–>RX.
But nothing show up in the sensors, even with the HLKRadar app.
can you please share your YAML, so I can correct mine?
Or any other idea regarding troubleshooting?
thx,
Doron
Sorry I am doing packet parsing in C++ or JS, never used RD-03 with esphome, But I guess LD2450 component should work out of box, as my C++ parsing is exactly the same for both, with less config options for RD-03.
Hi everyone,
I started playing with LD2450 and observed a noticeable delay in state updates, about 1s. Some people may tolerate that delay, but I find it annoying. I would like to see an instant tracking of the objects.
The device spec claims that it reports ten times a second. With debug level logs, it sends updates about twice a second and multiple warnings “Component uart took a long time for an operation…”
If you add signal processing in HA, the delays get more noticeable even with 0.5s interval updates in the plotly graph.
Is it just the way the device works or these delays can be reduced?
Anyone else have very poor wifi signal with the ld2450 hooked up? I can connect to the router in my office with it hooked up, but once even on the other side of the wall, or even within a feet of my extender, and it will not connect to wifi (exact same spot will get -19db).
tried 2 different sensors and 2 esp32 with the same results
The wifi connectivity is handled by your ESP32 board and not the LD2450. I am using ESP32-C3 micro-USB boards and have no issues with wifi connectivity when using them with the LD2450. You can try adding the following to see what the signal strength your ESP32 is getting:
sensor:
- platform: wifi_signal # Reports the WiFi signal strength/RSSI in dB
name: "WiFi Signal dB"
id: wifi_signal_db
update_interval: 60s
entity_category: "diagnostic"
I haven’t tried that implementation but I do notice that it has 6 zones defined. I use the SCREEK implementation and it has only 3 zones and the delay times are not too bad. The lights come on as soon as I enter the room.
As the Zone implementation for the LD2450 is handled by the ESP32 coding, it places more CPU load on the ESP32 board so maybe having 6 zones could be causing the delayed response from the ESP32 board.
My implementation (athua) is based on SCREEK and the static detection works pretty well within 2 to 3 metres of the sensor. Beyond that, it seems to need more movement to detect presence so it seems to loose its detected object if you don’t move very much.
Ok thanks. I have the screek 2a and noticed that it stops detecting me if I am still on the couch about 1 meter away. Its mounted about 4 feet on the wall and I am sitting at about a 30 degree angle. I disabled the zones.
If I want to flash your code or any othe code on the screek 2a, is it just a matter of first initializing the device in esphome and then flashing your YAML code (with changes for the sceek 2A hardware)?
Is there any advantage to uncle yuras code for static detection since it supports entry and exit zones?
