Zigbee Mesh Network Formation Animation
Trace how Zigbee routers and end devices form a mesh, choose parents, discover routes, and recover from a weak or failed link
Grow a Zigbee PAN into a working mesh, then watch the route evidence change
A Zigbee coordinator starts the PAN. Routers extend it, keep neighbor and route information, and may accept child devices. End devices attach to a parent and do not relay. This workbench shows that formation, routing, and repair are related but not the same thing.
Coordinator
Starts the PAN and usually has short address 0x0000. It is not automatically the path for every later data packet.
Router
Stays awake, relays packets, maintains neighbor evidence, and can accept child devices when joining is allowed.
End Device
Joins through one parent, can sleep, and depends on that parent for network access. It is not a relay.
Formation Evidence
Look for permit join, association, parent choice, link quality, route discovery, and repair after a relay fails.
Mesh Formation Scene
A healthy classroom mesh grows outward from the coordinator through routers before end devices attach.
Scenario
Choose a mesh condition, then use play or step. The route and evidence panels update together.
Current Decision
The coordinator has started a PAN. No routers or end devices are part of the mesh yet.
Parent Table
Route And Neighbor Evidence
Frame Log
Learning Support
Read The Scene
Follow the yellow token. During formation it marks beacons, association, and parent choice. During routing it marks route request, route reply, or data forwarding.
Beginner Ramp
A mesh is not just many lines on a diagram. It is a set of joined routers with link evidence and rules for selecting a usable path.
What Can Go Wrong
If joining is closed, new devices cannot attach. If routers are sparse or weak, the route may need more hops or may fail even though the PAN exists.
Quick Reference
Coordinator
- Starts the PAN and takes address
0x0000. - Often acts as Trust Center in centralized security.
- Can route, but is not necessarily every data path.
Routers
- Stay awake and relay for other nodes.
- Can accept children when joining is allowed.
- Maintain neighbor and route evidence.
End Devices
- Attach to one parent at a time.
- May sleep to save battery.
- Do not forward traffic for other nodes.
Formation
- Permit join controls admission timing.
- Association creates parent-child state.
- Security policy can still reject a device.
Routing
- Zigbee mesh routing is commonly AODV-derived.
- Route requests explore; replies establish a path.
- Many-to-one and source routing may appear in concentrator designs.
Repair
- A broken relay invalidates cached route evidence.
- Alternative parents and routers allow recovery.
- A sparse mesh has less room to self-heal.
Technical Accuracy Notes
Teaching Model
The workbench uses simplified LQI-style scores so learners can compare routes. Real stacks combine neighbor aging, retries, route records, security policy, and implementation choices.
Route Discovery
Zigbee NWK routing is often described as AODV-style on-demand discovery. Some networks also use many-to-one routing and source routes, especially with a concentrator.
End-Device Sleep
A sleepy end device normally polls its parent. It does not relay packets, so adding many sleepy leaves does not improve mesh resilience.
Practice Prompts
Trace
In Healthy mesh, step to Data Flows. Which routers carry the sensor-to-valve packet, and which nodes are only children?
Diagnose
Switch to Join closed. What evidence proves this is an admission problem, not a routing problem?
Compare
Compare Sparse routers with Relay failure. Which one still has enough alternate path evidence to recover?