RPi USB Bluetooth adapters
Revision as of 06:37, 3 October 2013 by Wrobell (Added Plugable USB-BT4LE Bluetooth 4.0 USB Adapter to the list of working Bluetooth USB adapters.)
Working Bluetooth adapters
- Asus USBIA-EG (paired with Asus Blutooth Keyboard/Media Center Remote)
- Verified works error-free in Multiple Distros (Openelec, Raspbian, RaspBMC, Xbian) Latest builds eliminate text echo problems.
- Asus BT211 (USB ID 0cf3:3005), works with firmware-atheros package.
- Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) - (USB ID 0a12:0001)
- Example of above is; TOPDIGI UA01 Bluetooth USB Dongle Plug and Play (install bluez package from std repos)
- Tesco own brand 'Technika' Nano Bluetooth Adapter has the Cambridge Silicon Radio chipset and works fine, cost £5.97 at time of posting.
- Hama USB Bluetooth 3.0 adapter (Class 1) ~£10 on amazon.co.uk.
- Another sample: Product ID: 0a12:0001, pictured here: http://www.element14.com/community/message/58288
- RiiTek RT-MWK02+ - comes with a USB Bluetooth adapter that works perfectly for both the RiiTek mini Bluetooth keyboard/mouse and other Bluetooth devices. Tested both on builtin USB and on powered USB hub. There are other RiiTek Bluetooth (and non-Bluetooth wireless) devices on the working list. Bluetooth adapter shows up in lsusb as "0a12:0001 Cambridge Silicon Radio" - this is notable as most other sources of this chipset do not seem to be available in the US.
- ICIDU USB Bluetooth Adapter Class II (Not the mini version) - Works out of the box with Raspbian and RaspBMC. Hot-plugging causes Pi restarts, however leaving it plugged in directly into the pi works fine. Powered USB Hub is advised if hotplugging. ~5 Euro in the Netherlands.
- Sabrent BT-USBT. CSR radio, bluetooth 2.0. Tested with Raspbian
- Azio BTD211. CSR radio, bluetooth 2.1 + EDR. Tested with Raspbian
- Azio BTD-V400. CSR BC8 radio, bluetooth 4.0. Tested with Raspbian using powered USB hub
- D-Link DBT-120, works OK in Raspian. Tested with Sony PS3 keypad.
- D-Link DBT-122, with ID 07d1:f101, using a Broadcom chip
- Note that DBT-122, Rev A (ID 2001:f111) is able to pair with another device but unable to send/receive messages via opened virtual COM-Port (e.g. tried in minicom and cutecom)
- IOGear GBU321 (Broadcom BCM2045 Chipset)
- Works with Raspbian Wheezy directly attached to Raspberry Pi and via powered USB hub.
- Note that some Raspberry Pi users are reporting problems with this device; see section below.
- Trust BT-2400p
- Working well with Raspbian Wheezy directly attached to Raspberry Pi. Using with sma-Bluetooth (SMA Solar Inverter reading software).
- Plugable USB-BT4LE Bluetooth 4.0 USB Adapter
- Used to connect to a NAP.
Working Bluetooth/Wifi Combo adapters
- PLANEX 2 in 1 Micro Size USB Bluetooth3.0 WiFi Combo Adapter - Model number: BT-Micro3H2X
- Cirago Bluetooth 3.0 High Speed & Wi-Fi Combo USB Mini Adapter, Class 2 (BTA7300)
- Lindy USB Bluetooth 3.0 HS + WLAN Adapter, Class 2 (Lindy No.52213)
Problem Bluetooth adapters
- Belkin F8T017. Tested with Raspbian 2012-07-15 and bluez installed with apt-get. When dongle is inserted into Pluscom powered USB hub, my remote PuTTY session scrolls incredibly slowly (testing with ls -R to generate text). Suspect network issue. Lots of errors on dmesg too. Raspberry Pi itself is responsive when using directly. On removal of the device everything goes back to normal.
- Bluetooth "3.0" Dongle. Doesn't work reliably - eg. after some time it will hang and the device will need to be reset using fcntl. The device id is 1131:1004 Integrated System Solution Corp. Bluetooth Device.
- Super Mini Bluetooth 2.0 Dongle. The device is recognized and after installing bluez-firmware you can bring it up with hcitool hci0 up. However whenever you try to pair with any device it will cause kernel panic and lock up the system. Confirmed on Raspbian, RaspBMC. The device is a counterfeit Cambridge Silicon Radio device, probably with several bugs in it causing lockups.
- Broadcom chipset Based Devices, e.g. BCM92045B3
- This is includes the IOGear GBU321 (listed above as working) among others. The device will show up via hciconfig, but reports as "down". The device will timeout after attempting to mount via hciconfig hci0 up". Workarounds linked below have worked for some, but are spotty at best, and may cause side effects:
- Bluetooth with Broadcom chip a no go?,
- Bluetooth TX Timeout Issue,
- Bluetooth dongle only works on usb 1.0 ....
- The best solution for these devices seems to be to return them or throw them away, and go with the ones with a genuine Cambridge Silicon Radio chipset.