-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
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
Not able to connect devices with external USB dongle #608
Comments
To be honest I don't know. You could try asking in the iobroker forums, maybe someone there knows more about the hardware side of this. |
Hey there, i run every test and troubleshooting methode that i wars able find but noway. I cant find Decives via Scan (Linux Console / Iobroker Adapter) and i cant also not found the Machine with my Phone. Now I have bought a "TP-Link UB400 Nano USB Bluetooth 4.0" and i can find the Devices via "bluetoothctl" (Linux Console) (my Phone) and also the Adapter found one the Devices but only with a MAC. The Adapter will not find my Phone but i think the Adapter is not made for what I had in mind (presence check with my phone via Bluetooth). So i think you have the same Problem like me, your dongle doesn't work with Linux. I hope it helps... Greetings Milcho :) |
Hi Some additional information from me: My experience with TP-Link UB500 Adapter under Linux is also sobering. You can get it to work but it does not support Bluetooth Low Energy (BLE)! TP-Link explicitly say that they only support Windows!
|
Hi!
I want to use an external Bluetooth USB, so with a usb cable extension I'd have a better reach to my Bluetooth devices. The adapter is green and hciconfig shows the following:
`sudo hciconfig -a; dmesg | egrep -i 'blue|firm'
hci1: Type: Primary Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:87200 acl:0 sco:0 events:2946 errors:0
TX bytes:1221 acl:0 sco:0 commands:91 errors:0
Features: 0xff 0xff 0x8f 0xfe 0xdb 0xff 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'raspberrypi #2'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 4.0 (0x6) Revision: 0x22bb
LMP Version: 4.0 (0x6) Subversion: 0x22bb
Manufacturer: Cambridge Silicon Radio (10)
hci0: Type: Primary Bus: UART
BD Address: DC:A6:32:D2:7B:B6 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:914194 acl:0 sco:0 events:30980 errors:0
TX bytes:2732 acl:0 sco:0 commands:126 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT
Name: 'raspberrypi'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 5.0 (0x9) Revision: 0x156
LMP Version: 5.0 (0x9) Subversion: 0x6119
Manufacturer: Cypress Semiconductor Corporation (305)
[ 0.090931] raspberrypi-firmware soc:firmware: Attached to firmware from 2021-05-27T14:02:15, variant start
[ 0.100945] raspberrypi-firmware soc:firmware: Firmware hash is 7d9a298cda813f747b51fe17e1e417e7bf5ca94d
[ 4.912135] vc4-drm gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4])
[ 5.372366] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2
[ 5.628521] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan 4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e
[ 14.299315] Bluetooth: Core ver 2.22
[ 14.299449] Bluetooth: HCI device and connection manager initialized
[ 14.299478] Bluetooth: HCI socket layer initialized
[ 14.299512] Bluetooth: L2CAP socket layer initialized
[ 14.299547] Bluetooth: SCO socket layer initialized
[ 14.306447] Bluetooth: HCI UART driver ver 2.3
[ 14.306470] Bluetooth: HCI UART protocol H4 registered
[ 14.306571] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 14.306902] Bluetooth: HCI UART protocol Broadcom registered
[ 14.479740] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 14.479749] Bluetooth: BNEP filters: protocol multicast
[ 14.479762] Bluetooth: BNEP socket layer initialized`
I'm using "1" in the adapter since the usb is hci1.
Everything should work, but I'm not able to receive data to the USB dongle. if if switch back to "0" (hci0, internal BT), then data is receiving as always.
Where is the problem?
Thank you for your help.
The text was updated successfully, but these errors were encountered: