Store & Forward β
New in 4.0 (Phase 0)
MeshMonitor is now a Store & Forward client. It recognizes S&F server nodes on your mesh and can request history from them. Full server functionality remains on the node itself.
What is Store & Forward? β
Meshtastic's Store & Forward module lets a powered node (usually a mains-powered repeater) cache messages while recipients are offline, then replay them on request. Nodes acting as S&F servers are marked as is_store_forward_server in their device metadata.
What MeshMonitor does β
- Detects S&F servers β nodes with the S&F server flag are visually marked in the Nodes list and on the map
- Labels relayed messages β messages that arrived
via_store_forwardare tagged in the message history so you can distinguish them from direct traffic - Receives replays β when an S&F server pushes
ROUTER_TEXT_DIRECT/ROUTER_TEXT_BROADCASThistory to the mesh, MeshMonitor ingests those messages and tags them accordingly - Preserves S&F metadata across upgrades β two new database fields (
is_store_forward_server,via_store_forward) were added in migrations 034 and 035
Passive client only
MeshMonitor does not actively request history from S&F servers β it reacts to replays the server decides to push. Enabling S&F history requests (a CLIENT_HISTORY message) is on the roadmap.
When it helps β
- Intermittent coverage β messages you missed while out of range are still retrievable
- Shared repeaters β a community repeater acts as a message buffer for the whole mesh
- Debugging β spot messages that transited an S&F peer instead of direct RF
Configuration β
Store & Forward itself is configured on the device (firmware config, not MeshMonitor). Use the device configuration UI or the Meshtastic mobile app to:
- Enable the Store & Forward module on the node
- Choose whether it runs as a server, client, or both
- Tune retention (history entries, record time window)
Once the node reports S&F capability to MeshMonitor (it comes through as part of device info), MeshMonitor's S&F awareness activates automatically β no per-source configuration needed.
Related β
- Device Configuration
- Message Search
- Meshtastic firmware S&F docs: https://meshtastic.org/docs/configuration/module-config/store-and-forward/