IoT Wireless Protocols

A door sensor reporting a few times a day, a field sensor uploading a packet every ten minutes, and a smart lock requiring immediate response upon user proximity can all be called "low-power IoT," yet they require different network and reception strategies. Selection should start by asking about payload, cycle, downlink latency, power supply, and infrastructure, before looking at protocol names; it is inappropriate to fill in distance, power consumption, and data rate as fixed rankings without conditions.

Mesh expands reachable paths, it does not keep all battery nodes awake for reception

Zigbee often distinguishes between Coordinator, Router, and End Device. The Coordinator establishes the network and assumes corresponding management responsibilities; Routers forward traffic; End Devices attach to a parent node; sleeping end devices cannot act as relays for others. Routing nodes need to remain reachable, so they are typically powered continuously, but one cannot infer solely from "plugged-in device" that it always works in the Router role. Silicon Labs: Zigbee Node Types

The parent node buffers downlinks for sleeping child devices, which retrieve them upon waking. This power saving comes from reduced listening, but it also means downlinks cannot arrive at any time. Multi-hop can bypass some failed paths, but it only makes sense if other available routes, resources, and coverage exist; when a mesh bulb powered by a wall switch loses power, a battery-operated door sensor will not automatically take over the mesh backbone.

The Coordinator is not equivalent to an application gateway: the same hardware box may simultaneously provide coordination, protocol translation, and automation services, but these three roles should be analyzed separately. Zigbee product interoperability also involves device types, Clusters, extensions, and controller support; it cannot be simply summarized as "same protocol means fully universal" or "all vendors are locked in."

Z-Wave cannot be listed as just one Mesh: traditional Z-Wave and Z-Wave Long Range have different topologies; LR uses a star connection from device to central controller. Compatible controllers can manage the respective networks, but device modes and regional capabilities need to be verified. Z-Wave Alliance: Long Range

Thread and Matter: After network interoperability, applications still need to recognize each other

Common Thread deployments are based on 2.4 GHz IEEE 802.15.4, using mechanisms like 6LoWPAN to carry IPv6. One cannot uniformly label all Thread products with Sub-GHz just because the 802.15.4 family includes other frequency bands. Thread routing roles, sleeping terminals, and Border Routers have distinct divisions of labor; one cannot infer from "native IPv6" that every node in the network directly connects to Wi-Fi.

The Border Router routes between Thread and other IP networks and assumes related discovery/network services; it usually does not need to translate every application command into a private protocol; but it is not an arbitrary transparent Layer 2 bridge. An isolated Thread network can communicate internally, but accessing external IP networks requires the corresponding boundary path. Thread Group: Border Router

Thread has mechanisms like re-electable Leaders, but it is not without roles, nor is any deployment free from single points of failure. If there is only one Border Router, its failure cuts off the corresponding external path; if automation runs on only one controller, normal network routing cannot replace that controller in executing logic. Multiple border routers also need to be configured as an appropriate common network; buying multiple boxes does not naturally form the same Mesh. Thread Group: Typical Network Topologies

Matter defines application-layer device models, interactions, and security, often running on top of Thread, Wi-Fi, or Ethernet; BLE is commonly used for discovery/provisioning, not as the general carrier for daily Matter control data. Matter Controller, provisioning Commissioner, Thread Border Router, and Matter Bridge (for bridging legacy devices) are different roles; a single box can assume multiple roles. CSA: Matter

How a door sensor event reaches automation

The door sensor wakes up, detects the door is open, and sends attributes/events via Matter interactions, reaching the controller through the Thread parent node and routing; if the controller is on a Wi-Fi/Ethernet network, it passes through the Border Router. The controller receives updates based on established subscriptions and authorizations, then decides whether to turn on the light. Physical wireless acknowledgment, IP arrival, successful Matter interaction, and the light actually turning on are different completion points.

Matter's multi-admin mechanism allows authorization and management across multiple Fabrics, but this does not mean all ecosystems automatically gain permissions after purchase. Device types, optional features, and platform support still affect available control. Network encryption protects transmission, while application permissions determine who can unlock/change configurations; cross-brand interoperability should not be understood as omitting authorization.

LoRa and LoRaWAN: Distinguish between wireless packets and network services first

LoRa is a spread-spectrum modulation technology system promoted by Semtech; LoRaWAN defines device access, messages, security, and network behavior. Using LoRa modulation to send private point-to-point packets does not automatically make them devices manageable by a LoRaWAN network. Frequency bands, channels, and transmission limits are determined by regional parameters and device implementations; one cannot treat 433/868/915 MHz as a menu freely interchangeable anywhere.

Common LoRaWAN is a star-of-stars: the same uplink can be received by multiple Gateways, sent back via IP to the Network Server, where the network side coordinates deduplication and corresponding network management. Gateways still perform RF reception, packet forwarding, and downlink scheduling; they are not "stateless wires that do no protocol." Application data is processed by application-side services; network and application keys have different responsibilities; one cannot uniformly write that all application payloads are decrypted by the Network Server. LoRa Alliance: LoRaWAN Architecture

OTAA establishes session relationships through the join process; session keys, counters, and state retention after reboot need to be handled correctly. Wireless ACK or the network server receiving an uplink does not mean the business database has already stored it; applications can still use message numbers for confirmation, deduplication, and fault recovery.

When SF increases, the same packet occupies the air interface longer

In the traditional LoRa model, symbol time is Tsym=2^SF/BW. At 125 kHz bandwidth, SF7 is 1.024 ms per symbol, and SF12 is 32.768 ms. Higher SF changes demodulation capability and airtime; one cannot generally say it is necessarily farther or more reliable; longer occupation also increases collision opportunities and transmission energy consumption. Semtech: LoRa FAQ

Take explicit modulation teaching conditions: physical payload 20 bytes, explicit header, CRC enabled, coding rate 4/5, preamble 8 symbols, SF12 with low data rate optimization enabled. According to the traditional LoRa packet length formula, SF7 airtime is approximately 56.576 ms, and SF12 is approximately 1318.912 ms. Here, 20 bytes is the modulator payload, not "20 bytes of LoRaWAN application data"; the latter requires adding protocol fields. Semtech: SX1276 Datasheet, LoRa time-on-air

Assume 100 nodes all use the latter, sending one packet every 600 s, concentrated on the same channel/SF; looking only at the sum of transmission durations, it occupies about 21.98% of the time; random overlaps, retransmissions, and downlinks will further change capacity. This is a load estimate, not a duty cycle allowed in a specific region, nor a promise of success rate. Actual deployments need to be re-budgeted according to regional parameters, regulations, and network policies.

Downlink latency is determined by receive windows

Class C is not a physical rule that "must be plugged in," but rather that continuous reception is usually more suitable for scenarios with ample power. If all nodes frequently require acknowledgments, it also increases downlink pressure; LoRaWAN is suitable for small amounts of periodic data, and kilometer coverage does not imply suitability for frequent low-latency control or large file upgrades.

Why can one byte add a whole symbol group?

Hold SF fixed and increment payload to see plateaus and jumps. Switching SF7 to SF12 changes the same 20 B packet from 56.576 ms to 1318.912 ms. A fixed vertical scale compares actual duration, not range or success probability.

Cellular IoT: Not building your own gateways still requires managing networks and wake-ups

NB-IoT/LTE-M leverages cellular infrastructure, saving some of the work of building LPWAN gateways on-site, but still requires compatible modules, SIM/eSIM, network coverage, and service management. Different deployments vary in mobility, data rate, roaming, and coverage enhancement capabilities; do not represent all versions and on-site performances with "NB-IoT fixed at 250 kbit/s."

PSM allows devices to enter a deeper power-saving state, during which they are typically not pageable by the network at any time; eDRX extends the paging listening cycle, trading off longer downlink waiting times. Attachment, weak coverage retries, and coverage enhancement retransmissions may consume much more energy than the application packet itself. Whether the network caches downlinks and for how long also depends on the deployment; one cannot equate "cloud command sent" with "device about to receive." GSMA: Mobile IoT Deployment Guide

NFC/RFID: Short distance does not equal trusted identity

NFC is based on 13.56 MHz near-field interaction, with common uses including reading/writing tags and card emulation. Passive tags harvest energy from the reader's field, meaning the tag itself requires no battery, but this does not mean the entire system is zero-power; read range is affected by coils, matching, metal environments, and device capabilities; one cannot uniformly guarantee a one-meter read for a certain tag type. NFC Forum: Technology Overview

NFC Forum Tag Type describes protocols and data mappings, etc., and is not a synonym for product brand, fixed capacity, or security level. Type 4 does not automatically mean all tags have the same security mechanisms; Type 5 being related to ISO 15693 does not mean phones can be used as industrial long-range readers. One should check the actual chip's authentication, storage access, and key capabilities. NFC Forum: Specifications

RFID covers a wider range; LF/HF often utilizes near-field coupling, while UHF tags often use backscatter. Reading a UID only indicates receiving an identifier; if used for access control, one should judge based on the specific protocol's authentication and anti-replay design, rather than treating the UID itself as an uncopyable secret.

UWB: ToF is distance, positioning requires geometry and calibration

UWB's wideband time-domain characteristics help in accurately estimating arrival times. If the response processing time has been correctly subtracted, and the round-trip propagation remaining is 20 ns, then d=c×20ns/2≈3.0 m; a round-trip measurement error of only 1 ns corresponds to a distance error of about 15 cm. Processing delays, clock differences between ends, and antenna delays cannot be ignored. FiRa: UWB Technology FAQ

A single distance only constrains a circle/sphere; complete positioning requires combining multiple anchors, angles, or motion information. Non-line-of-sight, human occlusion, multipath, and anchor geometry can introduce deviations; "centimeter-level" should come with test conditions. Secure ranging also requires corresponding protocols and identity binding; not any UWB pulse naturally possesses complete door lock security.

UWB can work with BLE: BLE is used for low-power discovery and control, waking up UWB when fine ranging is needed. Overall power consumption depends on ranging frequency and transmission/reception schedules; one cannot directly swap the technology name for "medium power consumption."

Write requirements as calculable selection conditions

These are evaluation directions, not fixed recommendations detached from regional, device, and business conditions.

Recalculate LoRa Airtime and ToF

from math import ceil, isclose

def airtime(sf, payload_bytes=20, bw=125000):
    # Fixed for this example: explicit header IH=0, CRC=1, CR=1(4/5), preamble=8.
    de = int(sf >= 11)  # Only for this example's BW=125 kHz selection
    tsym = 2**sf/bw
    numerator = 8*payload_bytes-4*sf+28+16
    payload_symbols = 8+max(ceil(numerator/(4*(sf-2*de)))*5, 0)
    return (8+4.25+payload_symbols)*tsym

assert isclose(airtime(7), 0.056576)
assert isclose(airtime(12), 1.318912)
assert isclose(100*airtime(12)/600, 0.2198186666666667)
c = 299792458
assert isclose(c*20e-9/2, 2.99792458)
assert isclose(c*1e-9/2, 0.149896229)
print('LoRa packet duration, aggregated load, and round-trip ToF conversion checks passed')

This is a model budget; no wireless packets were transmitted, nor was on-site coverage or positioning accuracy measured.

Continue Reading

• Wi-Fi and Bluetooth: Air interface resources, BLE services, and coexistence.
• Battery Technology: Energy and long-term power budgeting.
• Sensors: Sampling and measurement errors.