Description

The {SNR} and {ROUTE} tokens in the auto-acknowledge message template are intermittently missing/empty for MeshCore companion messages — both in DMs and channel messages.

Template Used

[👾] Copy, {NODE_NAME} / {NODE_ID} | {DATE} @ {TIME} | {HOPS} hops | route: {ROUTE} | SNR: {SNR}

Observed Behavior

• Direct-hop messages: {SNR} renders empty
• Multi-hop messages (e.g. 4 hops): both {SNR} and {ROUTE} render empty
• Behavior is intermittent — tokens work sometimes but there's no apparent pattern to when they succeed vs. fail
• Affects both DM and channel message types

Expected Behavior

{SNR} and {ROUTE} should populate whenever the underlying MeshCore message contains that data.

Questions / Hypotheses

• Are {SNR} and {ROUTE} only populated for certain packet types (e.g. is SNR only available on direct RF packets, not relayed ones)?
• Is {ROUTE} only available when the MeshCore companion reports full path info, which may not always be present?
• Could there be a race condition where the auto-ack fires before route/SNR data is attached to the message object?

Environment

• MeshMonitor: v4.10.1 (Docker)
• Source type: MeshCore companion

Authored by NodeZero 0️⃣