Bluetooth adapter stops responding every night

[sleek cradle]

I currently have a Bluetooth adapter I'm using in home assistant and have been for the past year or so. As of like a week ago, it seems to just stop working randomly every night. To fix this, I have just been rebooting home assistant fully and then it works again for the next day. Why is this and how can I fix it. Home assistant is fully up to date.

I get this warning when it happenes

Source: runner.py:289
First occurred: 9:35:37 PM (147 occurrences)
Last logged: 9:54:02 PM

Could not reset the power state of the Bluetooth adapter hci0 [00:E0:4C:4A:37:C8] (0) due to timeout after 5 seconds
Adapter with mac address 00:E0:4C:4A:37:C8 has moved to hci1
Could not reset the power state of the Bluetooth adapter hci1 [00:E0:4C:4A:37:C8] (1) due to timeout after 5 seconds
There are no BT controllers present in the system!
Could not find adapter with mac address 00:E0:4C:4A:37:C8 or hci0```

Directley after that, I get this error

Source: /usr/local/lib/python3.13/asyncio/events.py:89
First occurred: 9:36:15 PM (37 occurrences)
Last logged: 9:54:02 PM

hci0 (00:E0:4C:4A:37:C8): Failed to restart Bluetooth scanner: hci0 (00:E0:4C:4A:37:C8): Failed to start Bluetooth: adapter 'hci0' not found; Try power cycling the Bluetooth hardware.
Traceback (most recent call last):
  File "src/habluetooth/scanner.py", line 400, in habluetooth.scanner.HaScanner._async_start_attempt
  File "src/habluetooth/scanner.py", line 401, in habluetooth.scanner.HaScanner._async_start_attempt
  File "src/habluetooth/scanner.py", line 403, in habluetooth.scanner.HaScanner._async_start_attempt
  File "/usr/local/lib/python3.13/site-packages/bleak/__init__.py", line 179, in start
    await self._backend.start()
  File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/scanner.py", line 132, in start
    self._stop = await manager.passive_scan(
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<4 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/manager.py", line 561, in passive_scan
    self._check_adapter(adapter_path)
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/manager.py", line 210, in _check_adapter
    raise BleakError(f"adapter '{adapter_path.split('/')[-1]}' not found")
bleak.exc.BleakError: adapter 'hci0' not found

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

Traceback (most recent call last):
  File "src/habluetooth/scanner.py", line 602, in habluetooth.scanner.HaScanner._async_restart_scanner
  File "src/habluetooth/scanner.py", line 341, in _async_start
  File "src/habluetooth/scanner.py", line 447, in _async_start_attempt
habluetooth.scanner.ScannerStartError: hci0 (00:E0:4C:4A:37:C8): Failed to start Bluetooth: adapter 'hci0' not found; Try power cycling the Bluetooth hardware.```

This may be a proxmox issue. I am getting errors on that around the time the adapter stops working

[flat pasture]

you should try blacklisting the bluetooth driver on proxmox. so that it doesnt try and use the device and put it in a state where it doesn't work for the guest OS. there are sometimes issues with this.

My response on an issue HERE describes how to do it.

it looks like the Bluetooth adaptor is needing to reset for whatever reason and the host OS kernel is trying to initialize it but then the passthrough is reconnecting it to the guest OS but its stuck in semi initialized state so doesn't work correctly.

[sleek cradle]

Awesome! I think I was having a issue with how my backups were working and I just got done with that. Ill add thin in for good measures since Im already messing with stuff right now anyway

Thank you!

[flat pasture]

no worries. hopefully it works out for you 🙂

[sleek cradle]

Thanks, I dont even know how the backups and bluetooth adapter would be related to each other but apparently it magically is. I got to relearn how to adjust all of what I had set up originally witch was just a great time lol

[flat pasture]

updates on both host and guest OS can change how things work on occasion and you have to adapt 🙂

[sleek cradle]

I think it was my fault to start with (I know, shocker) I was doing backups through SMB witch was specifically mentioned to not do but I just assumed it would be fine. That assumption did not age well

[flat pasture]

sending backups to a smb server should be fine

my system has a smb fileshare as one of its backup targets

[sleek cradle]

Its a whole mess how I have it set up. I wont go into too much detail because I dont want to put you to sleep but I do my backups to a PBS server that is a VM on the device and the PBS server has my nas, which is also a VM on the same server, mounted through SMB where it saves its backups. If I was not using PBS, I think it would be fine but I think with how I had it before, it was jumping through too many things at once to work well

Or as of this week, not work at all...

[flat pasture]

this is how we learn, next time you decide to rebuild things you will build it better 🙂

[sleek cradle]

Yep, I just hope I wont need to learn more about it for a while now lol. I feel I have learned enough over the past week or so to last me some time

[flat pasture]

yeah using it for a while will help you build what you need next time.