Attachments (0)
Nordic Case Info
  • Case ID: 286937
Options

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!

Parents
  • 0

    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?

  • 0 in reply to mihnea17cristian

    Hi

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

    Regards,
    Sigurd Hellesvik

  • 0 in reply to 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:

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

    Regards,

    Mihnea Cristian Marin

  • 0 in reply to mihnea17cristian

    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

  • 0 in reply to 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

  • 0 in reply to Sigurd Hellesvik

    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

  • 0 in reply to mihnea17cristian

    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

Reply
  • 0 in reply to mihnea17cristian

    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

Children
Terms of service