This would be the default manager (in Raspbian) and also blueman-manager.Douglas6 wrote: What 'Bluetooth managers' do you refer to? What purpose is Bluetooth intended for? What is the response to an 'hciconfig -a' command?
Code: Select all
hci0: Type: Primary Bus: USB BD Address: 33:03:30:0A:6C:FC ACL MTU: 360:4 SCO MTU: 0:0 DOWN RX bytes:1106 acl:0 sco:0 events:56 errors:0 TX bytes:736 acl:0 sco:0 commands:60 errors:0 Features: 0xff 0xff 0xcd 0xfa 0xdb 0xbf 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT
I have since uninstalled blueman so this shouldn't be an issue.Douglas6 wrote: ↑Wed Apr 17, 2019 6:32 pmBlueman can potentially conflict with Simon Long's GUI Bluetooth manager extension. I would first recommend not using and even uninstalling Blueman. But that's not your problem.
The hciconfig command shows that your Bluetooth adapter is 'down'. You can try bringing it up with 'sudo hciconfig hci0 up' and check it again. If that fails, post the results.
I'm not sure what process starts the adapter at boot time; it would depend on your version of Raspbian. On Stretch it's the hciuart.service, although I'm not certain that applies to dongles. What are the results of 'systemctl status hciuart'?
Code: Select all
● hciuart.service - Configure Bluetooth Modems connected by UART Loaded: loaded (/lib/systemd/system/hciuart.service; enabled; vendor preset: enabled) Active: inactive (dead) Apr 17 14:42:16 hnet systemd: Dependency failed for Configure Bluetooth Modems connected by UART. Apr 17 14:42:16 hnet systemd: hciuart.service: Job hciuart.service/start failed with result 'dependency'.
Thanks for your help. It may be this specific dongle, at this point I'm considering just using a different dongle.Douglas6 wrote: ↑Wed Apr 17, 2019 6:53 pmI'm sorry my best guess is a bum dongle. That it works under Windows is not a good indication that it will work under Raspbian, or even Linux.
I'd be interested in any history of the dongle ("looks a bit like..." isn't really helpful.) People often have problems like yours with cheap knockoff Asian dongles that can be had for a dollar or two.
Alright, thanks for your help. I'll probably return this dongle and attempt a different brand.Douglas6 wrote: ↑Wed Apr 17, 2019 7:12 pmI can't find any manufacturer / vendor associated with your Bluetooth device address, which further supports my theory of a knockoff dongle. I've seen that mushroom style in both reputable and unreputable versions.
I would try to purchase a dongle from a reputable retailer. If you can determine the chipset before you buy, Broadcom and CSR are both known to work on the Pi. I would expect to pay $7 - $10 for a decent dongle; possibly less, but not much less.