Bluetooth XDO BT802 BT-802 and ZEXMTE Tutorial Home Assistant 2022.8.7

I recently purchased the XDO BT802 from Amazon. It’s on the list of “Known Working Adapters” on the Bluetooth Integration Page. I had some trouble getting this working on my Raspberry Pi 4 running Raspbian 11 / Bullseye with Home Assistant Core, so while I’m not an expert at either Linux or Bluetooth I thought I’d post how I got this working.

Posts below suggest the ZEXMTE Long Range Bluetooth Adapter has the same chipset, and the process below works for it as well.

You may also find my Xiaomi Mijia LYWSD03MMC Tutorial useful.

Core Problem

The key problem is that Linux requires a “firmware” / aka Driver to get a piece of hardware working. The firmware for this device is not installed in Raspbian by default, so getting it installed is the key. The error message I was getting in the home assistant user interface was

Failed to start Bluetooth: adapter ‘hci0’ not found

The XSO BT802 appears to have a Realtek RTL8761BU chipset. To download the firmware / driver for this chipset ssh into your Raspberry Pi and run the following commands.

cd /lib/firmware/rtl_bt
sudo wget
sudo wget

If you have a different model of Realtek chipset you may find it here or here. If they don’t have the “.bin” extension when you download them you’ll have to reload it.
Ensure Bluetooth is Enabled
sudo nano /boot/config.txt

Make sure the following line is NOT anywhere in the file.


Finding Chipset / Firmware Required

If you’re not sure which driver you need run the command below and look for messages that contain something like the “not found” message below. This should tell you the chipset model and the file you need to find.

dmesg|egrep -i "blu|hci|bt"

[ 1280.353319] bluetooth hci0: Direct firmware load for rtl_bt/rtl8761bu_fw.bin failed with error -2
[ 1280.353343] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8761bu_fw.bin not found

Once you’ve copied the correct driver onto your Pi reboot the pi with the "sudo reboot" command. Run the “dmesg” command from above to verify the firmware has been found and installed.

Install Packages
Installing these OS packages seemed to help reduce error messages in the HA logs.

sudo apt-get install libcap2 libpcap0.8-dev tcpdump
sudo apt-get install bluez*

Disable Built-In Raspberry Pi Bluetooth Adapter

See also the notes under “Disable Built-In Raspberry Pi Bluetooth Adapter 2022.09 and newer” below for an alternate and probably better way to disable bluetooth on startup

This page has a fairly simple method to disable the built in USB adapter.

Update 20221029: the old method didn’t seem to run on startup, I’ve added a new method below. I’m using the init.d method from this page.

First work out which adapter you want to disable. For me it was hci1. In short, you run ‘hciconfig -a’ do find the adapter to disable, then you run ‘hciconfig hci1 down’ to disable that adapter. The page goes on to tell you how to automate this with SystemD.


  1. hciconfig -a

Work out which of the bluetooth adapters to disable. In this case I want to disable hci1 which is on the UART bus, rather than hci0 on the USB bus.

hci1:   Type: Primary  Bus: UART
        UP RUNNING
        RX bytes:1616 acl:0 sco:0 events:93 errors:0
        TX bytes:2916 acl:0 sco:0 commands:73 errors:0
        Link policy: RSWITCH SNIFF
        Name: 'XXX'
        Class: 0x2c0000
        Service Classes: Rendering, Capturing, Audio
        Device Class: Miscellaneous,
        HCI Version: 5.0 (0x9)  Revision: 0x156
        LMP Version: 5.0 (0x9)  Subversion: 0x6119
        Manufacturer: Cypress Semiconductor (305)

hci0:   Type: Primary  Bus: USB
        RX bytes:9516 acl:0 sco:0 events:385 errors:0
        TX bytes:32162 acl:0 sco:0 commands:264 errors:0
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'USB'
        Class: 0x2c0000
        Service Classes: Rendering, Capturing, Audio
        Device Class: Miscellaneous,
        HCI Version: 5.1 (0xa)  Revision: 0x9a9
        LMP Version: 5.1 (0xa)  Subversion: 0x8a6b
        Manufacturer: Realtek Semiconductor Corporation (93)
  1. sudo nano /etc/init.d/disable_builtin_bluetooth
  2. Paste the text below in
# Provides:          disable_builtin_bluetooth2
# Required-Start:    $remote_fs $syslog
# Required-Stop:     $remote_fs $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Disable bluetooth on system startup - tw 20221029
# Description:       Disable bluetooth on system startup - tw 20221029
echo "Disabling hci1 bluetooth adapter"
/usr/bin/hciconfig hci1 down &
  1. sudo chmod +x /etc/init.d/disable_builtin_bluetooth
  2. sudo update-rc.d /etc/init.d/disable_builtin_bluetooth defaults
  3. sudo reboot
  4. hciconfig -a

At this point you should only see the bluetooth adapter that you want enabled - parts of the output have been removed for brevity

 hciconfig -a
hci1:   Type: Primary  Bus: UART

hci0:   Type: Primary  Bus: USB

Disable Built-In Raspberry Pi Bluetooth Adapter 2022.09 and newer
As of HA 2022.09 you also seem to see your bluetooth adapters in the HA dashboard. You will need to go in and disable it in there. It was autodetected for me, then I disabled it.


I’m also using a different method to disable Bluetooth on startup on my R.Pi4.

sudo nano /etc/systemd/system/bluetooth-disable.service

Put this into the file

Description=Disable R.Pi4 built in bluetooth on startup



sudo nano /opt/bluetooth/

Put this into the file - you will have to use hciconfig -a to find which hci adapter to disable (the one with bus type UART)

echo "Disabling hci1 built-in bluetooth adapter"
/usr/bin/hciconfig hci1 down &

Finally run this command to run this script every time the server starts

sudo systemctl enable bluetooth-disable.service

USB Extension Cable
I don’t know if this helps at all, but I have put the USB adapter on a 2m extension cable, with the antenna up as high as I could easily get it. I read that some drives in the Pi can cause Bluetooth interference, and it’s also good to keep the adapter away from WiFi antennas. I’ll have a play with this and update at some point.

List USB Connected Devices
This command lists devices plugged into the Pi USB ports. This doesn’t mean the device is working or has a driver / firmware, just that it’s attached and the Pi can see it.

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:a725 Realtek Semiconductor Corp. Bluetooth 5.1 Radio
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

List Bluetooth Devices / Interfaces
This command lists the Bluetooth devices plugged into to the Pi.

hciconfig -a

When I run that command I get the following - with some information redacted / removed for brevity. Given I know my external bluetooth device has a Realtek chipset I can tell that hci0 is the device I need to tell Home Assistant to use. Once you’ve done the step to disable the built in bluetooth above it will look different.

hci1:   Type: Primary  Bus: UART
        BD Address: E4:5F:...  ACL MTU: 1021:8  SCO MTU: 64:1
        UP RUNNING
        Name: '...'
        Service Classes: Rendering, Capturing, Audio
        Manufacturer: Cypress Semiconductor (305)

hci0:   Type: Primary  Bus: USB
        BD Address: 00:E0:...  ACL MTU: 1021:6  SCO MTU: 255:12
        UP RUNNING
        Name: '... #1'
        Manufacturer: Realtek Semiconductor Corporation (93)

List Bluetooth IDs
This seems to list the bluetooth adapter IDs.

hcitool dev
        hci1    E4:5F:01:xx:xx:xx
        hci0    00:E0:42::xx:xx:xx

I don’t really have any idea what this is, but if your output looks much different from mine maybe look into it.

 0 bluetooth hci0   unblocked unblocked
 1 bluetooth hci1   unblocked unblocked

Scan for Bluetooth Devices
This scans for bluetooth devices near you. Before I did this I plugged in a bluetooth receiver, enabled Bluetooth on my Android phone, and hit “add new device” to wake it up. The output is the IDs of the Bluetooth devices near you.

hcitool scan

If your built in bluetooth is enabled the range will be poor and likely nothing or only the closest bluetooth devices will be picked up.

Bluetooth Ping
Once you have device Bluetooth IDs you can ping the devices.

sudo l2ping -c 1 88:54:xx:xx:xx:xx
Ping: 88:54:xx:xx:xx:xx from E4:5F:xx:xx:xx:xx (data size 44) ...
44 bytes from 88:54:xx:xx:xx:xx id 0 time 7.31ms
1 sent, 1 received, 0% loss

You can also choose which Bluetooth device to ping from with the -i switch. I can ping my Android phone from either bluetooth adapter - see the third post in this thread.

l2ping -c 1 -i hci1 88:54:xx:xx:xx:xx
l2ping -c 1 -i hci0 88:54:xx:xx:xx:xx

Rename Bluetooth Broadcast ID

sudo hciconfig hci0 name ‘NewNameHere’


Thanks for posting this. I got this same device (because it is on the list of known working adapters) and I’m having the same issue. I’m on debian but the error is the same and nothing seems to work. I think I already tried your suggestions but I’ll give it another go later. If nothing less, there is some comfort knowing I’m not the only one with this issue.

Thanks @TXSpazz - there’s the old saying that misery loves company! I also hear that you can make BLE to WiFi relays with ESP32, but assembly is required… I might look into that instead if I can’t get this working. I can see in some Amazon reviews that people have gotten it working in Linux and on R.Pi, though I seem to have the rtl8761bu rather than rtl8761b they mention.

Interestingly, I can ping my phone using both the Bluetooth built into my R.Pi4 and also using the USB adapter - the “-i” switch to l2ping lets you choose which to use. However, while this works, I’m getting messages in my Home Assistant log.

l2ping -c 1 -i hci1 88:54:1F:4D:XX:XX
Ping: 88:54:1F:4D:XX:XX from E4:5F:01:7E:XX:XX (data size 44) ...
44 bytes from 88:54:1F:4D:XX:XX id 0 time 43.69ms
1 sent, 1 received, 0% loss

l2ping -c 1 -i hci0 88:54:1F:4D:XX:XX
Ping: 88:54:1F:4D:XX:XX from 00:E0:42:8B:XX:XX (data size 44) ...
44 bytes from 88:54:1F:4D:XX:XX id 0 time 7.49ms
1 sent, 1 received, 0% loss


88:54:1F:4D:XX:XX = Android Phone
E4:5F:01:7E:XX:XX = Raspberry Pi Bluetooth  (hci1)
00:E0:42:8B:XX:XX = USB Bluetooth BT-802 (hci0)

Here’s what’s in my HA log - I haven’t had a chance to look into this yet.

2022-09-01 20:52:31.283 ERROR (SyncWorker_2) [scapy.runtime] Cannot set filter: libpcap is not available. Cannot compile
 filter !
2022-09-01 20:52:31.587 ERROR (SyncWorker_2) [homeassistant.components.dhcp] Cannot watch for dhcp packets without a fun
ctional packet filter: libpcap is not available. Cannot compile filter !
2022-09-01 21:20:20.009 ERROR (MainThread) [homeassistant.components.bluetooth] Error stopping scanner: [org.freedesktop
.systemd1.ShuttingDown] Refusing activation, D-Bus is shutting down.

I’m also seeing email notifications with this

Error stopping scanner: [org.freedesktop.DBus.Error.NoReply] Message recipient disconnected from message bus without replying

OK, so when I try this…

I get “no such file or directory”. I know very little about linux, so I’m lost at that point.

Off the top of my head, try creating the directory like this, then using the sudo wget commands

mkdir -p /lib/firmware/rtl_bt

Might be a difference between Linux distributions or versions. @TXSpazz you should also look around for Debian specific instructions, I found this driver set for example.

I think it’s working… can someone else please test this ideally with a Raspberry Pi?

Thanks for the links to the drivers :heart:
Saved a lot of searching to find right drivers for the ZEXMTE adapter I picked up from Amazon

Installed the 8761b drivers on debian (intel nuc), and all works.

(I had to create the rtl_bt directory)

1 Like

Good to know thanks Pembo. I’ve added that adapter in the subject / post text so others can find this reasonable easily as well :slight_smile:

im still unable to get my Zexmte bluetooth adapter working im running a supervised docker installation ths is what i get when i run hciconfig -a

@Jailbreaker58 I don’t know much about using hardware from docker. I suggest you look at the section above “Finding Chipset / Firmware Required” to see if there are any error messages or useful info in that log. Like I said at the top of this tutorial, I’m not an expert, I just managed to muddle my way through and work it out.

I’ve just updated the tutorial because it wasn’t running the “disable bluetooth” script on startup. I’ve used a new method, which is detailed in the first post.

I am in the process of purchasing a long range bluetooth adapter to replace my NUC integrated one. Was about to buy the ZEXMTE mentionned when I reached your post, make me wonder if it the best choice now…

I understand the command your running but since I’m on Hass OS, I guess those commands needs to be run on the host level which we don’t have SSH access to. Am I right ?

I suspect you’re correct. Some of the other long range cards are the same chipset so be a bit careful what you buy.

This one works well with good range once you get it going.

1 Like