802.15.4

In the same meeting room, Wi-Fi signal may look full, but pages load slowly, video calls freeze, and ping latency jumps around. The first reaction is often “the signal is bad.”

But strong signal does not mean the air is free. Wireless devices do not have dedicated cables. Many clients, APs, Zigbee, Thread, or other 2.4 GHz devices may be competing for the same airtime.

At that point, experience is affected not only by RSSI and SNR, but also by a lower-level contention rule: who may transmit, when they may transmit, and what happens after a failed attempt.

Many Thread field issues sound simple at first: the device cannot join the network, or it has joined but the app still cannot find it. Once you break it apart, the bottleneck is often somewhere else. Some devices never even found the target PAN (Personal Area Network). Some completed commissioning but never truly attached to the Thread network. Some already have an on-network address but still have no usable prefix. Others can communicate inside the mesh, but still cannot reach a home LAN (Local Area Network) or a cloud service.

Many Zigbee field problems sound like very simple statements at first: the device cannot join the network, or it has already joined but still cannot be controlled. Once you break it apart, the bottleneck is often in a completely different stage. Some devices never found the target channel. Some saw the Beacon but were not allowed to join. Some already received a NWK (Network) short address, but ZCL (Zigbee Cluster Library) commands still would not go through. Others have no network-layer problem at all, and are instead blocked by endpoints, Clusters, or binding relations.