IoT Protocol Vocabulary: MQTT, CoAP, Zigbee, and Matter Explained
Essential IoT communication protocol vocabulary for embedded and IoT engineers: MQTT, CoAP, Zigbee, Thread, Matter, BLE, LoRaWAN, and more — explained with plain English definitions.
IoT systems communicate over a diverse set of protocols — each designed for specific constraints of power, bandwidth, range, and latency. Understanding this vocabulary is essential for designing IoT architectures, evaluating trade-offs, and communicating clearly in technical discussions. This guide covers the major IoT protocols and the vocabulary you need to work with them professionally.
Core IoT Communication Concepts
IoT (Internet of Things)
IoT refers to the network of physical devices — sensors, actuators, appliances, vehicles — embedded with processors, memory, and connectivity that enables them to collect and exchange data.
Constrained Device
A constrained device has limited resources — low power CPU, kilobytes of RAM, small flash storage. IoT protocols are designed around these constraints.
Low-Power / Energy-Harvested Device
Many IoT devices are battery-powered or energy-harvested (solar, kinetic), requiring protocols with minimal power draw and support for deep sleep modes.
Edge Computing
Edge computing processes data near the device (on edge nodes, gateways) rather than sending everything to the cloud — reducing latency, bandwidth, and privacy exposure.
MQTT
MQTT (Message Queuing Telemetry Transport)
MQTT is a lightweight publish-subscribe messaging protocol designed for constrained devices and unreliable networks. Runs over TCP. Port 1883 (unencrypted), 8883 (TLS).
Used for: IoT device telemetry, sensor data collection, home automation, industrial IoT.
MQTT Broker
An MQTT broker is the server that receives messages from publishers and routes them to subscribers. Examples: Mosquitto, EMQX, AWS IoT Core, HiveMQ.
“All our sensor nodes publish to the MQTT broker every 30 seconds. The cloud analytics service subscribes to the relevant topics.”
Publish / Subscribe
MQTT uses a pub/sub model — publishers send messages to topics without knowing who is listening. Subscribers register interest in topics and receive matching messages.
Topic
An MQTT topic is a string that organises messages — e.g., factory/line1/temperature. Topics use / separators and support wildcards: + (single level) and # (multi-level).
“Devices publish to
sensors/{device_id}/temperature. The analytics service subscribes tosensors/#to receive all sensor readings.”
QoS (Quality of Service)
MQTT has three QoS levels:
- QoS 0 — At most once (fire and forget — no acknowledgement)
- QoS 1 — At least once (acknowledged, may duplicate)
- QoS 2 — Exactly once (four-step acknowledgement, no duplicates)
“We use QoS 1 for alarms — we accept duplicates, but we can’t miss a critical alert.”
Retain Flag
With the retain flag, the broker stores the last message on a topic and delivers it immediately to new subscribers — useful for “last known state.”
Last Will and Testament (LWT)
LWT is a message the broker publishes automatically if the client disconnects unexpectedly — used to notify subscribers that a device went offline.
CoAP
CoAP (Constrained Application Protocol)
CoAP is a lightweight HTTP-like protocol for constrained IoT devices. Runs over UDP (lightweight). Supports REST-style GET, POST, PUT, DELETE operations.
Used when devices are too resource-constrained for HTTP but need a request-response model rather than pub/sub.
“The embedded sensor only has 4KB of RAM — we use CoAP instead of HTTP. The binary encoding is far more compact.”
Confirmable vs Non-Confirmable Messages
Confirmable CoAP messages are acknowledged (reliable delivery). Non-confirmable messages are fire-and-forget.
Observe
CoAP’s Observe extension allows a client to subscribe to updates on a resource — similar to MQTT subscribe but in a REST model.
Zigbee
Zigbee
Zigbee is a low-power, low-data-rate IEEE 802.15.4 wireless protocol for short-range mesh networks. Designed for home automation, industrial sensors, and building control.
Key characteristics: 2.4 GHz, very low power, mesh topology, up to 250 kbps, range 10–100m.
“Our smart lighting system uses Zigbee — each bulb is both a device and a router in the mesh.”
Mesh Network
In a mesh network, devices relay messages for each other — extending range beyond what a single device’s radio could reach. Zigbee, Thread, and Z-Wave are mesh protocols.
Coordinator / Router / End Device
Zigbee network roles:
- Coordinator — the root of the mesh, manages network formation (one per network)
- Router — forwards messages for others (mains-powered devices)
- End Device — communicates only with its parent router, sleeps to save power (battery devices)
Thread and Matter
Thread
Thread is a low-power IPv6 mesh networking protocol designed for IoT. Built on IEEE 802.15.4. Unlike Zigbee, Thread is IP-native — every device has an IPv6 address.
Key characteristics: IP-based, self-healing mesh, no single point of failure, designed for interoperability.
Border Router
A border router connects the Thread mesh to the rest of the IP network (Wi-Fi, Ethernet). Thread devices communicate with cloud services through the border router.
Matter (formerly Project CHIP)
Matter is an open-source, IP-based smart home interoperability standard supported by Apple, Google, Amazon, and Samsung. It runs over Thread, Wi-Fi, and Ethernet.
Key advantage: A single Matter device works with Apple Home, Google Home, Amazon Alexa, and SmartThings — no vendor lock-in.
“We’re building new smart home devices to the Matter standard — customers shouldn’t have to choose a single platform ecosystem.”
BLE (Bluetooth Low Energy)
Bluetooth Low Energy (BLE)
BLE is the low-power version of Bluetooth. Designed for devices that transmit small amounts of data infrequently — wearables, beacons, medical sensors.
Key characteristics: 2.4 GHz, very low power, range 10–100m, 1–3 Mbps.
GATT (Generic Attribute Profile)
GATT is the BLE application protocol — organises data into Services and Characteristics that devices can read, write, and get notifications from.
BLE Advertising
Advertising is how BLE devices broadcast their presence. A peripheral (sensor) advertises; a central (phone, gateway) scans and connects.
BLE Mesh
Bluetooth Mesh extends BLE to support many-to-many publish-subscribe messaging across a mesh — used in commercial lighting and building automation.
LoRaWAN
LoRa (Long Range)
LoRa is a spread-spectrum radio modulation technique enabling very long range (2–15km urban, 30–50km rural) with extremely low power consumption.
LoRaWAN
LoRaWAN is a MAC layer protocol and network architecture standard built on LoRa. Designed for very low data rate, long-range, massive-scale IoT deployments.
Used for: agricultural sensors, smart meters, asset tracking, environmental monitoring.
Key characteristics: 0.3–50 kbps, battery life 5–10 years, range up to 50km.
Gateway (LoRaWAN)
A LoRaWAN gateway receives radio signals from end devices and forwards them to the network server over backhaul (cellular, Ethernet).
Network Server
The network server manages the LoRaWAN network — deduplicates packets (many gateways may receive the same transmission), manages device sessions, and routes data to the application server.
Protocol Comparison
| Protocol | Range | Data Rate | Power | Topology | Use Case |
|---|---|---|---|---|---|
| MQTT | Network (TCP) | High | Medium | Star (via broker) | General IoT telemetry |
| CoAP | Network (UDP) | Medium | Low | P2P / Star | Constrained devices (REST) |
| Zigbee | 10–100m | 250 kbps | Very low | Mesh | Home/building automation |
| Thread | 10–100m | 250 kbps | Very low | Mesh (IPv6) | Smart home (IP-native) |
| Matter | Varies | Varies | Varies | Varies | Interop smart home |
| BLE | 10–100m | 1–3 Mbps | Very low | Star/Mesh | Wearables, beacons |
| LoRaWAN | 2–50km | 0.3–50 kbps | Extremely low | Star of stars | Long-range sensor networks |
Practice
Build your embedded and IoT vocabulary with the Embedded Systems & IoT exercise set and the Embedded & IoT Engineer learning path.