Currently as of this post I can’t get any BT adapter to work with my HA instance in virtualbox.
Provided is the current build I have updated to since the issue started:
Core 2024.3.1
Supervisor 2024.03.0
Operating System 12.1
Frontend 20240307.0
I have tried to apply the same fix as my skyconnect, which was to set the USB setting under remote from No to Any to allow consistent initialization even with multi-pan enabled as I do have an aquara door sensor via the matter integration; but that is not working for any of my BT adapters I have on hand.
I have also tried different USB hubs I have on hand as well as changing from 3.0 to 2.0 mode in the VM and even directly plugged into the NUC.
I will retest the adapter on the next update that comes up since the only devices I have at this time that need BT are a Govee Humidity sensor and my two switchbots.
Just wanted to post this up to see if any others are having the same issues at this time with their BT adapters and the current build of HA.
It shows up in the list when plugged in via the USB options but it does not show up in HA when trying to detect it
The broadcomm one is the original one I was using up until this update and the campbrige one is one I just took out of a package I had since I bought it previous and fogot about it to test, neither one shows up being detected in HA.
I am on 7.0.14-161095 build of virtualbox as I also updated to test if an update would help and I have the same issue.
I’ll be swapping the Govee sensor for a sonoff zigbee based one instead and ordered the hub 2 via OZ Smart Things to migrate my switchbots over via matter to HA instead of BT directly.
I don’t have a range issue as they reach just fine from my lounge room all the way to the bathroom where my govee is that I am using for the ceiling fan and dehumidifier control. Its just all of a sudden no BT adapters are showing up as detected with the only change being that of the recent HA update.
Where exactly is it failing to detect it? At an integration level, or at a hardware level?
To verify whether HA is detecting it at hardware level, go to System > Settings > Hardware > All Hardware and see if the device shows up there when you plug it in.
If it is detected, then it must be an integration issue.
Any idea if this started when you updated the OS, or did it start when you updated core?
Maybe something in the logs might help narrow it down. Only change mentioned in OS 12.1 relating to USB was the below, but that was just a revert to fix zwave usb sticks:
Revert USB core changes to workaround Z-Wave stick issues (#3224)
Just to sanity check it I set all the ports to the same as the skyconnect in the VM settings and restarted the host as well as swapped to a 3rd usb hub and still nothing, only the skyconnect and the usb speaker still show up at this time.
Think it was the supervisor update if not the core one that was the recent release that this started for me.
Everything else works as it should at this time its just BT that is having a fit not wanting to detect adapters atm.
The intergration stays as is, it just does not pull data from the device since there is no BT connection so its not erroring out like with the switchbot one.
Ah, understood. Looks like there were some changes to bluetooth in the latest release.
Again, without logs we can only guess. It could indeed be caused by the latest changes, or it could simply be something that got out of whack. Your options are to either downgrade to an earlier release to see if it fixes the issue or else post the relevant logs here.
Let me know what exact logs folks need, I can wait for an update to retest to validate any fixes. BT is not a prio just something I wanted to make sure it works.
Like I said in the mean time I am swapping over to a sonoff zigbee based humidity sensor and ordered the hub 2 for the switchbot bots, I may also in the future order an ESP board (may need a direct link to a suggested one) to see if that works as it should as updates are released in regards to the BT implementation.
You’ll probably find log entries related to bluetooth in Core/Supervisor/Host logs. If not, you might have to dig into the commandline & run something like dmesg | grep -i bluetooth.
For Bluetooth proxy ESP recommendations, any “plain” ESP32 will work according to this, though there’s a recommendation to use a board with Ethernet to improve bluetooth
Ok so I just had this come up after replugging things again (this time into one of the back nuc ports) and setting the ports in the VM settings again to 0001 and Any for all usb devices in the list:
Its the second adapter I had that is now coming up:
So far yes, I have removed the targus (model ACB75A) one completely and am leaving this spare one I have in its place… guess I will have that hub 2 as a backup for the future for matter devices through it from switchbot.
That said I have done probably 50 or so restarts until the adapter had shown up to this point since the HA updates.
edit: I’ll update again if things break and such, least folks can see this thread if they have a similar setup lol
It’s back to failing to intialise the BT intergration as its not detecting the adapter being plugged in… I think I am going to move away from these USB based adapters and test that ESP one when I have the chance and get that hub 2 installed when it arrives with everything else staying on wifi or zigbee.
Update 2:
After getting the switchbot hub 2 setup and working with the bots and its humidity sensor I did some more digging around and it looks like the two usb bt adapters I have are erroring out even in windows 11 on the nuc so there is something wrong with them… I am going to get another USB adapter and a ESP proxy setup when I can to validate the BT passthrough via the VM.
