← Back to the chapter

Technical detail · Z-Wave Routing and Healing

How Explorer discovery finds a replacement path

27.8 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. Duplicate suppression and the route limit keep the search bounded.

This is why classic Z-Wave meshes can be predictable and self-healing. 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 result still needs acceptance evidence: the new path, the acknowledgement, the endpoint role, and the installed-location dependency.

Walk through the failure. The controller sends to Node 24 using cached route controller -> 6 -> 14 -> 24. Node 6 forwards, but Node 14 no longer hears the frame because a powered repeater near the entry was moved. The sender gets no acknowledgement, so it tries another stored route. When stored options fail, an Explorer Frame asks nearby always-listening nodes to propagate the search while suppressing duplicates and respecting the route limit.

If Node 8 hears the Explorer Frame and can reach Node 14, the destination can return a discovered path such as controller -> 8 -> 14 -> 24. 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.

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. If the failed node is excluded, unpowered, region-incompatible, or waiting for a manual wake-up, route discovery cannot fix the underlying state.

Long Range changes this logic. An LR endpoint should be evaluated as a direct gateway link with its own signal and support evidence; it does not participate in the classic Explorer Frame repeater chain. In a mixed installation, write down whether each endpoint is classic mesh or LR before adding repeaters.

Accept a routing repair only after the new path, acknowledgement, endpoint role, and installed-location dependency are all recorded.

← Back to the chapter