Three of you are on a day hike, one person walks ahead, and on the app’s map their dot still sits at the last trail junction. Did they stop, or is the report old? That’s where your Meshtastic GPS settings matter. The short answer: leave smart position on and keep the broadcast interval at its 15-minute default. A moving node then reports far more often, while a stationary one barely uses airtime. Shorter intervals only pay off if someone truly needs minute-by-minute positions.
Keep three things apart: when the node determines a position, when it sends it to the mesh, and who may receive it at what precision. Adjust only one, and you’ll wonder why the map never changes.
Does every Meshtastic device have GPS?
No. Meshtastic runs on many radio boards, and plenty have no satellite receiver. The firmware’s GPS mode setting has three values: enabled, disabled and not present, and depending on the device it ships as enabled or not present. If your position settings show “not present,” your board has no receiver or the firmware doesn’t detect it.
A node without a receiver can still report a position: Meshtastic uses your paired phone’s coordinates while the app is connected over Bluetooth and has location permission. The limit is clear. Once the phone in your pack loses the connection or the operating system puts the app to sleep, the position stops updating.
A node with a built-in GNSS receiver works independently of your phone. GNSS is the umbrella term for satellite systems such as GPS, Galileo, GLONASS and BeiDou. The WisMesh Tag LW010-R, for example, combines an nRF52840 microcontroller, a Semtech SX1262 radio and an AT6558R GNSS module with integrated antennas for LoRa, Bluetooth and GNSS. It has no display; you configure it through the Meshtastic app.
At least one device on the mesh with GPS, a real-time clock or internet time also helps with timekeeping. For text messaging you don’t need a receiver; on Meshtastic, GPS is an add-on, not a requirement.
Meshtastic position settings: how do the interval and smart broadcast work?
This is where most confusion starts. The GPS update interval sets how often the node tries to determine a new position; the default is every two minutes. The broadcast interval sets how often that position goes out to the mesh; the default is every 15 minutes. So a fresh fix can sit on the device while everyone else still sees the report from ten minutes ago.
Smart broadcast, usually labeled smart position in the apps, is on by default. It adds to the fixed interval rather than replacing it: if the node has moved far enough since its last report, it sends earlier; if it’s standing still, the fixed interval applies. The minimum distance defaults to 100 meters. There’s also a minimum number of seconds between two reports, and the firmware additionally derives the actual pace from your channel’s data rate. The Meshtastic documentation lists two different default values for that minimum interval, so check what your app shows.
The documentation recommends leaving the broadcast interval at its default while smart position is active. Here’s which setting controls what:
| Setting | What it controls | Default (value 0) |
|---|---|---|
| GPS update interval | How often the node determines a new position | every 2 minutes |
| Broadcast interval | How often the position is sent without movement | every 15 minutes |
| Smart position | Earlier reports while moving | on |
| Smart position minimum distance | Distance since the last report before an early report is allowed | 100 meters |
What does that mean on the trail? Walking at about 4 km/h (2.5 mph), you cover roughly 67 meters per minute, so you pass the 100-meter threshold after about a minute and a half. Because the node only determines a new position every two minutes, reports in this case arrive at roughly two-minute intervals. On a bike at 15 km/h you cover 250 meters per minute, and the GPS update interval becomes the limiting factor. Only if that’s still too infrequent should you shorten the GPS update interval, not the broadcast interval.
Keep the group in mind: every report takes airtime on a shared channel, and ten nodes sending every minute produce ten times the packets of one. The TRACKER role makes the firmware prioritize position packets, for people and assets whose current location really matters.
Meshtastic map: how does your node appear?
The map in the Meshtastic app doesn’t show live positions; for each node it shows the most recent position report received. Your dot only appears on someone else’s device once their node has heard a position packet from you, so always check the time shown for a node. An old dot means nothing new arrived, not that the person stayed.
Who gets your position depends on the channel. By default, position data goes out over the primary channel. If that’s still LongFast with the well-known default key, every node in range on the default setup sees your location.
Online maps also display Meshtastic nodes. Your position only reaches them through an MQTT connection, via your own node or a nearby node that forwards packets to the internet. With the map reporting option, available from firmware 2.3.2, a node periodically sends an unencrypted map report to the MQTT server. It contains the node’s name, its position at configurable precision, altitude, hardware model, role and firmware version. The public MQTT server filters out precise positions. If you don’t want to appear there, check whether anyone in your group forwards to the internet.
How to share an approximate Meshtastic location (position precision)
A private conversation and a privately shared position are different things. You can chat on your own keyed channel while your coordinates keep going out over the public primary channel, which is why position precision is set per channel. Technically the value ranges from 0 to 32: at 0 the node sends no position on that channel, at 32 it sends full precision. In between, the number is the count of bits transmitted, and every bit you remove roughly doubles the blur.
| Precision bits | Approximate blur | Typical use |
|---|---|---|
| 32 | full precision | Meeting point within a trusted group |
| 19 | 45 m (148 ft) | Group knows which stretch of trail you’re on |
| 16 | 364 m (1,194 ft) | Neighborhood, but no house number |
| 13 | 2.9 km (1.8 mi) | Rough area for public channels |
| 10 | 23.3 km (14.5 mi) | Only the wider region |
| 0 | no position | Channel without location sharing |
The apps offer a practical selection rather than every value; set any specific value through the Python command-line interface. A sensible pattern: coarse or nothing on the public channel, only as precise as needed on your group channel.
From firmware 2.7.1, you can share your position on a private secondary channel and leave the primary channel public: turn location sharing off on channel 0 and on for the secondary channel you want. One catch: automatic position reports go to only one channel, namely the lowest-numbered secondary channel with sharing enabled. Other channels with sharing turned on can only request your position manually. Verify the result with a second node that knows only that channel rather than trusting your own client’s display.
How much battery does GPS use on Meshtastic?
No honest single runtime figure exists, because several consumers add up: the GNSS receiver, every packet the node sends and relays, the Bluetooth link to your phone and the device role you choose. The WisMesh Tag LW010-R has a built-in 1000 mAh battery. How long that lasts depends almost entirely on those settings and on how busy your mesh is.
For GPS, your biggest levers are two values. A longer GPS update interval runs the receiver less often. Smart position saves transmissions because only the fixed interval applies while you’re stationary. A very short broadcast interval, on the other hand, costs twice: power on your node and airtime for everyone who relays your packets.
The power-saving option turns off Bluetooth, serial, Wi-Fi and the screen, usually the wrong choice for a node you run from your phone on the go. The documentation recommends managing power mainly through the right role anyway.
Most reliable is your own comparison: note starting charge, duration, settings and remaining charge, and change only one value per run. That shows whether faster reports were worth the extra drain.
Meshtastic fixed position: when does it make sense for repeaters?
A node on a roof or in a window doesn’t move, which is what fixed position is for. When enabled, the node always reports the last saved coordinates, including altitude, taken from the built-in receiver, your phone or entered by hand. Your repeater then appears in the right spot on the map, and others can judge which area it covers.
One detail is easy to miss: even with a fixed position, a node with a built-in receiver keeps trying to determine its position at the GPS update interval. If your repeater has GPS hardware it doesn’t need, set the GPS mode to disabled after saving the coordinates. Alternatively, a very large GPS update interval allows a single fix at startup.
Think about privacy, too: on your house, an exact fixed position gives away your address, so reduce position precision on the public channel. The classic mistake runs the other way: a former stationary node taken on a trip keeps reporting the old location while fixed position is on. Turn it off before you hit the road.
Meshtastic GPS not getting a fix: what to do
Work step by step, and separate finding a position from delivering it. Check the GPS mode first: if it’s disabled or not present, the node isn’t even looking. Next, the sky: GNSS signals are weak, and a node inside a building, a car or a deep jacket pocket often takes long to get a fix, or never does. For the first attempt, put it under open sky with no metal above it.
Give it time on the first start after a long break; the first fix can take several minutes, especially after the node has been moved a long distance. Then check in the app whether a local position exists. Only once the node has a fix is delivery worth troubleshooting.
If the node has a position but others can’t see it, check the usual suspects: a fixed position overrides the real fix, position precision on the shared channel is set to 0, or the other node is on a different channel. Sometimes it just takes patience: without movement, the next report comes after the broadcast interval, by default up to 15 minutes. For deeper diagnosis, you can use the position flags to include values such as satellites in view or DOP in each report.
How to wear the WisMesh Tag as a Meshtastic tracker
The WisMesh Tag LW010-R is built for mobile use: a sealed IP66 enclosure, an operating range of −20 °C to +60 °C (−4 °F to 140 °F), a magnetic charging port and an included lanyard. The LoRa and GNSS antennas sit inside the housing. That makes it rugged, but no external antenna can make up for a poor carrying spot.
So the rule is simple: as high and as far outside as possible, with a clear view of the sky. On a shoulder strap or an outside loop of your pack, the receiver sees far more sky than in an inside pocket between a water bottle and a jacket. Your body absorbs radio signals, and metal objects right next to the node, like tools or an insulated steel bottle, degrade both reception and transmission further.
Test the way you’ll actually carry it. Walk a short loop with a stop and watch on a second node when reports arrive and how they match your route. Since the tag has no display, the status LEDs for heartbeat, Bluetooth and charging, together with the app, are your check. Charge it fully before longer trips and confirm a fix before you head out.
Where can you buy a Meshtastic device with GPS?
First decide whether the node needs its own GNSS receiver or your phone is a good enough position source. For trips where the phone stays in your pack or the connection might drop, a built-in receiver is the more robust choice. Look for integrated antennas and a sealed, weather-resistant enclosure if the node will hang on the outside of your pack. An eyelet or lanyard decides whether you’ll keep it in a good carrying position day to day. Battery capacity is a useful pointer, but the real runtime depends on your intervals, smart position and role.
Also check that you can configure the node comfortably through the app without a display, and that it runs firmware 2.7.1 or later if you want private location sharing on a secondary channel. With those criteria, you’ll find a node whose Meshtastic GPS settings fit your reporting plan. If you’re looking for a suitable device, you’ll find our models in the Meshtastic category.
Meshtastic GPS FAQ
Can Meshtastic use your phone’s GPS?
Yes. If your node has no receiver of its own, the Meshtastic app can pass your paired phone’s position to the node. This only works while the Bluetooth connection is up and the app has location permission. If the connection drops, the reported position stays at its last value.
How accurate is Meshtastic GPS?
Accuracy depends first on the receiver and its view of the sky; under open sky a GNSS receiver is typically within a few meters, and noticeably worse under trees or between buildings. What others see is further limited by the channel’s position precision, for example 45 meters at 19 bits or 2.9 kilometers at 13 bits. On top of that, a report can be several minutes old.
Does Meshtastic send its position when you’re not moving?
Yes. Even when you’re standing still, the node sends its position at the fixed broadcast interval, every 15 minutes by default. Smart position only adds extra reports while you’re moving. If no position should reach a particular channel at all, set position precision on that channel to 0.