FAQs
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Failed to commission with Google Nest Hub.

AkihiroN
Associate III

‎2024-08-20 11:57 PM

I am implementing a Matter device using the STM32WB5MMG. When attempting to commission the device with a Google Nest Hub, it fails to join the Thread Network.

Upon reviewing the logs, it appears that the NOC (Node Operational Certificate) verification is successful, but when trying to connect to the Google Nest Hub using the Thread Network information, there seems to be no response from the Google Nest Hub.

Could you suggest any solutions for this issue?

Labels:
Preview file
50 KB
4 REPLIES 4
Ouadi
ST Employee

‎2024-08-29 04:38 AM

Hello @AkihiroN,

Looking at your logs, as you mentioned, it seems that the end device does not receive any response from the thread leader ( Nest Hub) on the channel 18, so it moves to the next channel. Can you please describe the setup especially the distance between the Nest hub and the end device ? Is it possible to move the device as closer as possible to the border router for test, and share the Google home application output.

Could you also provide binaries version you are using ?

Thanks & best regards,

Ouadi

0 Kudos
AkihiroN
Associate III
In response to Ouadi

‎2024-09-01 05:53 PM

Thank you for your confirmation.
We can confirm the same phenomenon when the device is placed close to the Google Nest Hub.
Google Home App shows the following logs.
[Unable to connect to threaded network (NEST-PAN-577A)].
I have erased all Thread/BLE Stack binary on M0+ side, application binary and external memory on M4 side as a test, and the same phenomenon is confirmed.
Please check the above.

0 Kudos
AkihiroN
Associate III
In response to AkihiroN

‎2025-01-28 05:03 PM

Hi @Ouadi 

oogle has confirmed that each device should use a unique QR code.
I am developing using X-CUBE-MATTER v1.1.1 and would like to know how to generate a unique QR code for each device.

0 Kudos
Ouadi
ST Employee
In response to AkihiroN

‎2025-01-29 05:42 AM - edited ‎2025-01-29 09:10 AM

Hi @AkihiroN,

You can use either the Python script following this link : connectedhomeip/src/setup_payload/python at master · project-chip/connectedhomeip · GitHub

Or using the Chip-Tool :

 

// Generate the QR Code 
chip-tool payload generate-qrcode --discriminator 3840 --setup-pin-code 20202021 \
                                  --vendor-id 0xFFF1 --product-id 32768 \
                                  --version 0 --commissioning-mode 0 --rendezvous 2

// Generate the short manual pairing code (11-digit).
chip-tool payload generate-manualcode --discriminator 3840 --setup-pin-code 20202021 \
                                      --version 0 --commissioning-mode 0

// Generate a long manual pairing code (21-digit) that includes both the vendor ID and product ID,
// --commissioning-mode parameter must be set to either 1 or 2, indicating a non-standard commissioning flow.
chip-tool payload generate-manualcode --discriminator 3840 --setup-pin-code 20202021 \
                                      --vendor-id 0xFFF1 --product-id 32768 \
                                      --version 0 --commissioning-mode 1

 

You can also have a look on our wiki page : Connectivity:Matter develop and prototype - stm32mcu to know how to customize the device Discriminator, Serial Number and get the updated QR code through the UART log.

Best regards,

Ouadi

0 Kudos
Top