Skip to content
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

Pairing Issues on BigSur (previously working on Mojave) #55

Open
jwignall opened this issue Jun 29, 2021 · 4 comments
Open

Pairing Issues on BigSur (previously working on Mojave) #55

jwignall opened this issue Jun 29, 2021 · 4 comments
Labels

Comments

@jwignall
Copy link

Hey there,

Firstly thank you for making and sharing this tool, I've found it very useful.

I had been using blueutil on Mojave with no problems to pair and unpair devices as needed. However, I just upgraded to BigSur and I'm having issues. Now when I try to pair to device, it no longer connects to it as part of the pairing process. If I run --connect after pairing, it will say it's connected, but I won't see the Bluetooth device in Audio MIDI Setup (it's an audio device), and the device's Bluetooth indicator will not suggest it is connected. e.g.:

  1. blueutil --pair // pairs device, but device will appear in preferences as "not connected" - --info says the same
  2. blueutil --connect // it will say it is connected, but it isn't showing as an audio device
    So right now, I am unable to get a pairing to work via this tool.

What is strange is that if I do the initial pairing manually, it works; I can pair and unpair multiple times. Eventually (not sure what causes it, I think restarting the computer), it will stop working again and I'll need to repair manually. It's all very odd but this never happened on Mojave...

Any help would be much appreciated.

I'm using v2.9.0

@toy
Copy link
Owner

toy commented Jul 3, 2021

Firstly thank you :D

So if I understand correctly pairing using blueutil somehow does the process incomplete. Did you also try disconnecting and connecting back after initial pairing (instead of unpairing/pairing)? And do you have any other similar devices to try?
For now I can't yet help with BigSur.

@toy toy added the bug label Jul 3, 2021
@jwignall
Copy link
Author

jwignall commented Jul 6, 2021

Hi there,

Yeah it seems that way; my expectations from my experiences on Mojave is that --pair should take the device from unpaired to paired and connected, whereas I am just getting paired but not connected, and trying to use --connect doesn't properly complete the process either as my bluetooth device will not show up in Audio MIDI Setup.

I have tried disconnecting and connecting; it works as long as the initial pairing was carried out via the UI and not blueutil. I have tried on two devices and seem the same results each time.

Thanks!

@joaoasilva
Copy link

Hi all,

I'm having the same issues. It connects fine when I pair but after a restart/going to sleep it displays as connected but doesn't work. The only way to fix it again is going to the OS Bluetooth GUI, unpair and pair again.
I'm using a bluetooth keyboard (Logitech G613) and a bluetooth mouse (Logitech G603).

Thanks in advance.

@gazsiazasz
Copy link

I have an issue on Monterey with pairing the A1016 Apple Wireless Keyboard.
With running the ./blueutil --pair 00:0A:95:CC:BB:AA 000000 it gives the following output:

Input pin 000000 on "Gábor billentyűzete"
2021-09-21 21:38:19.062 blueutil[2351:47063] IOBluetoothDevicePair BluetoothHCIPINCodeRequestReply - 0
2021-09-21 21:38:19.656 blueutil[2351:47066] -[IOBluetoothDevicePair peerPairingCompleted:withError:]: Calling connectionComplete on IOBluetoothDevicePair. Status: 31
Failed to pair "00:0A:95:CC:BB:AA" with error 0x1f (Unspecified Error)

On the PacketLogger.app it looks like that the Keyboard requests (the keyboard sends the initial PIN code request) a 6 digit PIN, but the computer is replying with a 4 digit PIN (all 0s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants