I’m running HAOS on a VirtualBox VM in Windows on a NUC. As I learned you can’t pass the integrated Bluetooth to the virtual machine so I bought a Bluetooth adapter. The adapter works in windows but when I pass the USB device to the VM I just get errors. I looked it up on Google but all I can find is years old issues on GitHub that all where closed and no fix.
I’m done with my patience. I just want to connect Bluetooth devices to HA. Can someone with a similar setup recommend me the exact hardware they are using? It only has to be available on Amazon Germany.
Maybe I misunderstand but this is the software side of BT integration, right? I’m looking for the hardware side. Can’t integrate Bluetooth if I don’t have Bluetooth, no?
I asked because the Bluetooth proxy only supports BLE (as far as I know). Seems the Govee thermometers work with this, since you don’t want to say what the LED-strips are I am sure you can google those yourself.
Yes to both. I prefer these since they look a bit nicer and don’t have exposed pins, but both will work just fine. You can find them on other websites too. Buy multiple so you don’t get gaps in the coverage (for comparison I use 5 for 3 floors).
I tried to find one with some kind of case but all I could find was bare chips or it was 6 times the price. Guess I’ll go with the ones you linked. But that one only mentions IR and WiFi, can’t see anything about BT on the product page. Can I assume an ESP32 always has BT connectivity?
Most of them have, the ones you linked earlier (ESP32 WROOM) have BLE support. If you end up with looking at something else just google the specs and remember that the older ESP8266 do not have BLE.
I bought an Avantree DG45 off Amazon UK that I pass through to my HA VM running on Proxmox. Like you I struggled to find one is HA compatible but the DG45 worked for me. I have several BLE proxies but needed the full stack for something.
The right answer was already provided, as those are faster and can be deployed closer to the needed device location, but answering your original question:
I found multiple closed issues on GitHub about the exact error I get. The oldest are 3 years old. They all have multiple answers from people with the same issue and no solution. They all were closed after 6 months of inactivity with a fix. I guess it’s safe to say that problem can’t be solved.