Hi John, On Wed, Nov 15, 2017, John Klug wrote: > Over and over again it says device is not available. When does it > become available? Is there a way to do this deterministically? I > quickly entered trust (it was saved from previous executions > unsuccessfully) after pairing. Then after connecting, all to no > avail. > > Is there documentation on this? > > The remote in this case is Broadcom 6.5.1.6000 stack. > > [agent] Confirm passkey 702629 (yes/no): yes > [CHG] Device 5C:F3:70:74:04:AF UUIDs: 00001000-0000-1000-8000-00805f9b34fb > [CHG] Device 5C:F3:70:74:04:AF UUIDs: 00001115-0000-1000-8000-00805f9b34fb > [CHG] Device 5C:F3:70:74:04:AF ServicesResolved: yes > [CHG] Device 5C:F3:70:74:04:AF Paired: yes > [John Conduit Klug (SGH-M919)]# trust 5C:F3:70:74:04:AF > Device 5C:F3:70:74:04:AF not available I think bluetoothctl has a bug where it doesn't strip whitespace from the beginning of arguments. In your case you have two spaces between trust and the address. Try removing one. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
