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

[filipmrazek]

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.

[Charlie]

Hi Filipmrazek,

See the following suggestion for a similar issue, is this your case?

The possible reason may be that you are trying to use an already-reserved nodeID to commission the device. A typical mistake is the following scenario:

1) Developer commissions device using node ID 1

2) Developer factory resets the device

3) Developer tries to commission the same device using node ID=1.

In such a case, OTBR won't allow to register the same service again because it thinks it's already reserved. Resetting OTBR can be a workaround. Please also make sure that you are using the latest OTBR.

Best regards,

Charlie

[filipmrazek]

Hi Charlie,

thank you for your reply. This shouldn't be my case, because I have never successfully commissioned a device. Anyway, I tried to update my OTBR to the newest version (nrfconnect/otbr:1813352) and used the Node ID I never used. Unfortunately, I'm getting the same error. 

Maybe I forget to mention that I'm using OTBR within docker-compose with the following config:

version: '3.0'

networks:
  otbr:
    external: true

services:
  otbr:
    container_name: otbr
    image: nrfconnect/otbr:1813352
    privileged: true
    networks:
      - otbr
    volumes:
      - /dev/ttyACM0:/dev/radio
    ports:
      - 8080:80
    sysctls:
      - net.ipv6.conf.all.disable_ipv6=0
      - net.ipv4.conf.all.forwarding=1
      - net.ipv6.conf.all.forwarding=1
    command: --radio-url spinel+hdlc+uart:///dev/radio?uart-baudrate=1000000

EDIT: One more thing I noticed: In OTBR frontend, I cannot load topology, it's still loading. I would expect there will be only the connected co-processor as a leader.