Z-Wave Source Routing Animation (guided exercise)
Z-Wave Source Routing Animation (guided exercise)
See how a Z-Wave controller writes a complete route into a command frame
Exercise 1: Classic Route Feasibility
Model a controller, several always-listening repeaters, one sleeping sensor, and one lock. Define the allowed classic-mesh links manually. Then ask the simulator to find a path from the controller to the lock.
The pass condition is not “a route exists.” The pass condition is stricter:
- the route uses only always-listening classic mesh devices as repeaters;
- the route respects the configured classic repeater limit;
- the route does not use a sleeping battery endpoint as a forwarding node;
- the run records which link assumptions were synthetic and require RF validation.
If the path only works because the model allowed an endpoint to repeat while asleep, the model is wrong even if the graph search succeeds.
Run it: Test this controller-to-lock route in the source-routing animation below. Set the Route Request destination to Front lock #62 and run Discover Route to watch the controller build the hop list inside the command frame, checking that only always-listening repeaters carry it. Then compare a Cache hit against a Stale route, and use Clear Cache, to see when the controller trusts a cached path versus rediscovering one – the feasibility evidence this exercise asks you to record.
Plain check
- Name the site map. Name each node. Mark each radio type. Mark each sleep rule.
- Save the start route. Save the start time. Save the test fault. Save the expected result.
- Test one dead relay. Test one weak path. Test one slow node. Test one lost frame.
- Run the same case twice. Keep each result. Explain any change. Fix hidden chance.
- Mark model limits. Mark field unknowns. Plan the real test. Keep both records linked.
- Compare old and new paths. Check retry cost. Check user delay. Check safe recovery.
- Use Practitioner to run. Use deeper timing checks. Test the weak edge. State each bound.