connectedhomeip: Unable to establish ble connection between devices

Problem

expected behavior: Connect command in ChipDeviceController running on laptop should be able to connect to Lighting App running on RPi4B actual behavior: Connect command in ChipDeviceController is timeout and unable to connect to Lighting App running on RPi4B. system configuration: Topology: Intel Corei7 laptop running Ubuntu 20.04.2 LTS <-------------------> RPi4B running Ubuntu 20.04.2 LTS Branch: Test_event_2.2 Note: Both laptop and RPi using the default bluetooth radio (without any dongles). hciconfig on both devices is having hci0.

Laptop BD Address: 6C:6A:77:48:40:08
RPi4B BD Address: B8:27:EB:91:23:92

steps to reproduce: RPi4B running Lighting App as suggested in the page https://github.com/project-chip/connectedhomeip/tree/master/examples/lighting-app/linux Logs as below:

$out/debug/chip-lighting-app --ble-device 0 
SetupPINCode: [20202021]
SetupQRCode:  [CH:H34DV+700 V5C.71]
CHIP:ZCL: Using ZAP configuration...
CHIP:ZCL: deactivate report event
CHIP:ZCL: Unknown cluster ID: 40
CHIP:ZCL: Unknown cluster ID: 40
CHIP:ZCL: Unknown cluster ID: 40
CHIP:ZCL: Unknown cluster ID: 40
CHIP:ZCL: Unknown cluster ID: 40
CHIP:ZCL: Unknown cluster ID: 40
CHIP:ZCL: Unknown cluster ID: 40
CHIP:ZCL: Unknown cluster ID: 40
CHIP:ZCL: Unknown cluster ID: 40
CHIP:IN: TransportMgr initialized
CHIP:IN: local node id is 0x0000000000bc5c01
CHIP:DL: wpa_supplicant: _IsWiFiStationProvisioned: interface not connected
CHIP:BLE: Assigned local session key ID 0
CHIP:BLE: Waiting for PBKDF param request
CHIP:DIS: Start dns-sd server
CHIP:DIS: CHIP minimal mDNS started advertising.
CHIP:DIS: Replying to DNS-SD service listing request
CHIP:DIS: Replying to DNS-SD service listing request
CHIP:DIS: Replying to DNS-SD service listing request
CHIP:SVR: Server Listening...
CHIP:DL: TRACE: Bluez mainloop starting Thread
CHIP:DL: TRACE: Bus acquired for name CHIP-3840
CHIP:DL: CREATE service object at /chipoble/0e8a/service
CHIP:DL: Create characteristic object at /chipoble/0e8a/service/c1
CHIP:DL: Create characteristic object at /chipoble/0e8a/service/c2
CHIP:DL: CHIP BTP C1 /chipoble/0e8a/service
CHIP:DL: CHIP BTP C2 /chipoble/0e8a/service
CHIP:DL: CHIP_ENABLE_ADDITIONAL_DATA_ADVERTISING is TRUE
CHIP:DL: Create characteristic object at /chipoble/0e8a/service/c3
CHIP:DL: rotatingDeviceId: 00007C5F6E176CD40F68685D100A1CF8A98B
CHIP:DL: CHIP BTP C3 /chipoble/0e8a/service
CHIP:DL: PlatformBlueZInit init success
CHIP:DL: BluezPeripheralRegisterAppDone done
CHIP:DL: HandlePlatformSpecificBLEEvent 16392
CHIP:DL: Create adv object at /chipoble/0e8a/advertising
CHIP:DL: SET service data to {'0xFFF6': <[byte 0x00, 0x00, 0x0f, 0x5a, 0x23, 0xff, 0xfe]>}
CHIP:DL: HandlePlatformSpecificBLEEvent 16393
CHIP:DL: CHIPoBLE advertising config complete
CHIP:DL: RegisterAdvertisement complete
CHIP:DL: HandlePlatformSpecificBLEEvent 16394

Running ChipDeviceController on Laptop but ble connection is not established due to Timeout. Logs as bdlow:

root1@root1-Nitro-AN515-55:~/Nagesh/CHIP/test_event_2.2/connectedhomeip/src/controller/python$ ./chip-device-ctrl.py 
CHIP:IN: TransportMgr initialized
CHIP:IN: local node id is 0x000000000001b669
CHIP:ZCL: Using ZAP configuration...
CHIP:ZCL: deactivate report event
CHIP:DL: CHIP task running
CHIP:DL: Platform main loop started.
Chip Device Controller Shell

chip-device-ctrl > ble-scan
2021-04-28 19:10:50,408 ChipBLEMgr   INFO     scanning started
2021-04-28 19:10:52,146 ChipBLEMgr   INFO     Name            = CHIP-3840
2021-04-28 19:10:52,146 ChipBLEMgr   INFO     ID              = 2193682d-4caf-3a4a-9713-03a1a3329db8
2021-04-28 19:10:52,147 ChipBLEMgr   INFO     RSSI            = -65
2021-04-28 19:10:52,147 ChipBLEMgr   INFO     Address         = B8:27:EB:91:23:92
2021-04-28 19:10:52,148 ChipBLEMgr   INFO     Pairing State   = 0
2021-04-28 19:10:52,148 ChipBLEMgr   INFO     Discriminator   = 3840
2021-04-28 19:10:52,148 ChipBLEMgr   INFO     Vendor Id       = 9050
2021-04-28 19:10:52,148 ChipBLEMgr   INFO     Product Id      = 65279
2021-04-28 19:10:52,148 ChipBLEMgr   INFO     Adv UUID        = 0000fff6-0000-1000-8000-00805f9b34fb
2021-04-28 19:10:52,149 ChipBLEMgr   INFO     Adv Data        = 00000f5a23fffe
2021-04-28 19:10:52,149 ChipBLEMgr   INFO     

2021-04-28 19:11:00,718 ChipBLEMgr   INFO     scanning stopped
chip-device-ctrl > 
chip-device-ctrl > connect -ble 3840 20202021
Device is assigned with nodeid = 587015
CHIP:BLE: Assigned local session key ID 1
CHIP:EM: SessionEstablishmentExchangeDispatch::SendMessageImpl  mTransportMgr 0x22044f0
CHIP:IN: Message appended to BLE send queue
CHIP:BLE: Sent PBKDF param request
CHIP:BLE: BLE removing known devices.
CHIP:BLE: BLE initiating scan.
CHIP:BLE: Device 94:53:30:33:D8:8A does not look like a CHIP device.
CHIP:BLE: Device 79:87:B2:61:37:AF does not look like a CHIP device.
CHIP:BLE: Device CC:0B:2A:79:92:CE does not look like a CHIP device.
CHIP:BLE: Device 6C:E8:C6:F2:87:33 does not look like a CHIP device.
CHIP:BLE: Device 70:59:8E:47:B5:A4 does not look like a CHIP device.
CHIP:BLE: New device scanned: B8:27:EB:91:23:92
CHIP:BLE: Device discriminator match. Attempting to connect.
CHIP:BLE: Scan complete notification without an active scan.
CHIP:DL: HandlePlatformSpecificBLEEvent 16386
CHIP:IN: Clearing BLE pending packets.
CHIP:IN: BleConnection Error: CHIP Error 4050 (0x00000FD2): Timeout
CHIP:DL: FAIL: ConnectDevice : Operation was cancelled
CHIP:DL: HandlePlatformSpecificBLEEvent 16386
Failed to establish secure session to device: 4050
CHIP Error 4050 (0x00000FD2): Timeout

Proposed Solution

NA