Z-Wave Mesh Routing Animation

Explore controller-managed source routing, repeaters, sleeping endpoints, route cache, and repair

animation

z-wave

mesh

routing

source-routing

networking

intermediate

A guided Z-Wave mesh workbench for seeing why mains-powered repeaters matter, how source routes are chosen, and how failed routes are repaired.

Animation Z-Wave Mesh routing Intermediate

Z-Wave mesh routing: repeaters, route cache, and repair

Step through a home automation mesh where the controller chooses a bounded source route. The important design rule is visible immediately: mains-powered devices can repeat traffic, while sleeping battery endpoints should not be used as the mesh backbone.

1 -> 8 -> 18 Current source route

2 hops Routed hop count

1 repeater Forwarding nodes used

Discovery Route cache state

TryChoose the hall-to-lock scenario, set Radio range model to 30 m, enable Fail the selected repeater, and press Step.

ObserveThe Current source route, Routed hop count, and Route cache state change when 1 mains-powered repeater is removed.

ExplainZ-Wave forwards along a controller-selected repeater list; failing 1 listed relay invalidates that source route and triggers discovery of another awake path.

Technical boundariesThe graph uses deterministic range and wall penalties; RF fading, explorer-frame timing, route-cache lifetime, FLiRS behavior, security encapsulation, retries, network size limits, and controller heuristics are omitted.

Colour keyrfid nfc uwb identitycurrent / primaryreference / datasuccesscautionerror / failure

What moves

A command frame travels across the highlighted route after the explorer phase identifies a usable path.

What matters

Only the controller and routing-capable mains devices can forward for others in this teaching model.

What can fail

A cached route breaks when a repeater stops acknowledging, then route repair searches for an alternate path.

Boundary

The workbench uses the classic four-hop routing limit as a simplified learner model, not a full product stack.

Interactive Mesh Scene

A door lock is out of direct range, so the controller uses a mains-powered plug as a repeater.

Route ready: source route fits within four hops.

Controller Mains repeater Battery endpoint Explorer search Failed ACK

Measure

Check radio neighbors and which nodes can repeat.

Discover

Explorer-style search tests candidate paths.

Write route

The controller selects a source route.

Forward

The command frame moves hop by hop.

Cache or repair

Success is cached; failure triggers repair.

Source

Controller 1 Where the command starts.

Destination

Door lock 18 Endpoint receiving the command.

Constraint

4-hop limit Routes longer than this are rejected here.

Health

Healthy Based on repeaters and ACK result.

Route Evidence

Explorer search finds Controller 1 -> Smart plug 8 -> Door lock 18. Frame header: source=1, destination=18, route=[1, 8, 18]. Lesson: the battery door lock can receive the frame, but it is not a repeater for other devices.

Pair	Cached route	Status

Scenarios

Use presets first, then adjust range or failure to test the design.

Source node

Destination node

Radio range model

Short 168 px Long

Wall / placement penalty

Open 20 px loss Hard

Fail the selected repeater

Show rejected sleeping relay attempts

Human Check

If the highlighted path uses a gray battery endpoint in the middle, the route is wrong. Battery endpoints may be source or destination, but should not be selected as repeaters.

Learning Support

How to read the scene

Green nodes can forward for others. Gray nodes are endpoint devices. The thick green path is the actual route; faint lines are only possible radio neighbors.

Why source routing

The controller can embed the chosen hop list in the command frame. Each repeater follows the next-hop list instead of calculating a fresh path by itself.

When repair happens

Cached routes save airtime, but a failed ACK invalidates the route through that repeater. Discovery then searches for another path within the hop limit.

Quick Reference

Device roles

Controller manages inclusion and route knowledge.
Mains-powered routing nodes form the backbone.
Battery endpoints conserve power and do not relay here.

Route rules

The route is a hop list, not a broadcast path.
This animation enforces a four-hop teaching limit.
The destination may be a battery node.

Explorer search

Used when the cached route is missing or stale.
Can discover alternatives after a failed repeater.
Costs more airtime than using a valid cached route.

Design test

Place powered repeaters between weak endpoints and the controller.
Look for at least one alternate path for important devices.
Do not assume every visible node strengthens the mesh.

Practice Prompts

Spot the backbone

Select the sleeping sensor scenario. Which devices can actually carry another node's traffic, and which only appear to extend coverage?

Break the route

Turn on repeater failure. Does the controller still have a route? If not, decide where a powered plug would improve the design.

Compare protocols

Compare this page with Zigbee or Thread animations. Focus on who chooses the next hop and where route state is stored.

Model Boundaries And Related Pages

Simplified model

The workbench emphasizes the core mental model: bounded source routes, route cache, repeaters, sleeping endpoints, and repair. Real Z-Wave generations include additional details not modeled here.

Not Zigbee routing

Z-Wave's teaching model here is controller-managed source routing. Zigbee-style per-hop route discovery and RPL-style IPv6 routing are different concepts.

Frequency note

Z-Wave operates in sub-GHz regional bands. Exact frequency, range, and certification details depend on region and product generation.