Inquiry regarding Manual Pairing Code length

RE: Inquiry regarding Manual Pairing Code length

Elfving — Wed, 11 Mar 2026 14:51:58 GMT

Thanks for your patience here. So you need it programmatically. I assume you have tried PrintOnboardingCodes, which is used in some of our SDK samples (eg. this one). I am a bit uncertain if that gives you the short version, but I believe it does.

EDIT: Got some input from R&D here:

More specifically he needs to use this util GetManualPairingCode. Please note however, that Manual Pairing Code includes the Passcode. While device should have just SPAKE2+ Verifier (which is "encoded" passcode). The API will work only when Passcode is part of Factory Data.

In general both QR Code and Manual Pairing Code should be created during manufacturing and the fact we are showcasing QR code and Manual Pairing Code in the uart logs is just for debugging purpose -> but this is not always (in fact it should not be) possible to get from firmware (because of this passcode).

Regards,

Elfving

RE: Inquiry regarding Manual Pairing Code length

SunHuang — Mon, 02 Mar 2026 05:56:41 GMT

Hi,

Thanks for the response, but I think there's a misunderstanding. I am not looking for how to generate the code via chip-tool.

My requirement is to retrieve the 11-digit Manual Pairing Code format directly via an API call within the MCU firmware (e.g., after a reboot). I need the device to be able to read its own 11-digit pairing code programmatically to display it on a local screen or output it via UART.

In NCS (nRF Connect SDK), is there a specific API or a helper function in the Matter stack (connectedhomeip) to calculate or fetch the Short Format (11-digit) manual pairing code instead of the 21-digit one?

I have looked into ConfigurationManager and SetupPayload, but I would appreciate a code snippet or a specific function name that returns the 11-digit string.

RE: Inquiry regarding Manual Pairing Code length

Elfving — Fri, 13 Feb 2026 08:22:10 GMT

Then I understand the reasoning behind it.

Did you have any problems using the chip-tool command? My coworker here might describe its use better than I.

Regards,

Elfving

RE: Inquiry regarding Manual Pairing Code length

SunHuang — Fri, 13 Feb 2026 02:09:28 GMT

My goal is to implement a way for an external controller to read the Manual Pairing Code during mass production.

Since the 21-digit code is quite long for labeling and manual entry, I’m looking into using APIs to recalculate and force it into the 11-digit format.

I already have a general direction for the implementation (likely by stripping the VID/PID from the payload generation logic), but I’d appreciate it if you could share any other methods or best practices you’ve encountered. I'm always looking for a more robust or efficient approach for the production line.

Looking forward to your thoughts!

RE: Inquiry regarding Manual Pairing Code length

Elfving — Thu, 12 Feb 2026 09:22:09 GMT

Hi,

Having a quick look at the spec, I see that:

The required and optional elements, along with a check digit, are encoded into either an 11-digit or 21-digit decimal numeric string, depending on whether the optional Vendor and Product ID information is included.

Have you tried 'force-short' with the chip-tool?

./chip-tool payload generate-manualcode [--existing-payload] [--discriminator] [--setup-pin-code] [--version] [--vendor-id] [--product-id] [--commissioning-mode] [--allow-invalid-payload] [--force-short-code]

Regards,

Elfving