Can't connect to nRF52840-DK with Python CHIP Controller

[mihnea17cristian]

Hi,

I have an issue in regard to Matter. I would like to commision a device in my network, but I don't know why the Python CHIP Controller returns this error every time I try to talk to the device:

chip-device-ctrl > connect -ble 3840 20202021
Device is assigned with nodeid = 171557
[1648823813.002918][34530:34536] CHIP:IN: Prepared unauthenticated message 0x7f808d8f4940 to 0x0000000000000000 (0) of type 0x20 and protocolId (0, 0) on exchange 28181i with MessageCounter:2474507507.
[1648823813.003042][34530:34536] CHIP:IN: Sending unauthenticated msg 0x7f808d8f4940 with MessageCounter:2474507507 to 0x0000000000000000 at monotonic time: 7839668 msec
[1648823813.003077][34530:34536] CHIP:CTL: Network commissioning parameters are required for BLE auto commissioning.
CHIP Error 0x0000002F: Invalid argument
chip-device-ctrl > [1648823813.019544][34530:34534] CHIP:BLE: BLE removing known devices.
[1648823813.024382][34530:34534] CHIP:BLE: BLE initiating scan.
[1648823813.340056][34530:34534] CHIP:BLE: Failed to start discovery: GDBus.Error:org.bluez.Error.InProgress: Operation already in progress
[1648823843.004362][34530:34536] CHIP:SC: PASESession timed out while waiting for a response from the peer. Expected message type was 33
Failed to establish secure session to device: 50
Segmentation fault (core dumped)

I followed the instructions from this video:

https://www.youtube.com/watch?v=kdMJQFDRoss

Has anyone encountered this same issue? Thanks!

[mihnea17cristian]

Hi

I couldn't make the CHIP Contoller work on the VM. Fortunately, I hav a spare nVidia Jetson NX laying around and I managed to run the controller on that (on ubuntu 20.04).

However, after continuing with the webinar, I am not able to issue the command:

zcl NetworkCommissioning AddThreadNetwork ....

The error is the following:

An exception occurred during process ZCL command:
UnknownCommand: cluster: NetworkCommissioning, command: AddThreadNetwork

Does anybody know what this is about?

[Sigurd Hellesvik]

Hi

Try to use "AddOrUpdateThreadNetwork" instead.
Does that change anything?

Regards,
Sigurd Hellesvik

[Sigurd Hellesvik]

Hi

This error looks like the one in case 84317.

Try to follow the advise from Charlie in the case; Does it fix your issue?

Regards,
Sigurd Hellesvik

[mihnea17cristian]

Hi

So first, I checked the poste you shared with me, but it's the same as closing the ble connection and then running the resolve command, right? Which is exactly what I was doing...

Second, can you please tell me what python version I need to have to be able to run the chip-tool, and also how much free disk space is needed?

Thank you,
Mihnea Cristian Marin

[Sigurd Hellesvik]

Hi

I were unable to find the size and python version of chip-tool.
I suggest you make an issue on https://github.com/project-chip/connectedhomeip asking for this if you want to know.

From your past issue with the python chip controller, I found this issue, having a very similar log to your issue.
Maybe you are able to solve it from the discussion in that issue?

Regards,
Sigurd Hellesvik

[mihnea17cristian]

Hi

I would follow the steps on the last link you sent me, but right now I don't have enough space on the device...Once I manage to clean it and install the chip-tool, I will send you may status.

Regards,

Mihnea Cristian Marin

[mihnea17cristian]

Hi

I managed to install Matter and the chip tool on a bigger sd card (on the same nvidia jetson). However, by git cloning the repo and installing the chip tool, when I try to commision the device, I receive the same error from the first post on this ticket.

After some digging and finding this post https://github.com/project-chip/connectedhomeip/issues/6951, if I checkout to commit 762a204b04049dac01c7ecf8f695ddd58f085c29 I would get this error:

./chip_tool/chip-tool pairing ble-thread hex:0e080000000000010000000300000f35060004001fffe0020811111111222222220708fde7466588be63af051000112233445566778899aabbccddeeff030e4f70656e54687265616444656d6f010212340410445f2b5ca6f2a93a55ce570a70efeecb0c0402a0fff8 20202021 3840
[1651678493.027787][52926:52926] CHIP:CTL: Read local id 0x000000000001B669, remote id 0x0000000000BC5C01
[1651678493.037072][52926:52926] CHIP:IN: UDP::Init bind&listen port=5541
[1651678493.037151][52926:52926] CHIP:IN: UDP::Init bind&listen port=5541
[1651678493.037203][52926:52926] CHIP:IN: TransportMgr initialized
[1651678493.037221][52926:52926] CHIP:DIS: Init fabric pairing table with server storage
[1651678493.038040][52926:52926] CHIP:IN: Loading certs from KVS
[1651678493.038069][52926:52926] CHIP:IN: local node id is 0x000000000001B669
[1651678493.039022][52926:52926] CHIP:DL: MDNS failed to join multicast group on eth0 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:259: Inet Error 0x00000110: Address not found
[1651678493.039723][52926:52926] CHIP:DL: MDNS failed to join multicast group on rndis0 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:259: Inet Error 0x00000110: Address not found
[1651678493.040110][52926:52926] CHIP:DL: MDNS failed to join multicast group on usb0 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:259: Inet Error 0x00000110: Address not found
[1651678493.040409][52926:52926] CHIP:ZCL: Using ZAP configuration...
[1651678493.040486][52926:52926] CHIP:ZCL: deactivate report event
[1651678493.040511][52926:52926] CHIP:CTL: Getting operational keys
[1651678493.040525][52926:52926] CHIP:CTL: Generating credentials
[1651678493.040948][52926:52926] CHIP:CTL: Loaded credentials successfully
[1651678493.041282][52926:52931] CHIP:DL: CHIP task running
[1651678493.041332][52926:52926] CHIP:TOO: InitArgs: Wrong arguments number: 3 instead of 4
Usage:
  ./chip_tool/chip-tool pairing ble-thread operationalDataset fabric-id setup-pin-code discriminator
[1651678493.041431][52926:52926] CHIP:TOO: Run command failure: ../examples/chip-tool/commands/common/Commands.cpp:183: CHIP Error 0x0000002F: Invalid argument
[1651678493.041614][52926:52926] CHIP:CTL: Shutting down the commissioner
[1651678493.041656][52926:52926] CHIP:CTL: Shutting down the controller
[1651678493.041717][52926:52926] CHIP:DL: Inet Layer shutdown
[1651678493.041872][52926:52926] CHIP:DL: BLE layer shutdown
[1651678493.041887][52926:52926] CHIP:DL: System Layer shutdown

However, if I checkout to 8dc938d63504e0e44d204eca505cc893fbc4d690, the command asks me for fabric_id. What is that?

Regards,

Mihnea Cristian Marin

[Sigurd Hellesvik]

A Fabric is a logical collection of communicating Nodes, sharing a common root of trust,
and a common distributed configuration state.
To read more about it, see the Matter Specification.

The Specification is still not public, so you will have to contact the Matter Group if you need access to it.

I have installed both the python chip controller and the chip-tool on my computer and is testing the commissioning myself as well now.
Do not know if it is what you want to hear, but I am facing some issues myself.

When I get it to work successfully, I will share my experience with you.

Regards,
Sigurd Hellesvik

[Sigurd Hellesvik]

Hi

Have you enabled Router Advertisement on your OTBR, as explained in https://openthread.io/codelabs/openthread-border-router#6?

Regards,
Sigurd Hellesvik

[mihnea17cristian]

Hello

Yes, the 'ot-ctl br enable' command returned 'Done', but I don't see why this helps right now considering my issues are when I try to connect to a device using BLE, in order to connect it after to the thread network.

Regards,

Mihnea Cristian

[Sigurd Hellesvik]

Hi

Bluetooth Low Energy is only used to initiate the commissioning.
As a part of the commissioning, the Matter device is connecting to the thread network and the OTBR.

If the OTBR is not configured correctly, this may impact the commissioning.

Did you check net.ipv6.conf.wlan0.accept_ra as well?

Regards,
Sigurd Hellesvik

[mihnea17cristian]

Hi

Yes, its value is 2.

Regards,

Mihnea Marin