Zigbee Route Repair Evidence Workbench
Zigbee Route Repair Evidence Workbench
Route Repair and Concentrator Evidence
Route repair is the self-healing behavior a reviewer can actually observe. When a link on an established route fails, an upstream router can initiate a fresh discovery for that destination. A healthy repair usually appears as a short burst of route requests followed by traffic resuming on a new path. Continuous discovery that never settles is different evidence: it points to route churn, too few routers, a flapping link, or missing ownership.
For gateway-bound collection, many-to-one routing changes the evidence pattern. A concentrator such as the coordinator or gateway can issue a many-to-one request so routers learn a next hop toward the sink. Devices can then send route records that let the concentrator build reverse source routes for replies. This is useful evidence for collection-heavy systems, but it still must be retested after gateway replacement or topology changes.
| Mechanism | When used | Healthy evidence |
|---|---|---|
| Route repair | An in-use link fails. | One bounded discovery burst, then traffic resumes on an alternate path. |
| Many-to-one request | Many devices send toward one sink. | Sink-initiated discovery gives routers a next hop toward the concentrator. |
| Route record | The sink needs a reverse path. | Devices report route state that the concentrator can use for downstream replies. |