RFID, NFC & UWB · Study deck

Z-Wave Routing and Healing

A Z-Wave route fails at the worst time: after furniture moves, a repeater is unplugged, a sleeping sensor misses a wake window, or a device sits at the edge of coverage.

Radio Remi is your guide for this deck.

z-wavesource-routingroute-repair

Radio Remi, the module guide, in a scene from this chapter.

After studying this chapter

Learning objectives

You will be able to:

Explain how a classic Z-Wave source route is selected, carried, acknowledged, and remembered.
Identify which devices can act as repeaters and which devices should be treated as non-routing endpoints.
Describe how failed acknowledgements, alternate routes, Explorer Frames, and rediscovery fit into route repair.
Distinguish a targeted route repair from a broad network rediscovery or "heal" operation.

Major section

Start With the Story · In 60 Seconds

A Z-Wave route fails at the worst time: after furniture moves, a repeater is unplugged, a sleeping sensor misses a wake window, or a device sits at the edge of coverage.

The routing story is really a troubleshooting story.
Separate classic source routes, repeaters, repair behavior, sleeping endpoints, and Long Range direct paths so the evidence points to the real fault.
Classic Z-Wave routing is source-routed.

Major section

Checkpoint: Core Ideas · Source Routing, Not Hop-by-Hop Routing

Source route: the selected path is carried in the transmitted frame instead of being decided independently at every hop.

Repeater: an always-listening classic Z-Wave node that can forward routed traffic for other nodes.
Last Working Route (LWR): the most recently successful route a node can try before less proven alternatives.
Explorer Frame: a discovery frame used when known routes no longer reach the target.
Rediscovery or heal: a controller action that rebuilds route and neighbor evidence after topology changes or repeated failures.

Classic Z-Wave source route showing route evidence, a frame with an ordered hop list, repeater forwarding, acknowledgement, and Last Working Route update.

Major section

Source Route Evidence Is an Installed-Location Claim

A house might show one controller, nine mains-powered switches and plugs, four FLiRS locks or thermostats, and sixteen sleepy sensors.

The app reports thirty nodes, but the classic route backbone is only the nine always-listening devices.
The FLiRS and sleepy endpoints can be destinations; they are not the devices that carry another endpoint's command.
The repeater limit is also an acceptance constraint.

Major section

Repeaters and the Classic Mesh Backbone · Sleeping and Frequently Listening Endpoints

In classic Z-Wave, the reliable backbone is built from always-listening devices that can forward traffic.

Product category alone is not enough.
A wall switch, plug-in module, thermostat, or dedicated repeater may be part of the backbone when the device and controller expose it as a routing node.
A battery contact sensor, motion sensor, button, or handheld remote should normally be treated as an endpoint, not as a path-building device.
After relocation, the route record should be rebuilt and verified from the installed location.

Z-Wave endpoint behavior showing always-listening repeaters forwarding routed traffic, frequently listening endpoints receiving wake-up beams, and non-listening sleeping endpoints communicating only when awake.

Major section

Route Repair and Healing

Route repair starts when a command path stops producing the expected acknowledgement.

A controller or sending node may try the last working route, then other known routes, and then Explorer Frame discovery when known routes fail.
Explorer discovery may find a new path, which the controller stores and tests with a real command.
the Classic Z-Wave route repair loop showing a stored route, failed acknowledgement, alternate route attempts, Explorer Frame discovery, route update, and verification diagram starts with the last working route and ends with a tested command.
That test matters more than a successful discovery message: the post-repair command must reach the device.

Classic Z-Wave route repair loop showing a stored route, failed acknowledgement, alternate route attempts, Explorer Frame discovery, route update, and verification.

Major section

When Known Routes Fail

Furniture moves, a plug-in repeater is unplugged, a controller is relocated, a metal appliance appears near a route, or a battery device waits for a manual wake-up.

Z-Wave route recovery should be read as layered evidence rather than as one "heal" button.
If that fails, it tries other known routes from the controller's routing table.
If known routes fail, Explorer Frame discovery can search for a fresh path.

Major section

When Known Routes Fail (continued)

If both fail, the evidence points to a local path problem, not a reason to exclude every device.

If a new route through Node 8 and Node 14 acknowledges commands, record that before-and-after path and the physical change that made it work.
A broad rediscovery can produce useful route tables, but it can also hide the original cause if it is run before anyone records the failed path.
If a window sensor has a stale interview, wake it on schedule or manually before treating routing as broken.

Major section

Explorer Frames Are Controlled Flooding

Pure source routing has a weakness: if the controller's map is stale, every precomputed route can fail and the message is stuck.

Explorer Frames are the last-resort discovery mechanism.
When a node exhausts known routes, it broadcasts an Explorer Frame that neighboring always-listening nodes rebroadcast under a hop limit.
Long Range changes this logic.

Major section

Explorer Frames Are Controlled Flooding (continued)

Duplicate suppression and the route limit keep the search bounded.

Most commands use cheap precomputed source routes with bounded latency.
When topology has shifted, Explorer Frame discovery can repair the path without a full network heal.
The controller sends to Node 24 using cached route controller -> 6 -> 14 -> 24.

Major section

Explorer Frames Are Controlled Flooding (continued)

When stored options fail, an Explorer Frame asks nearby always-listening nodes to propagate the search while suppressing duplicates and respecting the route limit.

The sender then uses that route and caches the successful result as fresh route evidence.
If the route only works through a portable plug, the repair is operationally fragile even though the protocol found a path.
The evidence packet should include the physical role of each repeater.

Major section

Explorer Frames Are Controlled Flooding (continued)

Explorer Frames cannot make every case healthy.

If all candidate paths would require more than four repeaters, the topology is too stretched for classic routing.
If the only nearby devices are sleepy sensors, there is no forwarding backbone.
In a mixed installation, write down whether each endpoint is classic mesh or LR before adding repeaters.

Major section

Troubleshooting Evidence Packet

Z-Wave troubleshooting gets weaker when it is based on screenshots that only say "offline" or "busy." Build a packet that explains the route failure in terms an installer or future maintainer can retest.

Timestamped acknowledgements and retries show delivery, while link metrics and physical changes may explain a failure.
the Z-Wave routing evidence packet with seven fields: node identity, power and listening state, route evidence, delivery evidence, health evidence, physical evidence, and repair evidence that confirms a verified route diagram records node, power, route, and failure context for a retest.
The repair field records a wake, rediscovery, repeater move, or failed-node cleanup, then a post-repair command.
Calling a device reachable without the delivered command would leave the route result unverified.

Z-Wave routing evidence packet with seven fields: node identity, power and listening state, route evidence, delivery evidence, health evidence, physical evidence, and repair evidence that confirms a verified route.

Major section

Classic Mesh vs Z-Wave Long Range

Z-Wave Long Range changes the topology.

Z-Wave Alliance material describes LR as using a 12-bit address space with support for up to 4000 nodes, while classic Z-Wave uses the smaller classic node space.
The more important routing point is that LR nodes do not become repeaters for classic routes.
The classic mesh example sends a lock command through a source route with repeaters, so each forwarding node can affect the result.
The Long Range side uses a direct link from controller to endpoint, with no classic repeater chain.

Classic Z-Wave mesh contrasted with Z-Wave Long Range star topology, showing repeaters only on the classic side and direct gateway links on the Long Range side.

Major section

Checkpoint: Limits to Keep Visible · Worked Example: Smart Plug Moved

These limits are not reasons to avoid Z-Wave.

A home has a controller in the utility room, an in-wall switch near the stairs, a plug-in module in the upstairs hallway, and a battery lock at the front door.
The lock works for months.
The lock starts reporting late or unreachable.

Major section

Checkpoint: Summary · Key Takeaway

Classic Z-Wave routing depends on source routes, repeaters, acknowledgements, and route evidence that can become stale when the physical network changes.

Route repair should be evidence-driven: observe the failed route, fix physical causes, run targeted repair or rediscovery, then verify the updated route.
Z-Wave Long Range is a star-topology option, not a classic mesh repeater layer.
Z-Wave routing depends on device placement, powered repeaters, network healing, security, and diagnostics rather than a simple range claim.

Deck summary

Key takeaways

A Z-Wave route fails at the worst time: after furniture moves, a repeater is unplugged, a sleeping sensor misses a wake window, or a device sits at the edge of coverage.

Source route: the selected path is carried in the transmitted frame instead of being decided independently at every hop.
A house might show one controller, nine mains-powered switches and plugs, four FLiRS locks or thermostats, and sixteen sleepy sensors.
In classic Z-Wave, the reliable backbone is built from always-listening devices that can forward traffic.
Route repair starts when a command path stops producing the expected acknowledgement.

Retrieval practice

Recall check 1 of 3

Radio Remi says: answer from memory, then check your reasoning.

Q1How does classic Z-Wave routing move a frame toward its destination?

ASource routing: the sender puts a stored route in the frame and each repeater forwards it.

BHop-by-hop routing, where each node independently picks the next hop itself.

CFlooding every single frame to all nodes on the network at once.

DA fixed star where every device always reaches the hub directly on its own.

Show answer

Answer: A Classic Z-Wave is source-routed: the sender embeds a stored route and each repeater forwards to the next listed hop.

Retrieval practice

Recall check 2 of 3

Radio Remi says: answer from memory, then check your reasoning.

Q2A Z-Wave device's usual route stops working after a repeater is moved. How can the message still get through, and why is this not done for every message?

AEvery message is flooded to all nodes, so a moved repeater does not matter.

BBattery-powered sensors become repeaters to bypass the moved device.

CThe controller must be manually reset before any message can route again.

DKnown routes fail, then an Explorer Frame discovers and caches a new path.

Show answer

Answer: D Classic Z-Wave normally uses cached source routes through mains-powered repeaters.

Retrieval practice

Recall check 3 of 3

Radio Remi says: answer from memory, then check your reasoning.

Q3A classic Z-Wave command to a door lock fails after the controller tries the Last Working Route and several known alternatives. What is the next routing mechanism to look for in the evidence?

AExplorer Frame discovery, because it is used when known direct or routed paths fail.

BA cloud routing service, because Z-Wave route repair is handled outside the local network.

CBattery-sensor repeating, because nearby sleepy nodes can forward the failed command.

DLong Range fallback, because a direct LR link could bypass the failed repeaters.

Show answer

Answer: A After known routes fail, Explorer Frame discovery is the local mechanism that can discover a new path.

Print reference

Answers

Answer key.

A · Classic Z-Wave is source-routed: the sender embeds a stored route and each repeater forwards to the next listed hop.
D · Classic Z-Wave normally uses cached source routes through mains-powered repeaters.
A · After known routes fail, Explorer Frame discovery is the local mechanism that can discover a new path.