ble_monitor: [Bug]: WARNING no BT LE capabilities and will be ignored.

What happened?

I am suddenly getting this error - V 8.4.0

WARNING (MainThread) [custom_components.ble_monitor.bt_helpers] hci0 (00:0A:3A:67:D3:1C) have no BT LE capabilities and will be ignored.

I have 2 identical BLE dongles, one is fine the other complains!

May be linked to the latest HA OS update (this is running on a Blue).

Only offering one interface in options

image

Unplugging the working BLE dongle (hci1), results in this

022-03-31 10:14:20 ERROR (Thread-3) [custom_components.ble_monitor] HCIdump thread: OS error (hci1): [Errno 19] error while attempting to bind on interface 1: No such device
2022-03-31 10:14:20 ERROR (Thread-3) [custom_components.ble_monitor] HCIdump thread: Trying to power cycle Bluetooth adapter hci1 00:1A:7D:DA:71:13, will try to use it next scan period.
2022-03-31 10:14:20 ERROR (Thread-3) [custom_components.ble_monitor.bt_helpers] RF kill switch check failed - no data for hci1. Available data: {'hci0': {'idx': 0, 'type': 'bluetooth', 'soft': False, 'hard': False}}
2022-03-31 10:14:20 WARNING (Thread-3) [custom_components.ble_monitor.bt_helpers] hci0 (00:0A:3A:67:D3:1C) have no BT LE capabilities and will be ignored.
2022-03-31 10:14:20 ERROR (Thread-3) [custom_components.ble_monitor.bt_helpers] hci1 seems not to exist (anymore), check BT interface mac address in your settings. Available adapters: {} 

Unplugging the other (it is linked via RJ45/USB extenders) has no log entries as a result in homeassistant log, but it is noted in HA OS logs (first is hci1, second is hci0)

[ 8549.134958] usb 1-1.1.3: USB disconnect, device number 9
[ 8551.917493] usb 1-1.1.3: new full-speed USB device number 10 using xhci-hcd
[ 8613.133750] usb 1-1.3: USB disconnect, device number 4
[ 8615.170548] usb 1-1.3: new full-speed USB device number 11 using xhci-hcd

Sensor type

No response

Relevant log output

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15

Most upvoted comments

I unistalled everthing and changed the USB port of the adapter, and finally it came back. I’m good to go!