fabric

package module

v0.8.4 Latest Latest Go to latest Published: Oct 19, 2026 License: Apache-2.0 Imports: 0 Imported by: 0

Details

Valid go.mod file
Redistributable license
Tagged version
Stable version
Learn more about best practices

Repository

github.com/SukramJ/go-fabric

Links

Open Source Insights

README ¶

go-fabric

go-fabric is a pure-Go implementation of the Matter protocol, packaged as a library a host application embeds. On the device side it brings the TLV codec, the Interaction Model, PASE and CASE session establishment, MRP over IPv6 UDP and TCP, DNS-SD advertisement, the cluster servers a bridge needs (including the media clusters, the OTA requestor and provider, and DiagnosticLogs over BDX), and the endpoint assembler that turns a host's own device list into a Matter topology. The host keeps its device model; this module owns the wire format and hands back the port contracts (contract/) a device implements to appear as a bridged endpoint. On the controller side (controller/, ADR 0020) it is a full commissioner: discovery, attestation (with the CSA Distributed Compliance Ledger, opt-in), NOC issuance, the client interaction and a typed image of a remote node, bindings and the group sender — examples/reference-controller drives it from the command line. It is a semantic port of matter.js — cluster IDs, revisions, attribute IDs, constraints and wire shape are mirrored from matter.js HEAD rather than transcribed from the specification, and the extracted matter.js element model ships embedded so parity is a test, not a claim.

Status

As of v0.8.4 (2026-10-19); the numbers are the roadmap's baseline.

Area	State
Device side	118 of 135 clusters served, 79 of 91 device types generated (comparison, roadmap)
Controller side	full commissioner (BLE, Wi-Fi and Thread network steps, keys behind `crypto.Signer`, the embedded DCL snapshot), controller role stages 1–6b; Joint Fabric deferred (comparison)
BLE	controller: done with milestone 1 — `ble/bluez` on Linux, `pair --ble`, proven against a matter.js node over virtual controllers; device: milestone 7
Thread	dataset provisioning only, by the commissioner (milestone 1, phase 12); no Thread radio (comparison)
ICD	milestone 5
Certification	not pursued; certifiability is a goal (certifiability)
Verified ecosystems	Apple Home, Home Assistant; Google Home and Alexa pending (roadmap)

Not certified

This is an independent open-source implementation. It is not certified by the Connectivity Standards Alliance, and it is not a project of the Alliance. No warranty or assurance is made about rights that may be required to implement it. Using it does not certify anything: it does not assure compliance with the Matter specification, and it does not convey any right to describe a device, product or service built with it as Matter compliant, certified or similar. Certification requires membership in the Alliance and compliance with Alliance policy; so does any use of Alliance trademarks and logos. See licenses/NOTICE-matter.js.txt, reproduced from matter.js, which states the same terms for the project this one is ported from.

Certification is not pursued by this project. Certifiability is a goal: the module is meant to let a product built on it pass certification, and the CSA certification test families run against the reference daemon to hold it there. What passes, what does not and why, and what a product owner must supply that a library cannot is in docs/certifiability.md (ADR 0011).

Documentation

The site (rendered from docs/) is at https://sukramj.github.io/go-fabric/; the API reference is pkg.go.dev.


`docs/index.md`	Where to start, by role: embedding the device side, driving the controller, evaluating the architecture.
`docs/architecture.md`	The two roles, the layers, the request path, the package map and the scope boundaries that are decisions rather than backlog.
`docs/getting-started/`	A minimal device host and a minimal controller, each a compiling example.
`docs/guides/`	Host ports, concurrency, persistence.
`docs/security.md`	The security model of both roles.
`docs/matterjs-comparison.md`	Feature-by-feature against matter.js, with a verdict on whether each gap is worth closing here.
`docs/certifiability.md`	What the CSA certification families say about this module, family by family.
`docs/matter-parity-contract.md`	What parity means and which standing guards enforce it. Read before your first change.
`docs/matter-ecosystem-observations.md`	What Apple Home, Google Home and Alexa were actually observed to do.
`docs/adr/`	Architecture decision records.
`docs/history/`	Earlier planning concepts (German), kept for their reasoning.
`notes/parity/by_design.md`	The catalogue of intentional divergences from matter.js.
`notes/parity/matter_behaviour_findings.md`	Known behaviour gaps that are not intentional, as scoped fix packages.

Examples

examples/reference-bridge is the reference daemon: a bridge on this module, the binary the chip-tool suite runs against. examples/reference-controller is the controller role as a command-line tool — pair a node by its QR or manual code, read, write, invoke, subscribe, provision groups and bindings, serve an OTA image — with its fabric kept in one SQLite file; its README lists every command.

API stability

The module carries its own SemVer lane, independent of any host that embeds it.

What "public API" means here

Every exported identifier outside internal/ is public API. The module already draws that line for itself: internal/ holds the two one-way seams through which the test-support packages reach package internals (bridgeseam, channelseam) and the chip-tool suite, and Go makes those unimportable from outside. Nothing else is private by convention, so nothing else may be changed as if it were.

Depend freely on bdx/, binding/, bootid/, bridge/, cluster/…, commissioning/, contract/, controller/…, device/, diagevent/, eligibility/, endpoint/ (including endpoint/sqlitestore), groups/, im/, im/subscription, mdns/, node/, parity/, schema/, secure/…, store/, tlv/ and transport/…. The device layer device/ and the node facade node/ are public API since v0.3.0; that release freezes nothing, and the v1.0.0 freeze is still ahead.

bridge/bridgetest, endpoint/endpointtest, controller/ble/bletest, clock/clocktest and fabrictest are public API on the same terms as the rest, not a lower tier. They exist for the reason net/http/httptest exists — a consumer's tests need to place a bridge in a state the production API is not shaped to reach — and a consumer's test suite is as expensive to break as its production code.

Three things outside internal/ are still not API. conformance/ is this module's own suite, shaped for the tests in this repository rather than for a consumer -- one of its three exported identifiers takes a *testing.T, and the other two exist to serve it. examples/reference-bridge, examples/reference-controller and everything under script/ are package main — runnable, not importable. Copy from them; do not build against them.

One value-level caveat on parity/ and schema/: their Go surface is covered by everything below, but the data behind it is a matter.js HEAD extract. Cluster revisions, attribute IDs and constraint values move when upstream corrects them. That is a behaviour change, not a signature change, and it is announced the same way — see the exception under Pre-1.0.

The deprecation window

An identifier on its way out is marked, kept working, and only then removed.

Marked. Its doc comment gains a paragraph beginning Deprecated: , naming the replacement and the release the removal becomes permissible in. That exact prefix is what gopls, staticcheck (SA1019) and the Go documentation renderer key on, so a consumer sees it in an editor without reading a changelog.
Kept. A deprecated identifier keeps its exact behaviour for the whole window. It is not degraded, does not start logging, and does not become a no-op. A rename lands the new name first and leaves the old one delegating to it.
Removed no earlier than the second minor release after the one that marked it. Deprecated in v0.4.0 means removable in v0.6.0, not before. Consumers who upgrade minor-by-minor therefore see at least one release in which their code still compiles and the warning is already visible.

Currently deprecated, each with its replacement — all marked when the time port clock landed ([Unreleased] in the changelog), removable in v0.10.0 at the earliest:

Deprecated	Replacement
`transport/btp.Clock`, `btp.Timer`, `btp.SystemClock`, `btp.Options.Clock`	`btp.Options.TimeSource` (a `clock.Clock`), `clock.System`
`cluster/onoff.Clock`, `onoff.Config.Clock`	`onoff.Config.TimeSource`
`cluster/core.OtaClock`, `core.OTARequestorConfig.Clock`	`core.OTARequestorConfig.TimeSource`
`cluster/core.OTAProviderConfig.Now`	`core.OTAProviderConfig.Clock`
`cluster/core.CommissionerControlConfig.Now`	`core.CommissionerControlConfig.Clock`
`cluster.Quieter.Now`, `cluster.Quieter.AfterFunc`	`cluster.Quieter.Clock`
`cluster/closure.DimensionConfig.Now`	`closure.DimensionConfig.Clock`
`cluster/energy.CommodityTariffConfig.Now`, `energy.DeviceEnergyConfig.Now`, `energy.EvseConfig.Now`	the `Clock` field beside each
`secure/mattercert.SystemTime`	`clock.System` (the `TimeSource` parameter stays: a `clock.Clock` satisfies it)
`controller/ca.Config.Now`	`ca.Config.Clock`
`controller/ble.ErrScannerClosed` (marked by brief BH)	none: a discovery on a closed scanner returns the stored devices without an error
`cluster/wire.GenericSwitch`, `wire.NewGenericSwitch` (marked by brief BK)	`cluster/switch` (`switchserver.New`), which the MomentarySwitch materialiser builds

A patch release (v0.x.y) never removes or renames a public identifier and never changes a signature. Deprecations may be marked in a patch release; they are only ever acted on in a minor one.

Pre-1.0

The module is at v0; v0.1.0 is its first tag. Before it, main was the only consumable version and could break in any commit, which is why consumers tracked a pseudo-version. main is still consumable the same way — see CONTRIBUTING.md — but a tagged version is what a consumer should pin.

SemVer permits a v0 module to break on any minor bump. This module does not use that permission as a default. The window above applies at v0 exactly as it would at v1: a breaking change is a minor bump, never a patch, and wherever the old identifier can be kept working it is kept working for the full window.

v0.3.0 is the first release to act on the window: it removes the identifiers v0.2.0 marked for removal in it, each listed with its replacement under ### Removed in CHANGELOG.md.

Two changes bypass the window, and both are named as such in their entry:

A matter.js parity correction. matter.js HEAD is the gold standard for every cluster ID, revision, attribute ID and wire shape in this module. When upstream corrects one, this module follows it in the next release without a window. Holding a value stable because it is stable would mean knowingly shipping a wrong one, and the failure it produces is a silent pairing abort in a controller nobody can attach a debugger to.
A security fix that cannot be made without an API change. It ships in the next release, marked ### Security.

What v0 does not excuse: an unannounced break. Every one of these lands in the changelog before a consumer meets it.

How a consumer learns about a break

CHANGELOG.md is the single place. It follows Keep a Changelog, so the headings already carry the meaning:

### Deprecated — the release that marks an identifier. The entry gives the full import path and name, the replacement, and the earliest release the removal may happen in.
### Removed — the release that removes it. The entry repeats the replacement, so a consumer who skipped the deprecation release still finds it here rather than in a diff.
### Changed — behaviour that moved under an unchanged signature. A parity correction lands here and says which matter.js element changed.
### Security — a fix that forced an API change out of band.

A release note carries, for the version it names: every entry from those four headings, and an explicit statement of whether upgrading requires a source change. "No source change required" is a claim worth making when it is true, because it is the only sentence most consumers need to read.

The rule behind all of the above: a break that appears only in a commit message, a doc comment or a diff has not been announced. If it is not in the changelog, it does not ship.

Licence

Apache License 2.0 — see LICENSE and NOTICE (ADR 0023: the same licence as matter.js and connectedhomeip, with their patent grant; v0.4.0 and earlier were released under MIT and stay so). Upstream notices and the dependency licences are recorded in THIRD-PARTY-NOTICES.md. Contributions need the contributor licence agreement in CLA.md, agreed once per account in the first pull request.

Documentation ¶

Overview ¶

Package fabric is Matter in pure Go: the device and bridge side and a full commissioner/controller, as an embeddable library. A semantic port of matter.js; not certified by the Connectivity Standards Alliance. Subpackages:

node/ the facade: one node (root, aggregator, persistence, commissioning, OTA, client stack) from a config — where a host starts
device/ the generated Matter device types a host composes
bridge/ the composition root under node/: topology assembly, IM dispatcher wiring, UDP/TCP listener, mDNS — for hosts that wire it
contract/ the port contracts a host implements to expose a device
cluster/ cluster servers (core/ the system set, spec/ the generated definitions, media/ the media and content clusters, …)
endpoint/ endpoint topology assembler and device-type validation
im/ Interaction Model
controller/ the commissioner/controller role: discovery, PASE/CASE client, attestation (DCL opt-in), CA, client interaction, the client node model and registry
binding/, groups/ bindings and group messaging (send and receive)
bdx/ Bulk Data Exchange (OTA images, diagnostic logs)
commissioning/ on-network discovery, attestation, fabric join
secure/ PASE, CASE, session keys, AES-CCM, attestation, setup codes
transport/ UDP/IPv6, TCP, MRP, message framing
mdns/ DNS-SD advertisement and re-announce
store/ SQLite persistence: fabrics, NOCs, settings, migrations
tlv/ TLV codec (Matter Core Spec §A.7)
schema/, parity/ the embedded matter.js schema and its typed lookups
bootid/, diagevent/, eligibility/ UniqueID salt, pairing trace, host allowlist helpers
conformance/ golden-vector regression, load and chip-tool smoke tests

Architecture: rich model, dumb bridge — this module owns the Matter wire format only. Per-device cluster projection lives on the host's own types, which reach the bridge through the source-surface interfaces in github.com/SukramJ/go-fabric/contract. See docs/architecture.md.

Source Files ¶

View all Source files

doc.go

Directories ¶

?	: This menu
/	: Search site
f or F	: Jump to
y or Y	: Canonical URL

Path	Synopsis
bdx Package bdx is the Bulk Data Exchange protocol (Matter Core §11.22): the message codecs, a Messenger over one exchange, and the transfer roles — the initiating receiver an OTA Software Update Requestor runs to download an image (Receive), the initiating sender a DiagnosticLogs server runs to hand over its logs (Send, StartSend), and the responder an OTA Software Update Provider serves its images with (Responder, Serve).	Package bdx is the Bulk Data Exchange protocol (Matter Core §11.22): the message codecs, a Messenger over one exchange, and the transfer roles — the initiating receiver an OTA Software Update Requestor runs to download an image (Receive), the initiating sender a DiagnosticLogs server runs to hand over its logs (Send, StartSend), and the responder an OTA Software Update Provider serves its images with (Responder, Serve).
otaimage Package otaimage reads and writes Matter OTA software image files (Matter Core §11.21.2): a fixed little-endian prefix — file identifier 0x1BEEF11E (uint32), total size (uint64), header size (uint32) — then the header as an anonymous TLV structure, then the payload.	Package otaimage reads and writes Matter OTA software image files (Matter Core §11.21.2): a fixed little-endian prefix — file identifier 0x1BEEF11E (uint32), total size (uint64), header size (uint32) — then the header as an anonymous TLV structure, then the payload.
binding Package binding resolves the entries of the node's Binding servers into the peers they direct: matter.js's BindingManager (packages/node/src/behaviors/binding/BindingManager.ts at 0ceb202d), the node-scoped service its BindingServer registers every entry with.	Package binding resolves the entries of the node's Binding servers into the peers they direct: matter.js's BindingManager (packages/node/src/behaviors/binding/BindingManager.ts at 0ceb202d), the node-scoped service its BindingServer registers every entry with.
ble
bluez module
bootid Package bootid exposes a process-lifetime 16-byte random value that can optionally be mixed into Matter UniqueID derivations.	Package bootid exposes a process-lifetime 16-byte random value that can optionally be mixed into Matter UniqueID derivations.
bridge Package bridge orchestrates the Matter bridge runtime: endpoint topology assembly, IM dispatcher wiring, UDP listener, and mDNS advertisement.	Package bridge orchestrates the Matter bridge runtime: endpoint topology assembly, IM dispatcher wiring, UDP listener, and mDNS advertisement.
bridgetest Package bridgetest provides the affordances a test outside package bridge needs to put a bridge.Bridge into a chosen state without sending anything over the wire — and, in Commissioner, the controller a test needs to reach that state over the wire instead: a commissioner that commissions a device onto a fabric of its own and then reads, writes, invokes and subscribes over CASE.	Package bridgetest provides the affordances a test outside package bridge needs to put a bridge.Bridge into a chosen state without sending anything over the wire — and, in Commissioner, the controller a test needs to reach that state over the wire instead: a commissioner that commissions a device onto a fabric of its own and then reads, writes, invokes and subscribes over CASE.
clock Package clock is the module's one time port: the current time, one-shot timers and tickers behind an interface, so that a test can drive every interval of the stack — MRP retransmission, the acknowledgement pump, the subscription reporting loop, commissioning windows, cluster timers — by hand instead of waiting for the wall clock.	Package clock is the module's one time port: the current time, one-shot timers and tickers behind an interface, so that a test can drive every interval of the stack — MRP retransmission, the acknowledgement pump, the subscription reporting loop, commissioning windows, cluster timers — by hand instead of waiting for the wall clock.
clocktest Package clocktest is the test clock of the module: Fake, a clock.Clock whose time moves only when the test moves it.	Package clocktest is the test clock of the module: Fake, a clock.Clock whose time moves only when the test moves it.
cluster Package cluster contains Matter cluster server implementations that the bridge attaches to assembled endpoints.	Package cluster contains Matter cluster server implementations that the bridge attaches to assembled endpoints.
alarm Package alarm contains the Matter SmokeCoAlarm cluster server (0x005C), the one mandatory application cluster of the SmokeCoAlarm device type (0x0076).	Package alarm contains the Matter SmokeCoAlarm cluster server (0x005C), the one mandatory application cluster of the SmokeCoAlarm device type (0x0076).
alarmbase Package alarmbase contains one server for the Matter AlarmBase cluster family, instantiated for its three derivations: DishwasherAlarm (0x005D), RefrigeratorAlarm (0x0057) and TemperatureAlarm (0x0064).	Package alarmbase contains one server for the Matter AlarmBase cluster family, instantiated for its three derivations: DishwasherAlarm (0x005D), RefrigeratorAlarm (0x0057) and TemperatureAlarm (0x0064).
appliance Package appliance contains the servers of the appliance control clusters a device of the laundry, kitchen or oven families carries beside its OperationalState and ModeBase servers: MicrowaveOvenControl (0x005F), LaundryWasherControls (0x0053) and LaundryDryerControls (0x004A).	Package appliance contains the servers of the appliance control clusters a device of the laundry, kitchen or oven families carries beside its OperationalState and ModeBase servers: MicrowaveOvenControl (0x005F), LaundryWasherControls (0x0053) and LaundryDryerControls (0x004A).
boolcfg Package boolcfg contains the server for the Matter BooleanStateConfiguration cluster (0x0080), the optional companion of BooleanState on ContactSensor, WaterLeakDetector, RainSensor and WaterFreezeDetector: a sensitivity level, visual / audible alarms that a controller enables, disables and suppresses, and sensor faults.	Package boolcfg contains the server for the Matter BooleanStateConfiguration cluster (0x0080), the optional companion of BooleanState on ContactSensor, WaterLeakDetector, RainSensor and WaterFreezeDetector: a sensitivity level, visual / audible alarms that a controller enables, disables and suppresses, and sensor faults.
closure Package closure contains the Matter ClosureControl cluster server (0x0104) for the Positioning + Ventilation feature profile.	Package closure contains the Matter ClosureControl cluster server (0x0104) for the Positioning + Ventilation feature profile.
core Package core hosts the Matter cluster servers that every bridge endpoint (or the root endpoint specifically) mandates per Matter Core Specification 1.6.1.	Package core hosts the Matter cluster servers that every bridge endpoint (or the root endpoint specifically) mandates per Matter Core Specification 1.6.1.
cover Package cover contains the Matter WindowCovering cluster server (0x0102) for the position-aware lift and tilt feature profiles.	Package cover contains the Matter WindowCovering cluster server (0x0102) for the position-aware lift and tilt feature profiles.
energy Package energy holds the servers of the Matter energy-management clusters a bridged appliance offers: WaterHeaterManagement (0x0094) for the WaterHeater device type, and EnergyPreference (0x009B), optional on the Thermostat device type.	Package energy holds the servers of the Matter energy-management clusters a bridged appliance offers: WaterHeaterManagement (0x0094) for the WaterHeater device type, and EnergyPreference (0x009B), optional on the Thermostat device type.
fan Package fan contains the Matter FanControl cluster server (0x0202), the mandatory application cluster of the Fan (0x002B), AirPurifier (0x002D) and ExtractorHood (0x007A) device types.	Package fan contains the Matter FanControl cluster server (0x0202), the mandatory application cluster of the Fan (0x002B), AirPurifier (0x002D) and ExtractorHood (0x007A) device types.
filter Package filter contains one server for the Matter ResourceMonitoring cluster family, instantiated for the two derivations the AirPurifier and ExtractorHood device types offer: HepaFilterMonitoring (0x0071) and ActivatedCarbonFilterMonitoring (0x0072).	Package filter contains one server for the Matter ResourceMonitoring cluster family, instantiated for the two derivations the AirPurifier and ExtractorHood device types offer: HepaFilterMonitoring (0x0071) and ActivatedCarbonFilterMonitoring (0x0072).
levelcontrol Package levelcontrol contains the Matter LevelControl cluster server (0x0008) — the cluster Matter offers for a characteristic that moves along a continuous scale, as against the labelled choices of ModeSelect.	Package levelcontrol contains the Matter LevelControl cluster server (0x0008) — the cluster Matter offers for a characteristic that moves along a continuous scale, as against the labelled choices of ModeSelect.
light Package light provides standalone Matter cluster-server implementations for light device types (OnOffLight, DimmableLight, ColorTemperatureLight, ExtendedColorLight).	Package light provides standalone Matter cluster-server implementations for light device types (OnOffLight, DimmableLight, ColorTemperatureLight, ExtendedColorLight).
lock Package lock contains the DoorLock cluster server (0x0101): a semantic port of matter.js DoorLockBaseServer (packages/node/src/behaviors/ door-lock/DoorLockServer.ts, LockAuth.ts and LockSchedule.ts at 862ad75f).	Package lock contains the DoorLock cluster server (0x0101): a semantic port of matter.js DoorLockBaseServer (packages/node/src/behaviors/ door-lock/DoorLockServer.ts, LockAuth.ts and LockSchedule.ts at 862ad75f).
measurement Package measurement contains generic, Source-driven cluster server implementations for the read-only Matter measurement clusters (Temperature, Humidity, Illuminance, Pressure, Flow, BooleanState, OccupancySensing, AirQuality).	Package measurement contains generic, Source-driven cluster server implementations for the read-only Matter measurement clusters (Temperature, Humidity, Illuminance, Pressure, Flow, BooleanState, OccupancySensing, AirQuality).
media Package media holds the servers of the media and content clusters (ADR 0022): MediaPlayback, KeypadInput, ContentLauncher, ApplicationLauncher, ApplicationBasic, AccountLogin, AudioOutput, Channel, TargetNavigator, MediaInput, LowPower, WakeOnLan, ContentControl and ContentAppObserver.	Package media holds the servers of the media and content clusters (ADR 0022): MediaPlayback, KeypadInput, ContentLauncher, ApplicationLauncher, ApplicationBasic, AccountLogin, AudioOutput, Channel, TargetNavigator, MediaInput, LowPower, WakeOnLan, ContentControl and ContentAppObserver.
modebase Package modebase contains one server for the Matter ModeBase cluster family, instantiated for the derivations the appliance device types use: LaundryWasherMode (0x0051, LaundryWasher and LaundryDryer), RvcRunMode (0x0054, mandatory on RoboticVacuumCleaner), RvcCleanMode (0x0055), DishwasherMode (0x0059), OvenMode, MicrowaveOvenMode, RefrigeratorAndTemperatureControlledCabinetMode, EnergyEvseMode, WaterHeaterMode and DeviceEnergyManagementMode (ids from their generated definitions).	Package modebase contains one server for the Matter ModeBase cluster family, instantiated for the derivations the appliance device types use: LaundryWasherMode (0x0051, LaundryWasher and LaundryDryer), RvcRunMode (0x0054, mandatory on RoboticVacuumCleaner), RvcCleanMode (0x0055), DishwasherMode (0x0059), OvenMode, MicrowaveOvenMode, RefrigeratorAndTemperatureControlledCabinetMode, EnergyEvseMode, WaterHeaterMode and DeviceEnergyManagementMode (ids from their generated definitions).
modeselect Package modeselect contains the Matter ModeSelect cluster server (0x0050) — the cluster Matter offers for a characteristic that is set to one of several predefined, labelled values rather than to a number on a continuous scale.	Package modeselect contains the Matter ModeSelect cluster server (0x0050) — the cluster Matter offers for a characteristic that is set to one of several predefined, labelled values rather than to a number on a continuous scale.
onoff Package onoff carries the OnOff cluster's Matter identity for every projection that exposes it.	Package onoff carries the OnOff cluster's Matter identity for every projection that exposes it.
opstate Package opstate contains the Matter OperationalState cluster server (0x0060) and its derivations RvcOperationalState (0x0061) and OvenCavityOperationalState (0x0048): the state machine of a laundry washer, laundry dryer, dishwasher or microwave oven, of a robotic vacuum cleaner, and of an oven's heating cabinet.	Package opstate contains the Matter OperationalState cluster server (0x0060) and its derivations RvcOperationalState (0x0061) and OvenCavityOperationalState (0x0048): the state machine of a laundry washer, laundry dryer, dishwasher or microwave oven, of a robotic vacuum cleaner, and of an oven's heating cabinet.
pump Package pump contains the Matter PumpConfigurationAndControl cluster server (0x0200), the cluster the Pump device type (0x0303) mandates next to OnOff.	Package pump contains the Matter PumpConfigurationAndControl cluster server (0x0200), the cluster the Pump device type (0x0303) mandates next to OnOff.
servicearea Package servicearea contains the Matter ServiceArea cluster server (0x0150): the areas a robotic vacuum cleaner (or any device that serves areas) knows, the maps they lie on, which of them a controller selected, where the device is now and how far it got.	Package servicearea contains the Matter ServiceArea cluster server (0x0150): the areas a robotic vacuum cleaner (or any device that serves areas) knows, the maps they lie on, which of them a controller selected, where the device is now and how far it got.
spec Package spec is the runtime half of the generated cluster definitions: the types a generated definition is made of, and what a cluster server derives from one definition plus the host's declared features and optional elements.	Package spec is the runtime half of the generated cluster definitions: the types a generated definition is made of, and what a cluster server derives from one definition plus the host's declared features and optional elements.
spec/accountlogin Package accountlogin is the generated definition of the Matter AccountLogin cluster (0x050E, revision 2), from the matter.js model at 862ad75 (Matter 1.6.1).	Package accountlogin is the generated definition of the Matter AccountLogin cluster (0x050E, revision 2), from the matter.js model at 862ad75 (Matter 1.6.1).
spec/actions Package actions is the generated definition of the Matter Actions cluster (0x0025, revision 1), from the matter.js model at 862ad75 (Matter 1.6.1).	Package actions is the generated definition of the Matter Actions cluster (0x0025, revision 1), from the matter.js model at 862ad75 (Matter 1.6.1).
spec/activatedcarbonfiltermonitoring Package activatedcarbonfiltermonitoring is the generated definition of the Matter ActivatedCarbonFilterMonitoring cluster (0x0072, revision 1, derived from ResourceMonitoring), from the matter.js model at 862ad75 (Matter 1.6.1).	Package activatedcarbonfiltermonitoring is the generated definition of the Matter ActivatedCarbonFilterMonitoring cluster (0x0072, revision 1, derived from ResourceMonitoring), from the matter.js model at 862ad75 (Matter 1.6.1).
spec/administratorcommissioning Package administratorcommissioning is the generated definition of the Matter AdministratorCommissioning cluster (0x003C, revision 1), from the matter.js model at 862ad75 (Matter 1.6.1).	Package administratorcommissioning is the generated definition of the Matter AdministratorCommissioning cluster (0x003C, revision 1), from the matter.js model at 862ad75 (Matter 1.6.1).
spec/airquality Package airquality is the generated definition of the Matter AirQuality cluster (0x005B, revision 1), from the matter.js model at 862ad75 (Matter 1.6.1).	Package airquality is the generated definition of the Matter AirQuality cluster (0x005B, revision 1), from the matter.js model at 862ad75 (Matter 1.6.1).
spec/ambientcontextsensing Package ambientcontextsensing is the generated definition of the Matter AmbientContextSensing cluster (0x0431, revision 1), from the matter.js model at 862ad75 (Matter 1.6.1).	Package ambientcontextsensing is the generated definition of the Matter AmbientContextSensing cluster (0x0431, revision 1), from the matter.js model at 862ad75 (Matter 1.6.1).
spec/applicationbasic Package applicationbasic is the generated definition of the Matter ApplicationBasic cluster (0x050D, revision 1), from the matter.js model at 862ad75 (Matter 1.6.1).	Package applicationbasic is the generated definition of the Matter ApplicationBasic cluster (0x050D, revision 1), from the matter.js model at 862ad75 (Matter 1.6.1).