What distinguishes the nrfconnect/sdk-connectedhomeip repositories from utilizing the chip/connectedhomeip repository directly for constructing Matter products?

[Anthony Shivakumar]

When employing the chip/connectedhomeip repository, I can successfully build without encountering any errors. However, when I follow the instructions outlined on this page: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/protocols/matter/getting_started/testing/thread_one_otbr.html and use the source code available here: https://github.com/nrfconnect/sdk-connectedhomeip/releases, I encounter unexpected errors during the build process.

Is there a method to seamlessly integrate the connectedhomeip repository with nRF SDK 2.4.2 to ensure compatibility and avoid these issues?

  error: subprocess-exited-with-error
 
  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> See above for output.
 
  note: This error originates from a subprocess, and is likely not a problem with pip.
  Getting requirements to build wheel: finished with status 'error'
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.
['/home/antshiv/Software/sdk-connectedhomeip/.environment/pigweed-venv/bin/python', '-m', 'pip', 'install', '--log', '/home/antshiv/Software/sdk-connectedhomeip/.environment/pigweed-venv/pip-requirements.log', '--requirement=/home/antshiv/Software/sdk-connectedhomeip/scripts/setup/requirements.txt', '--constraint=/home/antshiv/Software/sdk-connectedhomeip/scripts/setup/constraints.txt'] {'stdout': <_io.TextIOWrapper name=3 mode='w+' encoding='UTF-8'>, 'stderr': -2}

None
Traceback (most recent call last):
  File "/home/antshiv/Software/sdk-connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/env_setup.py", line 877, in <module>
    sys.exit(main())
  File "/home/antshiv/Software/sdk-connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/env_setup.py", line 869, in main
    return EnvSetup(**vars(parse())).setup()
  File "/home/antshiv/Software/sdk-connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/env_setup.py", line 522, in setup
    result = step(spin)
  File "/home/antshiv/Software/sdk-connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/env_setup.py", line 682, in virtualenv
    if not virtualenv_setup.install(
  File "/home/antshiv/Software/sdk-connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/virtualenv_setup/install.py", line 296, in install
    pip_install(
  File "/home/antshiv/Software/sdk-connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/virtualenv_setup/install.py", line 262, in pip_install
    return _check_call(cmd)
  File "/home/antshiv/Software/sdk-connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/virtualenv_setup/install.py", line 88, in _check_call
    subprocess.check_call(args, **kwargs)
  File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/home/antshiv/Software/sdk-connectedhomeip/.environment/pigweed-venv/bin/python', '-m', 'pip', 'install', '--log', '/home/antshiv/Software/sdk-connectedhomeip/.environment/pigweed-venv/pip-requirements.log', '--requirement=/home/antshiv/Software/sdk-connectedhomeip/scripts/setup/requirements.txt', '--constraint=/home/antshiv/Software/sdk-connectedhomeip/scripts/setup/constraints.txt']' returned non-zero exit status 1.

[Amanda Hsieh]

Hi, 

What version of the https://github.com/nrfconnect/sdk-connectedhomeip are you using? Please use the same version as the NCS and follow this guide Working with the CHIP Tool. 

Regards,
Amanda H.

[Anthony Shivakumar]

I have a video youtube.com/.../xd9S0ZlmL1c demonstrating the challenges I'm encountering when attempting to connect via WiFi using a Linux-based Matter controller.

Here's my issue: I'm working on using Matter over WiFi with a Linux computer as the Matter controller. I have three boards, which consist of two NRF700DKs and one 5340DK. I've successfully commissioned one of the NRF700DKs, but I'm facing difficulties commissioning the other.

Occasionally, I can control the LED with the device that has been commissioned using the Matter controller, but sometimes it doesn't work as expected. How can we go about troubleshooting these problems?

Additionally, I'm curious about the concept of the "node ID." If I have three Matter accessories, how do they determine their respective node IDs? Strangely, one of the NRF700DKs accepts node ID 1, but I'm struggling to get the other one commissioned. Any assistance would be greatly appreciated.

Also,
Regarding the NRF002 devices, one of them successfully commissions, but the other does not. I understand that node IDs need to be unique, but how do these devices determine which ID to assign when they are all awaiting commissioning? If it's a random assignment, it doesn't seem like an efficient way to troubleshoot for a couple of reasons:

    With many accessories, you might not know which ID is already taken.
    It becomes challenging to figure out why a unique node ID didn't commission an available accessory.

The only solution appears to be repeatedly trying different node ID numbers until one successfully commissions. Is there a more effective method for assigning node IDs?

[Amanda Hsieh]

Hi, 

Anthony Shivakumar said:

Occasionally, I can control the LED with the device that has been commissioned using the Matter controller, but sometimes it doesn't work as expected. How can we go about troubleshooting these problems?

Please provide the from both the device and the chip tool. 

Anthony Shivakumar said:

how do they determine their respective node IDs?

The node ID is defined by you when you pair the device, so you can set this to what you want the ID to be.

-Amanda H.