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 not using additional Bluetooth Adapters #172

Closed
Nam-Ereh-Won opened this issue Jul 15, 2018 · 9 comments
Closed

Pairing not using additional Bluetooth Adapters #172

Nam-Ereh-Won opened this issue Jul 15, 2018 · 9 comments

Comments

@Nam-Ereh-Won
Copy link
Contributor

I purchased a second BT adapter to support more players, but the game doesn't want to use it. If I have either one plugged in it'll use it, but it will only use one if both are connected. The jm_dbus and pair files seem to indicate that it SHOULD pair a controller to whichever adapter has fewer moves on it, but this does not seem to be the case. I've ran the reset bluetooth script, but still getting the same behavior as I repair the controllers. I'm tempted just just reinstall from scratch, but that shouldn't be necessary.

It may be important to note that I'm using two of the same brand and model adapter.

@adangert
Copy link
Owner

I bet both adapters have the same Mac address, you can check if you go to /var/lib/Bluetooth

@Nam-Ereh-Won
Copy link
Contributor Author

Yup, making the dev version of bluez so I have bdaddr and we'll see what happens next.

@Nam-Ereh-Won
Copy link
Contributor Author

Well bdaddr doesn't work with the chipset it uses, but luckily I found another utility to change the MAC on one of them. Could be handy to note that in the documentation, especially when working with cheaper dongles.

@Nam-Ereh-Won
Copy link
Contributor Author

Could be handy to include some troubleshooting tips in the wiki.

@adangert
Copy link
Owner

Added

@nigelkennington
Copy link

How is it possible to know if the controllers are only pairing to one Bluetooth adapter? I'm only able to connect 5 and then my remaining 3 wont connect even after apparently pairing correctly (connecting with a wire and the light going white).

Also, it might be worth mentioning that the instruction "go to /var/lib/Bluetooth" is very unclear for linux newbies. To actually see the mac addresses, you need to do something like this in the terminal:

  1. sudo bash
  2. cd /var/lib/bluetooth
  3. ls

That should give you a list of numbers like this:

00:15:83:F4:A1:B5 00:15:83:FB:C6:7F 00:1A:5D:DA:71:13

That's 3 different mac addresses separated by spaces.

@DrDecagon
Copy link
Contributor

DrDecagon commented Jul 19, 2023

For users looking for another option to solve this problem. bdaddr is not included in debian builds of bluez but bccmd is included. bccmd only works on Cambridge Silicon Radio but according to this site, CSR produces 70% or more of bluetooth chips. bccmd can make the mac address change survive reboots or even change it permanently on chip.

Run hcitool dev to get the list of addresses
Then run sudo bccmd -d hci0 psset -s 0 bdaddr 0x44 0x00 0x66 0x55 0x33 0x00 0x22 0x11 replacing hci0 with the device number you want to change. Use -s 1 to -s 3 to store the address on chip. (highest number has priority)
Then reboot to test changes.

If you have 3 adapters with matching mac addresses, change one of the non-00 values in the mac address command for the next hci device.

@MattMorganMDP
Copy link

MattMorganMDP commented Apr 20, 2024

Also wondering what other troubleshooting can be done when unable to connect more than 12 controllers. Have multiple bluetooth receivers, with different addresses, and all controllers paired. Running of a Rapsberry Pi 5. Can't seem to get more than 12 connections going, though.

@KilianSSL
Copy link

For me, neither bdaddr nor bccmd seem to be installed, despite i have BlueZ installed. Does anyone know why or can recommend another tool to change the mac address?

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

No branches or pull requests

6 participants