LD2410 BLE recognized but fails to connect

[felix63]

The problem

I have a LD2410 BLE(B) which is recognised. When I start the config-flow I get 'failed to connect'.

What version of Home Assistant Core has the issue?

2023.2.4

What was the last working version of Home Assistant Core?

n.a.

What type of installation are you running?

Home Assistant Container

Integration causing the issue

LD2410 BLE

Link to integration documentation on our website

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

Diagnostics information

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant
Source: /usr/src/homeassistant/homeassistant/runner.py:100 
First occurred: 20:08:40 (4 occurrences) 
Last logged: 20:10:26

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/bleak_retry_connector/__init__.py", line 342, in establish_connection
    await client.connect(
  File "/usr/src/homeassistant/homeassistant/components/bluetooth/wrappers.py", line 249, in connect
    connected = await super().connect(**kwargs)
  File "/usr/local/lib/python3.10/site-packages/bleak/__init__.py", line 471, in connect
    return await self._backend.connect(**kwargs)
  File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/client.py", line 190, in connect
    assert_reply(reply)
  File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/utils.py", line 20, in assert_reply
    raise BleakDBusError(reply.error_name, reply.body)
bleak.exc.BleakDBusError: [org.bluez.Error.Failed] Software caused connection abort

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/ld2410_ble/ld2410_ble.py", line 325, in _reconnect
    await self._ensure_connected()
  File "/usr/local/lib/python3.10/site-packages/ld2410_ble/ld2410_ble.py", line 309, in _ensure_connected
    client = await establish_connection(
  File "/usr/local/lib/python3.10/site-packages/bleak_retry_connector/__init__.py", line 419, in establish_connection
    _raise_if_needed(name, device.address, exc)
  File "/usr/local/lib/python3.10/site-packages/bleak_retry_connector/__init__.py", line 318, in _raise_if_needed
    raise BleakConnectionError(msg) from exc
bleak_retry_connector.BleakConnectionError: HLK-LD2410B_EE2A - B6:FE:5A:C3:EE:2A: Failed to connect: [org.bluez.Error.Failed] Software caused connection abort

------------------------------------------
Logger: ld2410_ble.ld2410_ble
Source: runner.py:128 
First occurred: 20:07:47 (4 occurrences) 
Last logged: 20:08:56

HLK-LD2410B_EE2A: Device unexpectedly disconnected; RSSI: None

Additional information

No response

[home-assistant[bot]]

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` Change the title of 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)}}

[ChrisThomas42]

Just received my HLK-LD2410Bs (still waiting for Cs to arrive) from China and am having the same connectivity issues. The HLKRadarTool identifies and connects to the device. HA discovers the device but as reported above fails to connect.

Firmware reported by HLKRadarTool is V 1.07.22091516.

[david-collett]

FWIW, I also had the same issue near my hass instance with BT adapter. However I then powered it on in another room containing an esp32 esphome (2022.12.8) active bluetooth proxy and it connected and worked via that!

[felix63]

FWIW, I also had the same issue near my hass instance with BT adapter. However I then powered it on in another room containing an esp32 esphome (2022.12.8) active bluetooth proxy and it connected and worked via that!

If I try that I get an 'Unknown issue'

[david-collett]

hmm, well I powered mine off and back on again (still near the BT proxy) and its now unavailable :(

[tunip]

When my HLK-LD2410B is no longer available (e.g. after restarting the Bluetooth Proxy), I need to restart Home Assistant. After that my HLK-LD2410B is back online (until next restart of the Bluetooth Proxy).

[ryny24]

I have also noticed, if my HLK-LD2410C goes "unavailable", I delete it, restart Home Assistant, and it is detected again. Next time I will just restart Home Assistant.

[panhans]

I am facing the same disconnect till ha restart issue. LD2410 disconnects and falls back to pairing mode. Home assistant doesn't hold connection and is not able to repair until it gets restarted.

[david-collett]

hmm, well I powered mine off and back on again (still near the BT proxy) and its now unavailable :(

I can confirm that simply restarting home assistant makes mine available again.

[HausnerR]

I have same issue. After enabling ld2410_ble logs I capture this: ld2410_ble.log

I have two bluetooth proxies at home (Home air quality sensor and Home BLE gateway), 5 passive LYWSD03MMC and one LD2410. LD2410 is only BT device I use that needs connection.

Error after which ld2410 integration stopped getting data is:

Failed to connect: No backend with an available connection slot that can reach address CF:91:E2:BB:27:AF was found: The proxy/adapter is out of connection slots; Add additional proxies near this device

There was no available slots because HA disconnects from both proxies (don't know why, I have sometimes EOF like here #87158 so I suspect this).

I think problem is because integration not try to reconnect when free slots come back again. Another idea is that some dummy connection had left and it can't get free slot - but I think first one is more probable.

[nickrout]

Mine keeps going unavailable. Restarting HA fixed it this time. Next time I'll try restarting the integration.

[nununo]

Mine is connected through a Shelly v2. While it seems to successfully connect, it has only one sensor called "Signal strength". This sensor seems to be updated every few minutes. But nothing else gets configured. So it's useless.

[tunip]

@nununo This is expected, because the Shelly v2 is a passive Bluetooth Proxy. To use the full capabilities of the HLK-LD2410B you need an active ESPHome Bluetooth Proxy.

[DJBenson]

Just had some LD2410C's turn up and I've connected them to a M5-Stack Atom Lite which itself is running an active BT proxy and the sensor having initially been detected has gone unavailable. Restarting the Atom or the integration did not bring back the connection but restarting Home Assistant did...briefly...it's gone unavailable again.

[ryny24]

here is some YAML to alert you if the integration locks up. Basically, if the 'motion' gets stuck 'on', it sends an alert. This has been working for me for the past few days. Only once did it get stuck in the 'off' position. It sends me a telegram msg, but you can change the alert to the app notifcations.

- id: test.problem.ld2410c.garage
  alias: 'TEST.PROBLEM.LD2410C.GARAGE'
  trigger:
     platform: state
     entity_id: binary_sensor.garage_ld2410c_motion
     to: 'on'
     for: '00:10:00'
  action:
   - service: telegram_bot.send_message
     data:
      title: "Garage LD2410C Problem"
      message: "The integration is possibly stuck and needs a restart"
      target: "*********"
      disable_notification: True

[hmakmur]

I have the same issue. I find that I need 1 Bluetooth proxy for each LD2410B. The sensor has to be closed to the BT Proxy and I must limit it to 2 active sensors. (Motion and Occupancy). Enabling more sensors will cause disconnects. It seems that BT Proxy got flooded and crashed which requires restart of HA and power cycling BT Proxy and sensor. I am using Home Bluetooth Proxy which specifically says 3 simultaneous active connections. I wonder if non BT sensor + ESP32 may have less disconnect.

[DJBenson]

I have the same issue. I find that I need 1 Bluetooth proxy for each LD2410B. The sensor has to be closed to the BT Proxy and I must limit it to 2 active sensors. (Motion and Occupancy). Enabling more sensors will cause disconnects. It seems that BT Proxy got flooded and crashed which requires restart of HA and power cycling BT Proxy and sensor. I am using I use ESP Home Bluetooth Proxy which specifically says 3 simultaneous active connections. I wonder if non BT sensor + ESP32 may have less disconnect.

I've tried with an M5-Stack Atom Lite which is ESP32-based and had the sensor plugged in (powered) directly from the controller and it still disconnected.

I think you may be onto something with the data flooding issue, these sensors seem excessively "chatty" in terms of how much traffic they generate, hundreds of messages per minute seems the norm - I wonder if they can be quietened down a bit! 😄

[tunip]

I also use a M5-Stack Atom Lite as Proxy.

As workaround I try to reload the occupancy sensor in case if it is unavailable after 30 seconds. I do not need the motion sensor, so I deactivated it in HA. Lets see if it helps temporarily:

alias: ld2410b sensor reload if unavailable
description: ""
trigger:
  - platform: state
    entity_id:
      - binary_sensor.hlk_ld2410b_occupancy
    to: unavailable
    for:
      hours: 0
      minutes: 0
      seconds: 30
condition: []
action:
  - service: homeassistant.reload_config_entry
    target:
      entity_id: binary_sensor.hlk_ld2410b_occupancy
mode: single

[HausnerR]

@tunip are you checked if this automation helps? I tried just moment ago to run reload_config_entry manually when my sensor disappear but I've got error that says integration is unable to unload sensor.

In my case, only full HA restart helps, I don't need to restart proxies or anything else.

[tunip]

@HausnerR for now it helps. Sensor works since 9 am. In the meantime, the automation has triggered 2 times with the following log message: Failed to connect: No backend with an available connection slot that can reach address BB:57:27:DC:80:42 was found: The proxy/adapter is out of connection slots; Add additional proxies near this device

Config entry 'HLK-LD2410B' for ld2410_ble integration not ready yet: Could not find LD2410B device with address BB:57:27:DC:80:42; Retrying in background

Can't say if this is the trigger or action message :-).

First automation trigger was at 10:08 am, second one at 12:11 am:

Lets see the next hours... Let you know

[HausnerR]

@tunip I tried again your workaround and this time it worked! Thanks! It helps me for now!

[racingpassion]

I think the Bluetooth signal on these devices is very poor.

[panhans]

I think the Bluetooth signal on these devices is very poor.

Doesn't matter. Mine is 20cm away from my pi and it disconnects, too. There is definitely something wrong with the integration especially the reconnect logic.

[ChrisThomas42]

My LD2410C have arrived and to the HLKRadarTool they report as LD2410B and in the tool both the B and C variants look identical, at least to me. Also the LD2410C follows the same pattern with the integration as the B, if discovered then fails to connect.

I was watching the output from bluetoothctl in Terminal and the LD2410C appeared, but reported as LD2410B, the device was discovered but when tried to configure got the failed to connect error.

My HA is a Pi4 and I had to place the LD2410(either variant) within about 30cm to get a discovered notification in HA and then it took a minute or more before the discovered message appeared on my Notifications. I'm no expert and I don't know if this means anything, but once discovered the "prompt" on the terminal output changed from "bluetooth" to "LD2410B" and remained until I exited bluetoothctl, may not mean anything but I thought I'd mention it.

When I connect LD2410B or C to a D1Mini and ESPHome and use @rain931215 code, it performs as expected. I haven't yet tried the ESPHome LD2410 sensor with either variant.

Until I spot something different I think the B and C variants use the same chip just package onto a different PCB

[ChrisThomas42]

OK, more observations today. The device discovery seems to be time and distance sensitive? I've been successfull in adding a B and a C to my HA. It took me several attempts to get them recognised, if I tried to configure soon after the notification I got the failed to connect error. However, if I left it for a minute or so then they added successfully, first time I did this was by accident but I repeated it on the second device and it behaved the same. Also need to point out that for discovery I place the devices within 60cm of my HA, any more and I got th failed to connect error.

Regarding distance from HA to device, once discovered I could move the device further away, still not far, no more than 2m and depending and what's between Pi and device, sometimes less. I'm going to have to employ A LOT of proxies to get this work for me. Time to look at Bluetooth Proxies.

So from my experience, it does work but you need to be close for discovery and configuration but can then be moved further away, but not too much.

I hope that helps???

P.S. In the above tests the devices were powered from a USB battery pack ONLY so I could easily move them around.

[Bodge-IT]

OK, took me a while to figure this out. @ChrisThomas42 investigations are spot on. After moving, if the device goes unavailable, you need to reload the device through the integrations screen. It will not re-establish a connection on its own. My LD2410 is now 2m from proxy and 3m from main BT device. Getting good signal indicated by VERY fast detects. Proxy is set to Active not Passive but I don't know which of these works best. If power is cut to the device, you'll need to restart HA after reconnect, a reload wasn't working for me.

UPDATE: I've now turned off the proxy that was close by. The LD2410B (usb powered) still has strong connection to my Bluetooth device (Sabrent BTUB40) about 3 or 4m away, on the floor of the room above. Signal is solid, response is very quick. Amazing device for $4. I've implemented @nickrout's automation but log shows not triggered yet.

[nickrout]

I have an automation now that runs where the device goes unavailable, and reloads the integration. Seems to work well. According to my traces, it runs roughly once or twice a day.

I don't claim to be the best automation writer, but some may find it useful

alias: Reload LD
description: ""
trigger:
  - platform: state
    entity_id:
      - binary_sensor.hlk_ld2410b_6ae9_occupancy
    to: unavailable
condition: []
action:
  - service: homeassistant.reload_config_entry
    data: {}
    target:
      device_id: 786aed8ccd5ca100afe17ceb49018866
mode: single

[galdaka]

Hi I have the same problem. 50 cm from the Rpi4 and it only recognized it for an instant and couldn't match. These types of products and prices are the ones that create a community and those that must be given priority. Thank you very much and greetings

[verschup76]

I have an automation now that runs where the device goes unavailable, and reloads the integration. Seems to work well. According to my traces, it runs roughly once or twice a day.

I don't claim to be the best automation writer, but some may find it useful

alias: Reload LD
description: ""
trigger:
  - platform: state
    entity_id:
      - binary_sensor.hlk_ld2410b_6ae9_occupancy
    to: unavailable
condition: []
action:
  - service: homeassistant.reload_config_entry
    data: {}
    target:
      device_id: 786aed8ccd5ca100afe17ceb49018866
mode: single

Silly question, but the device_id, is that the sensor's device ID?

[nickrout]

Yes it is the sensor's device_id. I made the automation via the HA UI, so I didn't need to know, it was inserted by the UI editor on choosing "device" as the target and then choosing the correct device :)

[Blendi]

Hello,

I have the same issue and even though I reload the integration the device still shows in unavailable status. This are the logs I can see. No meter what I try the device won't connect.

Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 383, in async_setup result = await component.async_setup_entry(hass, self) File "/usr/src/homeassistant/homeassistant/components/ld2410_ble/init.py", line 39, in async_setup_entry await ld2410_ble.initialise() File "/usr/local/lib/python3.10/site-packages/ld2410_ble/ld2410_ble.py", line 279, in initialise await self._send_command(CMD_BT_PASS) File "/usr/local/lib/python3.10/site-packages/ld2410_ble/ld2410_ble.py", line 462, in _send_command await self._send_command_while_connected(commands, retry) File "/usr/local/lib/python3.10/site-packages/ld2410_ble/ld2410_ble.py", line 481, in _send_command_while_connected await self._send_command_locked(commands) File "/usr/local/lib/python3.10/site-packages/bleak_retry_connector/init.py", line 447, in _async_wrap_bluetooth_connection_error_retry return await func(*args, **kwargs) File "/usr/local/lib/python3.10/site-packages/ld2410_ble/ld2410_ble.py", line 434, in _send_command_locked await self._execute_command_locked(commands) File "/usr/local/lib/python3.10/site-packages/ld2410_ble/ld2410_ble.py", line 508, in _execute_command_locked assert self._client is not None # nosec AssertionError

[verschup76]

Yes it is the sensor's device_id. I made the automation via the HA UI, so I didn't need to know, it was inserted by the UI editor on choosing "device" as the target and then choosing the correct device :)

It seems to be holding for me - now running for a whole day and a half and 2 reboots 🤞

[Bodge-IT]

@blendi Try these steps:

• check that your LD2410 integration isn't set "Ignored Devices" on integrations page
• remove LD2410 integrations
• restart HA
• move LD2410 to within 1m from BT device (close as poss), use battery if necessary as @ChrisThomas42 suggests
• reload the BT integration
• manually add LD2410 integration if not already picked up by HA

That should get it seen. If not then double check your BT device for known good functionality with HA and maybe remove it and then re-add it after a restart and try the steps again.

If your device is recognised, then move it to it's final destination. At that point you may need to re-load the LD2410 integration to get the connection back.

Mine is about 4m from BT device, any further than that I think you'll have issues. FYI, I have my BT device on a long lead extension away from HA system.

[ChrisThomas42]

@Blendi What BlueTooth device are you using? I've never got anywhere near 4m with just my Pi4. As I mentioned above I've got LD2410B and LD2410C to work, but they need to be paired quite close and I can move them but I've never got more than 2m that last for more than a minute or two.

Which is a shame because they (both the B and C) do seem to work quite well! So I've to look at BlueTooth Proxies to see if I might be able to extend coverage to bedrooms/upstairs.

[Bodge-IT]

@ChrisThomas42 BT direct on PI are not well thought of in HA documentation: https://www.home-assistant.io/integrations/bluetooth/#cypress-based-adapters Rather than worry about proxies, trying out a BT device with extension cable may provide better results

[Blendi]

@ChrisThomas42 I am using the RPi4 on board Bluetooth device with Home assistants but I think you are right the range is ridiculous. For some reason now I don’t see the LD2410C devices in my HomeAssistant even though I have restarted the server, deleted Bluetooth integration and set it up again. Devices are few cm away from RPi4. Could be that because I have close a Zigbee antenna with extension cable there are some interferences. My Ld2410C devices are online because I can connect to them via my iphone app even 10 metters away.

I will see if I can use one esp32 with Bluetooth as a proxy.

By the way I can see my RPi4 on board Bluetooth discovered other devices like my xiaomi ble thermometer.

[nickrout]

LD2410C and esp32 bluetooth proxy definitely works

[Blendi]

@Blendi Try these steps:

• check that your LD2410 integration isn't set "Ignored Devices" on integrations page
• remove LD2410 integrations
• restart HA
• move LD2410 to within 1m from BT device (close as poss), use battery if necessary as @ChrisThomas42 suggests
• reload the BT integration
• manually add LD2410 integration if not already picked up by HA

That should get it seen. If not then double check your BT device for known good functionality with HA and maybe remove it and then re-add it after a restart and try the steps again.

If your device is recognized, then move it to it's final destination. At that point you may need to re-load the LD2410 integration to get the connection back.

Mine is about 4m from BT device, any further than that I think you'll have issues. FYI, I have my BT device on a long lead extension away from HA system.

I tried above suggestions. deleted integrations, set them up again, deleted again Bluetooth and 'LD2410 BLE' integrations, reboot HA on RPi4, set up integrations again. Sometimes it works well but after only 20-30 minutes connection drops and reloading the 'LD2410 BLE' integration does not help. Deleting integration does not help. Rebooting RPi4 helps but again for a connection that drops after 20-30 minutes.

I believe my issue with my RPi4 internal Bluetooth is that it is only 50cm away from my zigbee main antenna and I believe that is causing interferences. I will try 2 other options either connect a supported bluetooth usb dongle to RPi4 with a 2-3 meter extension cable or try our if esp32 bluetooth proxy is also a good fit. ESP32 bluetooth proxy I finally was able to make it work. Now will test it.

[Blendi]

LD2410C and esp32 bluetooth proxy definitely works

Yes I also confirm ESP32 bluetooth proxy works. I connected one of my LD2410C to HA via this Bluetooth Proxy. After restarting my LD2410C, entities become unavailable in my HA. I reloaded the LD2410 BLE integration, but did not help. Deleting and setting up again integration works well. Still testing the connection reliability with the esp32 bluetooth proxy configuration. So far considering my experience, I am not much optimistic :)

[ChrisThomas42]

For my testing, once I've managed to get the LD2410(B and C) integrated into HA, I've never had to remove the BlueTooth or LD2410 integration. However, I have had to move the devices back within the initial "detection range" and then I can move the devices back to "operational position".

Without a BlueTooth proxy though, my operational distance is no more than 3m and then it will drop off, sometimes very quickly, sometimes after a few hours. Leaving devices with detection range they haven't yet dropped off but my battery usually gives up first, 12+ hours.

So my limit is the integrated BlueTooth of my Pi4. I'm still unsure about an external BlueTooth dongle to replace the Pi or have a few BlueTooth Proxies dotted around.

When it works the integration DOES work in my test case, I just have a very limited BlueTooth range with my Pi and I therefore need to extend it by some means...

Specifically what devices have people used as a Bluetooth Integration in HA or as BlueTooth Proxies?

[Bodge-IT]

I have a couple of Shellies+ with the latest firmware running and configured as proxy in HA but not sure how to add new devices through them.

I have the Sabrent BTUB40 on an extension cable 3 or 4m away from my HA (a little 1l HP pc next to some other systems all with USB3), hence the need for the extension cable. The Sabrent seems to be rock solid but I still need to onboard the devices quite close to it before moving them to their destination. The Sabrent was only £7 on amazon, if I was to be rolling out to a house, I would probably buy an adapter with an arial for that benefit of onboarding in situ.

I can't find much info on passive over active proxy config.

[Electronlibre2012]

Specifically what devices have people used as a Bluetooth Integration in HA or as BlueTooth Proxies?

i use ESP32-dev-kit or ESP-WROOM-32 and it works great

Works great, if not considering the disconnections...

[nickrout]

Some random ESP32 dev board I had in a drawer.

[captshadab]

LD2410C and esp32 bluetooth proxy definitely works

Yes I also confirm ESP32 bluetooth proxy works. I connected one of my LD2410C to HA via this Bluetooth Proxy. After restarting my LD2410C, entities become unavailable in my HA. I reloaded the LD2410 BLE integration, but did not help. Deleting and setting up again integration works well. Still testing the connection reliability with the esp32 bluetooth proxy configuration. So far considering my experience, I am not much optimistic :)

90100

[hmakmur]

In a month or so using the LD2410B sensors, with only Occupancy detection is enabled, I find that my sensors occupancy do not get cleared even if the sensor is unplugged. It is stuck to 'clear' when the sensor is acting up. Looks like it hung. Manual reload does not fix it. Unplugging sensor does not fix it. The only fix is to restart HA. A restart will fix the sensor for a few hours and until it gets stuck again. I can rule out BT Proxy. if I power a new never configured sensor, it would get detected using the same BT Proxy almost immediately and HA will ask me to configure it. It seems that LD2410BLE implementation in HA could be the issue and we have not heard from @930913, the code owner yet. I am really hoping this sensor would work. I have a dozen of them and tested 3 of them so far with 3 different BT proxy in 3 different rooms.

[captshadab]

In a month or so using the LD2410B sensors, with only Occupancy detection is enabled, I find that my sensors occupancy do not get cleared even if the sensor is unplugged. It is stuck to 'clear' when the sensor is acting up. Looks like it hung. Manual reload does not fix it. Unplugging sensor does not fix it. The only fix is to restart HA. A restart will fix the sensor for a few hours and until it gets stuck again. I can rule out BT Proxy. if I power a new never configured sensor, it would get detected using the same BT Proxy almost immediately and HA will ask me to configure it. It seems that LD2410BLE implementation in HA could be the issue and we have not heard from @930913, the code owner yet. I am really hoping this sensor would work. I have a dozen of them and tested 3 of them so far with 3 different BT proxy in 3 different rooms.

90100

[jtenniswood]

I had this issue, fixed it by using the iPhone app and reflashing firmware over bluetooth

[ChrisThomas42]

I've got myself a Feasycom FSC-BP119 (CSR8510A10) and can confirm that the operational range extends from 2m (max) to 5m and in my house this compares well with the WiFi performance. So I'm putting the connectivity issues to the poor performance of the Pi Bluetooth.

Still not sure about the Bluetooth LD2410 integration as the UART integration has more functionality. Having said that, if you configure the setting with the HLK Radar app it should then work as you'd like?

More testing after a holiday...

[OzGav]

Interesting commentary here. I am thinking if I have to put a BT proxy that close to the sensor I may as well just connect the sensor directly to the ESP?

[Electronlibre2012]

@OzGav your node will be recognize automaticaly and then you can add your integration of the LD2410 BLE.

the LD2410 BLE connect to the nearest Bluetootht Proxy.

I have some at about 4 or 5m near a BLE proxy, it works great