-
Notifications
You must be signed in to change notification settings - Fork 54
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
‘blueutil --paired’ Failed to display the connected mouse. #82
Comments
Does it show up in the list of connected ( |
Can you try giving bluetooth permission (Settings > Privacy > Bluetooth) to your terminal and relaunching it? |
Thank you for your help, after this operation again it is normal. But before authorizing the terminal, using blueutil to switch on and off bluetooth works, other bluetooth devices can be detected, but only this logitech mouse can't be detected, it's really a bit strange. |
It is not the first report about problems caused by bluetooth privacy setting, unfortunately I still didn't see it properly documented somewhere (so still don't know why only some devices are affected). Also privacy constraining works in OSX only on the top application level, so unless blueutil is started directly by launchd (so not terminal/automator/launcher/keyboard shortcut executor), its constraints come from launching application and allowing something needed for one tool in the app makes it allowed for everything launched from that app. |
The model number of the mouse is MX Anywhere 2S
The text was updated successfully, but these errors were encountered: