If you run this command the list command should show you the device. The command line is bluetoothctl part of the bluez package. I am running 16.04 so things might be different. This doesn't happen when its in a broken state. I also have this device - the Cambridge Silicon Radio Bluetooth Dongle. Interesting here is that it states 'Discovery started'. Below is the output after I re-plugged the device. I have to re-plug the USB device or reboot to get things working again. Sensors are not unavailable, but just stop receiving input it seems. I'm running HA on a ProxMox VM on Ubuntu 20.04.My BT adapter is a TP-Link UB400 USB stick, which reports itself as a "Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)".I was using Passive BLE Monitor before and did not have these issues.Haven't really debugged it yet, but after reading this thread I will try the suggested steps and report back when it happens again. HSP/HFP with 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) 3 Failed to set mode: Failed (0x03) for Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) on ubuntu 20. A reboot of HA solves it for a couple of days, then it happens again. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. Integration seems to work fine for a while, then stops receiving data and sensors show as unavailable. Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. Jul 15 22:01:34 pawel_server bluetoothd: Bluetooth management interface 1.14 initializedĪug 06 12:28:04 pawel_server bluetoothd: Can't store name for private addressed device also experiencing issues with BLE since switching to the native BT integration in combination with the Xiaomi BLE integration, which I'm using to monitor my plants. Jul 15 22:01:34 pawel_server bluetoothd: Starting SDP server Jul 15 22:01:34 pawel_server systemd: Started Bluetooth service. Jul 15 22:01:34 pawel_server bluetoothd: Bluetooth daemon 5.48 Jul 15 22:01:33 pawel_server systemd: Starting Bluetooth service. Loaded: loaded (/lib/systemd/system/rvice enabled vendor preset: enabled)Īctive: active (running) since Fri 22:01:34 CEST 3 weeks 2 days ago Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3ĭevice Class: Computer, Desktop workstation No response Anything in the logs that might be useful for us?īD Address: 00:C2:C6:D8:75:83 ACL MTU: 1021:4 SCO MTU: 96:6 Home Assistant Container Integration causing the issueīluetooth Link to integration documentation on our website What version of Home Assistant Core has the issue?Ģ022.8.0 What was the last working version of Home Assistant Core?Ģ022.8.0 What type of installation are you running? Container has the `NET_ADMIN` capability and is running in a `mac_vlan` network. There are no Bluetooth integration errors/warnings in the Logs section. Restarting/recreating the container does not fix the issue. After about a day or two this happened:Īfter deleting the device it does not get re-discovered. is this normal? the issue I cannot bring the dongle up without hciconfig and trying to use bluetoothctl as it is the official tool.After successfully migrating from to the native new Bluetooth integration I've ran into some problems recently. However hcitool and hicconfig are deprecated, but what I use bluetoothctl list, I only get one adaptorĪny idea why all dongles has same address. TX bytes:1606 acl:0 sco:0 commands:92 errors:0īus 002 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)īus 002 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)īus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) RX bytes:1734 acl:0 sco:0 events:92 errors:0 TX bytes:987 acl:0 sco:0 commands:61 errors:0 RX bytes:1154 acl:0 sco:0 events:61 errors:0 Description: Supports all versions of Bluetooth 2.0/1.2/1.1 standard features, wireless headset. Right click and check Bluetooth settings, shows Bluetooth discovery and connections all ticked. USB Stick Bluetooth dongle Cambridge Silicon Radio Ltd. Microsoft Bluetooth enumerator is working properly. Device Manager shows: Generic Bluetooth radio is working properly. BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8 Ran Troubleshooter, updated drivers, already latest installed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |