Zigbee, Thread & Matter · Study deck
Zigbee Network Analyzer
Imagine a room sensor that stops reporting each afternoon.
Radio Remi is your guide for this deck.

After studying this chapter
Learning objectives
You will be able to:
- Explain: Device-health evidence records stale reporting, repeated retries, power-state warnings, missed check-ins, or changing link-quality observations without turning one metric into a universal diagnosis.
- Explain: A Zigbee network analyzer is useful when it turns device observations, route symptoms, bridge logs, and packet evidence into a bounded diagnostic record.
- Explain: A Zigbee analyzer sniffs raw IEEE 802.15.4 frames on one channel; Zigbee 2.4 GHz networks use channels 11 through 26.
- Explain: Route-record commands in many-to-one routing can reveal the source route the coordinator will use back to a device.
Major section
In 60 Seconds
Zigbee is a low-power wireless system used by many local device networks.
- A gateway is a bridge between that local network and another system.
- A network analyzer gathers observations that can help explain the missing report.
- A matching chart is a clue, not proof that one event caused the other.
Major section
In 60 Seconds (continued)
A gateway is the bridge from the local device network to another system.
- This quick check cannot see every radio signal, device fault, or outside service.
- Under the Hood examines capture limits, routing, and evidence conflicts.
- A Zigbee network analyzer is useful when it turns device observations, route symptoms, bridge logs, and packet evidence into a bounded diagnostic record.
Major section
Evidence Families
Topology evidence records parent, relay, coordinator, gateway, and single-dependency observations.
- Traffic evidence records source, destination, command class, direction, repetition, missing response, and visible delivery.
- Route-change evidence records what path changed, what symptom appeared, what recovered, and what remained unknown.
- Correlation evidence compares analyzer output with gateway logs, site observations, support reports, commissioning records, and recent changes.
Major section
Evidence Families (continued)
Device-health evidence records stale reporting, repeated retries, power-state warnings, missed check-ins, or changing link-quality observations without turning one metric into a universal diagnosis.
- A Zigbee analyzer sniffs raw IEEE 802.15.4 frames on one channel; Zigbee 2.4 GHz networks use channels 11 through 26.
- Reading a capture is therefore a layer-localization exercise.
- The review should name the layer before naming the fix.
Major section
Set the Capture Boundary
An analyzer record needs a boundary before the result can be trusted.
- A broad absence of evidence usually means the review did not define what it was trying to find.
- Two capture limits should be recorded before payload conclusions are trusted.
- A sniffer may see addresses, PAN ID, frame types, and route activity while the application payload remains ciphertext.
Major section
Review Traffic and Symptoms
Traffic review asks whether the analyzer sees the same problem that users, gateways, or support records describe.
- A falling link-quality observation, a stale report, or a repeated message is a clue.
- It becomes stronger evidence only when the review connects it to the path, event, user impact, and field context.
- A single dropped packet is noise.
Major section
Review Traffic and Symptoms (continued)
The diagnostic value of a capture is in trends across the timeline, not a single frame.
- Falling LQI on a link can foreshadow a route change.
- Repeated NWK route-request broadcasts can show route-discovery churn, meaning the route is unstable or missing rather than steady.
- Route-record commands in many-to-one routing can reveal the source route the coordinator will use back to a device.
Major section
Worked Review: Router Replacement
Scenario:: A relay device was replaced.
- The analyzer shows changed paths for a small endpoint group, but only some support records show visible impact.
- Separate analyzer-visible changes from user-visible service impact.
- Decision:: Revise the topology and support notes when the analyzer and field records agree.
Deck summary
Key takeaways
Zigbee is a low-power wireless system used by many local device networks.
- A gateway is the bridge from the local device network to another system.
- Topology evidence records parent, relay, coordinator, gateway, and single-dependency observations.
- Device-health evidence records stale reporting, repeated retries, power-state warnings, missed check-ins, or changing link-quality observations without turning one metric into a universal diagnosis.
- An analyzer record needs a boundary before the result can be trusted.
Retrieval practice
Recall check 1 of 6

Radio Remi says: answer from memory, then check your reasoning.
Q1A Zigbee analyzer shows a route change and repeated messages for one endpoint group. What is the strongest use of that observation?
Show answer
Answer: A Analyzer output is bounded evidence to correlate with gateway logs and field reports, not a complete explanation.
Retrieval practice
Recall check 2 of 6

Radio Remi says: answer from memory, then check your reasoning.
Q2In a Zigbee capture, what does the LQI value on a frame tell you?
Show answer
Answer: A A capture has MAC, NWK, and APS fields plus radio metadata such as LQI and RSSI.
Retrieval practice
Recall check 3 of 6

Radio Remi says: answer from memory, then check your reasoning.
Q3An analyzer shows Zigbee frames flowing between devices, but every application payload is unreadable. What is the most likely cause?
Show answer
Answer: A Zigbee headers can be visible without payload decryption; key material, channel, and RF placement bound capture evidence.
Retrieval practice
Recall check 4 of 6

Radio Remi says: answer from memory, then check your reasoning.
Q4A capture shows repeated NWK route-request broadcasts for the same destination over several minutes. What does this most likely indicate?
Show answer
Answer: A Diagnose from trends such as LQI decline, route-discovery churn, duplicate APS counters, and rejoins.
Retrieval practice
Recall check 5 of 6

Radio Remi says: answer from memory, then check your reasoning.
Q5A Zigbee analyzer shows a route change and repeated messages for one endpoint group. The record does not include gateway logs, field context, owner, or retest trigger. What is the strongest review decision?
Show answer
Answer: B The analyzer supports a bounded diagnostic claim, but deployment decisions need correlation plus an owner and retest trigger.
Retrieval practice
Recall check 6 of 6

Radio Remi says: answer from memory, then check your reasoning.
Q6A dashboard says all visible Zigbee devices are healthy, but users report intermittent control failures in one room. What review response best preserves quality?
Show answer
Answer: C Conflicting evidence requires correlation, a narrowed claim, recorded missing context, and an owned retest path.
Print reference
Answers 1 of 2
Answer key.
- A · Analyzer output is bounded evidence to correlate with gateway logs and field reports, not a complete explanation.
- A · A capture has MAC, NWK, and APS fields plus radio metadata such as LQI and RSSI.
- A · Zigbee headers can be visible without payload decryption; key material, channel, and RF placement bound capture evidence.
- A · Diagnose from trends such as LQI decline, route-discovery churn, duplicate APS counters, and rejoins.
Print reference
Answers 2 of 2
Answer key.
- B · The analyzer supports a bounded diagnostic claim, but deployment decisions need correlation plus an owner and retest trigger.
- C · Conflicting evidence requires correlation, a narrowed claim, recorded missing context, and an owned retest path.