Rasperry pi bluetooth keyboard - Revision history

Arco at 20:03, 18 January 2013

2013-01-18T20:03:15Z

← Older revision		Revision as of 20:03, 18 January 2013
Line 1:		Line 1:
	== Hardware setup ==		== Hardware setup ==
	----		----
	This howto was tested on 2012-09-18-wheezy-raspbian.img with a Sitecom CN500 dongle and a Motorola keyboard kit.		This howto was tested on 2012-09-18-wheezy-raspbian.img with a Sitecom CN500 dongle and a Motorola keyboard kit.
	----		----

Arco at 19:46, 9 October 2012

2012-10-09T19:46:26Z

← Older revision		Revision as of 19:46, 9 October 2012
Line 1:		Line 1:
	== Hardware setup ==		== Hardware setup ==
	----		----
	~~I verified this setup~~ on 2012-09-18-wheezy-raspbian.img with a Sitecom CN500 dongle and a Motorola keyboard kit.		This howto was tested on 2012-09-18-wheezy-raspbian.img with a Sitecom CN500 dongle and a Motorola keyboard kit.
	----		----
			Attach the bluetooth dongle to the Raspberry. Leave the keyboard powered off for now.

	== Install the needed software ==		== Install the needed software ==
	Please note that the bluez-compat was not used in this howto.		Please note that the bluez-compat was not used in this howto.
Line 16:		Line 18:

	== scan and pair ==		== scan and pair ==
			Turn on the device in pairing mode<br>
	Scan for devices, you should remember the bluetooth address		Scan for devices, you should remember the bluetooth address
	root@raspberrypi:/home/pi# hcitool scan		root@raspberrypi:/home/pi# hcitool scan
	Scanning ...		Scanning ...
	'''00:0F:F6:82:D1:BB''' Motorola Bluetooth Wireless Keyboard		'''00:0F:F6:82:D1:BB''' Motorola Bluetooth Wireless Keyboard
	Now pair the keyboard with the pin. ~~for~~ example 0000.		Now pair the keyboard with the pin. This example uses pin 0000.
	root@raspberrypi:/home/pi# echo '''0000'''\|bluez-simple-agent '''hci0 00:0F:F6:82:D1:BB'''		root@raspberrypi:/home/pi# echo '''0000'''\|bluez-simple-agent '''hci0 00:0F:F6:82:D1:BB'''
	RequestPinCode (/org/bluez/3964/hci0/dev_00_0F_F6_82_D1_BB)		RequestPinCode (/org/bluez/3964/hci0/dev_00_0F_F6_82_D1_BB)
Line 48:		Line 51:
	</pre>		</pre>

	To add an unknown device to udev edit the (non-existing) file /lib/udev/rules.d/62-bluez-hid2hci.rules and append the following line. logitech-hid can also be dell or csr		To add an unknown device to udev edit the (non-existing) file /lib/udev/rules.d/62-bluez-hid2hci.rules and append the following line. The method logitech-hid can also be dell or csr.
	ACTION=="add", ENV{ID_VENDOR}=="'''22b8'''", ENV{ID_MODEL}=="'''093d'''" RUN+="/lib/udev/hid2hci --method '''logitech-hid''' -v $env{ID_VENDOR} -p $env{ID_MODEL} --mode hid"		ACTION=="add", ENV{ID_VENDOR}=="'''22b8'''", ENV{ID_MODEL}=="'''093d'''" RUN+="/lib/udev/hid2hci --method '''logitech-hid''' -v $env{ID_VENDOR} -p $env{ID_MODEL} --mode hid"

Arco at 19:41, 9 October 2012

2012-10-09T19:41:50Z

← Older revision		Revision as of 19:41, 9 October 2012
Line 1:		Line 1:
	== My setup ==		== Hardware setup ==
	I ~~wanted to use~~ a Motorola ~~bluetooth~~ keyboard~~/mouse set on the Raspberry~~.		----
	~~Because a lot of older information is available I tried to merge all information into a new howto~~		I verified this setup on 2012-09-18-wheezy-raspbian.img with a Sitecom CN500 dongle and a Motorola keyboard kit.
			----
	== Install the needed software ==		== Install the needed software ==
			Please note that the bluez-compat was not used in this howto.
			pi@raspberrypi ~ $ sudo -s
			root@raspberrypi:/home/pi# apt-get install bluez python-gobject

	~~$ sudo -s~~		== check hardware ==
	~~# apt-get install bluez python-dbus python-gobject~~

	== ~~scan and pair~~ ==
	Check for bluetooth dongles		Check for bluetooth dongles
	# hcitool dev		root@raspberrypi:/home/pi# hcitool dev
	Devices:		Devices:
	'''hci0''' 00:10:60:A3:5A:AA		'''hci0''' 00:10:60:A3:5A:AA
	Scan for devices		Your bluetooth dongle should be visible. Otherwise you should check the driver or the [[RPi_VerifiedPeripherals\|USB Bluetooth adapters]] page.
	# hcitool scan
			== scan and pair ==
			Scan for devices, you should remember the bluetooth address
			root@raspberrypi:/home/pi# hcitool scan
	Scanning ...		Scanning ...
	'''00:0F:F6:82:D1:BB''' Motorola Bluetooth Wireless Keyboard		'''00:0F:F6:82:D1:BB''' Motorola Bluetooth Wireless Keyboard
	Now pair the keyboard with the pin. for example 0000.		Now pair the keyboard with the pin. for example 0000.
	echo "'''0000'''"\|bluez-simple-agent '''hci0 00:0F:F6:82:D1:BB'''		root@raspberrypi:/home/pi# echo '''0000'''\|bluez-simple-agent '''hci0 00:0F:F6:82:D1:BB'''
	~~To test~~ the keyboard~~, manually connect~~ it.		RequestPinCode (/org/bluez/3964/hci0/dev_00_0F_F6_82_D1_BB)
	~~hidd~~ --connect 00:0F:F6:82:D1:BB		Enter PIN Code: Release
	~~Check~~ the keyboard ~~on the console~~.		New device (/org/bluez/3964/hci0/dev_00_0F_F6_82_D1_BB)
			== Trust the device ==
			The Raspberry should trust the keyboard so it connects after every reboot.
			root@raspberrypi:/home/pi# bluez-test-device trusted 00:0F:F6:82:D1:BB yes
			== Test the device as an input ==
			root@raspberrypi:/home/pi# bluez-test-input connect 00:0F:F6:82:D1:BB
			After a reboot the keyboard should still connect. It's possibe a keystroke is needed to connect. Connection can take a few seconds.

	== ~~Autoconnect~~ ==		root@raspberrypi:/home/pi# hcitool con
	~~Now to make it connect after every reboot~~.		Connections:
	# cd /sys/class/bluetooth		< ACL 00:0F:F6:82:D1:BB handle 41 state 1 lm MASTER AUTH ENCRYPT
	~~# ls~~		== Debugging ==
	~~hci0 '''hci0:41'''~~		If the device isn't working the debugging tool hcidump can help.
	~~# cd~~ hci0\:41		# apt-get install bluez-hcidump
	~~# ls~~
	0005:'''22B8:093D'''.~~0002~~ device ~~input1~~ ~~subsystem~~ ~~uevent~~		If the connection is ok but the device does not respond as an input you can check the real vendor and model:
	~~address features~~ power type
	~~In the above directory the identifier contains the vendor and model. The 0005 is the bluetooth class.~~		root@raspberrypi:/home/pi# ls /sys/class/bluetooth/hci0\:*/
			0005:'''22B8:093D'''.0004 address device features input3 power subsystem type uevent
			<pre>
	ID_VENDOR 22B8		ID_VENDOR 22B8
	ID_MODEL 093D		ID_MODEL 093D
	~~In case of multiple devices you can check the address file.~~		</pre>
	~~On newer bluetooth implementations the udev system is used to connect hid devices.~~
	~~Append the following line to the (non-existing) file~~ /~~lib/udev/rules.d/62-bluez-hid2hci.rules~~

	ACTION=="add", ENV{ID_VENDOR}=="'''22b8'''", ENV{ID_MODEL}=="'''093d'''" RUN+="/~~usr~~/~~sbin~~/hid2hci --method '''logitech-hid''' -v $env{ID_VENDOR} -p $env{ID_MODEL} --mode hid"		To add an unknown device to udev edit the (non-existing) file /lib/udev/rules.d/62-bluez-hid2hci.rules and append the following line. logitech-hid can also be dell or csr
			ACTION=="add", ENV{ID_VENDOR}=="'''22b8'''", ENV{ID_MODEL}=="'''093d'''" RUN+="/lib/udev/hid2hci --method '''logitech-hid''' -v $env{ID_VENDOR} -p $env{ID_MODEL} --mode hid"

	~~I don't know why a trusts file is needed. In several other examples it's used and without it sometimes failed.~~
	~~#hcitool dev~~
	~~Devices:~~
	~~hci0 '''00:10:60:A3:5A:AA'''~~

	~~edit /var/lib/bluetooth/"00:10:60:A3:5A:AA"/trusts~~		== Mouse ==
	~~00:0F:F6:82:D1:BB [all]~~		The mouse uses the same procedure as the keyboard. Only the bluetooth address changes.
			To test the mouse on the console you can use the dreaded gpm
	~~after a reboot~~ the keyboard ~~should connect~~. ~~I have to tap a key~~ on ~~mine to make it connect. Connection takes a few seconds.~~		# apt-get install gpm

	~~== Debugging ==~~
	~~If the device isn't working the debugging tool hcidump can help.~~
	~~# apt-get install bluez-hcidump~~
	~~== Mouse ==~~
	~~The mouse uses the same procedure as the keyboard. Only the vendor/model changes.~~
	~~ACTION=="add", ENV{ID_VENDOR}=="22b8", ENV{ID_MODEL}=="093e" RUN+="/usr/sbin/hid2hci --method logitech-hid -v $env{ID_VENDOR} -p $env{ID_MODEL} --mode hid"~~

	~~to test the mouse on the console you can use the dreaded gpm~~		{{Template:Raspberry Pi}}
	~~# apt-get install gpm~~		[[Category:RaspberryPi]]

Arco at 12:01, 6 October 2012

2012-10-06T12:01:54Z

← Older revision		Revision as of 12:01, 6 October 2012
Line 53:		Line 53:
	If the device isn't working the debugging tool hcidump can help.		If the device isn't working the debugging tool hcidump can help.
	# apt-get install bluez-hcidump		# apt-get install bluez-hcidump
	== Mouse ===		== Mouse ==
	The mouse uses the same procedure as the keyboard. Only the vendor/model changes.		The mouse uses the same procedure as the keyboard. Only the vendor/model changes.
	ACTION=="add", ENV{ID_VENDOR}=="22b8", ENV{ID_MODEL}=="093e" RUN+="/usr/sbin/hid2hci --method logitech-hid -v $env{ID_VENDOR} -p $env{ID_MODEL} --mode hid"		ACTION=="add", ENV{ID_VENDOR}=="22b8", ENV{ID_MODEL}=="093e" RUN+="/usr/sbin/hid2hci --method logitech-hid -v $env{ID_VENDOR} -p $env{ID_MODEL} --mode hid"

Arco at 12:01, 6 October 2012

2012-10-06T12:01:39Z

← Older revision		Revision as of 12:01, 6 October 2012
Line 1:		Line 1:
			== My setup ==
			I wanted to use a Motorola bluetooth keyboard/mouse set on the Raspberry.
			Because a lot of older information is available I tried to merge all information into a new howto
	== Install the needed software ==		== Install the needed software ==

Line 9:		Line 11:
	# hcitool dev		# hcitool dev
	Devices:		Devices:
	'''hci0''' 00:10:60:A3:5A:FB		'''hci0''' 00:10:60:A3:5A:AA
	Scan for devices		Scan for devices
	# hcitool scan		# hcitool scan
	Scanning ...		Scanning ...
	'''00:0F:F6:82:D1:E8''' Motorola Bluetooth Wireless Keyboard		'''00:0F:F6:82:D1:BB''' Motorola Bluetooth Wireless Keyboard
	Now pair the keyboard with the pin. for example 0000.		Now pair the keyboard with the pin. for example 0000.
	echo "'''0000'''"\|bluez-simple-agent '''hci0 00:0F:F6:82:D1:E8'''		echo "'''0000'''"\|bluez-simple-agent '''hci0 00:0F:F6:82:D1:BB'''
	To test the keyboard, manually connect it.		To test the keyboard, manually connect it.
	hidd --connect 00:0F:F6:82:D1:E8		hidd --connect 00:0F:F6:82:D1:BB
	Check the keyboard on the console.		Check the keyboard on the console.

Line 41:		Line 43:
	#hcitool dev		#hcitool dev
	Devices:		Devices:
	hci0 '''00:10:60:A3:5A:FB'''		hci0 '''00:10:60:A3:5A:AA'''

	edit /var/lib/bluetooth/"00:10:60:A3:5A:FB"/trusts		edit /var/lib/bluetooth/"00:10:60:A3:5A:AA"/trusts
	00:0F:F6:82:D1:E8 [all]		00:0F:F6:82:D1:BB [all]

	after a reboot the keyboard should connect. I have to tap a key on mine to make it connect. Connection takes a few seconds.		after a reboot the keyboard should connect. I have to tap a key on mine to make it connect. Connection takes a few seconds.

Arco: Created page with " == Install the needed software == $ sudo -s # apt-get install bluez python-dbus python-gobject == scan and pair == Check for bluetooth dongles # hcitool dev Devices:..."

2012-10-06T11:58:07Z

Created page with " == Install the needed software == $ sudo -s # apt-get install bluez python-dbus python-gobject == scan and pair == Check for bluetooth dongles # hcitool dev Devices:..."

New page

== Install the needed software ==

$ sudo -s
# apt-get install bluez python-dbus python-gobject

== scan and pair ==
Check for bluetooth dongles
# hcitool dev
Devices:
'''hci0''' 00:10:60:A3:5A:FB
Scan for devices
# hcitool scan
Scanning ...
'''00:0F:F6:82:D1:E8''' Motorola Bluetooth Wireless Keyboard
Now pair the keyboard with the pin. for example 0000.
echo "'''0000'''"|bluez-simple-agent '''hci0 00:0F:F6:82:D1:E8'''
To test the keyboard, manually connect it.
hidd --connect 00:0F:F6:82:D1:E8
Check the keyboard on the console.

== Autoconnect ==
Now to make it connect after every reboot.
# cd /sys/class/bluetooth
# ls
hci0 '''hci0:41'''
# cd hci0\:41
# ls
0005:'''22B8:093D'''.0002 device input1 subsystem uevent
address features power type
In the above directory the identifier contains the vendor and model. The 0005 is the bluetooth class.
ID_VENDOR 22B8
ID_MODEL 093D
In case of multiple devices you can check the address file.
On newer bluetooth implementations the udev system is used to connect hid devices.
Append the following line to the (non-existing) file /lib/udev/rules.d/62-bluez-hid2hci.rules

ACTION=="add", ENV{ID_VENDOR}=="'''22b8'''", ENV{ID_MODEL}=="'''093d'''" RUN+="/usr/sbin/hid2hci --method '''logitech-hid''' -v $env{ID_VENDOR} -p $env{ID_MODEL} --mode hid"

I don't know why a trusts file is needed. In several other examples it's used and without it sometimes failed.
#hcitool dev
Devices:
hci0 '''00:10:60:A3:5A:FB'''

edit /var/lib/bluetooth/"00:10:60:A3:5A:FB"/trusts
00:0F:F6:82:D1:E8 [all]

after a reboot the keyboard should connect. I have to tap a key on mine to make it connect. Connection takes a few seconds.

== Debugging ==
If the device isn't working the debugging tool hcidump can help.
# apt-get install bluez-hcidump
== Mouse ===
The mouse uses the same procedure as the keyboard. Only the vendor/model changes.
ACTION=="add", ENV{ID_VENDOR}=="22b8", ENV{ID_MODEL}=="093e" RUN+="/usr/sbin/hid2hci --method logitech-hid -v $env{ID_VENDOR} -p $env{ID_MODEL} --mode hid"

to test the mouse on the console you can use the dreaded gpm
# apt-get install gpm