Description

The {ROUTE} token in MeshCore auto-acknowledge messages always resolves to — when the message arrives via hops. The preview correctly shows the route path (e.g., a3 → 7f → 02), but the actual sent auto-ack contains —.

Direct connections work correctly — {ROUTE} resolves to (direct) as expected.

Steps to Reproduce

1. Set up auto-acknowledge with a template containing {ROUTE}
2. Send a MeshCore message via a routed path (through one or more hops)
3. Observe the preview — route displays correctly (e.g., a3 → 7f → 02)
4. Observe the sent auto-ack — {ROUTE} resolves to —

Expected Behavior

{ROUTE} in the sent auto-ack should match what the preview shows.

Actual Behavior

Sent auto-ack contains — for {ROUTE} on any routed message. Only direct connections resolve correctly.

Environment

• MeshMonitor: v4.11.5 (also reproduced on v4.11.4)
• MeshCore companion firmware: 1.15.0 and 1.16.0
• Channel types tested: hashtag (#bot) and private — same result on both

Notes

The preview rendering correctly shows route data at compose time, suggesting the route path is available in the incoming packet context but is not being passed through to the template substitution when the auto-ack fires asynchronously.

Authored by NodeZero 0️⃣