Replies: 2 comments 2 replies
-
I came across this issue this week with my test setup as well! The relevant script already received a fix in the relevant git repository, but unfortunately they have not released it as a package update yet. An alternative to updating line manually is pulling the fixed script directly from the repository:
Then reboot the Pi. Once they release an updated version this file will just be replaced with the fixed version (plus any other changes that they might do until then), so there is nothing else to consider. Either way, thanks for posting this detailed write up! I've pinned it for more visibility. |
Beta Was this translation helpful? Give feedback.
-
This is very useful info. Thank you. Does the external USB dongle provide wider coverage than the built-in BT? |
Beta Was this translation helpful? Give feedback.
-
I have a number of Pi Zero-W deployed around the house each with an external USB Bluetooth dongle so that I can use both the BluetoothClassic integration on the built-in BT controller and BluetoothLE integration on the USB BT controller.
At some point over the last few month the built-in BT controllers stopped working on all the Pi Zeros. If the USB controller is plugged in after the Zero has booted then both controllers show. This looks due a change in Raspbian committed this year to the /usr/bin/btuart file.
The updated script exits if the onboard controller is already initialised but does this by incorrectly assuming that hci0 is the onboard BT controller which is not true if booted with a USB BT device. This can be fixed by only exiting if the MAC address of the BT controller matches a known address for the Pi Foundation controllers.
So in line 14ish of /usr/bin/btuart change:
to:
This took me a while to figure out so I hope it helps someone else.
Beta Was this translation helpful? Give feedback.
All reactions