Waiting to connect to bluetooth

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bluetoothctl : waiting for bluetoothd #1367

Bluetoothctl : waiting for bluetoothd #1367

Comments

Hardware Environment

System Health

version	core-2021.5.4
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
virtualenv	false
python_version	3.8.9
os_name	Linux
os_version	5.4.83-v7
arch	armv7l
timezone	UTC

Home Assistant Supervisor

host_os	Home Assistant OS 5.13
update_channel	stable
supervisor_version	supervisor-2021.04.3
docker_version	19.03.15
disk_total	13.9 GB
disk_used	3.4 GB
healthy	true
supported	true
board	rpi3
supervisor_api	ok
version_api	ok
installed_addons	File editor (5.3.0), Terminal & SSH (9.1.1)

Description

I just wanted to add a bluetooth keyboard to my installation, in order to use the «Keyboard Remote» integration.
So I installed the «Terminal & SSH» addon, in order to have an access to bluetoothctl for pairing my device.

~ $ bluetoothctl Waiting to connect to bluetoothd. 

And the terminal is stuck here, nothing moves, nothing happens, just waiting.
I see nothing in logs related to bluetooth.

The text was updated successfully, but these errors were encountered:

There hasn’t been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Источник

Не работает Bluetooth

Предположу, что команда «show» покажет вам в выводе «Powered: no». Если это так, то просто скомандуйте «power on».
Если не поможет, то покажите полностью вывод этого самого «show».

[[email protected] ~]$ lsusb Bus 002 Device 005: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller Bus 002 Device 004: ID 0489:e00d Foxconn / Hon Hai Broadcom Bluetooth 2.1 Device Bus 002 Device 003: ID 1c7a:0603 LighTuning Technology Inc. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b223 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [[email protected] ~]$ sudo lshw -businfo [sudo] пароль для mohax: Bus info Device Class Description ==================================================== system HuronRiver Platform (System SKUNumber) bus Emerald Lake memory 128KiB BIOS [email protected] processor Intel(R) Pentium(R) CPU B940 @ 2.00GHz memory 64KiB L1 cache memory 256KiB L2 cache memory 2MiB L3 cache memory 4GiB System Memory memory 4GiB SODIMM DDR3 Synchronous 1333 MHz ( memory DIMM [empty] memory DIMM [empty] memory DIMM [empty] [email protected] generic [email protected]:00:00.0 bridge 2nd Generation Core Processor Family DR [email protected]:00:01.0 bridge Xeon E3-1200/2nd Generation Core Proces [email protected]:01:00.0 display GF119M [GeForce 410M] [email protected]:00:02.0 display 2nd Generation Core Processor Family In [email protected]:00:16.0 communication 6 Series/C200 Series Chipset Family MEI [email protected]:00:1a.0 bus 6 Series/C200 Series Chipset Family USB [email protected] usb1 bus EHCI Host Controller [email protected]:1 bus Integrated Rate Matching Hub [email protected]:1.5 multimedia Lenovo EasyCamera [email protected]:00:1b.0 multimedia 6 Series/C200 Series Chipset Family Hig [email protected]:00:1c.0 bridge 6 Series/C200 Series Chipset Family PCI [email protected]:00:1c.1 bridge 6 Series/C200 Series Chipset Family PCI [email protected]:03:00.0 wlp3s0 network Centrino Wireless-N 1000 [Condor Peak] [email protected]:00:1c.3 bridge 6 Series/C200 Series Chipset Family PCI [email protected]:04:00.0 enp4s0 network RTL8111/8168/8411 PCI Express Gigabit E [email protected]:00:1d.0 bus 6 Series/C200 Series Chipset Family USB [email protected] usb2 bus EHCI Host Controller [email protected]:1 bus Integrated Rate Matching Hub [email protected]:1.3 generic EgisTec_ES603 [email protected]:1.4 communication Broadcom Bluetooth 2.1 Device [email protected]:1.6 generic USB2.0-CRW [email protected]:00:1f.0 bridge HM65 Express Chipset Family LPC Control [email protected]:00:1f.2 storage 6 Series/C200 Series Chipset Family 6 p [email protected]:00:1f.3 bus 6 Series/C200 Series Chipset Family SMB power Smart Battery power TBD by ODM [[email protected] ~]$ inix -n bash: inix: команда не найдена [[email protected] ~]$ inxi -n Resuming in non X mode: xdpyinfo not found. For package install advice run: inxi --recommends Network: Card-1: Intel Centrino Wireless-N 1000 [Condor Peak] driver: iwlwifi IF: wlp3s0 state: down mac: 74:e5:0b:ed:eb:80 Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: f0:de:f1:e7:5d:19 [[email protected] ~]$ inxi -N Resuming in non X mode: xdpyinfo not found. For package install advice run: inxi --recommends Network: Card-1: Intel Centrino Wireless-N 1000 [Condor Peak] driver: iwlwifi Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 [[email protected] ~]$ inxi -nN Resuming in non X mode: xdpyinfo not found. For package install advice run: inxi --recommends Network: Card-1: Intel Centrino Wireless-N 1000 [Condor Peak] driver: iwlwifi IF: wlp3s0 state: down mac: 74:e5:0b:ed:eb:80 Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: f0:de:f1:e7:5d:19 [[email protected] ~]$ rfkill list 0: ideapad_wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: ideapad_bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 3: hci0: Bluetooth Soft blocked: no Hard blocked: no [[email protected] ~]$ 

Bus 005 Device 002: ID 0e5e:6622 Conwise Technology Co., Ltd. CW6622

sudo systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: disabled) Active: active (running) since Пт 2016-10-28 22:22:15 MSK; 5s ago Docs: man:bluetoothd(8) Main PID: 2323 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) CGroup: /system.slice/bluetooth.service └─2323 /usr/lib/bluetooth/bluetoothd окт 28 22:22:15 localhost systemd[1]: Starting Bluetooth service. окт 28 22:22:15 localhost bluetoothd[2323]: Bluetooth daemon 5.42 окт 28 22:22:15 localhost systemd[1]: Started Bluetooth service. окт 28 22:22:15 localhost bluetoothd[2323]: Starting SDP server окт 28 22:22:15 localhost bluetoothd[2323]: Bluetooth management interface 1.13 initialized

hciconfig -a hci0: Type: Primary Bus: USB BD Address: 11:11:11:11:11:11 ACL MTU: 672:3 SCO MTU: 48:1 DOWN RX bytes:445 acl:0 sco:0 events:15 errors:0 TX bytes:63 acl:0 sco:0 commands:15 errors:0 Features: 0xff 0x3e 0x85 0x38 0x18 0x18 0x00 0x00 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: Link mode: SLAVE ACCEPT

sudo hciconfig hci0 up Can't init device hci0: Operation not supported (95)

bluetoothctl [bluetooth]# nnect to bluetoothd. 

Надпись эта висит постоянно, пока не введешь команду quit.
rfkill пишет что блокировки блютуса нет. Ни софтовой, ни железной.
В настройках кед, в секции bluetooth надпись на красном фоне «Адаптеры Bluetooth не найдены».

Поиск в интернете мне не очень помог, нашел только что проблема эта появилась где-то с 14-го года. Вроде бы из-за бага в ядре. Свежих записей не нашел с такой проблемой. Баг починили, или он касается ничтожно малого количества пользователей и я один из счастливчиков? Если нет, то подскажите, кто знает, решение.

Источник

bluetoothctl message «Waiting to connect to bluetoothd. «

You have forgotten to start bluetooth.service.

sudo systemctl start bluetooth 

If you want it to always start, make sure that you enable it.

sudo systemctl enable bluetooth 

Related videos on Youtube

user985675

Updated on September 18, 2022

Comments

Current arch linux My first attempt to use a bluetooth device, a Logitech keyboard. I inserted its dongle in usb port and from instructions on https://wiki.archlinux.org/index.php/bluetooth I did

pacman -S bluez bluez-utils modprobe btusb bluetoothctl Waiting to connect to bluetoothd. Ctrl-C hciconfig hci0 sspmode 0 Can't set Simple pairing mode on hci0: Network is down (100) 

Which network is it referring to? hci0? I can’t create that till I get the MAC address, for which I need bluetoothctl Additionally, I have also tried ‘bluetoothctl -a’ and adding my username to the lp line in /etc/groups, no difference

Источник

Waiting to connect to bluetoothd

I had the same problem. I found a solution on archlinux.org’s forums.

I had to load the kernel module btusb . To test if this will solve the problem for you, run as root :

modprobe btusb systemctl start bluetooth 

then test if bluetoothctl works. If it does you can make this fix permanent by loading the module on boot. To do that on Debian add (as root) the line:

at the end of the file /etc/modules .

You might also want to ask systemd to enable the bluetooth service on boot, in this case execute (as root):

systemctl enable bluetooth 

Solution 2

I had a similar situation (I had already enabled and started the bluetooth service and it used to work fine; the service became dead suddenly).

Restarting the bluetooth service solved it:

sudo systemctl restart bluetooth.service 

Related videos on Youtube

Admin

Updated on September 18, 2022

Comments

I can’t invoke my bluetoothctl anymore. It waits for connections withouth success showing this in the terminal:

[email protected]:~$ bluetoothctl Waiting to connect to bluetoothd. 

Any suggestion how to start the joyful debuging? I am using Debian 9.2. Edit Output of sudo systemctl status bluetooth.service

● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: inactive (dead) Docs: man:bluetoothd(8) 

Источник

Waiting to connect to bluetooth

So this is an odd one. Up until this evening, my Raspbian Lite (Jessie) OS was working just fine with bluetooth.
From the command line, I could just type «bluetoothctl» and it would work just fine. but now for some reason when I run that command, I get the following (currently running through Putty at the moment):

[bluetooth]# nnect to bluetoothd.

A cursory google search tells me the message others in this situation see «waiting to connect to bluetoothd. «
I have no idea why this is happening. I can run «sudo bluetoothctl» and am able to get in through the menus that way. Being a complete newb with debian and raspberry pi, I’m not sure the difference between one version of the command or another. I completely re-flashed from a brand new installation of Raspbian Lite before I forgot about the sudo bluetoothctl command.
Is this normal? Am I missing something? I vaguely remember having to create a file when I originally set things up to ensure it would always boot with bluetooth enabled or something along those lines.. I could be mistaking that for enabling SSH though.
Thoughts?

EDIT 1:
**As a result (potentially of this), my bluetooth keyboard never connects automatically anymore. I’m forced to re-pair it through Putty before it starts working again.

EDIT 2:
When I exit the «sudo bluetoothctl» mode, I notice that I get this:

pi@raspberrypi:~ $ sudo bluetoothctl [NEW] Controller B8:27:EB:B4:CF:4F raspberrypi [default] [NEW] Device 34:C7:31:20:88:45 34-C7-31-20-88-45 [NEW] Device CC:C5:0A:21:C8:3C Bluetooth 3.0 Macro Keyboard [bluetooth]# exit [DEL] Controller B8:27:EB:B4:CF:4F raspberrypi [default] pi@raspberrypi:~ $

I feel that it shouldn’t be «deleting» the controller (since it’s the built-in bluetooth adapter itself). I don’t remember ever noticing it do this before.

Источник