Сбой обеспечения на Bluez5.50.Пробовал с 2 разными узлами разных производителей - PullRequest
Новая
       2

Сбой обеспечения на Bluez5.50.Пробовал с 2 разными узлами разных производителей

0 голосов
/ 11 декабря 2018

Я использую meshctl из Bluez 5.50 (сборка с опцией --enable-mesh).(Пробовал в Linux 4.9.58 и 3.14).Из журналов btmon видно, что meshctl отправляет разъединение.Я также использовал bluetoothd из bluez5.50.

Ниже приведены журналы для meshctl: 

[meshctl]# discover-unprovisioned on
           SetDiscoveryFilter success
           Discovery started
           Adapter property changed 
           [CHG] Controller 00:50:43:22:22:94 Discovering: yes
           Mesh Provisioning Service (00001827-0000-1000-8000-00805f9b34fb)
           Device UUID: 001bdc0810210b0e0a0c000b0e0a0c00
           OOB: 0000
           [NEW] Device 00:50:43:22:30:85 Meshnode-1

[meshctl]# discover-unprovisioned off
           Discovery stopped
           Adapter property changed 
           [CHG] Controller 00:50:43:22:22:94 Discovering: no

[meshctl]# provision 001bdc0810210b0e0a0c000b0e0a0c00
           Trying to connect Device 00:50:43:22:30:85 Meshnode-1
           Connection successful
           Service added /org/bluez/hci0/dev_00_50_43_22_30_85/service0001
           Service added /org/bluez/hci0/dev_00_50_43_22_30_85/service0010
           Char added /org/bluez/hci0/dev_00_50_43_22_30_85/service0010/char0011:
           Char added /org/bluez/hci0/dev_00_50_43_22_30_85/service0010/char0013:
           Services resolved yes
           Found matching char: path /org/bluez/hci0/dev_00_50_43_22_30_85/service0010/char0011, uuid 00002adb-0000-1000-8000-00805f9b34fb
           Found matching char: path /org/bluez/hci0/dev_00_50_43_22_30_85/service0010/char0013, uuid 00002adc-0000-1000-8000-00805f9b34fb
           Start notification on /org/bluez/hci0/dev_00_50_43_22_30_85/service0010/char0013
           Characteristic property changed /org/bluez/hci0/dev_00_50_43_22_30_85/service0010/char0013
           AcquireNotify success: fd 7 MTU 111
           Notify for Mesh Provisioning Out Data started
           Open-Node: 0x192b5e0
           Open-Prov: 0x1939340
           Open-Prov: proxy 0x1934510
           Initiated provisioning
           Characteristic property changed /org/bluez/hci0/dev_00_50_43_22_30_85/service0010/char0011
            AcquireWrite success: fd 8 MTU 111
           GATT-TX:  03 00 10 
           GATT-RX:  03 01 01 00 01 00 00 00 00 00 00 00 00 
           Got provisioning data (12 bytes)  01 01 00 01 00 00 00 00 00 00 00 00 
           Provisioning failed
           Attempting to disconnect from 00:50:43:22:30:85
           Characteristic property changed /org/bluez/hci0/dev_00_50_43_22_30_85/service0010/char0013
           Write closed
           Services resolved no
           Characteristic property changed /org/bluez/hci0/dev_00_50_43_22_30_85/service0010/char0011
           SetDiscoveryFilter success
           Discovery started
           Adapter property changed
...