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 Varun,

    I assume you are following Overview  |  OpenThread to set up OTBR. Do you have RCP plugged in properly and detected? Unfortunately, I am not familiar with OTBR too much except for using it on RPI directly. I suggest you check with the OTBR developers here Issues · openthread/ot-br-posix (github.com).

    Some explanation about my previous suggestions:

    1) Matter(former Project CHIP) provides OTBR, commissioner tools in the beginning to help developers with their Matter accessaries development, but the setup process is complex and these tools may be less maintained now due to more commercial smart home ecosystems starting to support Matter. If you are just developing or testing Matter devices, I strongly suggest you use Apple Homekit(Homepod Mini), Google Home(Nest Hub), and so on for your development instead of setting up your own environment.

    2) If you still want to use the original Matter development environment, please make sure you tested with a known working Matter device (running Thread protocol for your test specifically) like Matter samples — nRF Connect SDK 2.4.0 documentation (nordicsemi.com), this will save some efforts to test with some uncertain device. 

    Best regards,

    Charlie  

Reply
  • Hi Varun,

    I assume you are following Overview  |  OpenThread to set up OTBR. Do you have RCP plugged in properly and detected? Unfortunately, I am not familiar with OTBR too much except for using it on RPI directly. I suggest you check with the OTBR developers here Issues · openthread/ot-br-posix (github.com).

    Some explanation about my previous suggestions:

    1) Matter(former Project CHIP) provides OTBR, commissioner tools in the beginning to help developers with their Matter accessaries development, but the setup process is complex and these tools may be less maintained now due to more commercial smart home ecosystems starting to support Matter. If you are just developing or testing Matter devices, I strongly suggest you use Apple Homekit(Homepod Mini), Google Home(Nest Hub), and so on for your development instead of setting up your own environment.

    2) If you still want to use the original Matter development environment, please make sure you tested with a known working Matter device (running Thread protocol for your test specifically) like Matter samples — nRF Connect SDK 2.4.0 documentation (nordicsemi.com), this will save some efforts to test with some uncertain device. 

    Best regards,

    Charlie  

Children
No Data
Related