Explain the Thread and Matter protocol stack for smart home

Thread is a low-power, IPv6-based mesh networking protocol designed for smart home and building automation. It operates on IEEE 802.15.4 radio (2.4 GHz, 250 kbps), the same physical layer as Zigbee, but uses a completely different network stack. Thread's key innovation is bringing standard IP networking to constrained devices: it uses 6LoWPAN for IPv6 header compression, MLE (Mesh Link Establishment) for neighbor discovery and routing topology, RPL or a simplified routing protocol for mesh routing, and DTLS/UDP for secure communication. Thread devices are assigned IPv6 addresses and can communicate with any IP device through a Border Router that bridges the Thread mesh to WiFi or Ethernet networks. The mesh is self-healing — devices automatically reroute around failed nodes, and the network supports up to 250+ devices per partition.

Matter (formerly Project CHIP) is an application layer protocol that runs on top of multiple transports — WiFi, Thread, and Ethernet. Matter defines a standardized data model for smart home devices: a Node contains Endpoints, each Endpoint implements Clusters (like On/Off, Level Control, Temperature Measurement), and each Cluster has Attributes, Commands, and Events. This is conceptually similar to BLE's GATT model but applied to home automation. Matter uses a standard commissioning flow (involving QR codes or NFC), certificate-based device authentication (Device Attestation Certificates issued by the Connectivity Standards Alliance), and supports multiple simultaneous controllers (so a device can be controlled by Apple Home, Google Home, and Amazon Alexa simultaneously via Multi-Admin).

The relationship between Thread and Matter is complementary, not competing: Thread provides the mesh network transport for battery-powered devices (door sensors, motion detectors, smart locks), while Matter provides the application protocol that ensures interoperability between manufacturers and ecosystems. A Matter-over-Thread device uses Thread for mesh networking and IP connectivity, and Matter for standardized device behavior. A Matter-over-WiFi device uses WiFi as the transport instead. The interview insight is that Thread solved the networking problem (reliable, low-power mesh with IP connectivity) while Matter solved the interoperability problem (one protocol understood by Apple, Google, Amazon, and Samsung). Together they replace the fragmented landscape of proprietary Zigbee profiles and Z-Wave command classes with a single, open standard.