home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.13k stars 29.8k forks source link

LD2410C sensor not discovered #97170

Open almirus opened 1 year ago

almirus commented 1 year ago

The problem

The LD2410C sensor with default settings is not discovered (via internal Bluetooth rpi4)

What version of Home Assistant Core has the issue?

core-2023.7.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

LD2410 BL

Link to integration documentation on our website

https://www.home-assistant.io/integrations/ld2410_ble

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

The device works fine (via LD2410 BLE) if the sensor is brought close to the RPI4. However, the sensor is not detected through the connected Bluetooth dongle (CSR8510 A10). image

home-assistant[bot] commented 1 year ago

Hey there @930913, mind taking a look at this issue as it has been labeled with an integration (ld2410_ble) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `ld2410_ble` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign ld2410_ble` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


ld2410_ble documentation ld2410_ble source (message by IssueLinks)

almirus commented 1 year ago

The built-in Bluetooth on RPi4 is disabled, and a CSR8510 A10 dongle is enabled (the Passive BLE monitor integration works perfectly). image

gielk commented 11 months ago

I have esp32-bluetooth-proxy, having the same problem not showing the sensor. Can find it with the app, but not HASS.

Judicael-Marchand commented 11 months ago

Hello I have the same problem as you. I have a docker container of home assistant running on a server. I have a usb bluetooth dongle and the dongle works well with the passive BLE integration I use for temperature sensors. However, the LD2410 is not found as you. However, I can see the LD2410 BLE advertising packets through my mobile phone using the nrF connect app

Judge-Tread commented 8 months ago

Also having this issue. No autodetection, and inability so set up new device - I'm 3-4m away from the RP4 hosting HA, so Bluetooth connection should be fine

tbrasser commented 7 months ago

Seems these things need:

TLaren commented 7 months ago

My system:

LD2410 is automatically detected in HA. I try to configure a box come up with the device name and MAC address. I click SUBMIT and it spins for randomly from 5 seconds to 30 seconds and then displays "Failed to connect". I can connect with the APP on my phone and it connects and stays connect, giving me the graphs and all.

Is there any configuration I can do from the APP that might fix this?

HA logs show:

2024-02-14 12:51:27.952 WARNING (MainThread) [bthome_ble.parser] The new encryption counter (4596) is lower than the previous value (12171). The data might be compromised. BLE advertisement will be skipped.
2024-02-14 12:51:28.579 WARNING (MainThread) [bthome_ble.parser] The new encryption counter (4597) is lower than the previous value (12171). The data might be compromised. BLE advertisement will be skipped.
2024-02-14 12:51:43.663 WARNING (MainThread) [bthome_ble.parser] The new encryption counter (4600) is lower than the previous value (12171). The data might be compromised. BLE advertisement will be skipped.
2024-02-14 12:52:01.549 WARNING (MainThread) [bthome_ble.parser] The new encryption counter (4605) is lower than the previous value (12171). The data might be compromised. BLE advertisement will be skipped.
2024-02-14 12:52:28.092 WARNING (MainThread) [bthome_ble.parser] The new encryption counter (4610) is lower than the previous value (12171). The data might be compromised. BLE advertisement will be skipped.
2024-02-14 12:52:30.240 WARNING (MainThread) [bthome_ble.parser] The new encryption counter (4611) is lower than the previous value (12171). The data might be compromised. BLE advertisement will be skipped.
2024-02-14 12:52:33.904 WARNING (MainThread) [ld2410_ble.ld2410_ble] HLK-LD2410_C11C: Device unexpectedly disconnected; RSSI: None
2024-02-14 12:52:46.531 WARNING (MainThread) [ld2410_ble.ld2410_ble] HLK-LD2410_C11C: Device unexpectedly disconnected; RSSI: None

My thought is that the encryption failing several times causes the chip to reboot? Any thoughts?

isisyodin commented 4 months ago

I am having the same issue. Latest version of HA 2024.5.3. I am using Bluetooth proxy. Other Bluetooth devices connect fine. In fact, when adding the 2410 for the first time, it gets discovered. I was having an issue with one 2410 where it was unavailable, so I deleted it. Now it won’t get rediscovered. Same issue with two different 2410s.

Orekaria commented 1 month ago

I encountered the same issue on a Raspberry Pi 4.

Solution:

  1. Navigate to the Bluetooth configuration: http://homeassistant.local:8123/config/integrations/integration/bluetooth
  2. Disable Passive scanning

After doing this, the LD2410 was detected immediately.

isisyodin commented 1 month ago

Mine gets detected but fails to install with a USB Bluetooth dongle plugged in to my Home Assistant server. Using a Bluetooth proxy, it connects and works for a short period of time and then it disconnects.

KlausHans commented 1 month ago

I have the same problem with two LD2410Bs via Esp32 Bluteooth Proxies. Home Assistant Core 2024.8.0, ESPHome 2024.7.3. They aren't discovered reliably. On of them was discovered, but after i added it the connection was lost.