Event loop stopped before Future completed

[Toukite]

Hello,

I think this is linked to #167, but since I upgraded to Home Assistant OS 5.12 yesterday, I have trouble with my bluetooth temperature sensors.
I don't see any other event that could have cause an issue, before that it was working perfectly well for months.

Now I can see this error multiple times in the logs:
**ERROR (Thread-3) [custom_components.ble_monitor] HCIdump thread: Runtime error while stop scan request on hci0: Event loop stopped before Future completed.**

By reading the previous issue, I didn't really get what was the solution.

Additional info: I am running "pure" HassOS on RPI 4B, so I don't have access to root or to the linux behind or to commands like hcitool, the only command that seems to work is bluetoothctl, with which I already tried to re-enable everything and repair all devices without success.
Another info, I use an external dongle (I identified its mac address by plugging it/unplugging it and by seing the output of bluetoothctl list command, and I set the external one as default controller with bluetoothctl)

Config:

ble_monitor:
  decimals: 1
  period: 60
  log_spikes: False
  use_median: False
  active_scan: False
  hci_interface:
    - 1
    - 0
  batt_entities: True
  discovery: False
  restore_state: False 
  report_unknown: False
  devices:
    - mac: 'xxx'
      name: 'xxx'
      temperature_unit: C

Thanks for the help !

[Ernst79]

There were some issues after a supervisor update recently, which need a full restart of the system. So, not only a restart of HA, but of the entire system.

Could you give this a try first? For most users, this solves the issue.

[Toukite]

Unfortunately, I tried many things before actually submitting this issue, including several hard reboots (core, supervisor, host). No luck yet :(

[Ernst79]

Ok, it was worth to try. I see you have two hci devices configured. Can you change this to the external one only?

and which dongle do you have?

[Ernst79]

With the ssh addon you can get some access to the Linux system, although limited. You might try the following command, not sure it will work

sudo setcap 'cap_net_raw,cap_net_admin+eip' `readlink -f \`which python3.8\`` 

[Toukite]

I have this dongle:
https://www.domadoo.fr/fr/interface-domotique/4947-jeedom-dongle-usb-bluetooth.html

As for the hci device, well the problem is that I have no idea which one is correct since I only have access to bluetoothctl command ... I need to be sure that the external one is taken into account and not the RPI one since I have range issues.

[Toukite]

[Toukite]

I will try to downgrade to HassOS 5.11 tonight in order to confirm that the issue is coming from there. I'll let you know

[Ernst79]

Run the command without sudo. HassOs is already running as root

[Toukite]

I downgraded to 5.11 and everything works fine again

[Ernst79]

Ok, that’s strange. Let m.e have a look at the changes

[Ernst79]

the only thing I suspect is a firmware update for a raspberry (I assume you have a Pi?). I will try installing Home assistant OS myself on a second raspberry pi 3b

[Toukite]

Yes I'm on raspberry pi 4b

[Ernst79]

But I doubt that a firmware update is reverted if you return to 5.11. But I will try. I have just downloaded 5.11

[Toukite]

Issue is on 5.12 not 5.11

[Ernst79]

yes, I know, I want to check myself if it works on 5.11 first, and than do the upgrade