Overview

Commissioning adds a Matter device to a fabric and, for RainMaker Matter devices, links the Matter node to the RainMaker cloud account.

What this module does

End users scan a QR code (or paste an onboarding payload). Your app must:

1. Run the Matter pairing session (native)
2. Obtain a device CSR and issue a Node Operational Certificate (cloud)
3. Confirm the node with RainMaker (cloud), including challenge-response for RainMaker Matter devices

The SDK provides a high-level startCommissioning API; you can also drive issueNodeNoC and confirmMatterNodeCommissioning yourself.

Node types

Node type	Description
rainmaker_matter	Node on Matter fabric and RainMaker cloud; requires rainmakerNodeId, challenge response
pure_matter	Matter-only Node on the fabric

Prerequisites

• Logged-in userInstance
• Fabric created and fabric details loaded via getFabricDetails()
• matterCommissioningAdaptor configured

Documentation

Commission Adaptor

• What the adaptor implements (generateCSR, startEcosystemCommissioning, postMessage)
• How the SDK uses it with startCommissioning

Device commissioning

• Recommended: fabric.startCommissioning with progress callback
• Manual flow for custom UI or debugging
• Platform behavior (iOS vs Android)

Native Bridge

• How React Native, platform Matter UI, CHIP, and Headless JS connect during commissioning
• Android native bridge — ChipTool commissioning + ChipDeviceController + ESPMatterModule
• iOS native bridge — Apple MatterSupport + MTRDeviceController + ESPMatterModule