Matter Fabric Interface

about

ESP RainMaker Matter Fabric Interface is an optional cloud API add-on. It is not required to build, commission, or control Matter devices with ESP RainMaker. It is intended mainly for cloud-to-cloud integration, where the customer's own business cloud stays in charge and ESP RainMaker provides only the Matter Fabric layer. It can also be used in the unified RainMaker model if a product needs it, though it is not typically required there.

---

The Interface builds on existing RainMaker Matter Fabric Support capabilities and exposes a simplified, Matter-like API. Customer apps and backends do not need to implement a full Matter cloud, certificate authority, controller service, or mobile stack from scratch.

The add-on is not publicly available. Firmware, provisioning, attribute reporting, and remote control can still be evaluated with current Matter products and the matter_controller examples. For production use or add-on access, please contact us.

When you need it

Whether you need the add-on depends on which integration model you use:

• Cloud-to-cloud integration: useful. The customer's own cloud owns users, devices, and business logic. RainMaker supplies only the Matter Fabric layer: fabric management, PKI/NOC issuance, Matter protocol parsing, and controller relay. The Fabric Interface is the cloud API the customer's cloud uses to reach that layer. It can list the Matter devices in a fabric, read and write attributes, and invoke commands, all without building a full Matter backend.
• Unified management on ESP RainMaker: not typically required. Matter and non-Matter devices are managed through the standard RainMaker APIs, the RainMaker Matter App SDK, and the ESP RainMaker Home app. Customers can still choose to use the Fabric Interface if their product needs it.

How it works

A RainMaker Matter controller (dedicated hub, display, gateway, or other ESP device) joins the user's fabric:

1. The controller is provisioned and authorized in the RainMaker product flow.
2. It is bound to the RainMaker group that represents that fabric.
3. Matter devices are commissioned through the product app.
4. The controller keeps a cloud-visible view of online state and selected attributes.
5. Remote Matter operations are routed through the controller when the product needs cloud access.

After RainMaker authentication, the customer's app or backend can use the Fabric Interface to:

• List Matter devices in fabrics
• Work with devices, attributes, and commands in a descriptive, human-readable JSON data model instead of the raw Matter data model with numeric cluster, attribute, and command IDs
• Send read, write, or invoke requests through RainMaker

The application talks to RainMaker and the Fabric Interface. The ESP-based controller handles Matter access inside the home.

Combine with other Espressif solutions

The Interface can sit alongside ESP Private Agents for natural-language control, OpenThread Border Router products for Matter-over-Thread, and display, gateway, or hub designs that mix RainMaker remote access, Matter, local UI, voice, or automation. Architecture is product-dependent. Start from the Matter controller examples and discuss the fit with Espressif.

Evaluate without the add-on

Without the add-on, you can already validate:

• Provisioning Matter devices into a RainMaker-associated fabric with the ESP RainMaker Home app
• Attribute subscription and cloud reporting
• Remote Matter control through RainMaker command-response

See Try it on the Matter Fabric Support overview, and the RainMaker Controller docs. For add-on access and architecture guidance, contact Espressif.