Error on commissioning step 'FindOperational' while pairing matter sample over ble-thread

Hi,

I'm following this tutorial https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/nrf/ug_matter.html - I use the nrf52840 dongle as a co-processor connected to a raspberry pi running OTBR, nrf52840 DK flashed with matter door lock sample and I downloaded chip tool (release version 2.0.0) on my laptop with Linux. I want to connect the door lock sample to OTBR as described here. Unfortunately, step 6 causes the problem. When I execute this command:

./chip-tool-release pairing ble-thread 1000 hex:0e080000000000010000000300000f35060004001fffe0020811111111222222220708fd05128ef262a22b051000112233445566778899aabbccddeeff030e4f70656e54687265616444656d6f010212340410445f2b5ca6f2a93a55ce570a70efeecb0c0402a0f7f8 20202021 3840

I get the following error:

 

CHIP:DIS: Operational discovery failed for 0x00000000000003E8: ../../src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:174: CHIP Error 0x00000032: Timeout

and I have no idea what should be wrong. (Does it mean there is something wrong with OTBR? But if I execute `service otbr-agent status` on raspberry pi I get otbr-agent is running and for command  `ot-ctl state` the response is Leader.  

Can anybody help me figure it out? Thank you.

If you want to see full output from the command, you can find it here.

Parents
  • Hi,

    thank you for your answer.

    Yes, I pressed button 4 before executing the command. I also tried to execute the command without pressing button 4 and the command outputs lines something like: "device {address} does not seem to be matter device".

    I also looked at the terminal from the development kit and it seems it's doing something. I don't have the development kit with me right now, but I can send you the output from the uart terminal in few hours. 

Reply
  • Hi,

    thank you for your answer.

    Yes, I pressed button 4 before executing the command. I also tried to execute the command without pressing button 4 and the command outputs lines something like: "device {address} does not seem to be matter device".

    I also looked at the terminal from the development kit and it seems it's doing something. I don't have the development kit with me right now, but I can send you the output from the uart terminal in few hours. 

Children
No Data
Related