Open m1keil opened 3 months ago
Did you give bluetooth permission to your terminal? (I guess yes, given that you are able to connect a device)
But I doubt that it is related to the headphones ability to pair with multiple devices.
Yes, terminal has bluetooth permission. Tried in both iTerm and the stock terminal.app (which prompted me to allow access to bluetooth before first use).
Let me know if you want me to attempt any further debug steps.
Unfortunately no good ideas what to debug currently. I checked the headphones I have that can pair with two devices and they are displayed connected by blueutil both when audio comes from the mac and from the other device. If you have access to some other bluetooth headphones, especially ones that can pair/connect to multiple devices and you can check if they will be displayed connected. Yes would be suggestion towards an issue with headphones, no towards os/framework, but still a very vague/circumstantial one.
This is just another data point similar to #82.
The device appears in the
--paired
list but will show up as "not connected" and won't appear in the--connected
list even when it is actually connected and visible in the regular MacOS bluetooth devices list.Interestingly enough, doing
--connect <id>
does work and the device connects to the laptop but still appears as "not connected" via blueutil.This seem to be replicated across two different Macbooks (M1 Pro and M2 Pro).
I wonder if this is somehow related to the fact that these headphones support multi-device pairing?