← Back to the chapter

Technical detail · Z-Wave Simulation: Timing and Evidence Analysis

Trace Node 21 through route repair

Use an event log rather than a single final state. A route-repair scenario for Node 21 can start with cached path controller -> 6 -> 12 -> 21. At event 1, remove Node 12 or mark its acknowledgement as failed. At event 2, retry the same route according to policy. At event 3, try an alternate stored path such as controller -> 8 -> 14 -> 21. At event 4, if stored paths fail, launch the explorer-frame search.

The flood model should track duplicate suppression and hop budget. If Node 6 and Node 8 both hear the explorer, each may rebroadcast according to the ruleset. If Node 14 receives duplicates, it should forward only according to the model’s suppression rule. If every discovered candidate exceeds the classic repeater limit, the run should fail with “no valid classic route” instead of inventing a longer path.

Record three counters: normal route attempts, repair transmissions, and accepted path length. A healthy scenario might show 1 normal attempt before failure, 2 retries, 5 explorer-related transmissions, and then a recovered two-repeater route. A weak scenario might show many repair transmissions but no valid route because the only apparent bridge was a sleeping endpoint.

← Back to the chapter