Home › Forums › Mooshimeter Support › Pairing from a PC without BLE113 › Reply To: Pairing from a PC without BLE113
September 9, 2016 at 7:50 am #13996
Inactive
After reading the README at https://github.com/ghtyrant/libsooshi (Thanks!), I tried fetching the BlueZ stack from git and running it with experimental features enabled (this currently includes BLE and GATT as far as I can tell), and some new things happened:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 | [bluetooth]# agent KeyboardOnly Agent registered [bluetooth]# pair 68:9E:19:CB:DE:AE Attempting to pair with 68:9E:19:CB:DE:AE [CHG] Device 68:9E:19:CB:DE:AE Connected: yes Request passkey [NEW] Primary Service /org/bluez/hci0/dev_68_9E_19_CB_DE_AE/service000c Generic Attribute Profile [NEW] Characteristic /org/bluez/hci0/dev_68_9E_19_CB_DE_AE/service000c/char000d Service Changed [NEW] Descriptor /org/bluez/hci0/dev_68_9E_19_CB_DE_AE/service000c/char000d/desc000f Client Characteristic Configuration [NEW] Primary Service /org/bluez/hci0/dev_68_9E_19_CB_DE_AE/service0010 Vendor specific [NEW] Characteristic /org/bluez/hci0/dev_68_9E_19_CB_DE_AE/service0010/char0011 Vendor specific [NEW] Descriptor /org/bluez/hci0/dev_68_9E_19_CB_DE_AE/service0010/char0011/desc0013 Characteristic User Description [NEW] Characteristic /org/bluez/hci0/dev_68_9E_19_CB_DE_AE/service0010/char0014 Vendor specific [NEW] Descriptor /org/bluez/hci0/dev_68_9E_19_CB_DE_AE/service0010/char0014/desc0016 Client Characteristic Configuration [NEW] Descriptor /org/bluez/hci0/dev_68_9E_19_CB_DE_AE/service0010/char0014/desc0017 Characteristic User Description [CHG] Device 68:9E:19:CB:DE:AE UUIDs: 00001800-0000-1000-8000-00805f9b34fb [CHG] Device 68:9E:19:CB:DE:AE UUIDs: 00001801-0000-1000-8000-00805f9b34fb [CHG] Device 68:9E:19:CB:DE:AE UUIDs: 1bc5ffa0-0200-62ab-e411-f254e005dbd4 [CHG] Device 68:9E:19:CB:DE:AE ServicesRehttps://github.com/ghtyrant/libsooshihttps://github.com/ghtyrant/libsooshisolved: yes [agent] Enter passkey (number in 0-999999): 000000 Failed to pair: org.bluez.Error.AuthenticationFailed [CHG] Device 68:9E:19:CB:DE:AE ServicesResolved: no [CHG] Device 68:9E:19:CB:DE:AE Connected: no [bluetooth]# |
This new output only appears about a second after the passkey prompt first comes up, but the authentication still fails, both with and without passkey.