This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Thread device commissioning over Android CHIP tool failing

Hi there,

I have gotten to the very last step of the following tutorial: https://www.youtube.com/watch?v=kdMJQFDRoss

The issue I am facing is that when pairing the Matter device to the thread network, it appears to timeout or not successfully pair.

I currently have a Rpi with nRF52840 Dongle setup as a border router and have formed a thread network.

I flashed a nRF52840 DK with the sample matter light bulb application. Upon boot the output is as follows. Note that there are a few errors shown, I am not sure if this is expected/normal.

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
uart:~$ I: nRF5 802154 radio initialized
I: 8 Sectors of 4096 bytes
I: alloc wra: 0, fd0
I: data wra: 0, 1c
*** Booting Zephyr OS build v2.7.99-ncs1-17-gc3208e7ff49d ***
I: Init CHIP stack
uart:~$ I: 223 [DL]BLE address: F6:A6:C4:23:09:AE
I: SoftDevice Controller build revision:
I: 73 50 13 e4 e1 27 34 b5 |sP...'4.
I: aa 22 21 6a b2 cb 9e 5e |."!j...^
I: a9 55 8d 25 |.U.%
I: 248 [DL]OpenThread started: OK
I: 251 [DL]Setting OpenThread device type to FULL END DEVICE
I: 257 [ZCL]Using ZAP configuration...
I: 263 [ZCL]Initiating Admin Commissioning cluster.
I: 267 [ZCL]OpCreds: Initiating OpCreds cluster by writing fabrics list from fabric table.
D: 275 [DIS]Set the fabric pairing table delegate
I: 280 [ZCL]0xc5744ep 0 clus 0x0000_0028 attr 0x0000_000F not supported
E: 287 [ZCL]Error setting Serial Number String: 0x86
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

I then open the CHIP tool on an android phone, press 'PROVISION CHIP DEVICE WITH THREAD' and then scan the QR code provided in the link from the text above.

The android app will show the little text saying 'pairing' for about 2 seconds and then just displays a blank white screen. After about 1-2 minutes it shows 'pairing failed;.

During this 'pairing' LED1 on the DK goes from flashing to solid green.

The output of the comm port during this 'pairing' is as follows:

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
I: 212015 [DL]BLE connection established (ConnId: 0x00)
I: 212020 [DL]Current number of connections: 1/1
I: 212025 [DL]CHIPoBLE advertising stopped
I: 212029 [DL]NFC Tag emulation stopped
D: 213008 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
I: 213014 [BLE]local and remote recv window sizes = 5
I: 213018 [BLE]selected BTP version 4
I: 213022 [BLE]using BTP fragment sizes rx 244 / tx 244.
D: 213154 [DL]ConnId: 0x00, New CCCD value: 0x0001
D: 213158 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 6)
D: 213165 [IN]BLE EndPoint 0x20008440 Connection Complete
I: 213170 [DL]CHIPoBLE connection established (ConnId: 0x00, GATT MTU: 247)
D: 213251 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 213258 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
I: 213264 [EM]Received message of type 0x20 with protocolId (0, 0) and MessageCounter:3812032413 on exchange 23286r
D: 213274 [EM]Handling via exchange: 23286r, Delegate: 0x20005658
D: 213280 [SC]Received PBKDF param request
D: 213284 [SC]Peer assigned session ID 1
D: 213288 [SC]Found MRP parameters in the message
D: 213293 [SC]Including MRP parameters in PBKDF param response
I: 213524 [IN]Prepared unauthenticated message 0x2002c760 to 0x0000000000000000 (0) of type 0x21 and protocolId (0, 0) on exchange 23286r with MessageCounter:1702822331.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Thanks in advance for your support.

Regards,

Gideon