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

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!

Parents
  • 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:

    Does anybody know what this is about?

  • Hi

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

    Regards,
    Sigurd Hellesvik

  • Hi

    I used it and it works, also used the "ConnectNetwork" instead of "EnableNetwork". However, when I try to run the "resolve" command (only with nodeid as parameter), it doesn't do anything other than quitting the chip-device-ctrl.... Is there a substitute for the resolve command also?

    Thank you,

    Mihnea Marin

  • Hi

    I do not think there are any other command doing the same as the resolve command.
    Do you get any error message from the resolve command?

    Just so you know: As an alternative to the Python Chip Controller, you could try the chip-tool for Linux of MacOS.

    Regards,
    Sigurd Hellesvik

Reply Children
  • This is the output

  • 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

  • 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

  • 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

  • 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