Disable onboard BT use adapter instead?

[blkmajik]

Hey guys I have an rp3 with raspbian Jessie lite. How can I disable the onboard Bluetooth and use a Bluetooth adapter instead?

[ktb]

You don't mention which external Bluetooth adapter you're trying to use, but you can disable the PI3B onboard Bluetooth by adding dtoverlay=pi3-disable-bt on its own line to the file located at /boot/config.txt and then disabling the hciuart systemd service by running sudo systemctl stop hciuart and sudo systemctl disable hciuart.

More information:
viewtopic.php?t=138223
https://github.com/raspberrypi/linux/bl ... ays/README
https://github.com/raspberrypi/linux/bl ... verlay.dts

[blkmajik]

You don't mention which external Bluetooth adapter you're trying to use, but you can disable the PI3B onboard Bluetooth by adding dtoverlay=pi3-disable-bt on its own line to the file located at /boot/config.txt and then disabling the hciuart systemd service by running sudo systemctl stop hciuart and sudo systemctl disable hciuart.

More information:
viewtopic.php?t=138223
https://github.com/raspberrypi/linux/bl ... ays/README
https://github.com/raspberrypi/linux/bl ... verlay.dts

thank you for the response! went ahead and tried it and it works for a little bit but then the keyboard got dropped and picked up again for a bit. Im using the: Plugable USB Bluetooth 4.0 Low Energy Micro Adapter

im getting some errors on startup and not sure if that has to do with anything.

Code: Select all

 ● raspberrypi
    State: degraded
     Jobs: 0 queued
   Failed: 3 units
    Since: Wed 1969-12-31 18:00:01 CST; 47 years 2 months ago
   CGroup: /
           ├─1 /sbin/init
           ├─system.slice
           │ ├─avahi-daemon.service
           │ │ ├─541 avahi-daemon: running [raspberrypi.local
           │ │ └─551 avahi-daemon: chroot helpe
           │ ├─dbus.service
           │ │ └─548 /usr/bin/dbus-daemon --system --address=systemd: --nofork -
           │ ├─home-assistant.service
           │ │ └─824 /srv/homeassistant/homeassistant_venv/bin/python3 /srv/home
           │ ├─cron.service
           │ │ └─544 /usr/sbin/cron -f
           │ ├─lighttpd.service
           │ │ ├─902 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf
           │ │ ├─923 /usr/bin/php-cgi
           │ │ ├─935 /usr/bin/php-cgi
           │ │ ├─936 /usr/bin/php-cgi
           │ │ ├─937 /usr/bin/php-cgi

[ktb]

Unfortunately, the generic name "Plugable USB Bluetooth 4.0 Low Energy Micro Adapter" doesn't really tell me anything about which model Bluetooth adapter you have or what chip that adapter might have.

When you have the USB Bluetooth adapter plugged into your Pi, run the command lsusb and post the output in this thread, please.

Example:

Code: Select all

pi@raspberrypi:~$ lsusb
Bus 001 Device 010: ID 1546:01a7 U-Blox AG 
Bus 001 Device 007: ID 1058:0820 Western Digital Technologies, Inc. My Passport Ultra (WDBMWV, WDBZFP)
Bus 001 Device 009: ID 05ac:1500 Apple, Inc. SuperDrive [A1379]
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The systemd service information you posted with three failed units doesn't really tell me anything. You might get more information about the failing units, by using commands such as:

sudo systemctl list-units --failed

-and-

sudo systemctl status avahi-daemon.service
sudo systemctl status dbus.service
sudo systemctl status home-assistant.service
sudo systemctl status cron.service
sudo systemctl status lighttpd.service

Use the systemctl status command for the actual services which are failing. Then post the output of those commands and we may be able to help you.