MSP Mesh INFRASTRUCTURE Settings

Infrastructure config settings:

  • “Medium Range – Fast” LoRa preset
  • Channel slot 45 (913.125mhz)
    • You may need to manually enter “45” into the Channel Slot configuration input.
  • Node Broadcast Interval: 12 hours (or more)
  • Device type: (varies by infrastructure location – consult MSP Mesh Discord for preferred setting, but default to “Client”)
  • Hops:
    • If node is unattended, 3 hops. If used directly for communication, adjust to your preference.
  • Telemetry settings:
    • Device Metrics: 1-3 hours
    • Environment Metrics (if applicable): 1-3 hours
    • Power metrics (if applicable): 1-3 hours
  • Channel settings:
    • The Key for the primary channel should be ‘AQ==‘
    • If you are using the iOS client the channel may appear to be simply named “Primary Channel”. That is fine.
    • If you are using the Android client the channel will need to be named “MediumFast” to properly function. Simply ensure that it is named that in Channel settings. (It may or may not show a space between the words, either is fine)
  • Position/Location: GPS position coordinates are not critical to mesh performance, and can be obfuscated to your preference. GPS accuracy is set via Settings > Channels > Channel 0/Primary with a slider. Left on the slider is more obfuscated, Right on the slider becomes more accurate/less obfuscated.

Am I infrastructure?

Most active nodes participate in infrastructure behavior to some degree, but when we refer here to an “infrastructure” node, it usually means a node that is in a high, advantageous place, and usually unattended. Think: radio towers, building tops, skyscraper balconies, etc. If you are unsure if your node qualifies as an infrastructure node, please visit our Discord and chat with the MSP Mesh team!

Why not the default settings?

Due to the very large amount of nodes on the MSP Mesh network (currently at least 500, but likely many more) the default settings that come pre-configured with all Meshtastic devices cause too much airtime congestion.

With so many nodes, even without anyone actually chatting with each other, that many devices constantly blasting telemetry caused the network to be congested nearly all the time.

By changing to a shorter “chirp” preset (Medium Fast, in this case) the actual time spent on each of these broadcasts is significantly shorter, and frees up more of the frequency to be used at any given time.

1 hour = 3600 seconds
3 hours = 10800 seconds
12 hours = 43200 seconds
24 hours = 86400 seconds