Matter Device Commissioning – STM32WB5MM-DK & NUCLEO-WB55RG Unable to Join Thread Network

[AkihiroN]

I am developing a Matter device (Thread) using the STM32WB5MM-DK and NUCLEO-WB55RG.

When commissioning the device using the Google Home app on a Google Nest Hub:

The first STM32WB5MM-DK was successfully commissioned.
However, the second STM32WB5MM-DK failed to join the Thread Network.
I encountered the same issue when using NUCLEO-WB55RG.
I have attached the error logs for reference.

To troubleshoot the issue, I modified the Device Attestation Certificate (DAC) in the firmware and tested commissioning again:

NUCLEO-WB55RG was successfully commissioned with the modified DAC.
However, STM32WB5MM-DK still failed, even with the modified DAC.

Questions:
Is it expected behavior that the ability to join the Thread Network depends on the DAC when commissioning with a Google Nest Hub?
Why does changing the DAC allow NUCLEO-WB55RG to join the Thread Network, but not STM32WB5MM-DK?
Could there be differences in how the Google Home app or Google Nest Hub handles DAC validation for different hardware?
What specific checks does the Google Home app or Google Nest Hub perform regarding the DAC?
Can you confirm if the same issue occurs on your side?
I am using the following repositories for testing:

NUCLEO-WB55RG: https://github.com/stm32-hotspot/stm32wb-matter-device-over-thread
STM32WB5MM-DK: https://www.st.com/ja/embedded-software/x-cube-matter.html

Any insights or guidance would be greatly appreciated.
Thank you in advance!

[Ouadi]

Hi @AkihiroN,

After analyzing the provided logs, it seems that the device fails to find an operational thread network, even after scanning all the channels, the issue looks related to thread network stability and not to Data factory parameters.

Please note that the data factory management is done using the flag CONFIG_STM32_FACTORY_DATA_ENABLE set to 0 for test meaning that Matter test VID/PID & certificates will be used at commissioning time.

From the logs, I see that you are using a very old version of X-Cube-Matter V 1.0.3, so as a first step I suggest to update the version to the latest one v1.1.1 and make sure to update the STM32WB M0 firmware as well.

Since this version, there have been some improvements linked to radio robustness that may solve your issue.

Also, please make sure to put the device close to the Google Nest for the commissioning phase.

I hope this helps.

Best regards, Ouadi

[AkihiroN]

Hello, @Ouadi 

Thank you for your confirmation.
Yes, I too believe that it may be a threading network issue, not a data factory parameter.
What I think is the problem is that this problem occurs on the second STM32WB5MM-DK, while the first STM32WB5MM-DK can be commissioned successfully without this problem.
Also, both NUCLEO-WB55RGs were successfully commissioned by changing the first DAC and the second DAC.
With STM32WB5MM-DK, this problem occurs even if the second DAC is changed.

I will also attach the logs, but this problem still occurs even with the latest X-Cube-Matter v1.1.1.
This problem occurs only in the Google environment and not in the Apple or Amazon platforms.

Is there any solution to this problem?

 

 

Translated with DeepL.com (free version)

[Ouadi]

Hello,

Is this problem occurs only with the same STM32WB5MM-DK board ? As you mentioned, the commissioning is successful with the first STM32WB5MM-DK board and Nucelos. So it may be linked to this specific board, Can you try to commission with a third board to confirm ?

Have you done a full chip erase + external flash memory erase before testing ?

Regards,

Ouadi

 

[AkihiroN]

Hello, @Ouadi 

 

How is it going since then?
Have you been able to confirm the phenomenon?

[Ouadi]

Hi @AkihiroN,

The setup you described is working properly on my side, I can commission multiple STM32WB5MM-DK to Google Nest thread Matter network with no issues and no modification in the firmware.

The only difference we may have both of us is the radio environnement that may have an impact.

If the issue still persists, please raise a ticket on our online website and provide much more information about your test environment, logs and sniffer file to further analyze => Online Support

Best regards,

Ouadi