![]() This doesn't happen when its in a broken state. 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. A reboot of HA solves it for a couple of days, then it happens again. Integration seems to work fine for a while, then stops receiving data and sensors show as unavailable. ![]() 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 Pick Generic Bluetooth Adaptor in place of CSR. Jul 15 22:01:34 pawel_server systemd: Started Bluetooth service. By default it will be set as a Generic Bluetooth Radio, but you need to select Generic Bluetooth Adapter. 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. And when the drivers weren't installed the light in the dongle would light but now that the drivers are installed it doesnt.After successfully migrating from to the native new Bluetooth integration I've ran into some problems recently. So you can use this keyword on Google to find related information and users having similar issues with the Bluetooth adapter. Then I tried to disable and enable it in Safe Mode and it disabled and enabled it. Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) The 0a12:0001 part is the most important part, because it is the ID of the chipset running inside the Bluetooth adapter. I tried again but it caused a BSOD again. I tried to disable the device and I disabled but then when I pressed enable it caused a BSOD. Buy Bluetooth CSR 4.0 USB Dongle Adapter, EKSEN Bluetooth Transmitter of Electronic Signals for Windows 10/8/7/Vista - Plug and Play on Win 8 and Above. I tried to uninstall and reinstall the device as well, it installed again but it still didnt show up. I changed all Bluetooth Services to Automatic. Now my dongle was put in Bluetooth USB category.īut still no bluetooth icon showed to scan and connect with devices. Bluetooth Dongle (HCI mode) Port 2: Dev 13, If 1, ClassWireless, Driver. It found and installed the CSR Bluetooth Device driver. Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 003 Device 002. Then I decided to use an Driver update app called "Driver Easy". I googled for 2 hours to find the drivers because I couldn't find Siyoteam official page for drivers. ![]() The windows couldn't find the driver or even indentfy the device, it showed up as a "Unknown Device" in "Other Devices" category in Device Manager. My desktop pc is running Windows 7 Proffesinal 64bit. I recently bought a Siyoteam Model HK-968 Bluetooth dongle.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |