Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
bluetooth_controllers_-_manual_setup [2021/04/30 17:50] – Multiple BT adapters + fix formatting lbrpdx | bluetooth_controllers_-_manual_setup [2023/01/11 07:19] (current) – [Pair Bluetooth Controllers - manual setup] no more blank spaces atari | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ~~NOTOC~~ | + | ====== Pair Bluetooth Controllers - manual setup ====== |
- | ===== Pair Bluetooth Controllers - manual setup ===== | + | |
- | You need to establish a [[access_the_batocera_via_ssh|SSH connection]] or a terminal windows with keyboard to accomblish this further. You can connect your bluetooth controller manually by doing some commands step by step. | + | First ensure that Bluetooth is enabled on your device. First, the line '' |
- | Get started by typing '' | + | Establish an [[: |
- | Now you are in the Bluetooth control unit. Type following commands and confirm every single one with //Enter// | + | Now you are in the Bluetooth control unit. Type following commands and confirm every single one with '' |
- | | + | < |
- | default-agent | + | agent on |
- | power on | + | default-agent |
- | scan on | + | power on |
+ | scan on | ||
+ | </ | ||
- | **Important: | + | Now set the controller in pairing |
- | So you are in Pairing Mode and you likely | + | An example of the output |
- | [bluetooth]# | + | < |
- | | + | [root@BATOCERA / |
- | | + | Agent registered |
- | | + | [bluetooth]# |
+ | Agent is already registered | ||
+ | [bluetooth]# | ||
+ | Default agent request successful | ||
+ | [bluetooth]# | ||
+ | Changing power on succeeded | ||
+ | [bluetooth]# | ||
+ | Discovery started | ||
+ | [CHG] Controller 43: | ||
+ | [NEW] Device E4: | ||
+ | </ | ||
+ | |||
+ | <WRAP center round tip> | ||
+ | If you're having trouble detecting devices, check out the [[: | ||
+ | </ | ||
- | Now we want to connect to our controller. So we type following commands to connect to discovered controller with MAC adress | + | Now we want to connect to our controller. So we type following commands to connect to discovered controller with MAC address |
- | We need to wait a few seconds after entering | + | |
pair E4: | pair E4: | ||
Line 29: | Line 43: | ||
trust E4: | trust E4: | ||
- | + | This would be the output from our example: | |
- | So we see for a example | + | |
| | ||
Line 52: | Line 65: | ||
[CHG] Device E4: | [CHG] Device E4: | ||
| | ||
- | |||
Type '' | Type '' | ||
Type '' | Type '' | ||
Type '' | Type '' | ||
- | |||
If you have multiple Bluetooth adapters on your machine and you want to tell which one is used, you can use the command '' | If you have multiple Bluetooth adapters on your machine and you want to tell which one is used, you can use the command '' | ||
Line 71: | Line 82: | ||
| | ||
[CHG] Controller 90: | [CHG] Controller 90: | ||
- | + | ||
+ | ===== Batocera is automatically pairing a device I don't want it to! ===== | ||
+ | |||
+ | Some devices out there break Bluetooth protocol and are always in " | ||
+ | |||
+ | To work around this, it is possible to pair to only strictly pads. Put your controller into its pairing mode and then run the following: | ||
+ | |||
+ | < | ||
+ | batocera-bluetooth trust-pad | ||
+ | </ | ||
+ | |||
+ | Batocera will explicitly only search for and connect to Bluetooth controllers. This may take a while as it methodically goes through, parses and accepts/ | ||
+ | |||
+ | < | ||
+ | [root@RPI3-BATOCERA / | ||
+ | Pairing 8BitDo M30 gamepad... | ||
+ | Trusting 8BitDo M30 gamepad... | ||
+ | [root@RPI3-BATOCERA / | ||
+ | </ | ||
+ | |||
+ | The Bluetooth controller can now be used with Batocera. | ||
+ | |||
+ | Conversely, the same can be done to connect strictly to audio devices: | ||
+ | |||
+ | < | ||
+ | batocera-bluetooth trust-audio | ||
+ | </ | ||
+ | |||
+ | --> Blacklisting a device in Batocera v33 # | ||
+ | |||
+ | <WRAP center round important> | ||
+ | The functionality of this has been supplanted by '' | ||
+ | </ | ||
+ | |||
+ | There might be some device that is perpetually in pairing mode that you don't want your Batocera machine to connect to (such as your neighbor' | ||
+ | |||
+ | In order to do this via SSH, run the following command: | ||
+ | |||
+ | < | ||
+ | batocera-bluetooth blacklist <device address> <device name> | ||
+ | </ | ||
+ | |||
+ | For example: | ||
+ | |||
+ | FIXME | ||
+ | |||
+ | To show a list of all the currently blacklisted devices: | ||
+ | |||
+ | < | ||
+ | batocera-bluetooth list_blacklistable | ||
+ | </ | ||
+ | |||
+ | To remove a device from the blacklist: | ||
+ | |||
+ | < | ||
+ | batocera-bluetooth unblacklist <device address> | ||
+ | </ | ||
+ | |||
+ | <-- | ||
+ | |||
+ | ===== Using batocera-bluetooth ===== | ||
+ | |||
+ | <WRAP center round todo> | ||
+ | Still needs further investigation/ | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | batocera-bluetooth list Print the list of currently trusted and saved Bluetooth devices. | ||
+ | batocera-bluetooth trust Scan for and trust a new, randomly(?) selected device. Good luck! | ||
+ | batocera-bluetooth trust-pad | ||
+ | batocera-bluetooth trust-audio | ||
+ | batocera-bluetooth starttrust | ||
+ | batocera-bluetooth stoptrust | ||
+ | batocera-bluetooth remove <device address> | ||
+ | batocera-bluetooth save Saves the newly trusted device to memory. | ||
+ | batocera-bluetooth restore | ||
+ | batocera-bluetooth live_devices | ||
+ | </ | ||
+ | |||
+ | --> v33 specific commands# | ||
+ | |||
+ | < | ||
+ | batocera-bluetooth list_blacklistable | ||
+ | batocera-bluetooth blacklist <device address> <device name> | ||
+ | batocera-bluetooth unblacklist <device address> | ||
+ | </ | ||
+ | |||
+ | <-- | ||
- bluetooth_controllers_-_manual_setup.1619797811.txt.gz
- Last modified: 3 years ago
- by lbrpdx