castalla wrote: > Pretty much any dongle might work - the real trick is to get the bt > device paired and trusted - and then to build a script which will allow > the device and the debian squeezelite process to cleanly connect and > disconnect. Unless you do this, you'll have to be prepared to enter > convoluted command lines each time you want to connect squeezelite to a > bt device
Okay, so I've got the Bluetooth module loading at bootup, I can do a hcitool scan and see my device, I can execute hcitool -i hci0 cc 00:11:22:33:44:55 without error. When I run hcitool con it briefly shows the device connected, but it doesn't last. hcitool auth 00:11:22:33:44:55 comes back with HCI authentication request failed: Input/output error Before I get into configuring the output device in /etc/asound.conf is there a foolproof way to know whether I've got it properly pairing? It's difficult to gauge when I don't know what the expected behaviour is. Two track 1's and no track 2 after a scan for new and changed? Please vote for serious scanning bug '17782' (http://bugs.slimdevices.com/show_bug.cgi?id=17782) Receiver stuck at blue LED state after reboot? Please vote for bug '17462' (http://bugs.slimdevices.com/show_bug.cgi?id=17462) ------------------------------------------------------------------------ paulster's Profile: http://forums.slimdevices.com/member.php?userid=23073 View this thread: http://forums.slimdevices.com/showthread.php?t=101872 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
