Well, you made me look and itās a good thing you did. I fact, I used the ameriDroid one you linked to with the N2 I used before I got the Blue (for which it worked fine), but for the Blue I use this one instead. I switched the Bluetooth dongles, rebooted, but my Flower Care monitors wouldnāt work with it.
I therefore retract my previous statement.
Just ordered one. I see they have a Bluetooth 5.0 version but I stuck with the known working 4.0 version. Iām just using it for presence detection so good 'nuff.
You should check the Odroid forum for known working dongles. In theory all dongles should work, there is no need for a special Odroid dongle. But as reality shows, if you have a non working dongle, the Odroid team is more than supportive and adds all necessary ādriversā to the Odroid repository.
To those that have a bluetooth dongle working on their HA Blueāis there anything you need to do to enable bluetooth? I purchased the dongle that @Groto said works for their Blue. Iāve tried restarting it and even power cycling it and itās doesnāt seem to be registering. Is there something that needs to be added to the configuration.yaml? (Iām trying to get my Switchbots working and they require Bluetooth.)
Iām not really sure how to confirm the HA Blue Odroid is recognizing the USB dongle. Is there anything specific you have to do for it to enable Bluetooth or is it supposed to be truly plug and play?
I had an old Cirago bluetooth dongle laying around, but it didnāt work. Iāve got one of those Techkey dongles on their way. Amz claims itāll be here tomorrow. Iāll report back.
Ah. Thanks. Yep - I see that the controller is there and pairable. Lemme experiment a bit and see if I can figure out why itās not seeing my Switchbot. Iām not using an extension cable, but my Switchbot is about 3 feet from my Odroid.
Iām watching this conversation with interest. I have bluetooth presence detection up and running dandy on my Blue but I recently switched out our phones for Pixel 6ās w/ Android 12 and they are not being recognized by HA bluetooth.
To be honest, Iām not sure if the issue is with Android or HA. All my other devices are recognized.
This is buggering up my presence detection automations a bit though, wifi and gps take too long to register as home.
On another note, @nanobra1n do you happen to know if is there a way the bluetoothctl can be set up as a command line sensor to create a ābluetooth is workingā sensor? Not really an issue now as bluetooth has been pretty solid on my blue, but it used to go down all the time on my old rpi and Iād have to reboot it to get it going. A sensor like this would be nice to automate that.
Hmmm. After rebooting again, the Switchbot integration āseesā my switch. I removed it and re-added it successfully. The switch just wonāt respond.
Do you happen to have MAC randomization turned on on your Pixel? Also unlike iPhones, Android phones donāt do Bluetooth advertisement, which makes them harder to use for Bluetooth presence detection.
I played around with the monitor script on distributed Pi Zeros, but it never worked to my satisfaction with my Android. I am now sticking with wifi presence detection.
I guess scanning the system log bluetooth for error might be a way to approach this, but I havenāt done so. Something like dmesg --level=err,warn | grep bluetooth | wc -l (totally not tried out)
Not sure if itāll last, but Iāve got my Switchbot working now on my Odroid. I opened an SSH session and used bluetoothctl to pair manually.
bluetoothctl pair AA:BB:CC:11:22:33
edit: I spoke too soon. It worked great (faster than I was used to from the Pi) for a bit. Just checked it now and it doesnāt respond. bluetoothctl says itās still paired. Sigh.