Difference between revisions of "Bluetooth keyboard"

From ArchWiki
Jump to: navigation, search
(linking bluetooth)
 
(17 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 
[[Category:Bluetooth]]
 
[[Category:Bluetooth]]
 
[[Category:Keyboards]]
 
[[Category:Keyboards]]
[[ru:Bluetooth Keyboard]]
+
[[ru:Bluetooth keyboard]]
This article describes how to set up a Bluetooth HID keyboard with Arch Linux, bluez version 5.
+
This article describes how to set up a [[Bluetooth]] HID keyboard with Arch Linux, bluez version 5.
  
Start bluetooth service and do
+
== Pairing process ==
  $ bluetoothctl -a
+
  # pair <XX:XX:XX:XX:XX:XX>
+
  # trust <XX:XX:XX:XX:XX:XX>
+
  # connect <XX:XX:XX:XX:XX:XX>
+
  
device should be added as /dev/input/event* and your Xorg should add it automatically if you did not disable such feature.
+
Login to the affected computer by a wired keyboard or by ssh.
  
== Bluetooth Keyboard at Startup ==
+
First, make sure the local BT controller (e.g. a BT dongle the built in BT radio) is recognized:
 +
{{hc|# lsusb|
 +
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
 +
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
 +
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. LAN9500 Ethernet 10/100 Adapter / SMSC9512/9514 Hub
 +
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 +
}}
  
TBD
+
The above output is from a Raspberry-Pi revision 'B' with archlinux-arm and a Keysonic BT Dongle.
 +
 
 +
Start bluetooth service with ''systemctl'', or even better, enable it permanently in the start up process. See [[systemd]].
 +
 
 +
Three items worth remembering:
 +
* BT devices (keyboard) and controllers (dongle) need to be paired once.
 +
* The BT controller needs to be powered up after every boot.
 +
* The BT controller needs to be told to connect to the keyboard after every boot.
 +
 
 +
''Pairing'' is a one time process, required only once. There are BT keyboards sold with a BT dongle which come already paired, but that's not certain.  We will use the {{ic|bluetoothctl}} command from bluez5 to pair our dongle and the keyboard.
 +
 
 +
''Power up'' can be done with {{ic|bluetoothctl}}, or with {{ic|hciconfig}} which is more suitable for scripting. See below.
 +
 
 +
Same for ''connecting'', either {{ic|bluetoothctl}} or {{ic|hcitool}} can be used, the latter is more useful for scripting.
 +
 
 +
We will use {{ic|bluetoothctl}} for the pairing process:
 +
 
 +
{{hc|# bluetoothctl -a|
 +
[bluetooth]#
 +
}}
 +
puts you at the {{ic|[bluetooth]#}} prompt. If you are on a colour console: the word "bluetooth" is in the default colour as long as no devices are available, and blue as soon as required devices and/or controllers have been found.
 +
 
 +
While in ''bluetoothctl'' power up the controller:
 +
{{hc|[bluetooth]# power on|
 +
Changing power on succeeded
 +
[CHG] Controller 06:05:04:03:02:01 Powered: yes
 +
}}
 +
 
 +
Next, tell {{ic|bluetoothctl}} to look only for keyboards, and make that the default agent:
 +
{{hc|[bluetooth]# agent KeyboardOnly|
 +
Agent registered
 +
}}
 +
 
 +
{{hc|[bluetooth]# default-agent|
 +
Default agent request successful
 +
}}
 +
 
 +
Next, put your controller (the local dongle) in ''pairable'' mode:
 +
{{hc|[bluetooth]# pairable on|
 +
Changing pairable on succeeded
 +
}}
 +
 
 +
Next, put your keyboard in an active mode, where it is ''discoverable'', i.e. pairable. Some keyboards have a special button for this on the underside, or require a special key combination to be pressed. See the documentation of your keyboard. Please note that this ''discoverability'' of a device is time limited, some devices are only visible 30 seconds, other for 2 minutes. Your mileage may vary.
 +
 
 +
Next, let the controller scan the BT frequencies for a suitable device:
 +
{{hc|[bluetooth]# scan on|
 +
Discovery started
 +
[CHG] Controller 06:05:04:03:02:01 Discovering: yes
 +
}}
 +
 
 +
After a few seconds the adress of the keyboard should be listed as found. This line will repeat over and over, but won't stop you from entering new commands.
 +
 
 +
Next, actually do the pairing. The address used is the BT-MAC address of the keyboard:
 +
{{hc|[bluetooth]# pair 01:02:03:04:05:06|
 +
Pairing successful
 +
}}
 +
 
 +
Next, make this a trusted device (this allows the device to establish the connection on itself). Again, the BT-MAC address is the address of the keyboard device:
 +
{{hc|[bluetooth]# trust 01:02:03:04:05:06|
 +
Trusted
 +
}}
 +
 
 +
Next and finally connect to the device (keyboard). Again, the BT-MAC address is the address of the keyboard device:
 +
{{hc|[bluetooth]# connect 01:02:03:04:05:06|
 +
Connection successful
 +
}}
 +
 
 +
Done. Leave the {{ic|bluetoothctl}} utility:
 +
[bluetooth]# quit
 +
 
 +
Now the external device (i.e. keyboard) and the USB BT dongle are paired permanently, unless you break the pairing intenionally. This does not mean that the keyboard will connect automatically to your BT device after a boot. ''Power up'' of the controller and ''connecting'' device and controller needs to be done after every startup of your computer.
 +
 
 +
== Manually enabling a Bluetooth Keyboard ==
 +
 
 +
Although the device and the controller are now paired (see above), you need to connect them every time the computer starts.
 +
 
 +
First the BT controller (i.e. BT Dongle) needs to be powered up. This is done with the {{ic|hciconfig}} utility. We assume that you have only one BT device connected, and this one has the symbolic name {{ic|hci0}}.
 +
# hciconfig hci0 up
 +
 
 +
Next, make the connection, now using the {{ic|hcitool}} utility. Make sure that the keyboard is powered up and connectable, i.e. not in a power saving sleep state.
 +
# hcitool cc 01:02:03:04:05:06
 +
 
 +
Your BT keyboard should be useable now, even if an error message ("Can't create connection: Input/output error") is shown. Next we will discuss how to automate this process with [[systemd]].
 +
 
 +
== Automatically enabling a Bluetooth Keyboard ==
 +
 
 +
Remember that you have to pair and trust your device in bluetoothctl to cause autoconnect. Then you can power up your adapter automatically in several ways:
 +
 
 +
'''Custom systemd service file:'''
 +
 
 +
Create a config file {{ic|/etc/btkbd.conf}}
 +
 
 +
{{bc|<nowiki>
 +
# Config file for btkbd.service
 +
# change when required (e.g. keyboard hardware changes, more hci devices are connected)
 +
BTKBDMAC = ''mac_address_of_your_device''
 +
HCIDEVICE = ''hci_device_identifier''
 +
</nowiki>}}
 +
 
 +
{{ic|''mac_address_of_your_device''}} can be found with the {{ic|scan on}} command of the ''bluetoothctl'' utility.
 +
 
 +
{{ic|''hci_device_identifier''}} can be found with:
 +
 
 +
{{hc|# hcitool dev|Devices:
 +
  hci0  06:05:04:03:02:01
 +
}}
 +
 
 +
We are looking for the identifier {{ic|hci0}} in this case. The MAC address shown here is the address of the controller, not the address of the keyboard itself.
 +
 
 +
Next, create a new service file at {{ic|/etc/systemd/system/btkbd.service}}.
 +
 
 +
{{bc|<nowiki>
 +
[Unit]
 +
Description=systemd Unit to automatically start a Bluetooth keyboard
 +
Documentation=https://wiki.archlinux.org/index.php/Bluetooth_Keyboard
 +
Requires=dbus-org.bluez.service
 +
After=dbus-bluez.org.service
 +
ConditionPathExists=/etc/btkbd.conf
 +
ConditionPathExists=/usr/bin/hcitool
 +
ConditionPathExists=/usr/bin/hciconfig
 +
 
 +
[Service]
 +
Type=oneshot
 +
EnvironmentFile=/etc/btkbd.conf
 +
ExecStart=
 +
ExecStart=/usr/bin/hciconfig ${HCIDEVICE} up
 +
# ignore errors on connect, spurious problems with bt? so start next command with -
 +
ExecStart=-/usr/bin/hcitool cc ${BTKBDMAC}
 +
 
 +
[Install]
 +
WantedBy=multi-user.target
 +
</nowiki>}}
 +
 
 +
And then enable this service with systemd's tools.
 +
 
 +
Or '''udev rule:'''
 +
 
 +
Create new file {{ic|/etc/udev/rules.d/10-local.rules}}
 +
 
 +
{{bc|<nowiki>
 +
# Set bluetooth power up
 +
ACTION=="add", KERNEL=="hci0", RUN+="/usr/bin/hciconfig hci0 up"
 +
</nowiki>}}
 +
 
 +
== Troubleshooting ==
 +
{{Expansion|TBD}}
 +
* What if the BT controller does not show up in {{ic|lsusb}} ?
 +
* What if the BT controller is not visible in {{ic|bluetoothctl}} ?
 +
* My BT keyboard still does not work. What to do?
 +
** Check: Does it have power?
 +
** Check: Did it connect to the BT controller? If not, try with another controller or your smart phone.
 +
 
 +
== Xorg ==
 +
Device should be added as {{ic|/dev/input/event*}} and your Xorg should add it automatically if you did not disable such feature.

Latest revision as of 15:58, 21 August 2016

This article describes how to set up a Bluetooth HID keyboard with Arch Linux, bluez version 5.

Pairing process

Login to the affected computer by a wired keyboard or by ssh.

First, make sure the local BT controller (e.g. a BT dongle the built in BT radio) is recognized:

# lsusb
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. LAN9500 Ethernet 10/100 Adapter / SMSC9512/9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The above output is from a Raspberry-Pi revision 'B' with archlinux-arm and a Keysonic BT Dongle.

Start bluetooth service with systemctl, or even better, enable it permanently in the start up process. See systemd.

Three items worth remembering:

  • BT devices (keyboard) and controllers (dongle) need to be paired once.
  • The BT controller needs to be powered up after every boot.
  • The BT controller needs to be told to connect to the keyboard after every boot.

Pairing is a one time process, required only once. There are BT keyboards sold with a BT dongle which come already paired, but that's not certain. We will use the bluetoothctl command from bluez5 to pair our dongle and the keyboard.

Power up can be done with bluetoothctl, or with hciconfig which is more suitable for scripting. See below.

Same for connecting, either bluetoothctl or hcitool can be used, the latter is more useful for scripting.

We will use bluetoothctl for the pairing process:

# bluetoothctl -a
[bluetooth]#

puts you at the [bluetooth]# prompt. If you are on a colour console: the word "bluetooth" is in the default colour as long as no devices are available, and blue as soon as required devices and/or controllers have been found.

While in bluetoothctl power up the controller:

[bluetooth]# power on
Changing power on succeeded
[CHG] Controller 06:05:04:03:02:01 Powered: yes

Next, tell bluetoothctl to look only for keyboards, and make that the default agent:

[bluetooth]# agent KeyboardOnly
Agent registered
[bluetooth]# default-agent
Default agent request successful

Next, put your controller (the local dongle) in pairable mode:

[bluetooth]# pairable on
Changing pairable on succeeded

Next, put your keyboard in an active mode, where it is discoverable, i.e. pairable. Some keyboards have a special button for this on the underside, or require a special key combination to be pressed. See the documentation of your keyboard. Please note that this discoverability of a device is time limited, some devices are only visible 30 seconds, other for 2 minutes. Your mileage may vary.

Next, let the controller scan the BT frequencies for a suitable device:

[bluetooth]# scan on
Discovery started
[CHG] Controller 06:05:04:03:02:01 Discovering: yes

After a few seconds the adress of the keyboard should be listed as found. This line will repeat over and over, but won't stop you from entering new commands.

Next, actually do the pairing. The address used is the BT-MAC address of the keyboard:

[bluetooth]# pair 01:02:03:04:05:06
Pairing successful

Next, make this a trusted device (this allows the device to establish the connection on itself). Again, the BT-MAC address is the address of the keyboard device:

[bluetooth]# trust 01:02:03:04:05:06
Trusted 

Next and finally connect to the device (keyboard). Again, the BT-MAC address is the address of the keyboard device:

[bluetooth]# connect 01:02:03:04:05:06
Connection successful

Done. Leave the bluetoothctl utility:

[bluetooth]# quit

Now the external device (i.e. keyboard) and the USB BT dongle are paired permanently, unless you break the pairing intenionally. This does not mean that the keyboard will connect automatically to your BT device after a boot. Power up of the controller and connecting device and controller needs to be done after every startup of your computer.

Manually enabling a Bluetooth Keyboard

Although the device and the controller are now paired (see above), you need to connect them every time the computer starts.

First the BT controller (i.e. BT Dongle) needs to be powered up. This is done with the hciconfig utility. We assume that you have only one BT device connected, and this one has the symbolic name hci0.

# hciconfig hci0 up

Next, make the connection, now using the hcitool utility. Make sure that the keyboard is powered up and connectable, i.e. not in a power saving sleep state.

# hcitool cc 01:02:03:04:05:06

Your BT keyboard should be useable now, even if an error message ("Can't create connection: Input/output error") is shown. Next we will discuss how to automate this process with systemd.

Automatically enabling a Bluetooth Keyboard

Remember that you have to pair and trust your device in bluetoothctl to cause autoconnect. Then you can power up your adapter automatically in several ways:

Custom systemd service file:

Create a config file /etc/btkbd.conf

# Config file for btkbd.service
# change when required (e.g. keyboard hardware changes, more hci devices are connected)
BTKBDMAC = ''mac_address_of_your_device''
HCIDEVICE = ''hci_device_identifier''

mac_address_of_your_device can be found with the scan on command of the bluetoothctl utility.

hci_device_identifier can be found with:

# hcitool dev
Devices:
   hci0   06:05:04:03:02:01

We are looking for the identifier hci0 in this case. The MAC address shown here is the address of the controller, not the address of the keyboard itself.

Next, create a new service file at /etc/systemd/system/btkbd.service.

[Unit]
Description=systemd Unit to automatically start a Bluetooth keyboard
Documentation=https://wiki.archlinux.org/index.php/Bluetooth_Keyboard
Requires=dbus-org.bluez.service
After=dbus-bluez.org.service
ConditionPathExists=/etc/btkbd.conf
ConditionPathExists=/usr/bin/hcitool
ConditionPathExists=/usr/bin/hciconfig

[Service]
Type=oneshot
EnvironmentFile=/etc/btkbd.conf
ExecStart=
ExecStart=/usr/bin/hciconfig ${HCIDEVICE} up
# ignore errors on connect, spurious problems with bt? so start next command with -
ExecStart=-/usr/bin/hcitool cc ${BTKBDMAC}

[Install]
WantedBy=multi-user.target

And then enable this service with systemd's tools.

Or udev rule:

Create new file /etc/udev/rules.d/10-local.rules

# Set bluetooth power up
ACTION=="add", KERNEL=="hci0", RUN+="/usr/bin/hciconfig hci0 up"

Troubleshooting

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: TBD (Discuss in Talk:Bluetooth keyboard#)
  • What if the BT controller does not show up in lsusb ?
  • What if the BT controller is not visible in bluetoothctl ?
  • My BT keyboard still does not work. What to do?
    • Check: Does it have power?
    • Check: Did it connect to the BT controller? If not, try with another controller or your smart phone.

Xorg

Device should be added as /dev/input/event* and your Xorg should add it automatically if you did not disable such feature.