Reference · built on requestConnectorIndustrial & building protocols

Matter

Attributes, events, and commands from Matter devices over Wi-Fi, Thread, and Ethernet, through a controller on the fabric.

Request accessPricing ↗

About

Matter is an IP-based application protocol from the Connectivity Standards Alliance. It runs over IPv6 on Ethernet, Wi-Fi, and Thread, and uses Bluetooth Low Energy only to commission a device. A device is a Node made of Endpoints; each Endpoint holds Clusters, and a Cluster holds Attributes, Commands, and Events. Device Types such as Dimmable Light or Door Lock fix which Clusters are mandatory. Nodes that share a root certificate and a 64-bit Fabric ID form a Fabric. The reference SDK is open source under the Apache 2.0 license.

Through Fibric, a connector acts as a Controller on your fabric. It reads and subscribes to Attributes and Events and, when an operator proposes a Command or an Attribute write, sends it once after your approval.

This is a reference listing. It documents what Fibric would read from Matter and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Attribute values on any server Cluster, read by path: node, endpoint, cluster, attribute
  • Subscriptions that deliver Report Data as Attributes change, in place of polling
  • Events, a journal of past state transitions with a counter, a timestamp, and a priority
  • Endpoint structure from the Descriptor Cluster on endpoint 0, which lists each endpoint's server and client Clusters and its Device Types
  • Vendor ID, Product ID, Product Name, and Serial Number from the Basic Information Cluster
  • Devices bridged from other technologies such as Zigbee, exposed as Endpoints on a Bridge node

Proposed actions

  • Target capability: propose invoking a Command on a Cluster, such as On/Off on a light or lock on a Door Lock, for your approval
  • Target capability: propose a Write to an Attribute on a server Cluster, such as a thermostat setpoint
  • Target capability: propose a Groupcast Command to a Group ID so several Nodes act in one Action

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Reset the meeting room between bookings

    Lights, blinds, and the thermostat in a room are Matter Endpoints. After a booking ends, the operator proposes the room's default Commands as one batch and records which nodes answered.

    With Meeting Room Reset

  • Audit what stayed on overnight

    A subscription to On/Off attributes across the fabric lists every device still on after closing. The operator proposes Off for each and leaves a receipt naming the endpoint.

    With After-Hours Audit

  • Locks that report their state

    Door Lock cluster attributes and events show a lock that is not engaged. The operator proposes the lock Command and notes the event counter it acted on.

    With Door Held Open

  • Setpoints that wander

    Thermostat attributes read by path show each room's setpoint. A value outside the schedule gets a proposed Write and a receipt with the value it replaced.

    With Setpoint Drift

Requirements

  • A Matter fabric with a Commissioner that can commission the connector's controller node and obtain its Node Operational Certificate
  • IPv6 reach to the Wi-Fi or Ethernet subnet and to any Thread subnet the fabric spans
  • Devices already commissioned onto the fabric; a new device is commissioned over Bluetooth Low Energy or on-network with its onboarding payload
  • DNS-SD on the local network, which Matter uses for operational discovery of commissioned nodes
Authentication
Node Operational Certificates issued when the connector's controller is commissioned onto your fabric; each session is established with Certificate Authenticated Session Establishment (CASE).

Limits

  • Matter runs on the local IPv6 network without needing globally routable IPv6, so the connector must sit on that network
  • Bluetooth Low Energy is a commissioning transport only; it cannot be the sole transport for a device
  • The Matter specification, Application Cluster Library, and Device Library are downloaded from the Alliance site and are not public domain
  • A Fabric shares one root of trust; devices on another ecosystem's fabric are reachable only after they are commissioned onto yours

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Matter ↗

Questions and answers

Which networks does Matter run on?
Ethernet, Wi-Fi, and Thread, all over IPv6. Bluetooth Low Energy is used during commissioning to pass Wi-Fi or Thread credentials to a new device and is required for Thread devices. Matter cannot use Bluetooth as its only transport.
How does a controller get access to devices?
By commissioning. A Commissioner connects with the device's passcode over PASE, checks its Device Attestation Certificate, installs the fabric's root certificate and a Node Operational Certificate, and provisions the network. Later sessions use CASE with those certificates.
Can Matter reach Zigbee or Z-Wave devices?
Yes, through a Bridge. The Matter handbook describes a Bridge as a member device of both a Matter network and the bridged technology, so Zigbee, Bluetooth Mesh, and Z-Wave devices can be operated as if they were Matter devices.
Ask about Matter

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Matter through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy