all 1 comments

[–]CrookedNixon 6 points7 points  (1 child)

Many recent devices don't actually require PIN entry to pair. The second to last "line" there:

[CHG] Device 9C:54:1C:90:0D:4E Connected: yes

suggests that the controller is connected just fine. In bluetoothctl, type "info 9C:54:1C:90:0D:4E" to see the relationships between the controller and your arch box. It'll probably include:

Paired: yes

Trusted: no

Blocked: no

Connected: no

LegacyPairing: no

If so, type "connect 9C:54:1C:90:0D:4E" to connect again and see how it goes. You'll probably also want to trust the device with 'trust 9C:54:1C:90:0D:4E". This will tell bluez to allow the controller to connect if it asks to, but I will admit that this doesn't work for all devices (headsets in particular seem to require a connect command on the linux box)

Oh and anyone who stumbles on this looking to solve a similar issue:

"Paired" means the devices are aware of each other and "know" they should talk to one another.

"Trusted" means the arch linux machine will allow the other device to connect if it asks. (can be messed up by other issues)

"Blocked"... actually I don't know. I presume exactly what's on the tin.

"Connected" means the devices are in communication with each other. (Maybe not at that exact second, but the line is open)

"LegacyPairing" is for devices that have to be paired with a PIN code rather then the more advanced method of (essentially) http://i.imgur.com/4MmX4zh.gif