home / set_it_up / pocket_node

Set up your pocket node the right way.

Welcome to the mesh! Got a little Meshtastic node to carry around the Twin Cities? We'll get you set up properly in about ten minutes, using the official iOS or Android app. No experience needed — and we'll explain the why as we go, so the settings actually make sense instead of being a list you copy blindly.

// the_big_idea

Here's the one idea that makes everything else click: a node in your pocket (or indoors at street level) is in a bad spot to relay other people's messages — if it tries, it just adds noise and clogs the network without extending anyone's range. So MSP Mesh asks pocket nodes to use a role called CLIENT_MUTE. Your node still sends and receives all your messages and shows on the map — it just politely stays quiet instead of rebroadcasting. Think of it as good manners on a crowded radio channel. As a bonus, CLIENT_MUTE also sips the least battery of any role, so your node lasts longer. Win-win.

// settings per mspmesh.org/settings · current as of May 2026

// before_you_touch_anything

A few tips that save the most headaches

None of this is hard — these four habits are just what trip up most newcomers, so keeping them in mind from the start saves a lot of head-scratching later.

✅ Do charge your node and set Region = US the very first time it powers on — it's the one setting that, if skipped, quietly breaks everything else. ✅ Do change settings one at a time and let the node reboot & reconnect between each. It's tempting to rush, but patience here prevents confusion. 🚫 Don't crank up every interval "just in case." On a 1,000+ node network, less is more — quiet nodes make a healthy mesh. 🚫 Don't panic if you see no nodes at first. That's completely normal, and we'll fix it together — keep reading.

// step_00 · get_connected

First, get your phone talking to the radio

This is the easy part — once your phone is paired, the rest is just a few toggles. The app is how you'll read and send messages and change every setting below.

1

Power on & install the official app

App Store for iPhone/iPad; Google Play or F-Droid for Android.

🚫 Don't grab a random third-party app — there are copycats. Stick with the official Meshtastic one.
2

Connect to your node

Tap the connect / radio icon and pick your node from the list — it'll look like Meshtastic_xxxx

3

Enter the pairing code

Usually 123456 by default, or the code shown right on the device's screen.

4

You're in 🎉

When you see your node's name and a connected indicator, you're paired and ready. That's the trickiest bit done.

Brand-new radio that needs flashing first?
Some DIY boards need Meshtastic firmware installed before they'll pair — no worries, it's a one-time thing. Plug it in via a USB data cable, open flasher.meshtastic.org in Chrome/Edge/Brave, pick your model, click Install. Many radios (SenseCAP T1000-E, LilyGo T-Echo, prebuilt kits) ship ready and skip this entirely.

// cheat_sheet

Where we're headed

Here's the whole destination on one screen. Don't memorize it — we walk through each line below for your phone. It's just nice to see the map before the drive.

SettingYour pocket nodeA stationary home node
LoRa presetMedium Range – FastMedium Range – Fast
Device roleCLIENT_MUTECLIENT (or CLIENT_BASE)
Node Info broadcast6 hours or more12 hours or more
TelemetryOff6 hours+ or off
Position / Smart PositionOff (12h+ if needed)Off (18h+)
Max hops3–5 (up to 7 if needed)1–2 max
📍 Local tip on hops: inside the 494/694 metro loop and the suburbs bordering it, 3–5 hops is usually plenty. If your messages aren't reaching far enough out into greater Minnesota or western Wisconsin, bump it toward 6–7.

// walk_through_it_on_your_phone

Now, step by step on your device

Pick your platform below. For each setting we'll say what to change and why it matters, so you're never just flipping switches blindly.

On Apple devices the menus live under Settings (the gear), grouped into "Radio Configuration" and "Device Configuration."

1

LoRa preset — always do this one first

Why first: this puts your radio on the same "wavelength" as everyone else. If it's off, you'll hear pure silence and think the node is broken — so we lock it in before anything else.

Settings → Radio Configuration → LoRa

Region: US · Use Preset: on · Modem Preset: Medium Range – Fast · Max Hops: start at 5. Save and let it reboot.

✅ Double-check Region = US — the #1 reason a new node sees nothing🚫 Don't pick a different preset for "more range" — off the shared preset, you simply won't hear anyone🚫 Don't default to max hops — extra hops mean extra airtime for the whole network
2

Device role → CLIENT_MUTE

Why: this is the heart of a well-behaved pocket node — the "good manners" setting from up top.

Settings → Device Configuration → Device

Role: CLIENT_MUTE · Node Info Broadcast Seconds: 21600 (6h) or higher. Save.

🚫 Don't announce every few minutes — your node shouting "I'm here!" constantly is wasted airtime
3

Telemetry → off

Why: a pocket node really doesn't need to broadcast its battery temperature to the whole city.

Settings → Module Configuration → Telemetry

Turn the update intervals off.

4

Position → keep it quiet

Why: Smart Position chatters constantly as you move around — fine for a fixed node, noisy for one in your pocket.

Settings → Radio Configuration → Position

Smart Position: off. Only if you truly need occasional location: Broadcast Interval 43200 (12h)+, Update Interval 1h+, then switch it back off when you're done.

On Android the menus sit directly under Settings.

1

LoRa preset — always do this one first

Why first: it puts you on the same settings as everyone else. Skip it and you'll be on your own private island, unable to hear a soul.

Settings → LoRa

Region: US · Use Preset: on · Modem Preset: Medium Range – Fast · Max Hops: 5 to start. Save / send, and let it reboot.

✅ Confirm Region = US — don't skip this🚫 Don't choose a different preset thinking it helps — it just isolates you
2

Device role → CLIENT_MUTE

Why: the polite, battery-friendly role for anything you carry.

Settings → Device

Role: CLIENT_MUTE · Node Info Broadcast Interval: 6 hours or more. Save / send.

3

Telemetry → off

Why: no need to broadcast battery stats to the whole network.

Settings → Telemetry

Disable the telemetry intervals. Save / send.

4

Position → keep it quiet

Why: don't leave Smart Position on for something you carry around — it never stops talking.

Settings → Position

Smart Position: off. If occasional position is needed: Broadcast Interval 12 hours or more. Save / send.

That's it — you've got a well-behaved pocket node. 🎉 Quietly listening, sending your messages, and being a good neighbor on the mesh.

What if it's actually a home node, not a pocket one?
Good question — and here the rules flip a little. If you're mounting a node outdoors where it can genuinely help relay, it's allowed to be a helper:
  • Role: CLIENT — or CLIENT_BASE for a well-placed attic/roof node that should rebroadcast for your weaker indoor nodes.
  • Node Info broadcast: 12 hours or more.
  • Telemetry: 6 hours or more, or off.
  • Position / Smart Position: off; broadcast 18 hours or more.
  • Hops: 1–2 max. (Good to know: relaying doesn't "use up" your hop setting — every message carries its own hop count, so a relay just passes it along.)
🚫 Don't set a pocket node to CLIENT or ROUTER thinking you're "helping more." At street level you're genuinely not — CLIENT_MUTE is the helpful choice.

// if_something's_not_working

Hit a snag? Start here — don't despair

Almost everyone hits a bump setting up their first node. It's not you — it's just easy to mis-click one box. Here's the calm way through the common ones.

"I can't see any nodes!"
Take a breath — this one's usually a quick fix. Factory reset, then change only the LoRa preset to Medium Range – Fast and confirm Region = US. Wait a few minutes — nodes trickle in. Once they appear, re-apply the settings above one at a time.
✅ Resist the urge to change ten things at once while troubleshooting — change one, observe, repeat
"Max transmissions reached" / the sad cloud-with-a-slash
This is the single most common surprise for new folks — and here's the reassuring part: it's not a settings mistake at all. It deserves a real explanation, which is right below. 👇
A setting won't stick / the node goes unresponsive
Don't worry — that's almost always just the reboot after a change. Give it a moment to reconnect over Bluetooth before you touch the next setting.
the_big_one

"If I can hear them, why can't they hear me?"

This one trips up almost everyone, so let's clear it up properly. When you first power on, you'll see lots of activity — nodes popping into your list, chatter on the public channel — but the moment you send a message you get "Max transmissions reached" or a little cloud-with-a-slash. Frustrating! But totally normal, and not a sign anything's broken.

⚡ Listening is cheap; talking is expensive. Your node barely sips power to receive, so it happily hears distant nodes on rooftops and towers. But transmitting takes far more energy, and a pocket node pushes only about 0.25 watts — a tiny whisper. Home WiFi runs 1–2 watts (on a frequency that punches through walls more easily than our 913 MHz), and a cell tower is hundreds to a thousand times stronger. So you can hear the loud voices on the hill; your whisper from inside a building just doesn't reach them. It's physics, not a broken node.

How loud is a pocket node, really?
Pocket node
Home WiFi
Cell tower

~0.25 W vs far stronger transmitters

The fix isn't a setting — it's a friend nearby

To get your messages onto the mesh, your pocket node needs to be within range of another node that can actually hear it — ideally one up high with a clear view. Crossing that gap is the barrier every new member has to get past. The most reliable fix from home: put up a small outdoor "HQ" node nearby — just outside where you live or work, as high as you can safely reach. Often solar-powered and shaped like an unassuming utility box, it listens for your pocket node and relays it onward. This one step does more than any app tweak ever will.

A few MSP Mesh–recommended pre-assembled HQ nodes from reputable sellers:

✅ Ask the community on the Discord before spending any money — this hobby has a steep learning curve, and folks will gladly steer you right. 🚫 Don't rush to eBay or Amazon for your first device; start with the trusted sellers above. Full write-up ↗

// values per MSP Mesh (current as of May 2026). App labels shift a little between versions — if one looks different, glance at mspmesh.org/settings