Device type: (varies by infrastructure location – please consult the MSP Mesh Discord for preferred or experimental settings, but default to “Client” or “Client Base”)
Hops:
1-3 hops. Even if only set to 1 hop, it will still repeat mesh traffic according to the originating node’s hop setting
Telemetry settings:
Device Metrics: at least 6 hours unless telemetry is required for an experimental build.
Environment Metrics (if applicable): at least 6 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. If privacy-obsessed, simply don’t report GPS coordinates at all.
Why different than my pocket node?
Most nodes participate in infrastructure behavior to some degree. When we refer here to an “unattended” node, it means a node that is at or above rooftop level in the immediate area, and generally not used to directly send messages or chat.