All people with a such-like problems had different causes apparently then mine, because none of the plentyful of 'tricks' didn't work. I looked throughout the whole google searchable part of the internet to find more information. So I expect there is a bug somewhere in the 64 bit version. When I tried the dongles (I have two of them) on a 32 bit system, everything worked perfectly. I also tried this with the stock bluez/libbluetooth etc and with the newest version from the Blueman PPA repository, also all with the same result. I tried this on 2 (different) 圆4 systems, with the stock kernel (2.6.31-14-generic) and the new 2.6.32-rc5 kernel. This device doesn't work, I always get from the kernel this error: command tx timeout It’s seems to me that it isn’t accessible to dbus on reboot but if I restart dbus it became available but it breaks some things in ha.I tried to connect an usb bluetooth dongle of this type on Ubuntu Karmic on a 64 bit system:īus 006 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) I checked the docs and it says "The Bluetooth adapter must be accessible to D-Bus ". My adapter is recognized by home assistant but I get unsupported system errors. TX bytes:4116 acl:0 sco:0 commands:256 errors:0 I think that for some reason this adapter doesn’t have dbus communication. Bluetooth: BNEP socket layer initialized Bluetooth: BNEP filters: protocol multicast Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: L2CAP socket layer initialized Bluetooth: HCI device and connection manager initialized Integrated Rate Matching Hubīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)īus 002 Device 002: ID c0f4:05e0 SZH usb keyboardīus 002 Device 004: ID 1a86:7523 QinHeng Electronics CH340 serial converterīus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Integrated Rate Matching Hubīus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 001 Device 002: ID 8087:8008 Intel Corp. I removed avahi-daemon from my system but it didn’t changed anything.īus 003 Device 002: ID 8087:8000 Intel Corp. But if it is I don’t know how to fix it.Īfter checking some things I found out that mdns stoped running after I restarted dbus-broker. I’m not sure is this a case, its my guess. In my opinion something problem might be in the dbus socket and its avability to home assistant. Manufacturer: Cambridge Silicon Radio (10) TX bytes:4058 acl:0 sco:0 commands:248 errors:0ĭevice Class: Computer, Desktop workstation If I do hciconfig -a I get his BD Address: 00:1A:7D:DA:71:05 ACL MTU: 310:10 SCO MTU: 64:8 I can’t see in the menu configuration for network interfaces.Īnd I can’t open ssh web terminal because it’s waiting for supervisor to startup. It seems that after reboot bluetooth dongle doesnt work and it’s not recognized in home assistant.īut if I restart dbus-broker my bluetooth dongle is recognized but I get his ├─482 /usr/bin/dbus-broker-launch -scope system -audit When I run sudo systemctl status dbus-broker I got this Loaded: loaded (/lib/systemd/system/rvice enabled vendor preset: enabled)Īctive: active (running) since Thu 19:38:54 CET 14min agoĬGroup: /system.slice/rvice Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3Ĭan't read class of device on hci0: Connection timed out (110) TX bytes:417 acl:0 sco:0 commands:37 errors:0įeatures: 0xff 0xff 0x8f 0xfe 0xdb 0xff 0x5b 0x87 RX bytes:696 acl:0 sco:0 events:30 errors:0 On system when I run hciconfig -a I get this hci0: Type: Primary Bus: USBīD Address: 00:1A:7D:DA:71:05 ACL MTU: 310:10 SCO MTU: 64:8 Both ha and debian are fully updated to the latest stable version. I’m running debian bullseye with supervised installation. I have a problem setting bluetooth dongle in my ha.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |