BluetoothConnector: disconnecting doesn't seem to be working if not passing --notify under Monterey

weird, i know. but it seems to be the case. whether passing the --disconnect flag or not. adding --notify fixes it, but, well, notification.

About this issue

Original URL
State: open
Created 3 years ago
Comments: 20 (6 by maintainers)

Most upvoted comments

As a workaround in the meantime I am just completely disabling bluetooth. Not ideal, no but if you don’t need it for other things, it works.

Here’s what I use for disabling bluetooth: blueutil Link: https://github.com/toy/blueutil

Good tip there about blueutil, also I found something for you on their issues page - instead of disabling bluetooth you can use their disconnect function which I can confirm is working if you use the following syntax (replace 24-d0-df-85-28-62 with your device’s MAC):

blueutil --disconnect ‘24-d0-df-85-28-62’ --wait-disconnect ‘24-d0-df-85-28-62’

Hopefully this info may assist BluetoothConnector devs with a workaround for their tool also

alphabitnz on Dec 7, 2021

Okay that’s good news then, it means 12.3 probably fixes the issue everyone’s been encountering with disconnections.

lapfelix on Jan 31, 2022

Didn’t mean to close this issue. I could reproduce. Not sure what’s causing the problem here though. IOBluetoothDevice’s closeConnection() just doesn’t seem to do what it’s supposed to do (and returns kIOReturnSuccess!)

lapfelix on Dec 29, 2021