[SQA] Issue with Ble pairing.

[Saravana-kr22]

Description:

There is an issue in ble pairing, While chip-tool tries to pair using ble -wifi or ble-thread chip-tool is struct at the moment it finds the device as below.

[1683804286.845358][20060:20061] CHIP:BLE: Device 0B:8F:44:BE:EF:DC does not look like a CHIP device.
[1683804286.857739][20060:20061] CHIP:BLE: New device scanned: C9:37:E9:D1:9A:6F
[1683804286.857841][20060:20061] CHIP:BLE: Device discriminator match. Attempting to connect.

Steps to reproduce: ./chip-tool pairing ble-wifi 1 <ssid> <password> 20202021 3840

System configuration:
Chip-tool - RPI-4, 8GB RAM
DUT - RPI - RPI-4, 8GB RAM and Thread - nrf52840-dk.
Platform : ble-wifi,ble-threda
Commit-ID:6c0c5ea6d2b8f38c6b36b83195b6ee55384bb599
Dut application: all-clusters-app

Logs:
ble-wifi:
Wifi log TH.txt
Wifi log DUT.txt
ble-thread:
threadlog.txt

[bzbarsky-apple]

@tehampson

[bzbarsky-apple]

Chances are #26418 fixed this.

[oidebrett]

I am having the same issue with esp32 as DUT and the RPi as matter controller. Chip-tool just stops after Device discriminator match and waits at "Attempting to connect"

System configuration:
Chip-tool - RPI-4, 8GB RAM
DUT - esp32 dev kit
Platform : ble-wifi,
Commit-ID: 8f66f42 (tags/v1.1.0.1)
Dut application: all-clusters-app

I have tried Ubuntu 22.04, 22.10 on the RPi and I tried all the steps regarding turning on /off Bluetooth device. And also I tried reinstalling bluez. Same logs as @Saravana-kr22

[tehampson]

This is a known issue and should be fixed with #26418.

@Saravana-kr22
Can you please try it out with a tip of tree build that includes that PR now that is it merged?

@oidebrett
Since you seems to be using a tag, that doesn't have the PR that is breaking I think that your issue might be different. There has been quite a few changes around how BLE is done, as well as strict checks that you are in the matter context. If you are not able to reproduce on tip of tree master branch then I don't know if I can help out for a particular tag

[oidebrett]

@oidebrett Since you seems to be using a tag, that doesn't have the PR that is breaking I think that your issue might be different. There has been quite a few changes around how BLE is done, as well as strict checks that you are in the matter context. If you are not able to reproduce on tip of tree master branch then I don't know if I can help out for a particular tag

Now works! I possibly was using a more recent commit. Anyway I tried the commit hash for the above fix (d55c592) and commissioning over BLE now works for me. I must have been mistaken on the commit hash I was using when I experienced the error.

[1683833109.175347][1094:1096] CHIP:TOO: Device commissioning completed with success

Thanks!

[Saravana-kr22]

@tehampson I have verified with the latest ToT master: a3b4005. This issue is resolved.