-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"--disconnect" doesn't work on MacOS Monterey #58
Comments
Hi Tom and thank you for opening the issue. Does the command have success exit code and is there any output at all? |
With |
Heh, I didn't expect it to fix it, but wanted to see if right after disconnection the status is shown as connected or not. The way it was fixed makes me think in direction of something being released to early, worth investigating. But good that it is at least temporarily fixed for you. |
can confirm the same behavior: Macbook Air - M1 blueutil --disconnect '04-fe-a1-a2-fe-f8' --info '04-fe-a1-a2-fe-f8'
address: 04-fe-a1-a2-fe-f8, connected (master, 0 dBm), not favourite, paired, name: "EDIFIER R1280DB", recent access date: 2021-11-16 22:41:13 +0000 |
@fire1ce Thank you for confirming, odd behaviour especially as info outputs that speakers are connected, so they are disconnected right after. |
I also have the same problem with my M1 Mac mini. After upgrading to Monterey, the disconnect feature stopped working. And for me the workaround described above (adding the "--info" part) does not work. Running the command with info added gives the same result as above, but the device will not disconnect: |
@hkuokka Can you please try |
This works perfectly, thank you so much! I've used blueutil and switchaudio-osx together to have a quick keyboard shortcut (done with Keyboard Maestro) to quickly connect and disconnect my AirPods Pro and set my audio input/output correctly. And after upgrading to Monterey this stopped working and I've missed this functionality so much. Blueutil has been by far the fastest and most reliable way of accomplishing what I want and now it works again :) |
This solution works, thanks! |
This works perfectly |
Neither |
"blueutil --recent" and "blueutil --disconnect" don't work in Monterey (among others) Until these are fixed, this patch replaces them with "--paired" and "--wait-disconnect" respectively per: toy/blueutil#63 toy/blueutil#58
I can report that 12.4 on an M1 Max that |
@FantaZZ Is |
@toy I have not try other action,
I do not know why I should disconnect using gui, my purpose is disconnect use cmd line. And I found something maybe useful. So I try this. mac mini m1, macOS 14.6.1 , blueutil 2.10.0 |
@FantaZZ Do you have Bluetooth privacy permission granted for your terminal application (I guess iTerm2)?
This is very odd, when device is found in list of connected or by name, it is connected, paired and has a name, but not when found by address. Just a note that not quoting or quoting address will have no difference, as quoting is a shell feature that doesn't in this case affect the argument that |
@toy Yes, I have given iTrem2 bluetooth permissions, I confirmed in System Setting. |
Hi there,
I am using blueutil to pair my MacBook Pro (2016) on MacOS Monterey with my Google Pixel Buds.
Connecting works perfectly but disconnecting via "blueutil --disconnect f8-0f-f9-ff-93-f9" doesn't do anything.
This worked previously on BigSur.
I am using 2.9.0 of blueutil.
Cheers
Tom
The text was updated successfully, but these errors were encountered: