Virtual Machine and Bluetooth dongle losing connection

Princessalbert · August 8, 2023, 2:36pm

Hello
I have a HA install running on a VM install on my windows workstation.
Used Hyper-V for a long time, until i started experimenting with LD2410B mmwave sensors (to control lights) over Bluetooth and wanted to use my realtek-bluetooth dongle and realized Hyper-V and USB pass-through isn’t working…

So i moved my install to vmware, It seemed fine at first, only thing was that the dongle would disconnect after 1-2 hours and needed to restart the vm to get it working again…

So now I’m on Virtualbox.
It is more stable. but still get the same connection issue as seen below

I tried all sorts of “fixes” like adding adapter after ha is booted, pass-through via USB hub, auto connect hard-coded in vm instance and some other stuff…
Im about to order a new dongle with the home to get a more compatible one (and to get better range).
But before I do i throw this out there to see if anyone of you had similar problems and maybe know of a workaround?

I will try to move to a dedicated machine for HA some day, but for now VM is the way to go.
Already have some docker instances and a plex server so computer is always on anyway.

edjurkowski · August 18, 2023, 7:58pm

I’m having the same issue. I’m running ha on VirtualBox VM. But I had many months of reliable bluetooth connectivity until recently. My host PC is windows pro 10. The bluetooth adapter is a Realtek. I see the following in the log:
Log Details (WARNING)

Logger: bluetooth_auto_recovery.recover
Source: components/bluetooth/util.py:78
First occurred: 3:08:22 PM (117 occurrences)
Last logged: 3:54:47 PM

Bluetooth adapter hci0 [00:00:00:00:00:00] could not be reset:
Closing Bluetooth adapter hci0 [00:00:00:00:00:00] failed: [Errno 9] Bad file descriptor
Could not determine the power state of the Bluetooth adapter hci0 [00:00:00:00:00:00] due to timeout after 5 seconds
Could not cycle the Bluetooth adapter hci0 [00:00:00:00:00:00]: [Errno 110] Operation timed out

Logger: bluetooth_auto_recovery.recover
Source: runner.py:179
First occurred: 3:08:58 PM (30 occurrences)
Last logged: 3:56:27 PM

Bluetooth management socket connection lost: [Errno 22] Invalid argument

I have no solution to date.

krskrab · August 18, 2023, 8:35pm

I added “custom bluetooth tracker” to my HA which is on VM.
Now it was working properly

github.com/home-assistant/core

Bluetooth tracker does not work with newer python - Can't run HA Core on python 3.11.2 because of dependency to pybluez==0.22

opened 06:04PM - 03 Mar 23 UTC

ferinelo

problem in dependency waiting-for-upstream integration: bluetooth_tracker

### The problem I created new venv with python 3.11.2, installed HA Core 2023.3….1 there and run hass --script check_config I have a bluetooth tracker enabled in my configuration. HA tries to install pybluez==0.22 and fails with error: ``` gcc -pthread -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fno-semantic-interposition -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free -ljemalloc -DTHREAD_STACK_SIZE=0x100000 -fPIC -I./port3 -I/srv/homeassistant_3.11.2/include -I/usr/local/include/python3.11 -c bluez/btmodule.c -o build/temp.linux-armv7l-cpython-311/bluez/btmodule.o bluez/btmodule.c: In function ‘PyInit__bluetooth’: bluez/btmodule.c:2837:22: error: lvalue required as left operand of assignment 2837 | Py_TYPE(&sock_type) = &PyType_Type; | ^ bluez/btmodule.c:2838:29: error: lvalue required as left operand of assignment 2838 | Py_TYPE(&sdp_session_type) = &PyType_Type; | ^ error: command '/usr/bin/gcc' failed with exit code 1 [end of output] ``` With python 3.10.9 I had no issue at all (currently running venv). I managed to install pybluez from source/github, however this did not solve the issue. Seems like device_tracker integration requires pybluez==0.22 and forces HA to install this version, which is not compatible with python 3.11. I failed to migrate to venv python 3.11 because of this issue. ### What version of Home Assistant Core has the issue? 2023.3.1 ### What was the last working version of Home Assistant Core? 2023.3.1 ### What type of installation are you running? Home Assistant Core ### Integration causing the issue Bluetooth Tracker ### Link to integration documentation on our website https://www.home-assistant.io/integrations/bluetooth_tracker/ ### Diagnostics information _No response_ ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? ```txt gcc -pthread -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fno-semantic-interposition -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free -ljemalloc -DTHREAD_STACK_SIZE=0x100000 -fPIC -I./port3 -I/srv/homeassistant_3.11.2/include -I/usr/local/include/python3.11 -c bluez/btmodule.c -o build/temp.linux-armv7l-cpython-311/bluez/btmodule.o bluez/btmodule.c: In function ‘PyInit__bluetooth’: bluez/btmodule.c:2837:22: error: lvalue required as left operand of assignment 2837 | Py_TYPE(&sock_type) = &PyType_Type; | ^ bluez/btmodule.c:2838:29: error: lvalue required as left operand of assignment 2838 | Py_TYPE(&sdp_session_type) = &PyType_Type; | ^ error: command '/usr/bin/gcc' failed with exit code 1 [end of output] ``` ### Additional information _No response_

ScreenShot_20230818213739

kr0n · March 31, 2024, 1:16pm

Im having the same problem with the built-in bluetooth but it also happens with Zigbee SkyConnect dongle. I’m running Home Assistant OS on VirtualBox in a Intel NUC with Windows 10.

TH3xR34P3R · March 31, 2024, 1:58pm

I set my skyconnect for my VM to port 0001 and remote in the drop down to any to keep it locked to the same port:

and did the same for the intel one that was showing up:

My nuc is running W11 currently. I have yet to retest any bluetooth dongle as I have yet to buy another one after testing the two I had when I was trying to diagnose why they were failing to show up in my VM (will prob go the network proxy route via an esp32 setup instead of usb if I can’t get a usb dongle to work in my setup as they issue was they were getting errored out at the driver level on the host anyway when looking at device manager at the time).