Understanding star, tree, and mesh configurations with Coordinator, Router, and End Device roles
By the end of this chapter, you will be able to:
Zigbee supports three network topologies: star, tree, and mesh. Each topology offers different tradeoffs between simplicity, range, and reliability. Understanding these topologies and the device roles within them is essential for designing effective Zigbee networks.
Imagine a company with offices and employees:
In Zigbee networks, devices similarly can connect in different patterns. The choice affects how messages travel and what happens when a device fails.
In a star topology, all devices communicate directly with the central Coordinator:
Characteristics:
| Aspect | Star Topology |
|---|---|
| Hop count | Always 1 hop |
| Latency | Lowest (10-50ms) |
| Range | Limited to Coordinator range (10-30m) |
| Single point of failure | Coordinator |
| Complexity | Simplest |
| Best for | Small deployments, single room |
Advantages:
Disadvantages:
Tree topology adds hierarchical structure with Routers between End Devices and the Coordinator:
Characteristics:
| Aspect | Tree Topology |
|---|---|
| Hop count | Variable (1-5 typical) |
| Latency | Medium (50-200ms) |
| Range | Extended through Routers |
| Single point of failure | Parent Router |
| Complexity | Medium |
| Best for | Buildings with clear floor/room structure |
Advantages:
Disadvantages:
Mesh topology allows multiple routing paths between any two devices:
Characteristics:
| Aspect | Mesh Topology |
|---|---|
| Hop count | Variable (1-10+) |
| Latency | Higher (100-500ms) |
| Range | Maximum (multi-hop) |
| Redundancy | Multiple paths |
| Complexity | Highest |
| Best for | Large deployments, reliability-critical |
Advantages:
Disadvantages:
Zigbee defines three device roles, each with specific capabilities and power profiles:
The Coordinator is the network controller and trust center:
Responsibilities:
Hardware Requirements:
Example Coordinators:
- SmartThings Hub (1,000 devices)
- Hubitat Elevation (128 devices)
- Zigbee2MQTT with CC2652P (200 devices)
- ConBee II USB adapter (100 devices)Key Point: There is exactly ONE Coordinator per Zigbee network. Losing the Coordinator means the network cannot accept new devices and may lose critical state.
Routers extend the mesh network by forwarding messages:
Responsibilities:
Hardware Requirements:
Determining Router Capability:
| Power Source | Device Type | Router Capable? |
|---|---|---|
| Wall outlet | Smart plug | Yes |
| Light socket | Smart bulb | Yes |
| 24V wired | Thermostat | Yes |
| Battery | Door sensor | No |
| Battery | Motion sensor | No |
| Solar | Outdoor sensor | Usually No |
End Devices are leaf nodes that cannot route messages:
Responsibilities:
Hardware Requirements:
Power Management:
End Device Power States:
1. Deep Sleep: 1-5 µA (99% of time)
2. Wake: Check for work (10ms)
3. Poll: Ask parent for messages (15ms)
4. Transmit: Send sensor data (10ms)
5. Return to sleep
Result: 5-10 year battery life on CR2450 coin cell| Feature | Coordinator | Router | End Device |
|---|---|---|---|
| Power | Always on | Always on | Sleeps |
| Routing | Yes | Yes | No |
| Children | Yes | Yes (20-50) | No |
| Network per | 1 only | Many | Many |
| Memory | High | Medium | Low |
| Battery life | N/A (mains) | N/A (mains) | 5-10 years |
A smart plug that is always connected to a wall outlet and needs to relay Zigbee messages to nearby sensors would be configured as which device role?
B) Router. A mains-powered smart plug is an ideal Router because it is always on and can continuously relay messages for nearby End Devices. The Coordinator role is reserved for the single network-forming hub. End Devices sleep to save battery, which a wall-powered plug does not need to do. Power source is the primary factor: mains-powered devices should be Routers, battery-powered devices should be End Devices.
To determine router placement for mesh coverage:
Indoor range (conservative): 10-15 meters
Outdoor range (open area): 30-100 meters
Coverage area per router (indoor): ~150 m² (10m radius)
Overlap requirement: 30% for redundancy
Example: 200 m² apartment
- Minimum routers: 200 / 150 = 2 routers
- With redundancy: 3-4 routers recommendedA 5,000 m2 single-story warehouse needs temperature monitoring with 40 battery-powered sensors (End Devices) reporting every 5 minutes.
Step 1 – Router count:
Step 2 – End Device battery life:
A CR2450 coin cell (620 mAh) with 5-minute reporting:
| State | Duration | Current | Charge per cycle |
|---|---|---|---|
| Deep sleep | 299.95 s | 3 uA | 899.85 uAs |
| Wake + poll parent | 15 ms | 8 mA | 120 uAs |
| TX sensor data (127 B) | 4.3 ms | 17 mA | 73.1 uAs |
| RX ACK | 1 ms | 14 mA | 14 uAs |
| Total per 5-min cycle | 1,107 uAs |
How long does a Zigbee End Device battery really last? Let’s calculate for a warehouse temperature sensor on a CR2450 coin cell.
Battery capacity: CR2450 = 620 mAh at 3V $ E_{} = 620 = 1{,}860 $
Energy per 5-minute cycle (deep sleep 299.95s, wake 15ms, TX 4.3ms, RX ACK 1ms): $ E_{} = (3 ) + (8 ) + (17 ) + (14 ) $ $ E_{} = 0.90 + 0.12 + 0.073 + 0.014 = 1.11 = 0.00031 $
Battery life: \(\frac{620 \text{ mAh}}{0.00031 \text{ mAh/cycle}} \times 5 \text{ min} = 10{,}000{,}000 \text{ min} \approx 19.2 \text{ years}\)
Reality check: Battery self-discharge (~1-2%/year) and temperature effects reduce this to 5-8 years in practice.
Step 3 – Latency analysis:
Step 4 – Channel selection:
Use this tool to estimate how many Zigbee routers your deployment needs based on floor area and environment type.
| Deployment | Area per Router | Redundancy Factor |
|---|---|---|
| Apartment | 150-200 m² | 1.3x |
| House | 200-300 m² | 1.5x |
| Office | 300-500 m² | 2.0x |
| Warehouse | 500-1000 m² | 2.5x |
| Industrial | Custom survey | 3.0x |
A typical 2-story home deployment illustrates device role assignment:
Inventory:
- 1 SmartThings Hub (Coordinator)
- 10 Smart bulbs (Routers)
- 1 Smart thermostat (Router)
- 8 Door/window sensors (End Devices)
- 4 Motion sensors (End Devices)
- 2 Smart plugs (Routers)
Device Role Summary:
- Coordinator: 1 (hub)
- Routers: 13 (bulbs + thermostat + plugs)
- End Devices: 12 (sensors)
Router:End Device ratio: 13:12 (excellent coverage)Why this works well:
Bad deployment:
- 1 Coordinator (hub in basement)
- 20 door sensors (all battery-powered end devices)
- 0 routers!
Result:
- Only sensors within 10-15m of hub work
- Far sensors drop offline constantly
- No mesh - just a very limited starFix: Add mains-powered devices (smart plugs, bulbs) as routers between the Coordinator and distant sensors.
Problem:
- User turns off bedroom smart bulb at wall switch
- Bulb loses power
- Router goes offline
- Bedroom sensor loses parent
- Automations stop workingFix:
Max the Microcontroller is the Coordinator: “I’m the team captain! I start the network and make sure everyone has an address.”
Lila the LED is a Router: “I’m plugged into the wall, so I’m always awake. I can relay messages for other devices. Think of me as a hallway monitor passing notes between classrooms!”
Sammy the Sensor is an End Device: “I run on batteries, so I sleep most of the time. When I wake up, I talk to my parent Router and go back to sleep. Like a student who raises their hand, answers the question, and goes back to working quietly.”
Bella the Battery explains topologies: “In a star, everyone talks directly to Max. In a tree, messages go parent-to-child like a family tree. In a mesh, any Router can talk to any other Router – like everyone in school being friends with everyone. Mesh is strongest because if one friend is absent, you can always find another path!”
Key ideas for kids:
Q1: Why must Zigbee Routers be mains-powered (plugged in) rather than battery-powered?
B) Routers must always be awake to relay messages, which would drain batteries quickly – Routers act as relay points in the mesh, so they must be ready to forward messages at any time. If a Router slept to save battery, messages would be lost and the mesh would have gaps. End Devices can sleep because their parent Router holds their messages until they wake up and poll.
IKEA’s TRADFRI smart lighting system provides a revealing case study of how Zigbee topology decisions change as deployments scale. IKEA initially launched with a simple star topology around their TRADFRI Gateway (Coordinator), but as customers added more devices, the topology evolved and exposed design trade-offs.
Phase 1: Small apartment (5–15 devices, 2017 launch)
IKEA shipped the TRADFRI Gateway with star topology as default. All bulbs and remotes communicated directly with the gateway. This worked reliably because:
Customer satisfaction in this phase was high (4.2/5 on IKEA.com reviews).
Phase 2: Larger homes (15–40 devices, 2019–2020)
As IKEA expanded the product line (blinds, outlets, sensors), customers in larger homes (120+ m2) began reporting connectivity issues. The root cause: devices in far rooms were outside the gateway’s single-hop range.
IKEA’s solution was to enable mesh routing on mains-powered devices (bulbs and smart plugs). The TRADFRI firmware update in late 2019 promoted all mains-powered devices to Zigbee Routers, automatically forming a mesh topology.
| Metric | Star only (pre-2019) | Mesh enabled (post-2019) |
|---|---|---|
| Max reliable range | 15 m from gateway | 45+ m (3 hops through bulbs) |
| Max practical devices | 15–20 | 50+ |
| Latency (far room) | N/A (out of range) | 120–180 ms (3 hops) |
| Latency (same room) | 30–50 ms | 30–50 ms |
Phase 3: Dense mesh problems (40+ devices, 2021–present)
With mesh enabled, new problems emerged in densely-equipped homes:
Routing table overflow: The TRADFRI Gateway’s NXP JN5168 chip has 32 KB RAM, limiting the routing table to ~40 entries. Homes with 50+ devices experienced random disconnections as the routing table overflowed and discarded routes.
Bulb-as-Router fragility: When users turned off a light switch (cutting power to the bulb), the Router disappeared from the mesh, orphaning any End Devices using it as a parent. IKEA partially addressed this by recommending that users keep power switches on and use Zigbee remotes for control – a counterintuitive user experience for smart lighting.
Channel 11 congestion: TRADFRI Gateway defaults to Zigbee channel 11 (2.405 GHz), which overlaps with Wi-Fi channel 1. In apartment buildings with many Wi-Fi networks, this caused 5–15% packet loss. IKEA did not provide a user-facing channel selection option until the DIRIGERA hub (2022).
The DIRIGERA redesign (2022):
IKEA’s replacement hub, DIRIGERA, addressed these scaling limitations:
Design lesson: Star topology is correct for initial product launch (simplest, most reliable for small scale). But the transition to mesh must be designed from the start – hardware RAM, routing table capacity, and the “Routers must stay powered” requirement must be communicated to end users. IKEA’s experience shows that mesh topology is not a drop-in upgrade; it changes the user experience and requires purpose-built Router devices.
Zigbee networks with few or no routers are effectively star networks — all devices depend on the coordinator for routing. Always deploy routers (always-on devices) to enable mesh routing benefits.
Zigbee mesh formation is automatic but not always optimal. After deployment, verify actual routing paths using coordinator diagnostics to ensure no unexpected bottlenecks or long hop-count paths.
Tree routing creates predictable latency proportional to depth; mesh routing can create variable latency as routes adapt. Applications with strict latency requirements need topology analysis, not just coverage analysis.
This chapter covered Zigbee network topologies and device roles:
Star Topology: Simple, lowest latency, limited range
Tree Topology: Extended range, hierarchical structure
Mesh Topology: Maximum reliability, self-healing, highest complexity
Coordinator: One per network, forms PAN, trust center
Router: Extends mesh, always powered, forwards messages
End Device: Leaf node, battery-powered, sleeps to conserve power
Key design principles: - Match device role to power source (battery = End Device, mains = Router) - Maintain adequate router density for coverage - Plan for redundancy in reliability-critical applications - Consider mesh topology for deployments over 20 devices
::
::
| Concept | Related To | How They Connect |
|---|---|---|
| Star Topology | Network Formation | Simplest to deploy, all devices connect directly to Coordinator |
| Mesh Topology | Self-Healing | Multiple paths enable automatic rerouting when devices fail |
| Router Role | Mesh Density | More routers = stronger mesh with better redundancy |
| End Device Role | Battery Life | Sleeping capability enables 5-10 year battery operation |
| Coverage Calculation | Router Placement | Coverage area determines minimum router count needed |
| Hop Count | Latency | Each hop adds 10-30ms, affecting real-time control responsiveness |
| Chapter | Why It Matters |
|---|---|
| Zigbee Routing and Self-Healing | Learn how AODV route discovery and mesh self-healing keep messages flowing when devices fail |
| Zigbee Network Formation | Understand the joining process that adds Routers and End Devices to a live network |
| Zigbee Protocol Stack | See how the NWK, APS, and ZCL layers support the topologies covered here |
| Zigbee Deployment Planning | Apply topology and role decisions to real-world router placement strategies |
| Network Topologies Fundamentals | Revisit general star, tree, and mesh concepts across all IoT protocols |