bonding and filter_accept_list is not working with nRF Connect Mobile Android APP

RE: bonding and filter_accept_list is not working with nRF Connect Mobile Android APP

Amanda Hsieh — Thu, 26 Jan 2023 16:44:53 GMT

Happy to help. 🙂

-Amanda H.

RE: bonding and filter_accept_list is not working with nRF Connect Mobile Android APP

devbook — Thu, 26 Jan 2023 16:00:14 GMT

Hi Amanda,

I just tested CONFIG_BT_PRIVACY=y and it seems to work as expected with the filter accept-/whitelist. :)

Thanks alot for your support.

devbook

RE: bonding and filter_accept_list is not working with nRF Connect Mobile Android APP

Amanda Hsieh — Wed, 25 Jan 2023 20:49:53 GMT

Hi,

Try to enable CONFIG_BT_PRIVACY. IRK handling is automatic in the sense that if you enable privacy (CONFIG_BT_PRIVACY=y), it is automatically generated and used by the stack.

-Amanda H.

RE: bonding and filter_accept_list is not working with nRF Connect Mobile Android APP

devbook — Mon, 23 Jan 2023 07:35:49 GMT

Hi Amanda,

the way they handled it in this thread works :) , however, I would prefer to use the filter_accept_list

We could use the whitelist/filter_accept_list as expected with the peer management in the old nRF5 SDK.

Thanks for your support

devbook

RE: bonding and filter_accept_list is not working with nRF Connect Mobile Android APP

Amanda Hsieh — Fri, 20 Jan 2023 18:54:01 GMT

Hi,

Mobile phones for instance typically always use a random resolvable address (privacy), so there you need the IRK (and pairing/bonding) in order to do whitelisting. If the devices do not use privacy, then you can simply whitelist the BLE address as this never changes in that case. That can explain why it can work for nRF Connect Desktop APP with an nRF52840-DK as central instead of mobile. Maybe this post can help.

With your code, I got the log as

00> [00:00:00.015,686] <inf> fs_nvs: 6 Sectors of 4096 bytes
00> [00:00:00.015,716] <inf> fs_nvs: alloc wra: 0, fe8
00> [00:00:00.015,777] <inf> fs_nvs: data wra: 0, 0
00> [00:00:00.016,021] <inf> sdc_hci_driver: SoftDevice Controller build revision: 
00>                                          6d 90 41 2a 38 e8 ad 17  29 a5 03 38 39 27 d7 85 |m.A*8... )..89'..
00>                                          1f 85 d8 e1                                      |....             
00> [00:00:00.021,881] <inf> bt_hci_core: No ID address. App must call settings_load()
00> [00:00:00.021,911] <inf> peripheral_uart: Bluetooth initialized
00> [00:00:00.025,268] <inf> peripheral_uart: Bonded devices: 0
00> 
00> [00:00:22.847,808] <inf> peripheral_uart: Connected EF:06:74:2A:38:07 (random)
00> [00:00:30.342,407] <inf> peripheral_uart: Passkey for EF:06:74:2A:38:07 (random): 652399
00> [00:00:39.073,089] <inf> peripheral_uart: Security changed: EF:06:74:2A:38:07 (random) level 3
00> [00:00:39.170,043] <inf> peripheral_uart: Pairing completed: EF:06:74:2A:38:07 (random), bonded: 1
00> [00:01:42.553,344] <inf> peripheral_uart: Disconnected: EF:06:74:2A:38:07 (random) (reason 19)
00> [00:01:51.567,047] <inf> peripheral_uart: Connected EF:06:74:2A:38:07 (random)
00> [00:01:51.642,669] <inf> peripheral_uart: Security changed: EF:06:74:2A:38:07 (random) level 3
00> [00:02:18.051,269] <inf> peripheral_uart: Disconnected: EF:06:74:2A:38:07 (random) (reason 19)
00> [00:00:00.014,678] <inf> fs_nvs: 6 Sectors of 4096 bytes
00> [00:00:00.014,678] <inf> fs_nvs: alloc wra: 0, fb8
00> [00:00:00.014,709] <inf> fs_nvs: data wra: 0, 88
00> [00:00:00.014,923] <inf> sdc_hci_driver: SoftDevice Controller build revision: 
00>                                          6d 90 41 2a 38 e8 ad 17  29 a5 03 38 39 27 d7 85 |m.A*8... )..89'..
00>                                          1f 85 d8 e1                                      |....             
00> [00:00:00.020,660] <inf> bt_hci_core: No ID address. App must call settings_load()
00> [00:00:00.020,690] <inf> peripheral_uart: Bluetooth initialized
00> [00:00:00.029,663] <inf> peripheral_uart: Bonded devices: 1
00> 
00> [00:00:25.254,882] <inf> peripheral_uart: Connected EF:06:74:2A:38:07 (random)
00> [00:00:25.315,521] <inf> peripheral_uart: Security changed: EF:06:74:2A:38:07 (random) level 3
00> [00:01:01.489,227] <inf> peripheral_uart: Disconnected: EF:06:74:2A:38:07 (random) (reason 19)

Here is my test project devzone.nordicsemi.com/.../peripheral_5F00_uart_5F00_301474.7z

[quote user="devbook"]Is it possible to get more information from the filter_accept_list, e.g. how many entries are stored? At the moment I count when adding devices. I did not find any way to get any information from that list.[/quote]

The application needs to count. If you look at the implementation of int bt_le_filter_accept_list_add(const bt_addr_le_t *addr), you can see that the Bluetooth host is not doing validation - the controller will signalize when it is full.

[quote user="devbook"]Afterwards, I tested with the LESC modification. I did not need to press the Button for bonding anymore but I even could not connect after bonding.[/quote]

I can reproduce and see the same sniffer log as this thread. The team has verified that there is a bug in the library handling key retrieval. It will take some time to have a fix on this. For now, it's considered a known issue, and don't have a workaround yet, unfortunately.

Regards,
Amanda H.

RE: bonding and filter_accept_list is not working with nRF Connect Mobile Android APP

devbook — Thu, 19 Jan 2023 07:52:08 GMT

Hi Amanda,

Log with RTT with connection to mobile app and no further modifications for LESC:

Connected via RTT with settings mem-address:auto

SEGGER J-Link V7.80c - Real time terminal output
J-Link OB-SAM3U128-V2-NordicSemi compiled Sep 21 2022 09:57:39 V1.0, SN=682317443
Process: JLink.exe
[00:00:00.004,669] <dbg> peripheral_uart: uart_cb: UART_RX_BUF_REQUEST
[00:00:00.007,934] <dbg> peripheral_uart: uart_cb: UART_TX_DONE
[00:00:00.015,502] <inf> fs_nvs: 6 Sectors of 4096 bytes
[00:00:00.015,533] <inf> fs_nvs: alloc wra: 0, fd0
[00:00:00.015,594] <inf> fs_nvs: data wra: 0, 1c
[00:00:00.015,777] <inf> sdc_hci_driver: SoftDevice Controller build revision:
                                         6d 90 41 2a 38 e8 ad 17  29 a5 03 38 39 27 d7 85 |m.A*8... )..89'..
                                         1f 85 d8 e1                                      |....
[00:00:00.021,759] <inf> bt_hci_core: No ID address. App must call settings_load()
[00:00:00.021,759] <inf> peripheral_uart: Bluetooth initialized
[00:01:05.067,016] <inf> peripheral_uart: Connected 6E:22:C9:8E:61:69 (random)
[00:01:11.214,233] <inf> peripheral_uart: Passkey for 6E:22:C9:8E:61:69 (random): 272678
[00:01:11.214,263] <inf> peripheral_uart: Press Button 1 to confirm, Button 2 to reject.
[00:01:15.619,293] <inf> peripheral_uart: Numeric Match, conn 0x20001f90
[00:01:15.892,303] <inf> peripheral_uart: Security changed: 6E:22:C9:8E:61:69 (random) level 4
[00:01:15.989,685] <inf> peripheral_uart: Pairing completed: A8:3E:0E:F3:7B:70 (public), bonded: 1
[00:01:24.532,806] <inf> peripheral_uart: Disconnected: A8:3E:0E:F3:7B:70 (public) (reason 19)
[00:01:28.335,449] <inf> peripheral_uart: Connected A8:3E:0E:F3:7B:70 (public)
[00:01:29.661,376] <inf> peripheral_uart: Security changed: A8:3E:0E:F3:7B:70 (public) level 4
[00:01:35.782,318] <inf> peripheral_uart: Disconnected: A8:3E:0E:F3:7B:70 (public) (reason 19)
[00:00:00.004,852] <dbg> peripheral_uart: uart_cb: UART_RX_BUF_REQUEST
[00:00:00.008,117] <dbg> peripheral_uart: uart_cb: UART_TX_DONE
[00:00:00.015,319] <inf> fs_nvs: 6 Sectors of 4096 bytes
[00:00:00.015,319] <inf> fs_nvs: alloc wra: 0, f88
[00:00:00.015,350] <inf> fs_nvs: data wra: 0, c0
[00:00:00.015,594] <inf> sdc_hci_driver: SoftDevice Controller build revision:
                                         6d 90 41 2a 38 e8 ad 17  29 a5 03 38 39 27 d7 85 |m.A*8... )..89'..
                                         1f 85 d8 e1                                      |....
[00:00:00.021,453] <inf> bt_hci_core: No ID address. App must call settings_load()
[00:00:00.021,514] <inf> peripheral_uart: Bluetooth initialized

And the log from the APP:

nRF Connect, 2023-01-19
Nordic_UART_Service (F2:17:D9:08:8C:FA)
I	08:12:23.987	[Server] Server started
V	08:12:24.008	Unknown Service (00001091-0000-1000-8000-00805f9b34fb)
- Unknown Characteristic [R] (00002080-0000-1000-8000-00805f9b34fb)
Unknown Service (00001020-0000-1000-8000-00805f9b34fb)
- Unknown Characteristic [N R] (00002090-0000-1000-8000-00805f9b34fb)
   Client Characteristic Configuration (0x2902)
V	08:12:24.423	Connecting to F2:17:D9:08:8C:FA...
D	08:12:24.423	gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D	08:12:25.087	[Server callback] Connection state changed with status: 0 and new state: DISCONNECTED (0)
I	08:12:25.087	[Server] Device disconnected
D	08:12:25.113	[Callback] Connection state changed with status: 133 and new state: DISCONNECTED (0)
E	08:12:25.113	Error 133 (0x85): GATT ERROR
I	08:12:25.113	Disconnected
D	08:12:35.202	gatt.close()
D	08:12:35.206	wait(200)
V	08:12:35.407	Connecting to F2:17:D9:08:8C:FA...
D	08:12:35.408	gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D	08:12:35.793	[Server callback] Connection state changed with status: 0 and new state: DISCONNECTED (0)
D	08:12:35.793	[Callback] Connection state changed with status: 133 and new state: DISCONNECTED (0)
I	08:12:35.793	[Server] Device disconnected
E	08:12:35.793	Error 133 (0x85): GATT ERROR
I	08:12:35.793	Disconnected
D	08:12:37.733	gatt.close()
D	08:12:37.736	wait(200)
V	08:12:37.942	Connecting to F2:17:D9:08:8C:FA...
D	08:12:37.943	gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D	08:12:38.538	[Callback] Connection state changed with status: 133 and new state: DISCONNECTED (0)
E	08:12:38.538	Error 133 (0x85): GATT ERROR
I	08:12:38.538	Disconnected
D	08:12:38.540	[Server callback] Connection state changed with status: 0 and new state: DISCONNECTED (0)
I	08:12:38.540	[Server] Device disconnected
D	08:12:39.621	gatt.close()
D	08:12:39.624	wait(200)
V	08:12:39.828	Connecting to F2:17:D9:08:8C:FA...
D	08:12:39.828	gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D	08:12:40.426	[Server callback] Connection state changed with status: 0 and new state: DISCONNECTED (0)
I	08:12:40.426	[Server] Device disconnected
D	08:12:40.445	[Callback] Connection state changed with status: 133 and new state: DISCONNECTED (0)
E	08:12:40.446	Error 133 (0x85): GATT ERROR
I	08:12:40.446	Disconnected
D	08:12:41.165	gatt.close()
D	08:12:41.169	wait(200)
V	08:12:41.373	Connecting to F2:17:D9:08:8C:FA...
D	08:12:41.373	gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D	08:12:41.820	[Server callback] Connection state changed with status: 0 and new state: DISCONNECTED (0)
I	08:12:41.820	[Server] Device disconnected
D	08:12:41.821	[Callback] Connection state changed with status: 133 and new state: DISCONNECTED (0)
E	08:12:41.821	Error 133 (0x85): GATT ERROR
I	08:12:41.821	Disconnected
D	08:12:42.547	gatt.close()
D	08:12:42.549	wait(200)
V	08:12:42.751	Connecting to F2:17:D9:08:8C:FA...
D	08:12:42.751	gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D	08:12:43.488	[Server callback] Connection state changed with status: 0 and new state: DISCONNECTED (0)
I	08:12:43.488	[Server] Device disconnected
D	08:12:43.509	[Callback] Connection state changed with status: 133 and new state: DISCONNECTED (0)
E	08:12:43.510	Error 133 (0x85): GATT ERROR
I	08:12:43.510	Disconnected

After the restart no connection request is shown in the logging in this case.

Yes, I need to and I do so, pressing Button 1 for Bonding.

Logging from connection with desktop app and no LESC modifications:

Connected via RTT with settings mem-address:auto

SEGGER J-Link V7.80c - Real time terminal output
J-Link OB-SAM3U128-V2-NordicSemi compiled Sep 21 2022 09:57:39 V1.0, SN=682317443
Process: JLink.exe
[00:00:00.004,669] <dbg> peripheral_uart: uart_cb: UART_RX_BUF_REQUEST
[00:00:00.007,934] <dbg> peripheral_uart: uart_cb: UART_TX_DONE
[00:00:00.016,387] <inf> fs_nvs: 6 Sectors of 4096 bytes
[00:00:00.016,387] <inf> fs_nvs: alloc wra: 0, fe8
[00:00:00.016,448] <inf> fs_nvs: data wra: 0, 0
[00:00:00.016,693] <inf> sdc_hci_driver: SoftDevice Controller build revision:
                                         6d 90 41 2a 38 e8 ad 17  29 a5 03 38 39 27 d7 85 |m.A*8... )..89'..
                                         1f 85 d8 e1                                      |....
[00:00:00.022,613] <inf> bt_hci_core: No ID address. App must call settings_load()
[00:00:00.022,674] <inf> peripheral_uart: Bluetooth initialized
[00:00:16.593,292] <inf> peripheral_uart: Connected F1:5C:5A:F7:A5:3D (random)
[00:00:22.078,979] <inf> peripheral_uart: Passkey for F1:5C:5A:F7:A5:3D (random): 289904
[00:00:22.079,010] <inf> peripheral_uart: Press Button 1 to confirm, Button 2 to reject.
[00:00:26.633,331] <inf> peripheral_uart: Numeric Match, conn 0x20001f90
[00:00:26.854,919] <inf> peripheral_uart: Pairing completed: F1:5C:5A:F7:A5:3D (random), bonded: 1
[00:00:26.855,285] <inf> peripheral_uart: Security changed: F1:5C:5A:F7:A5:3D (random) level 4


Disconnected

Connected via RTT with settings mem-address:auto

SEGGER J-Link V7.80c - Real time terminal output
J-Link OB-SAM3U128-V2-NordicSemi compiled Sep 21 2022 09:57:39 V1.0, SN=682317443
Process: JLink.exe


Disconnected

Connected via RTT with settings mem-address:auto

SEGGER J-Link V7.80c - Real time terminal output
J-Link OB-SAM3U128-V2-NordicSemi compiled Sep 21 2022 09:57:39 V1.0, SN=682317443
Process: JLink.exe
[00:00:00.004,852] <dbg> peripheral_uart: uart_cb: UART_RX_BUF_REQUEST
[00:00:00.008,117] <dbg> peripheral_uart: uart_cb: UART_TX_DONE
[00:00:00.015,472] <inf> fs_nvs: 6 Sectors of 4096 bytes
[00:00:00.015,502] <inf> fs_nvs: alloc wra: 0, fb8
[00:00:00.015,533] <inf> fs_nvs: data wra: 0, 88
[00:00:00.015,777] <inf> sdc_hci_driver: SoftDevice Controller build revision:
                                         6d 90 41 2a 38 e8 ad 17  29 a5 03 38 39 27 d7 85 |m.A*8... )..89'..
                                         1f 85 d8 e1                                      |....
[00:00:00.021,759] <inf> bt_hci_core: No ID address. App must call settings_load()
[00:00:00.021,789] <inf> peripheral_uart: Bluetooth initialized
[00:00:08.329,681] <inf> peripheral_uart: Connected F1:5C:5A:F7:A5:3D (random)
[00:00:08.382,629] <wrn> peripheral_uart: Security failed: F1:5C:5A:F7:A5:3D (random) level 1 err 9
[00:00:08.383,850] <inf> peripheral_uart: Disconnected: F1:5C:5A:F7:A5:3D (random) (reason 61)

And Desktop APP log:

LESC connection without modification
08:23:20.417	Disconnected from device F2:17:D9:08:8C:FA, reason: BLE_HCI_CONNECTION_TIMEOUT
08:23:44.959	Connecting to device
08:23:45.007	Connected to device F2:17:D9:08:8C:FA: interval: 7.5ms, timeout: 4000ms, latency: 0
08:23:45.062	Security updated, mode:1, level:1
08:23:45.074	Phy updated for device F2:17:D9:08:8C:FA, tx: 2 Mb/s, rx: 2 Mb/s
08:23:45.273	Attribute value read, handle: 0x0B, value (0x): 4E-6F-72-64-69-63-5F-55-41-52-54-5F-53-65-72-76-69-63-65
08:23:50.050	Connection parameters updated for device F2:17:D9:08:8C:FA: interval 30ms, timeout 420ms, latency: 0
08:23:55.246	Security updated, mode:1, level:4
08:23:55.252	Storing bond info for device F2:17:D9:08:8C:FA
08:24:21.766	Disconnected from device F2:17:D9:08:8C:FA, reason: BLE_HCI_CONNECTION_TIMEOUT
08:24:29.551	Connecting to device
08:24:30.066	Connected to device F2:17:D9:08:8C:FA: interval: 7.5ms, timeout: 4000ms, latency: 0
08:24:34.116	Disconnected from device F2:17:D9:08:8C:FA, reason: BLE_HCI_CONNECTION_TIMEOUT

The security Level results in an error and an BLE_HCI_CONNECTION_TIMEOUT. However, this is not shown in the connection with the app.

Afterwards, I tested with the LESC modification. I did not need to press the Button for bonding anymore but I even could not connect after bonding.

I hope that the logs helps to find a solution.

Is it possible to get more information from the filter_accept_list, e.g. how many entries are stored? At the moment I count when adding devices. I did not find any way to get any information from that list. It is a black box for me.

RE: bonding and filter_accept_list is not working with nRF Connect Mobile Android APP

Amanda Hsieh — Wed, 18 Jan 2023 14:23:12 GMT

Hi,

[quote user=""]I tested with the Android APP and the first connect and bonding process works. However, if I restart the peripheral I cannot connect any more. The APP shows Error 133 (0x85): GATT ERROR.[/quote]

Could you provide the debug log by Connecting using RTT?

Do you press Button 1 on the device and accept the passkey value on the smartphone to confirm pairing or bonding?

[quote user=""]If I check "Enable LE Secure Connection pairing", I can also not reconnect after restart. However, the errors are different to the ones with the mobile app.[/quote]

What is the error log?

It needs to modify the peripheral_uart example to support LESC. See this post.

Regards,
Amanda H.