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!
