Network planning before pairing
Keep the Matter controller, commissioning device and supporting network infrastructure reachable according to the platform's instructions. Matter uses IPv6 and discovery mechanisms on the local network; an ISP-supplied public IPv6 connection is not a prerequisite for local operation. Guest-network isolation, blocked multicast or an incorrectly configured VLAN boundary can prevent discovery/control even when internet access works.
For a first installation, use a documented supported network arrangement before experimenting with segmentation. Do not disable security or expose devices/controllers directly to the internet to solve pairing trouble.
Thread is not Zigbee
Both can use IEEE 802.15.4 radios, but their network stacks and commissioning differ. A Zigbee lamp does not join a Thread mesh simply because the radios operate in the same band. A supported Matter bridge can translate selected devices from another system; it does not turn their radio protocol into Thread.
Thread border routers provide IP connectivity. They do not themselves translate all lighting application commands. A Thread-capable product is not necessarily a Matter product, so check certification and supported application software. Plan the mesh and powered devices using actual manufacturer placement guidance, not a promised universal range.
Inside the Matter application layer
Endpoints organise a device's functions. Clusters describe capabilities such as on/off or level control, using attributes, commands and events. Device types specify required combinations. A Matter fabric is a security/administrative domain, not another Wi-Fi SSID. Multi-admin can share supported devices with additional ecosystems; use the platform's sharing process rather than repeatedly factory-resetting them.
Where to read the specifications
The Alliance's official download portal provides Matter Core, Application Clusters and Device Type Library documents under its stated terms. Core covers architecture/security; the cluster and device-type documents explain lighting behaviour. Publicly available specifications remain copyrighted and are not the same thing as unrestricted certification/trademark rights.
The transport guide is an accessible companion, not a replacement for the normative specification. Match the specification revision and feature support to your actual device/controller firmware rather than assuming the newest document describes every installed bulb.
Official reading
Official Matter transport documentation
Alliance specification downloads: Core, clusters and device types
Alliance FAQ: bridging, local control and multi-admin