Commission Matter accessory using the Android CHIPTool and then control it with the Python CHIP controller, and vice versa

Hi,

I have been trying out the Matter samples as shown in this webinar. I have been following the instructions for version 1.7.0 of the SDK, specifically the ones in Configuring Matter development environment. In turn, the instructions pointed me to Thread border router, Working with Python CHIP controller, and Commissioning nRF Connect Accessory using Android CHIPTool.

After configuring the Thread Border Router using a Raspberry Pi and building the software for the radio co-processor, downloading the pre-built Python CHIP controller from GitHub, and installing the Android CHIPTool, I tried to follow the instructions in Using Python CHIP Controller for Matter accessory testing. I have managed to commission the Matter Accessory to the Thread network and toggle the LED on the device using the Python controller. However, I can only get the tool to work if I set the Node ID to 1. Furthermore, even though I have checked that the Fabric ID is (in this case) 1 using get-fabricid, I still need to use the hard-coded Fabric ID (5544332211) to Discover IPv6 address of the Matter accessory.

Once I have commissioned the accessory, I cannot discover it again using the known Fabric and Node ID values with the Android CHIPTool. That is, if I did the commissioning with the Python CHIP controller, I cannot use the Android tool to send CHIP commands as shown in these instructions. My first question: is this problem related to the issue mentioned in the known issues document (KRKNWK-11225: Android CHIPTool cannot communicate with a Matter device after the device reboots)?

Conversely, I have successfully commissioned and controlled the Matter accessory using the Android CHIPTool, but I cannot then use the Python CHIP controller to discover the IPv6 address of the accessory (even though I know the Fabric and Node IDs), and therefore, cannot control the accessory using the Python controller.

For reference, I have made sure to use the same version of the SDK (1.7.0) when building the Matter sample and the software for the OpenThread Border Router, the Python CHIP controller, and have used the specific version of the radio co-processor per the instructions in Installing OTBR manually (Raspberry Pi).

My second question: am I missing some steps in order to commission the Matter accessory with the Android CHIPTool, and then control it with the Python CHIP controller, and vice versa?

I will appreciate any information you can provide.

  • Hi David,

    I am sorry for the very late reply, but I am looking into this now, so will give you an answer as soon as possible.

    Best regards,

    Marjeris

  • Hi David,

    I am very sorry I haven't been able to provide answers to your questions yet. I have forwarded your questions to our Matter team since I am quite new at working in the Matter enviroment myself so hasn't been able to find out how the Android CHIP tool is support to work yet.. Just let me know if you have any progress in the issue or if you have other questions.

    Best regards,

    Marjeris

Related