Raspberry bluetooth no default controller available

Raspberry Pi 3 Bluetooth No Controller

Bluetooth is loaded, active and running

$sudo su $apt-get update $apt-get install bluetooth bluez blueman $service bluetooth start $systemctl status bluetooth bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled) Active: active (running) since Tue 2017-09-12 15:38:58 UTC; 1h 51min ago Docs: man:bluetoothd(8) Main PID: 1419 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─1419 /usr/lib/bluetooth/bluetoothd Sep 12 15:38:58 grassberry systemd[1]: Starting Bluetooth service. Sep 12 15:38:58 grassberry bluetoothd[1419]: Bluetooth daemon 5.23 Sep 12 15:38:58 grassberry systemd[1]: Started Bluetooth service. Sep 12 15:38:58 grassberry bluetoothd[1419]: Starting SDP server Sep 12 15:38:58 grassberry bluetoothd[1419]: Bluetooth management interface 1.14 initialized Sep 12 16:39:06 grassberry systemd[1]: Started Bluetooth service. 

Using bluetooth

$bluetoothctl $list => no result $scan on => no default controller 

Modprobe:

$modprobe bcm203x modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could not open moddep file '/lib/modules/4.9.24-v7+/modules.dep.bin' $modprobe btbcm modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could not open moddep file '/lib/modules/4.9.24-v7+/modules.dep.bin' 

Other solutions I found and tried

Hcitool

$hcitool scan Device is not available: No such device 

I tried diff. things and rebooted inbetween: Installing raspberrypi-sys-mods : Raspberry Pi 3 Bluetooth «No default controller available» Upgrading everything:

$sudo apt-get update $sudo apt-get upgrade -y $sudo apt-get dist-upgrade -y $sudo rpi-update 

$sudo hciconfig hci0 up Can't get device info: No such device $hciconfig -a => nothing $sudo systemctl start hciuart.service Job for hciuart.service failed. See 'systemctl status hciuart.service' and 'journalctl -xn' for details. $systemctl status hciuart.service ● hciuart.service - Configure Bluetooth Modems connected by UART Loaded: loaded (/lib/systemd/system/hciuart.service; enabled) Active: failed (Result: exit-code) since Tue 2017-09-12 18:05:05 UTC; 37s ago Process: 1762 ExecStart=/usr/bin/btuart (code=exited, status=1/FAILURE) Sep 12 18:05:05 grassberry btuart[1762]: Initialization timed out. Sep 12 18:05:05 grassberry btuart[1762]: bcm43xx_init Sep 12 18:05:05 grassberry systemd[1]: hciuart.service: control process exited, code=exited status=1 Sep 12 18:05:05 grassberry systemd[1]: Failed to start Configure Bluetooth Modems connected by UART. Sep 12 18:05:05 grassberry systemd[1]: Unit hciuart.service entered failed state. 

Installing pi-bluetooth

$apt-get install pi-bluetooth 

Источник

Fix Bluetooth Problems on Raspberry Pi running Raspberry Pi OS (Raspbian)

20 November 2022 / Raspberry Pi

The Raspberry Pi is a great tool for your home to control other devices and enter the world of home automation. Besides the old and first versions of the Raspberry Pi, the new ones like the Raspberry Pi 3* and the Raspberry Pi 4* come with an integrated WiFi and Bluetooth Low Energy (BLE) module. This allows direct communication with other devices and gets rid of external USB WiFi and Bluetooth dongles. Those who have already worked with the integrated modules know that they have limited capabilities and are sometimes frustrating to use due to unexpected problems. In this article, I will show some solutions to problems that often occur on Raspberry Pi OS (former Raspbain).

Check Bluetooth

First, it should be clear how to check if Bluetooth works and which devices are configured. In the command line, just type bluetoothctl . This should show you a Controller and maybe Bluetooth devices around you. In this [bluetooth]# command line, it is further possible to use other commands like scan on or scan off or get information from other devices with info . Just give it a try!

If Bluetooth isn’t available, start the service with sudo systemctl start bluetooth .

«No default controller available»

After a routine update/upgrade process, Bluetooth stopped working on my Raspberry Pi. bluetoothctl showed «No default controller available» and a restart couldn’t fix the problem. In such a case, hciuart isn’t running. Start it with sudo systemctl start hciuart . In my case, the start failed with the following error:

Job for hciuart.service failed because the control process exited with error code.
See «systemctl status hciuart.service» and «journalctl -xe» for details.

The logs gave me further details:

Since this problem is widely discussed on the internet, the solution that worked for me was just deleting existing Bluetooth software and reinstalling pi-bluetooth as suggested by a user in the Raspberry Pi forum:

$ sudo apt purge bluez $ sudo apt bluez-firmware $ sudo apt purge pi-bluetooth $ sudo apt install pi-bluetooth

After a reboot ( sudo reboot ), everything worked as expected again.

Bluetooth in Docker Container

When working with containerization like docker and docker-compose, things get more interesting and complex.

As suggested in this StackOverflow answer, the best way is to install the relevant packages in the docker container (for example by adding a RUN command to the Dockerfile ): sudo apt install bluez bluetooth

Next, the following two commands have to be executed when the container starts:

$ service dbus start $ bluetoothd &

In order to get it working correctly, the bluetoothd service has to be stopped. I added the following line to my Raspberry Pi crontab with sudo crontab -e : @reboot killall -9 bluetoothd

Save on close the file by typing :wq .

This should help get Bluetooth working in home automatism software like Home Assistant or Homebridge.

References / Footnotes

Raspberry Pi

Malte Hellmeier

Источник

Raspberry bluetooth no default controller available

I’ve been trying to get my bluetooth to work but I don’t even see the icon for it.
When I restart the pi and check the status I get:

pi@raspberrypi:~ $ systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: inactive (dead) Docs: man:bluetoothd(8) pi@raspberrypi:~ $ sudo modprobe btusb pi@raspberrypi:~ $ sudo systemctl start bluetooth.service pi@raspberrypi:~ $ systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Thu 2021-08-26 11:18:10 EDT; 2s ago Docs: man:bluetoothd(8) Main PID: 1444 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) CGroup: /system.slice/bluetooth.service └─1444 /usr/lib/bluetooth/bluetoothd 

I saw somewhere to do the modprobe thing which then makes the bluetooth active until I restart the pi, at which point it just reverts to inactive.
When I turn the bluetooth on I just get a no controller available message:

pi@raspberrypi:~ $ sudo bluetoothctl Agent registered [bluetooth]# power on No default controller available 

pi@raspberrypi:~ $ lspci 00:00.0 PCI bridge: Broadcom Limited Device 2711 (rev 10) 01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) pi@raspberrypi:~ $ lspci -k 00:00.0 PCI bridge: Broadcom Limited Device 2711 (rev 10) Kernel driver in use: pcieport 01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) Subsystem: VIA Technologies, Inc. VL805 USB 3.0 Host Controller Kernel driver in use: xhci_hcd pi@raspberrypi:~ $ lsmod | grep blue bluetooth 376832 11 btrtl,btintel,bnep,btbcm,btusb ecdh_generic 16384 1 bluetooth rfkill 28672 6 bluetooth,cfg80211 pi@raspberrypi:~ $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 258a:0001 Bus 001 Device 003: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical Mouse Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi@raspberrypi:~ $ rfkill list all 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 

I also messed up at some point while troubleshooting and tried this which did not fix anything but messed up my wifi so i no longer get network options to connect to I just get the 2 blue arrows that indicate that I’m connected but when I click on it to change the network I get no interfaces found and eth0 is down.

sudo apt install pulseaudio-module-bluetooth

I would really appriciate if anyone has any idea how to revert it

Источник

Raspberry bluetooth no default controller available

I have purchased three Raspberry Pi 4 devices (Model B 4GB edition). I’m trying to put BlueWave’s Open Auto build on them but each device I’ve tried has the Bluetooth disabled and lists «No Default Controller Available». I can’t believe that all 3 of my devices came with defective Bluetooth controllers. Any assistance would be greatly appreciated! Thank you

Re: Raspberry Pi 4 Bluetooth

Re: Raspberry Pi 4 Bluetooth

If you just run Raspbian Buster with Desktop does the issues still exist ??

If not then ask the Software Developers to support their software.

deepo Posts: 1154 Joined: Sun Dec 30, 2018 8:36 pm Location: Denmark

Re: Raspberry Pi 4 Bluetooth

I’m sure your bluetooth works, it’s just that the software you’re running isn’t set up to work with the bluetooth controller on the Raspberry Pi.

Try booting on Buster and try this:

pi@raspberrypi:~ $ sudo systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Wed 2020-03-11 21:30:09 GMT; 4 days ago Docs: man:bluetoothd(8) Main PID: 473 (bluetoothd) Status: "Running" Tasks: 1 (limit: 2200) Memory: 2.7M CGroup: /system.slice/bluetooth.service └─473 /usr/lib/bluetooth/bluetoothd 

pi@raspberrypi:~ $ sudo bluetoothctl Agent registered [bluetooth]# list Controller B8:27:EB:5F:42:C4 raspberrypi [default] [bluetooth]# show Controller B8:27:EB:5F:42:C4 (public) Name: raspberrypi Alias: raspberrypi Class: 0x00000000 Powered: yes Discoverable: no Pairable: yes UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no [bluetooth]# 

Источник