Learning · Source briefing
Why a new node may not hear the mesh next door
The story
The Meshtastic project explains the usual reasons a new radio hears nothing: a different modem preset, a renamed primary channel that moves the frequency slot, or a local group using its own settings. In the US, Long Fast, Long Turbo and Medium Fast each land on a different slot. With 2.8 firmware, setting the US region on the device itself starts on Long Turbo, while a phone or CLI setup stays on Long Fast. The post also notes that old node lists can make other meshes look reachable, and that only an acknowledged direct message proves delivery.
What it means for your next build
Ask the nearest group which preset and channels it uses before you change anything. Keep private groups on secondary channels, and test with an acknowledged direct message rather than a channel post.
Make your first contactThis is BackCountrySignal's own short briefing. Read the original source for its complete details. Firmware and app announcements do not establish tested Graham County Mesh compatibility.