When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
إعدادات الجهاز
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
الوصف
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
الوصف
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
الوصف
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
استغرق وقت طويل
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
الوصف
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
الوصف
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
الوصف
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
الوصف
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
الوصف
Canned message enabled
⚠️ Deprecated in the protobuf schema
الرسائل
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
الوصف
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
الوصف
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
الوصف
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
الوصف
LED state
Turn the LED on or off
الحالي
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
الوصف
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
الوصف
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
الإدارة
Remote Administration
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
إعادة التشغيل
Restarts the node
Shutdown
Powers the node down
Factory reset
Returns every setting to its factory default
NodeDB reset
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Debug Panel
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
حول
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
إعدادات الجهاز
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
الوصف
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
الوصف
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
الوصف
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
استغرق وقت طويل
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
الوصف
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
الوصف
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
الوصف
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
الوصف
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
الوصف
Canned message enabled
⚠️ Deprecated in the protobuf schema
الرسائل
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
الوصف
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
الوصف
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
الوصف
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
الوصف
LED state
Turn the LED on or off
الحالي
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
الوصف
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
الوصف
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
الإدارة
Remote Administration
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
إعادة التشغيل
Restarts the node
Shutdown
Powers the node down
Factory reset
Returns every setting to its factory default
NodeDB reset
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Debug Panel
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
حول
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
diff --git a/main/assets/js/search-data.json b/main/assets/js/search-data.json
index 55029760ff..054fd3f4ff 100644
--- a/main/assets/js/search-data.json
+++ b/main/assets/js/search-data.json
@@ -3704,7 +3704,7 @@
},"529": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/sk-rSK/user/debug-logs.html#desktop",
"relUrl": "/sk-rSK/user/debug-logs.html#desktop"
@@ -3746,7 +3746,7 @@
},"535": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/be-rBY/user/debug-logs.html#desktop",
"relUrl": "/be-rBY/user/debug-logs.html#desktop"
@@ -3788,7 +3788,7 @@
},"541": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/it-rIT/user/debug-logs.html#desktop",
"relUrl": "/it-rIT/user/debug-logs.html#desktop"
@@ -3830,7 +3830,7 @@
},"547": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/es-rES/user/debug-logs.html#desktop",
"relUrl": "/es-rES/user/debug-logs.html#desktop"
@@ -3872,7 +3872,7 @@
},"553": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/sl-rSI/user/debug-logs.html#desktop",
"relUrl": "/sl-rSI/user/debug-logs.html#desktop"
@@ -3914,7 +3914,7 @@
},"559": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/no-rNO/user/debug-logs.html#desktop",
"relUrl": "/no-rNO/user/debug-logs.html#desktop"
@@ -3956,7 +3956,7 @@
},"565": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/hu-rHU/user/debug-logs.html#desktop",
"relUrl": "/hu-rHU/user/debug-logs.html#desktop"
@@ -3998,7 +3998,7 @@
},"571": {
"doc": "Отладочные журналы",
"title": "Desktop",
- "content": "У компьютерного приложения нет системного logcat, поэтому вкладка Журналы приложения вместо этого показывает собственный захваченный вывод журнала приложения. Поиск, фильтрация и экспорт работают точно так же. ",
+ "content": "У компьютерного приложения нет системного logcat, поэтому вкладка Журналы приложения вместо этого показывает собственный захваченный вывод журнала приложения. Поиск, фильтрация и экспорт работают точно так же. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/ru-rRU/user/debug-logs.html#desktop",
"relUrl": "/ru-rRU/user/debug-logs.html#desktop"
@@ -4040,7 +4040,7 @@
},"577": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/cs-rCZ/user/debug-logs.html#desktop",
"relUrl": "/cs-rCZ/user/debug-logs.html#desktop"
@@ -4082,7 +4082,7 @@
},"583": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/bg-rBG/user/debug-logs.html#desktop",
"relUrl": "/bg-rBG/user/debug-logs.html#desktop"
@@ -4124,7 +4124,7 @@
},"589": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/ga-rIE/user/debug-logs.html#desktop",
"relUrl": "/ga-rIE/user/debug-logs.html#desktop"
@@ -4166,7 +4166,7 @@
},"595": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/fr-rCA/user/debug-logs.html#desktop",
"relUrl": "/fr-rCA/user/debug-logs.html#desktop"
@@ -4208,7 +4208,7 @@
},"601": {
"doc": "Дебаг логови",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/srp/user/debug-logs.html#desktop",
"relUrl": "/srp/user/debug-logs.html#desktop"
@@ -4250,7 +4250,7 @@
},"607": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/ca-rES/user/debug-logs.html#desktop",
"relUrl": "/ca-rES/user/debug-logs.html#desktop"
@@ -4292,7 +4292,7 @@
},"613": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/ko-rKR/user/debug-logs.html#desktop",
"relUrl": "/ko-rKR/user/debug-logs.html#desktop"
@@ -4334,7 +4334,7 @@
},"619": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/sv-rSE/user/debug-logs.html#desktop",
"relUrl": "/sv-rSE/user/debug-logs.html#desktop"
@@ -4376,7 +4376,7 @@
},"625": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/ht-rHT/user/debug-logs.html#desktop",
"relUrl": "/ht-rHT/user/debug-logs.html#desktop"
@@ -4418,7 +4418,7 @@
},"631": {
"doc": "Дебаг логови",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/sr-rLatn/user/debug-logs.html#desktop",
"relUrl": "/sr-rLatn/user/debug-logs.html#desktop"
@@ -4460,7 +4460,7 @@
},"637": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/nl-rNL/user/debug-logs.html#desktop",
"relUrl": "/nl-rNL/user/debug-logs.html#desktop"
@@ -4502,7 +4502,7 @@
},"643": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/uk-rUA/user/debug-logs.html#desktop",
"relUrl": "/uk-rUA/user/debug-logs.html#desktop"
@@ -4544,7 +4544,7 @@
},"649": {
"doc": "Virheenjäljityslokitiedot",
"title": "Työpöytä",
- "content": "Työpöytäsovelluksessa ei ole järjestelmän logcat-lokitietoa, joten Sovelluslokit-välilehti näyttää sen sijaan sovelluksen itse keräämät lokit. Haku, suodatus ja vienti toimivat samalla tavalla. ",
+ "content": "Työpöytäsovelluksessa ei ole järjestelmän logcat-lokitietoa, joten Sovelluslokit-välilehti näyttää sen sijaan sovelluksen itse keräämät lokit. Haku, suodatus ja vienti toimivat samalla tavalla. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/fi-rFI/user/debug-logs.html#ty%C3%B6p%C3%B6yt%C3%A4",
"relUrl": "/fi-rFI/user/debug-logs.html#työpöytä"
@@ -4586,7 +4586,7 @@
},"655": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/is-rIS/user/debug-logs.html#desktop",
"relUrl": "/is-rIS/user/debug-logs.html#desktop"
@@ -4628,7 +4628,7 @@
},"661": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/lt-rLT/user/debug-logs.html#desktop",
"relUrl": "/lt-rLT/user/debug-logs.html#desktop"
@@ -4670,7 +4670,7 @@
},"667": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/gl-rES/user/debug-logs.html#desktop",
"relUrl": "/gl-rES/user/debug-logs.html#desktop"
@@ -4712,7 +4712,7 @@
},"673": {
"doc": "デバッグログ",
"title": "デスクトップ",
- "content": "デスクトップアプリにはシステムの logcat がないため、「アプリログ」タブは代わりに、アプリ自身がキャプチャしたログ出力を表示します。検索、絞り込み、エクスポートは同じように機能します。 . ",
+ "content": "デスクトップアプリにはシステムの logcat がないため、「アプリログ」タブは代わりに、アプリ自身がキャプチャしたログ出力を表示します。検索、絞り込み、エクスポートは同じように機能します。 Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/ja-rJP/user/debug-logs.html#%E3%83%87%E3%82%B9%E3%82%AF%E3%83%88%E3%83%83%E3%83%97",
"relUrl": "/ja-rJP/user/debug-logs.html#デスクトップ"
@@ -4754,7 +4754,7 @@
},"679": {
"doc": "Fehlersuchprotokolle",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/de-rDE/user/debug-logs.html#desktop",
"relUrl": "/de-rDE/user/debug-logs.html#desktop"
@@ -4796,7 +4796,7 @@
},"685": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/ar-rSA/user/debug-logs.html#desktop",
"relUrl": "/ar-rSA/user/debug-logs.html#desktop"
@@ -4838,7 +4838,7 @@
},"691": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/hr-rHR/user/debug-logs.html#desktop",
"relUrl": "/hr-rHR/user/debug-logs.html#desktop"
@@ -4880,7 +4880,7 @@
},"697": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/pt-rPT/user/debug-logs.html#desktop",
"relUrl": "/pt-rPT/user/debug-logs.html#desktop"
@@ -4922,7 +4922,7 @@
},"703": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/pl-rPL/user/debug-logs.html#desktop",
"relUrl": "/pl-rPL/user/debug-logs.html#desktop"
@@ -4964,7 +4964,7 @@
},"709": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/zh-rCN/user/debug-logs.html#desktop",
"relUrl": "/zh-rCN/user/debug-logs.html#desktop"
@@ -5006,7 +5006,7 @@
},"715": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/sq-rAL/user/debug-logs.html#desktop",
"relUrl": "/sq-rAL/user/debug-logs.html#desktop"
@@ -5048,7 +5048,7 @@
},"721": {
"doc": "Debug Logs",
"title": "桌面版",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/zh-rTW/user/debug-logs.html#%E6%A1%8C%E9%9D%A2%E7%89%88",
"relUrl": "/zh-rTW/user/debug-logs.html#桌面版"
@@ -5090,7 +5090,7 @@
},"727": {
"doc": "Arendaja logid",
"title": "Töölaud",
- "content": "Töölauarakendusel puudub süsteemi logcat, seega kuvatakse vahekaardil Rakenduse logid rakenduse enda jäädvustatud logide väljundit. Otsimine, filtreerimine ja eksportimine toimivad samamoodi. ",
+ "content": "Töölauarakendusel puudub süsteemi logcat, seega kuvatakse vahekaardil Rakenduse logid rakenduse enda jäädvustatud logide väljundit. Otsimine, filtreerimine ja eksportimine toimivad samamoodi. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/et-rEE/user/debug-logs.html#t%C3%B6%C3%B6laud",
"relUrl": "/et-rEE/user/debug-logs.html#töölaud"
@@ -5132,7 +5132,7 @@
},"733": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/fr-rFR/user/debug-logs.html#desktop",
"relUrl": "/fr-rFR/user/debug-logs.html#desktop"
@@ -5174,7 +5174,7 @@
},"739": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/tr-rTR/user/debug-logs.html#desktop",
"relUrl": "/tr-rTR/user/debug-logs.html#desktop"
@@ -5216,7 +5216,7 @@
},"745": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/el-rGR/user/debug-logs.html#desktop",
"relUrl": "/el-rGR/user/debug-logs.html#desktop"
@@ -5258,7 +5258,7 @@
},"751": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/ro-rRO/user/debug-logs.html#desktop",
"relUrl": "/ro-rRO/user/debug-logs.html#desktop"
@@ -5300,7 +5300,7 @@
},"757": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/iw-rIL/user/debug-logs.html#desktop",
"relUrl": "/iw-rIL/user/debug-logs.html#desktop"
@@ -5342,7 +5342,7 @@
},"763": {
"doc": "Debug Logs",
"title": "Desktop",
- "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
+ "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds. ",
"url": "/Meshtastic-Android/main/pt-rBR/user/debug-logs.html#desktop",
"relUrl": "/pt-rBR/user/debug-logs.html#desktop"
@@ -29919,7 +29919,7 @@
},"4274": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/sk-rSK/user/onboarding.html#permissions",
"relUrl": "/sk-rSK/user/onboarding.html#permissions"
@@ -29954,7 +29954,7 @@
},"4279": {
"doc": "Начало работы",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/be-rBY/user/onboarding.html#permissions",
"relUrl": "/be-rBY/user/onboarding.html#permissions"
@@ -29989,7 +29989,7 @@
},"4284": {
"doc": "Come iniziare",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/it-rIT/user/onboarding.html#permissions",
"relUrl": "/it-rIT/user/onboarding.html#permissions"
@@ -30024,7 +30024,7 @@
},"4289": {
"doc": "Primeros Pasos",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/es-rES/user/onboarding.html#permissions",
"relUrl": "/es-rES/user/onboarding.html#permissions"
@@ -30059,7 +30059,7 @@
},"4294": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/sl-rSI/user/onboarding.html#permissions",
"relUrl": "/sl-rSI/user/onboarding.html#permissions"
@@ -30094,7 +30094,7 @@
},"4299": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/no-rNO/user/onboarding.html#permissions",
"relUrl": "/no-rNO/user/onboarding.html#permissions"
@@ -30129,7 +30129,7 @@
},"4304": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/hu-rHU/user/onboarding.html#permissions",
"relUrl": "/hu-rHU/user/onboarding.html#permissions"
@@ -30164,7 +30164,7 @@
},"4309": {
"doc": "Начало работы",
"title": "Разрешения",
- "content": "Приложение запрашивает несколько разрешений во время настройки. Каждое из них служит определенной цели, и некоторые необходимы для основной функциональности. Разрешения Bluetooth . Bluetooth — это основной способ подключения твоего телефона к радиостанции Meshtastic. Экран Bluetooth показывает, что даёт тебе это разрешение: . | Обнаружение — найди и определи устройства Meshtastic рядом с тобой. | Настройки — управляйте параметрами устройства и каналами по беспроводной сети. | . На Android 12 и новее система спрашивает один раз про ближайшие устройства, и это разрешение покрывает и сканирование, и подключение. Без него придётся использовать USB или TCP-соединения. Разрешение на доступ к местоположению . ℹ️ Примечание: Для Bluetooth на Android 12 и выше местоположение не требуется. Android 11 и старше показывают один шаг для местоположения на экране Bluetooth, а не два — эти версии рассматривают сканирование Bluetooth как функцию определения местоположения, поэтому приложение запрашивает доступ к Местоположению вместо “Ближайшие устройства”. Если спросить дважды, это приведёт к тому, что Android вообще перестанет показывать диалог (второй отказ на Android 11; галочка “Больше не спрашивать” на Android 10 и старее). На Android 12 и новее это два разных момента: “Ближайшие устройства” объявлены как neverForLocation, и отказ от доступа к местоположению не мешает находить или подключаться к радио. Meshtastic также использует местоположение для: . | Показ вашего положения на карте | Вычисление расстояний до других нод | Обмен GPS-координатами с другими участниками сети (если включено) | . Предоставьте “При использовании приложения”. Приложение не запрашивает фоновое определение местоположения — в его манифесте нет параметра ACCESS_BACKGROUND_LOCATION — поэтому Android не предлагает опцию “Всегда”, и обновление местоположения происходит, когда приложение находится на переднем плане или выполняет функцию службы переднего плана. При отключении остальная часть приложения продолжает работать: на Android 12 и более новых версиях Bluetooth не затрагивается, отключаются только отображение местоположения на карте и обмен данными о местоположении. На Android 11 и более ранних версиях сканирование Bluetooth также прекращается, поскольку для этого требуется разрешение, которое Android блокирует. Кроме того, для получения каких-либо результатов сканирования необходимо включить системные службы определения местоположения. Разрешение на уведомления . Уведомления оповещают тебя о: . | Входящие сообщения из каналов и личных сообщений | Новые ноды, присоединившиеся к сети | Низкий заряд на удаленной ноде | . 💡 Совет: Ты можешь тонко настроить уведомления позже в настройках системы — приложение создает отдельный канал уведомлений по категориям (плюс несколько внутренних, как фоновая служба), поэтому ты можешь включить или заглушить их по отдельности. Разрешение на критические уведомления . Критические оповещения — это уведомления с высоким приоритетом, которые проходят через режим «Не беспокоить» и предназначены для экстренных вызовов и срочных сообщений. Этот шаг не является запросом на разрешение запуска. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Пересмотреть разрешения позже . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | Состояние | What tapping the row does | . | Разрешено | Открывает страницу системы, на которой можно просмотреть или отозвать запрос | . | Ещё не спрашивали | Запросить | . | Отклонено — нажми для разрешения | Объясняет, для чего нужно разрешение, а затем снова спрашивает, согласен ли ты. | . | Заблокировано — нажми, чтобы открыть системные настройки | Android больше не будет отображать диалоговое окно, поэтому откроется страница, на которой можно снова его включить | . | Не требуется для данной версии Android | Ничего — разрешения на твоём устройстве нет | . Это больше всего важно для уведомлений. Если вы отклонил их во время настройки, эта строка станет обратной: Android перестанет показывать диалоговое окно, как только ты решительно откажешься (повторный отказ), после чего эта строка переключится на ** Заблокировано ** и вместо этого отправит тебя на страницу настроек системы. Подсказка уведомлений есть только на Android 13 и новее — на более старых версиях уведомления включены по умолчанию и ими управляют через настройки самого Android. ",
+ "content": "Приложение запрашивает несколько разрешений во время настройки. Каждое из них служит определенной цели, и некоторые необходимы для основной функциональности. Разрешения Bluetooth . Bluetooth — это основной способ подключения твоего телефона к радиостанции Meshtastic. Экран Bluetooth показывает, что даёт тебе это разрешение: . | Обнаружение — найди и определи устройства Meshtastic рядом с тобой. | Настройки — управляйте параметрами устройства и каналами по беспроводной сети. | . На Android 12 и новее система спрашивает один раз про ближайшие устройства, и это разрешение покрывает и сканирование, и подключение. Без него придётся использовать USB или TCP-соединения. Разрешение на доступ к местоположению . ℹ️ Примечание: Для Bluetooth на Android 12 и выше местоположение не требуется. Android 11 и старше показывают один шаг для местоположения на экране Bluetooth, а не два — эти версии рассматривают сканирование Bluetooth как функцию определения местоположения, поэтому приложение запрашивает доступ к Местоположению вместо “Ближайшие устройства”. Если спросить дважды, это приведёт к тому, что Android вообще перестанет показывать диалог (второй отказ на Android 11; галочка “Больше не спрашивать” на Android 10 и старее). На Android 12 и новее это два разных момента: “Ближайшие устройства” объявлены как neverForLocation, и отказ от доступа к местоположению не мешает находить или подключаться к радио. Meshtastic также использует местоположение для: . | Показ вашего положения на карте | Вычисление расстояний до других нод | Обмен GPS-координатами с другими участниками сети (если включено) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Предоставьте “При использовании приложения”. Приложение не запрашивает фоновое определение местоположения — в его манифесте нет параметра ACCESS_BACKGROUND_LOCATION — поэтому Android не предлагает опцию “Всегда”, и обновление местоположения происходит, когда приложение находится на переднем плане или выполняет функцию службы переднего плана. При отключении остальная часть приложения продолжает работать: на Android 12 и более новых версиях Bluetooth не затрагивается, отключаются только отображение местоположения на карте и обмен данными о местоположении. На Android 11 и более ранних версиях сканирование Bluetooth также прекращается, поскольку для этого требуется разрешение, которое Android блокирует. Кроме того, для получения каких-либо результатов сканирования необходимо включить системные службы определения местоположения. Разрешение на уведомления . Уведомления оповещают тебя о: . | Входящие сообщения из каналов и личных сообщений | Новые ноды, присоединившиеся к сети | Низкий заряд на удаленной ноде | . 💡 Совет: Ты можешь тонко настроить уведомления позже в настройках системы — приложение создает отдельный канал уведомлений по категориям (плюс несколько внутренних, как фоновая служба), поэтому ты можешь включить или заглушить их по отдельности. Разрешение на критические уведомления . Критические оповещения — это уведомления с высоким приоритетом, которые проходят через режим «Не беспокоить» и предназначены для экстренных вызовов и срочных сообщений. Этот шаг не является запросом на разрешение запуска. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Пересмотреть разрешения позже . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | Состояние | What tapping the row does | . | Разрешено | Открывает страницу системы, на которой можно просмотреть или отозвать запрос | . | Ещё не спрашивали | Запросить | . | Отклонено — нажми для разрешения | Объясняет, для чего нужно разрешение, а затем снова спрашивает, согласен ли ты. | . | Заблокировано — нажми, чтобы открыть системные настройки | Android больше не будет отображать диалоговое окно, поэтому откроется страница, на которой можно снова его включить | . | Не требуется для данной версии Android | Ничего — разрешения на твоём устройстве нет | . Это больше всего важно для уведомлений. Если вы отклонил их во время настройки, эта строка станет обратной: Android перестанет показывать диалоговое окно, как только ты решительно откажешься (повторный отказ), после чего эта строка переключится на ** Заблокировано ** и вместо этого отправит тебя на страницу настроек системы. Подсказка уведомлений есть только на Android 13 и новее — на более старых версиях уведомления включены по умолчанию и ими управляют через настройки самого Android. ",
"url": "/Meshtastic-Android/main/ru-rRU/user/onboarding.html#%D1%80%D0%B0%D0%B7%D1%80%D0%B5%D1%88%D0%B5%D0%BD%D0%B8%D1%8F",
"relUrl": "/ru-rRU/user/onboarding.html#разрешения"
@@ -30199,7 +30199,7 @@
},"4314": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/cs-rCZ/user/onboarding.html#permissions",
"relUrl": "/cs-rCZ/user/onboarding.html#permissions"
@@ -30234,7 +30234,7 @@
},"4319": {
"doc": "Първи стъпки",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | Състояние | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | Състояние | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/bg-rBG/user/onboarding.html#permissions",
"relUrl": "/bg-rBG/user/onboarding.html#permissions"
@@ -30269,7 +30269,7 @@
},"4324": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/ga-rIE/user/onboarding.html#permissions",
"relUrl": "/ga-rIE/user/onboarding.html#permissions"
@@ -30304,7 +30304,7 @@
},"4329": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/fr-rCA/user/onboarding.html#permissions",
"relUrl": "/fr-rCA/user/onboarding.html#permissions"
@@ -30339,7 +30339,7 @@
},"4334": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/srp/user/onboarding.html#permissions",
"relUrl": "/srp/user/onboarding.html#permissions"
@@ -30374,7 +30374,7 @@
},"4339": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/ca-rES/user/onboarding.html#permissions",
"relUrl": "/ca-rES/user/onboarding.html#permissions"
@@ -30409,7 +30409,7 @@
},"4344": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/ko-rKR/user/onboarding.html#permissions",
"relUrl": "/ko-rKR/user/onboarding.html#permissions"
@@ -30444,7 +30444,7 @@
},"4349": {
"doc": "Kom igång",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/sv-rSE/user/onboarding.html#permissions",
"relUrl": "/sv-rSE/user/onboarding.html#permissions"
@@ -30479,7 +30479,7 @@
},"4354": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/ht-rHT/user/onboarding.html#permissions",
"relUrl": "/ht-rHT/user/onboarding.html#permissions"
@@ -30514,7 +30514,7 @@
},"4359": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/sr-rLatn/user/onboarding.html#permissions",
"relUrl": "/sr-rLatn/user/onboarding.html#permissions"
@@ -30549,7 +30549,7 @@
},"4364": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/nl-rNL/user/onboarding.html#permissions",
"relUrl": "/nl-rNL/user/onboarding.html#permissions"
@@ -30584,7 +30584,7 @@
},"4369": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/uk-rUA/user/onboarding.html#permissions",
"relUrl": "/uk-rUA/user/onboarding.html#permissions"
@@ -30619,7 +30619,7 @@
},"4374": {
"doc": "Aloittaminen",
"title": "Käyttöoikeudet",
- "content": "Sovellus pyytää määrityksen aikana useita käyttöoikeuksia. Jokaisella niistä on oma tarkoituksensa, ja osa niistä on välttämättömiä perustoimintojen kannalta. Bluetooth-käyttöoikeus . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Sijaintikäyttöoikeus . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Käyttöoikeuden pyytäminen kahdesti voisi johtaa tilanteeseen, jossa Android lakkaa näyttämästä valintaikkunaa kokonaan (toinen hylkäys Android 11:ssä, Älä kysy uudelleen -valintaruutu Android 10:ssä ja sitä vanhemmissa versioissa). Android 12:ssa ja uudemmissa versioissa nämä ovat erillisiä: “Lähistön laitteet” on määritelty asetuksella neverForLocation, eikä sijaintikäyttöoikeuden hylkääminen estä radion löytämistä tai siihen yhdistämistä. Meshtastic käyttää sijaintiasi myös seuraaviin tarkoituksiin: . | Sijaintisi näyttäminen mesh-kartalla | Etäisyyksien laskeminen muihin radioihin | GPS-koordinaattiesi jakaminen muiden verkon jäsenten kanssa (jos käytössä) | . Myönnä Sovelluksen käytön aikana. Sovellus ei pyydä taustasijaintia — sen manifestissa ei ole ACCESS_BACKGROUND_LOCATION-oikeutta — joten Android ei tarjoa Aina-vaihtoehtoa, ja sijaintipäivitykset tapahtuvat sovelluksen ollessa etualalla tai sen suorittaessa taustapalvelua. Sijaintikäyttöoikeuden hylkääminen ei estä sovelluksen muuta toimintaa. Android 12:ssa ja uudemmissa versioissa Bluetooth toimii edelleen, ja vain kartta, sijainnin näyttäminen ja sijainnin jakaminen poistuvat käytöstä. Android 11:ssä ja uudemmissa versioissa myös Bluetooth-skannaus estyy, koska Android liittää sen tähän käyttöoikeuteen — lisäksi järjestelmän Sijaintipalvelut on oltava käytössä, jotta skannaus palauttaa tuloksia. Ilmoituskäyttöoikeus . Ilmoitukset kertovat sinulle: . | Saapuvista viesteistä kanavilta ja yksityisviesteistä | Uusista mesh-verkkoon liittyvistä radioista | Etäradion akun vähäisestä virrasta | . 💡 Vinkki: Voit myöhemmin säätää ilmoitusasetuksia Androidin järjestelmäasetuksissa. Sovellus luo jokaiselle ilmoitusluokalle oman ilmoituskanavan (sekä muutamia sisäisiä kanavia, kuten taustapalvelulle), joten voit ottaa ne käyttöön tai mykistää ne yksitellen. Kriittisten hälytysten käyttöoikeus . Kriittiset hälytykset ovat korkean prioriteetin ilmoituksia, jotka ohittavat Älä häiritse -tilan — niitä käytetään mesh-verkon hätähälytyksiin ja kiireellisiin viesteihin. Tämä vaihe ei ole käyttöoikeuspyyntö. Hyväksy/hylkää-valintaikkunaa ei ole: painike avaa Androidin järjestelmäasetusten sivun sovelluksen Hälytykset-ilmoituskanavalle, jossa voit itse ottaa käyttöön Älä häiritse -tilan ohituksen. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Käyttöoikeuksien tarkistaminen myöhemmin . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | Tila | Mitä rivin napauttaminen tekee | . | Sallittu | Avaa järjestelmän sivun, jossa voit tarkistaa tai peruuttaa käyttöoikeuden | . | Ei kysytty vielä | Pyytää sitä | . | Estetty - napauta salliaksesi | Selittää, mihin käyttöoikeutta tarvitaan, ja pyytää sitä uudelleen, jos hyväksyt | . | Estetty - napauta avataksesi järjestelmäasetukset | Android ei enää näytä käyttöoikeusikkunaa, joten tämä avaa sivun, jossa voit ottaa käyttöoikeuden uudelleen käyttöön | . | Ei tarvita tässä Android-versiossa | Ei mitään – tätä käyttöoikeutta ei ole laitteessasi | . Tämä koskee erityisesti ilmoituksia. Jos hylkäät ne käyttöönoton aikana, tämä rivi toimii paluutienä: Android lakkaa näyttämästä valintaikkunaa, kun olet hylännyt pyynnön lopullisesti (toinen hylkäys), jolloin tämän rivin tilaksi vaihtuu Estetty ja se avaa sen sijaan järjestelmäasetukset. Ilmoituskäyttöoikeutta pyydetään vain Android 13:ssa ja uudemmissa versioissa — vanhemmissa versioissa ilmoitukset ovat oletusarvoisesti käytössä ja niitä hallitaan Androidin omista asetuksista. ",
+ "content": "Sovellus pyytää määrityksen aikana useita käyttöoikeuksia. Jokaisella niistä on oma tarkoituksensa, ja osa niistä on välttämättömiä perustoimintojen kannalta. Bluetooth-käyttöoikeus . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Sijaintikäyttöoikeus . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Käyttöoikeuden pyytäminen kahdesti voisi johtaa tilanteeseen, jossa Android lakkaa näyttämästä valintaikkunaa kokonaan (toinen hylkäys Android 11:ssä, Älä kysy uudelleen -valintaruutu Android 10:ssä ja sitä vanhemmissa versioissa). Android 12:ssa ja uudemmissa versioissa nämä ovat erillisiä: “Lähistön laitteet” on määritelty asetuksella neverForLocation, eikä sijaintikäyttöoikeuden hylkääminen estä radion löytämistä tai siihen yhdistämistä. Meshtastic käyttää sijaintiasi myös seuraaviin tarkoituksiin: . | Sijaintisi näyttäminen mesh-kartalla | Etäisyyksien laskeminen muihin radioihin | GPS-koordinaattiesi jakaminen muiden verkon jäsenten kanssa (jos käytössä) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Myönnä Sovelluksen käytön aikana. Sovellus ei pyydä taustasijaintia — sen manifestissa ei ole ACCESS_BACKGROUND_LOCATION-oikeutta — joten Android ei tarjoa Aina-vaihtoehtoa, ja sijaintipäivitykset tapahtuvat sovelluksen ollessa etualalla tai sen suorittaessa taustapalvelua. Sijaintikäyttöoikeuden hylkääminen ei estä sovelluksen muuta toimintaa. Android 12:ssa ja uudemmissa versioissa Bluetooth toimii edelleen, ja vain kartta, sijainnin näyttäminen ja sijainnin jakaminen poistuvat käytöstä. Android 11:ssä ja uudemmissa versioissa myös Bluetooth-skannaus estyy, koska Android liittää sen tähän käyttöoikeuteen — lisäksi järjestelmän Sijaintipalvelut on oltava käytössä, jotta skannaus palauttaa tuloksia. Ilmoituskäyttöoikeus . Ilmoitukset kertovat sinulle: . | Saapuvista viesteistä kanavilta ja yksityisviesteistä | Uusista mesh-verkkoon liittyvistä radioista | Etäradion akun vähäisestä virrasta | . 💡 Vinkki: Voit myöhemmin säätää ilmoitusasetuksia Androidin järjestelmäasetuksissa. Sovellus luo jokaiselle ilmoitusluokalle oman ilmoituskanavan (sekä muutamia sisäisiä kanavia, kuten taustapalvelulle), joten voit ottaa ne käyttöön tai mykistää ne yksitellen. Kriittisten hälytysten käyttöoikeus . Kriittiset hälytykset ovat korkean prioriteetin ilmoituksia, jotka ohittavat Älä häiritse -tilan — niitä käytetään mesh-verkon hätähälytyksiin ja kiireellisiin viesteihin. Tämä vaihe ei ole käyttöoikeuspyyntö. Hyväksy/hylkää-valintaikkunaa ei ole: painike avaa Androidin järjestelmäasetusten sivun sovelluksen Hälytykset-ilmoituskanavalle, jossa voit itse ottaa käyttöön Älä häiritse -tilan ohituksen. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Käyttöoikeuksien tarkistaminen myöhemmin . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | Tila | Mitä rivin napauttaminen tekee | . | Sallittu | Avaa järjestelmän sivun, jossa voit tarkistaa tai peruuttaa käyttöoikeuden | . | Ei kysytty vielä | Pyytää sitä | . | Estetty - napauta salliaksesi | Selittää, mihin käyttöoikeutta tarvitaan, ja pyytää sitä uudelleen, jos hyväksyt | . | Estetty - napauta avataksesi järjestelmäasetukset | Android ei enää näytä käyttöoikeusikkunaa, joten tämä avaa sivun, jossa voit ottaa käyttöoikeuden uudelleen käyttöön | . | Ei tarvita tässä Android-versiossa | Ei mitään – tätä käyttöoikeutta ei ole laitteessasi | . Tämä koskee erityisesti ilmoituksia. Jos hylkäät ne käyttöönoton aikana, tämä rivi toimii paluutienä: Android lakkaa näyttämästä valintaikkunaa, kun olet hylännyt pyynnön lopullisesti (toinen hylkäys), jolloin tämän rivin tilaksi vaihtuu Estetty ja se avaa sen sijaan järjestelmäasetukset. Ilmoituskäyttöoikeutta pyydetään vain Android 13:ssa ja uudemmissa versioissa — vanhemmissa versioissa ilmoitukset ovat oletusarvoisesti käytössä ja niitä hallitaan Androidin omista asetuksista. ",
"url": "/Meshtastic-Android/main/fi-rFI/user/onboarding.html#k%C3%A4ytt%C3%B6oikeudet",
"relUrl": "/fi-rFI/user/onboarding.html#käyttöoikeudet"
@@ -30654,7 +30654,7 @@
},"4379": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/is-rIS/user/onboarding.html#permissions",
"relUrl": "/is-rIS/user/onboarding.html#permissions"
@@ -30689,7 +30689,7 @@
},"4384": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/lt-rLT/user/onboarding.html#permissions",
"relUrl": "/lt-rLT/user/onboarding.html#permissions"
@@ -30724,7 +30724,7 @@
},"4389": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/gl-rES/user/onboarding.html#permissions",
"relUrl": "/gl-rES/user/onboarding.html#permissions"
@@ -30759,7 +30759,7 @@
},"4394": {
"doc": "はじめに",
"title": "権限",
- "content": "アプリはセットアップ中にいくつかの権限を要求します。それぞれに特定の目的があり、一部は主要な機能に必要です。 . Bluetooth の権限 . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. 位置情報の権限 . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic は、次の目的でも位置情報を使用します： . | メッシュマップ上に自分の位置を表示する | 他のノードまでの距離を計算する | 他のメッシュメンバーと GPS 座標を共有する（有効な場合） | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. 通知の権限 . 通知は、次のことをお知らせします： . | チャンネルおよびダイレクトメッセージの受信 | メッシュに参加する新しいノード | リモートノードのバッテリー低下 | . 💡 ヒント： 通知の設定は、後で Android のシステム設定で細かく調整できます。アプリはカテゴリごとに個別の通知チャンネルを作成する（さらに、バックグラウンドサービスなどの内部用のものもいくつか作成する）ため、個別に有効化したり消音したりできます。 . 重要なアラートの権限 . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | 状態 | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "アプリはセットアップ中にいくつかの権限を要求します。それぞれに特定の目的があり、一部は主要な機能に必要です。 . Bluetooth の権限 . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. 位置情報の権限 . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic は、次の目的でも位置情報を使用します： . | メッシュマップ上に自分の位置を表示する | 他のノードまでの距離を計算する | 他のメッシュメンバーと GPS 座標を共有する（有効な場合） | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. 通知の権限 . 通知は、次のことをお知らせします： . | チャンネルおよびダイレクトメッセージの受信 | メッシュに参加する新しいノード | リモートノードのバッテリー低下 | . 💡 ヒント： 通知の設定は、後で Android のシステム設定で細かく調整できます。アプリはカテゴリごとに個別の通知チャンネルを作成する（さらに、バックグラウンドサービスなどの内部用のものもいくつか作成する）ため、個別に有効化したり消音したりできます。 . 重要なアラートの権限 . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | 状態 | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/ja-rJP/user/onboarding.html#%E6%A8%A9%E9%99%90",
"relUrl": "/ja-rJP/user/onboarding.html#権限"
@@ -30794,7 +30794,7 @@
},"4399": {
"doc": "Erste Schritte",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | Status | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | Status | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/de-rDE/user/onboarding.html#permissions",
"relUrl": "/de-rDE/user/onboarding.html#permissions"
@@ -30829,7 +30829,7 @@
},"4404": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/ar-rSA/user/onboarding.html#permissions",
"relUrl": "/ar-rSA/user/onboarding.html#permissions"
@@ -30864,7 +30864,7 @@
},"4409": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/hr-rHR/user/onboarding.html#permissions",
"relUrl": "/hr-rHR/user/onboarding.html#permissions"
@@ -30899,7 +30899,7 @@
},"4414": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/pt-rPT/user/onboarding.html#permissions",
"relUrl": "/pt-rPT/user/onboarding.html#permissions"
@@ -30934,7 +30934,7 @@
},"4419": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/pl-rPL/user/onboarding.html#permissions",
"relUrl": "/pl-rPL/user/onboarding.html#permissions"
@@ -30969,7 +30969,7 @@
},"4424": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/zh-rCN/user/onboarding.html#permissions",
"relUrl": "/zh-rCN/user/onboarding.html#permissions"
@@ -31004,7 +31004,7 @@
},"4429": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/sq-rAL/user/onboarding.html#permissions",
"relUrl": "/sq-rAL/user/onboarding.html#permissions"
@@ -31039,7 +31039,7 @@
},"4434": {
"doc": "新手入門",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | 狀態 | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | 狀態 | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/zh-rTW/user/onboarding.html#permissions",
"relUrl": "/zh-rTW/user/onboarding.html#permissions"
@@ -31081,7 +31081,7 @@
},"4440": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "Rakendus küsib seadistamise ajal mitmeid lube. Igal neist on kindel eesmärk ja mõned on vajalikud põhifunktsioonide täitmiseks. Sinihamba load . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Asukoha luba . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic kasutab sinu asukohta ka järgmiseks: . | Kuvatakse asukoht kärgvõrgu kaardil | Calculating distances to other nodes | GPS koordinaatide jagamine teiste kärgvõrgu liikmetega (kui lubatud) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Märguannete load . Märguanded teavitavad teid järgmisest: . | Sissetulevad sõnumid kanalitelt ja otsesõnumid | New nodes joining the mesh | Kaugsõlmel on aku tühjenenud | . 💡 Vihje: Teavituste eelistusi saab hiljem Androidi süsteemiseadetes täpsustada – rakendus loob iga kategooria kohta eraldi teavituskanali (lisaks mõned sisemised, näiteks taustateenus), nii et saad need eraldi lubada või vaigistada. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | Olek | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "Rakendus küsib seadistamise ajal mitmeid lube. Igal neist on kindel eesmärk ja mõned on vajalikud põhifunktsioonide täitmiseks. Sinihamba load . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Asukoha luba . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic kasutab sinu asukohta ka järgmiseks: . | Kuvatakse asukoht kärgvõrgu kaardil | Calculating distances to other nodes | GPS koordinaatide jagamine teiste kärgvõrgu liikmetega (kui lubatud) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Märguannete load . Märguanded teavitavad teid järgmisest: . | Sissetulevad sõnumid kanalitelt ja otsesõnumid | New nodes joining the mesh | Kaugsõlmel on aku tühjenenud | . 💡 Vihje: Teavituste eelistusi saab hiljem Androidi süsteemiseadetes täpsustada – rakendus loob iga kategooria kohta eraldi teavituskanali (lisaks mõned sisemised, näiteks taustateenus), nii et saad need eraldi lubada või vaigistada. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | Olek | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/et-rEE/user/onboarding.html#permissions",
"relUrl": "/et-rEE/user/onboarding.html#permissions"
@@ -31116,7 +31116,7 @@
},"4445": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/fr-rFR/user/onboarding.html#permissions",
"relUrl": "/fr-rFR/user/onboarding.html#permissions"
@@ -31151,7 +31151,7 @@
},"4450": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/tr-rTR/user/onboarding.html#permissions",
"relUrl": "/tr-rTR/user/onboarding.html#permissions"
@@ -31186,7 +31186,7 @@
},"4455": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/el-rGR/user/onboarding.html#permissions",
"relUrl": "/el-rGR/user/onboarding.html#permissions"
@@ -31221,7 +31221,7 @@
},"4460": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/ro-rRO/user/onboarding.html#permissions",
"relUrl": "/ro-rRO/user/onboarding.html#permissions"
@@ -31256,7 +31256,7 @@
},"4465": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/iw-rIL/user/onboarding.html#permissions",
"relUrl": "/iw-rIL/user/onboarding.html#permissions"
@@ -31291,7 +31291,7 @@
},"4470": {
"doc": "Getting Started",
"title": "Permissions",
- "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
+ "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location. Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
"url": "/Meshtastic-Android/main/pt-rBR/user/onboarding.html#permissions",
"relUrl": "/pt-rBR/user/onboarding.html#permissions"
@@ -31403,7 +31403,7 @@
},"4486": {
"doc": "Settings — Modules & Admin",
"title": "Administrácia",
- "content": "Administrácia na diaľku . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reštartovať | Restarts the node | . | Vypnúť | Powers the node down | . | Obnova do výrobných nastavení | Returns every setting to its factory default | . | Reset databázy uzlov | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Zálohovanie a Obnovenie . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Debug okno . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O aplikácii . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Administrácia na diaľku . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reštartovať | Restarts the node | . | Vypnúť | Powers the node down | . | Obnova do výrobných nastavení | Returns every setting to its factory default | . | Reset databázy uzlov | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Zálohovanie a Obnovenie . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Debug okno . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O aplikácii . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/sk-rSK/user/settings-module-admin.html#administr%C3%A1cia",
"relUrl": "/sk-rSK/user/settings-module-admin.html#administrácia"
@@ -31438,7 +31438,7 @@
},"4491": {
"doc": "Settings — Modules & Admin",
"title": "Administration",
- "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Перазагрузіць | Restarts the node | . | Shutdown | Powers the node down | . | Factory reset | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Панэль адладкі . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. О нас . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Перазагрузіць | Restarts the node | . | Shutdown | Powers the node down | . | Factory reset | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Панэль адладкі . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. О нас . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/be-rBY/user/settings-module-admin.html#administration",
"relUrl": "/be-rBY/user/settings-module-admin.html#administration"
@@ -31473,7 +31473,7 @@
},"4496": {
"doc": "Settings — Modules & Admin",
"title": "Amministrazione",
- "content": "Amministrazione Remota . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Imposta l’ora | Sends your phone’s clock to the node | . | Riavvia | Restarts the node | . | Spegni | Powers the node down | . | Ripristina impostazioni di fabbrica | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Ripristino . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avanzate . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Azzera il database dei nodi . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Pannello Di Debug . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Informazioni . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Ringraziamenti . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Amministrazione Remota . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Imposta l’ora | Sends your phone’s clock to the node | . | Riavvia | Restarts the node | . | Spegni | Powers the node down | . | Ripristina impostazioni di fabbrica | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Ripristino . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avanzate . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Azzera il database dei nodi . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Pannello Di Debug . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Informazioni . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Ringraziamenti . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/it-rIT/user/settings-module-admin.html#amministrazione",
"relUrl": "/it-rIT/user/settings-module-admin.html#amministrazione"
@@ -31508,7 +31508,7 @@
},"4501": {
"doc": "Settings — Modules & Admin",
"title": "Administración",
- "content": "Administración remota . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reiniciar | Restarts the node | . | Apagar | Powers the node down | . | Restablecer los valores de fábrica | Returns every setting to its factory default | . | Reinicio de NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Hacer copia de seguridad y restaurar . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avanzado . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Limpiar nodos de la base de datos . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panel de depuración . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Acerca de . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Agradecimientos . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Administración remota . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reiniciar | Restarts the node | . | Apagar | Powers the node down | . | Restablecer los valores de fábrica | Returns every setting to its factory default | . | Reinicio de NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Hacer copia de seguridad y restaurar . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avanzado . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Limpiar nodos de la base de datos . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panel de depuración . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Acerca de . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Agradecimientos . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/es-rES/user/settings-module-admin.html#administraci%C3%B3n",
"relUrl": "/es-rES/user/settings-module-admin.html#administración"
@@ -31543,7 +31543,7 @@
},"4506": {
"doc": "Settings — Modules & Admin",
"title": "Administracija",
- "content": "Administracija na daljavo . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Ponovni zagon | Restarts the node | . | Ugasni | Powers the node down | . | Povrnitev tovarniških nastavitev | Returns every setting to its factory default | . | Ponastavi NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Plošča za odpravljanje napak . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O programu . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Administracija na daljavo . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Ponovni zagon | Restarts the node | . | Ugasni | Powers the node down | . | Povrnitev tovarniških nastavitev | Returns every setting to its factory default | . | Ponastavi NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Plošča za odpravljanje napak . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O programu . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/sl-rSI/user/settings-module-admin.html#administracija",
"relUrl": "/sl-rSI/user/settings-module-admin.html#administracija"
@@ -31578,7 +31578,7 @@
},"4511": {
"doc": "Settings — Modules & Admin",
"title": "Administrasjon",
- "content": "Fjernadministrasjon . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Omstart | Restarts the node | . | Avslutt | Powers the node down | . | Tilbakestill til fabrikkstandard | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Feilsøkningspanel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Om . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Fjernadministrasjon . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Omstart | Restarts the node | . | Avslutt | Powers the node down | . | Tilbakestill til fabrikkstandard | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Feilsøkningspanel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Om . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/no-rNO/user/settings-module-admin.html#administrasjon",
"relUrl": "/no-rNO/user/settings-module-admin.html#administrasjon"
@@ -31613,7 +31613,7 @@
},"4516": {
"doc": "Settings — Modules & Admin",
"title": "Adminisztráció",
- "content": "Távoli Adminisztráció . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Újraindítás | Restarts the node | . | Leállítás | Powers the node down | . | Gyári beállítások visszaállítása | Returns every setting to its factory default | . | NodeDB törlése | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Biztonsági mentés és visszaállítás . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Haladó . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Csomópont-adatbázis tisztítása . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Hibakereső panel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. A programról . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Visszaigazolások (ACK-ek) . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Távoli Adminisztráció . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Újraindítás | Restarts the node | . | Leállítás | Powers the node down | . | Gyári beállítások visszaállítása | Returns every setting to its factory default | . | NodeDB törlése | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Biztonsági mentés és visszaállítás . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Haladó . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Csomópont-adatbázis tisztítása . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Hibakereső panel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. A programról . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Visszaigazolások (ACK-ek) . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/hu-rHU/user/settings-module-admin.html#adminisztr%C3%A1ci%C3%B3",
"relUrl": "/hu-rHU/user/settings-module-admin.html#adminisztráció"
@@ -31648,7 +31648,7 @@
},"4521": {
"doc": "Настройки — Модули и администрирование",
"title": "Администрирование",
- "content": "Удаленное администрирование . Удалённо настраивай ноды, которые используют твой ключ администрирования: . | Выбери целевую ноду в списке нод. | Перейди в Настройки этой ноды. | Измени конфигурацию. | Нажми Сохранить — изменения отправляются через сеть. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Действие | Что она делает | . | Установить время | Sends your phone’s clock to the node | . | Перезагрузка | Restarts the node | . | Выключение | Powers the node down | . | Сброс до заводских настроек | Returns every setting to its factory default | . | Очистка списка нод сети | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Бэкап & Восстановление . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Расширенные . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Очистить базу данных нод . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Панель отладки . Открывает вкладки Пакет и Журналы приложений для просмотра, фильтрации и экспорта диагностических выходов. См. Отладочные журналы для полного прохождения. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. О приложении . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Благодарности . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “Нет ответа от целевого узла” — цель может находиться вне диапазона, в автономном режиме или иметь несоответствующий ключ администратора. Проверьте соответствие ключа администратора на обоих узлах. | Изменения не применены — чтобы некоторые настройки вступили в силу, нужно перезагрузить устройство. Попробуй перезагрузить после сохранения. | Не видны настройки удалённой ноды — убедись, что твоя нода имеет админ-ключ для целевой ноды. Админ-канал настраивается автоматически, когда задан ключ администратора. | . ",
+ "content": "Удаленное администрирование . Удалённо настраивай ноды, которые используют твой ключ администрирования: . | Выбери целевую ноду в списке нод. | Перейди в Настройки этой ноды. | Измени конфигурацию. | Нажми Сохранить — изменения отправляются через сеть. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Действие | Что она делает | . | Установить время | Sends your phone’s clock to the node | . | Перезагрузка | Restarts the node | . | Выключение | Powers the node down | . | Сброс до заводских настроек | Returns every setting to its factory default | . | Очистка списка нод сети | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Бэкап & Восстановление . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Расширенные . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Очистить базу данных нод . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Панель отладки . Открывает вкладки Пакет и Журналы приложений для просмотра, фильтрации и экспорта диагностических выходов. См. Отладочные журналы для полного прохождения. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. О приложении . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Благодарности . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “Нет ответа от целевого узла” — цель может находиться вне диапазона, в автономном режиме или иметь несоответствующий ключ администратора. Проверьте соответствие ключа администратора на обоих узлах. | Изменения не применены — чтобы некоторые настройки вступили в силу, нужно перезагрузить устройство. Попробуй перезагрузить после сохранения. | Не видны настройки удалённой ноды — убедись, что твоя нода имеет админ-ключ для целевой ноды. Админ-канал настраивается автоматически, когда задан ключ администратора. | . ",
"url": "/Meshtastic-Android/main/ru-rRU/user/settings-module-admin.html#%D0%B0%D0%B4%D0%BC%D0%B8%D0%BD%D0%B8%D1%81%D1%82%D1%80%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5",
"relUrl": "/ru-rRU/user/settings-module-admin.html#администрирование"
@@ -31676,7 +31676,7 @@
},"4525": {
"doc": "Settings — Modules & Admin",
"title": "Administrace",
- "content": "Vzdálená administrace . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Nastavení času | Sends your phone’s clock to the node | . | Restartovat | Restarts the node | . | Vypnout | Powers the node down | . | Obnovení továrního nastavení | Returns every setting to its factory default | . | Reset NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Zálohování a obnovení . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Rozšířené . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Vyčistit databázi uzlů . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panel pro ladění . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O aplikaci . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Poděkování . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Vzdálená administrace . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Nastavení času | Sends your phone’s clock to the node | . | Restartovat | Restarts the node | . | Vypnout | Powers the node down | . | Obnovení továrního nastavení | Returns every setting to its factory default | . | Reset NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Zálohování a obnovení . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Rozšířené . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Vyčistit databázi uzlů . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panel pro ladění . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O aplikaci . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Poděkování . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/cs-rCZ/user/settings-module-admin.html#administrace",
"relUrl": "/cs-rCZ/user/settings-module-admin.html#administrace"
@@ -31711,7 +31711,7 @@
},"4530": {
"doc": "Settings — Modules & Admin",
"title": "Администриране",
- "content": "Отдалечено администриране . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Действие | Какво прави | . | Set time | Sends your phone’s clock to the node | . | Рестартиране | Restarts the node | . | Изключване | Powers the node down | . | Фабрично нулиране | Returns every setting to its factory default | . | Нулиране на базата данни с възли | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Архивиране & Възстановяване . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Разширени . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Почистване на базата данни с възлите . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Панел за отстраняване на грешки . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Мерни единици — метрични, имперски или според системата. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Относно . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Благодарности . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Отдалечено администриране . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Действие | Какво прави | . | Set time | Sends your phone’s clock to the node | . | Рестартиране | Restarts the node | . | Изключване | Powers the node down | . | Фабрично нулиране | Returns every setting to its factory default | . | Нулиране на базата данни с възли | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Архивиране & Възстановяване . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Разширени . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Почистване на базата данни с възлите . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Панел за отстраняване на грешки . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Мерни единици — метрични, имперски или според системата. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Относно . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Благодарности . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/bg-rBG/user/settings-module-admin.html#%D0%B0%D0%B4%D0%BC%D0%B8%D0%BD%D0%B8%D1%81%D1%82%D1%80%D0%B8%D1%80%D0%B0%D0%BD%D0%B5",
"relUrl": "/bg-rBG/user/settings-module-admin.html#администриране"
@@ -31746,7 +31746,7 @@
},"4535": {
"doc": "Settings — Modules & Admin",
"title": "Rialachas",
- "content": "Rialú iargúlta . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Athmhaoinigh | Restarts the node | . | Dún | Powers the node down | . | Athshocraigh an fhactaraí | Returns every setting to its factory default | . | Athshocraigh NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Painéal Laige . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Maidir le . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Rialú iargúlta . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Athmhaoinigh | Restarts the node | . | Dún | Powers the node down | . | Athshocraigh an fhactaraí | Returns every setting to its factory default | . | Athshocraigh NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Painéal Laige . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Maidir le . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/ga-rIE/user/settings-module-admin.html#rialachas",
"relUrl": "/ga-rIE/user/settings-module-admin.html#rialachas"
@@ -31781,7 +31781,7 @@
},"4540": {
"doc": "Settings — Modules & Admin",
"title": "Administration",
- "content": "Administration à distance . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Redémarrer | Restarts the node | . | Éteindre | Powers the node down | . | Réinitialisation d’usine | Returns every setting to its factory default | . | Reconfiguration de NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Sauvegarder & Restaurer . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avancé . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Nettoyer la base de données des nœuds . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panneau de débogage . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. A propros . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Remerciements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Administration à distance . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Redémarrer | Restarts the node | . | Éteindre | Powers the node down | . | Réinitialisation d’usine | Returns every setting to its factory default | . | Reconfiguration de NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Sauvegarder & Restaurer . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avancé . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Nettoyer la base de données des nœuds . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panneau de débogage . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. A propros . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Remerciements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/fr-rCA/user/settings-module-admin.html#administration",
"relUrl": "/fr-rCA/user/settings-module-admin.html#administration"
@@ -31816,7 +31816,7 @@
},"4545": {
"doc": "Settings — Modules & Admin",
"title": "Администрација",
- "content": "Удаљена администрација . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Поновно покретање | Restarts the node | . | Искључи | Powers the node down | . | Рестартовање на фабричка подешавања | Returns every setting to its factory default | . | Ресетовање базе чворова | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Напредно . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Панел за отклањање грешака . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. Подешавања апликације . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. О . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Удаљена администрација . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Поновно покретање | Restarts the node | . | Искључи | Powers the node down | . | Рестартовање на фабричка подешавања | Returns every setting to its factory default | . | Ресетовање базе чворова | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Напредно . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Панел за отклањање грешака . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. Подешавања апликације . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. О . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/srp/user/settings-module-admin.html#%D0%B0%D0%B4%D0%BC%D0%B8%D0%BD%D0%B8%D1%81%D1%82%D1%80%D0%B0%D1%86%D0%B8%D1%98%D0%B0",
"relUrl": "/srp/user/settings-module-admin.html#администрација"
@@ -31851,7 +31851,7 @@
},"4550": {
"doc": "Settings — Modules & Admin",
"title": "Administration",
- "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reiniciar | Restarts the node | . | Apagar | Powers the node down | . | Restauració dels paràmetres de fàbrica | Returns every setting to its factory default | . | Restablir NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panell de depuració . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Sobre . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reiniciar | Restarts the node | . | Apagar | Powers the node down | . | Restauració dels paràmetres de fàbrica | Returns every setting to its factory default | . | Restablir NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panell de depuració . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Sobre . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/ca-rES/user/settings-module-admin.html#administration",
"relUrl": "/ca-rES/user/settings-module-admin.html#administration"
@@ -31886,7 +31886,7 @@
},"4555": {
"doc": "Settings — Modules & Admin",
"title": "관리",
- "content": "원격 설정 . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | 재부팅 | Restarts the node | . | 종료 | Powers the node down | . | 공장초기화 | Returns every setting to its factory default | . | 노드 목록 리셋 | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. 백업 & 복구 . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. 고급 . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. 디버그 패널 . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. 앱에 대하여 . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "원격 설정 . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | 재부팅 | Restarts the node | . | 종료 | Powers the node down | . | 공장초기화 | Returns every setting to its factory default | . | 노드 목록 리셋 | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. 백업 & 복구 . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. 고급 . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. 디버그 패널 . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. 앱에 대하여 . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/ko-rKR/user/settings-module-admin.html#%EA%B4%80%EB%A6%AC",
"relUrl": "/ko-rKR/user/settings-module-admin.html#관리"
@@ -31921,7 +31921,7 @@
},"4560": {
"doc": "Settings — Modules & Admin",
"title": "Administration",
- "content": "Fjärradministration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Ställ in tid | Sends your phone’s clock to the node | . | Starta om | Restarts the node | . | Stäng av | Powers the node down | . | Återställ till standardinställningar | Returns every setting to its factory default | . | Nollställ NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Säkerhetskopiering och återställning . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advancerat . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Rensa noddatabas . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Felsökningspanel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Om . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Bekräftelser . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Fjärradministration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Ställ in tid | Sends your phone’s clock to the node | . | Starta om | Restarts the node | . | Stäng av | Powers the node down | . | Återställ till standardinställningar | Returns every setting to its factory default | . | Nollställ NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Säkerhetskopiering och återställning . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advancerat . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Rensa noddatabas . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Felsökningspanel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Om . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Bekräftelser . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/sv-rSE/user/settings-module-admin.html#administration",
"relUrl": "/sv-rSE/user/settings-module-admin.html#administration"
@@ -31956,7 +31956,7 @@
},"4565": {
"doc": "Settings — Modules & Admin",
"title": "Administrasyon",
- "content": "Administrasyon Remote . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Rekòmanse | Restarts the node | . | Fèmen | Powers the node down | . | Reyajiste nan faktori | Returns every setting to its factory default | . | Reyajiste NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panno Debug . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Sou . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Administrasyon Remote . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Rekòmanse | Restarts the node | . | Fèmen | Powers the node down | . | Reyajiste nan faktori | Returns every setting to its factory default | . | Reyajiste NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panno Debug . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Sou . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/ht-rHT/user/settings-module-admin.html#administrasyon",
"relUrl": "/ht-rHT/user/settings-module-admin.html#administrasyon"
@@ -31991,7 +31991,7 @@
},"4570": {
"doc": "Settings — Modules & Admin",
"title": "Administracija",
- "content": "Udaljena administracija . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Поново покрени | Restarts the node | . | Искључи | Powers the node down | . | Рестартовање на фабричка подешавања | Returns every setting to its factory default | . | Ресетовање базе чворова | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Напредно . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panel za otklanjanje grešaka . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. Подешавања апликације . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O nama . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Udaljena administracija . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Поново покрени | Restarts the node | . | Искључи | Powers the node down | . | Рестартовање на фабричка подешавања | Returns every setting to its factory default | . | Ресетовање базе чворова | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Напредно . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panel za otklanjanje grešaka . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. Подешавања апликације . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O nama . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/sr-rLatn/user/settings-module-admin.html#administracija",
"relUrl": "/sr-rLatn/user/settings-module-admin.html#administracija"
@@ -32026,7 +32026,7 @@
},"4575": {
"doc": "Settings — Modules & Admin",
"title": "Beheer",
- "content": "Extern beheer . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Herstart | Restarts the node | . | Zet uit | Powers the node down | . | Reset naar fabrieksinstellingen | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Back-up & Herstellen . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Debug-paneel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Over . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Extern beheer . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Herstart | Restarts the node | . | Zet uit | Powers the node down | . | Reset naar fabrieksinstellingen | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Back-up & Herstellen . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Debug-paneel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Over . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/nl-rNL/user/settings-module-admin.html#beheer",
"relUrl": "/nl-rNL/user/settings-module-admin.html#beheer"
@@ -32061,7 +32061,7 @@
},"4580": {
"doc": "Settings — Modules & Admin",
"title": "Адміністрування",
- "content": "Віддалене керування . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Встановити час | Sends your phone’s clock to the node | . | Перевантажити | Restarts the node | . | Вимкнути | Powers the node down | . | Скинути до заводських налаштувань | Returns every setting to its factory default | . | Очищення бази вузлів | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Резервна копія & Відновлення . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Розширені . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Очистити базу даних вузлів . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Панель налагодження . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Про . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Подяки . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Віддалене керування . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Встановити час | Sends your phone’s clock to the node | . | Перевантажити | Restarts the node | . | Вимкнути | Powers the node down | . | Скинути до заводських налаштувань | Returns every setting to its factory default | . | Очищення бази вузлів | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Резервна копія & Відновлення . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Розширені . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Очистити базу даних вузлів . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Панель налагодження . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Про . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Подяки . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/uk-rUA/user/settings-module-admin.html#%D0%B0%D0%B4%D0%BC%D1%96%D0%BD%D1%96%D1%81%D1%82%D1%80%D1%83%D0%B2%D0%B0%D0%BD%D0%BD%D1%8F",
"relUrl": "/uk-rUA/user/settings-module-admin.html#адміністрування"
@@ -32096,7 +32096,7 @@
},"4585": {
"doc": "Asetukset — Moduulit ja ylläpito",
"title": "Ylläpito",
- "content": "Etähallinta . Määritä etänä radiot, jotka jakavat saman ylläpitoavaimen: . | Valitse kohderadio radioluettelosta. | Siirry kyseisen radion Asetukset-kohtaan. | Muokkaa määrityksiä. | Napauta Tallenna — muutokset lähetetään verkon kautta. | . ⚠️ Tärkeää: Edellyttää, että järjestelmänvalvojan avain on määritetty sekä omassa radiossasi että kohderadiossa. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Toiminto | Mitä se tekee | . | Aseta aika | Sends your phone’s clock to the node | . | Käynnistä uudelleen | Restarts the node | . | Sammuta | Powers the node down | . | Palauta tehdasasetukset | Returns every setting to its factory default | . | Tyhjennä NodeDB-tietokanta | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Varmuuskopiointi ja palautus . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Lisäasetukset . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Tyhjennä NodeDB-tietokanta . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Vianetsintäpaneeli . Avaa Paketit- ja Sovelluslokit-välilehdet diagnostiikkatietojen tarkastelua, suodatusta ja vientiä varten. Katso Virheenjäljityslokit, jossa on täydellinen käyttöohje. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Tietoja . Settings → About carries the app’s own identity rather than the node’s: . Kolme osiota: . | Mikä on Meshtastic? – lyhyt kuvaus projektista. | Sovellukset — avaa Tarvitsetko laitteiston? -näkymän, jossa on suosittujen laitteiden karuselli ja linkit niiden ostopaikkoihin. Siellä näytetään myös GitHub-tietovarasto, käytössä oleva sovellusversio ja Tekijätiedot (katso seuraava osio). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Kiitokset . Tietoja-kohdasta avattava näkymä, jossa luetellaan kaikki sovelluksen käyttämät avoimen lähdekoodin kirjastot lisensseineen. Luettelo luodaan käännöshetkellä AboutLibraries-kirjastolla. Tätä kutsuttiin aiemmin lisenssinäkymäksi. Troubleshooting remote admin . | Ei vastausta kohderadiolta — kohderadio voi olla kuuluvuusalueen ulkopuolella, poissa verkosta tai siinä voi olla eri ylläpitoavain. Varmista, että ylläpitoavain on sama molemmissa radioissa. | Muutokset eivät tule voimaan — jotkin asetukset edellyttävät uudelleenkäynnistystä ennen kuin ne astuvat voimaan. Kokeile Uudelleenkäynnistystä tallennuksen jälkeen. | Et näe etäasetuksia — varmista, että radiossasi on kohderadion ylläpitoavain. Ylläpitokanava määritetään automaattisesti, kun ylläpitoavain on asetettu. | . ",
+ "content": "Etähallinta . Määritä etänä radiot, jotka jakavat saman ylläpitoavaimen: . | Valitse kohderadio radioluettelosta. | Siirry kyseisen radion Asetukset-kohtaan. | Muokkaa määrityksiä. | Napauta Tallenna — muutokset lähetetään verkon kautta. | . ⚠️ Tärkeää: Edellyttää, että järjestelmänvalvojan avain on määritetty sekä omassa radiossasi että kohderadiossa. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Toiminto | Mitä se tekee | . | Aseta aika | Sends your phone’s clock to the node | . | Käynnistä uudelleen | Restarts the node | . | Sammuta | Powers the node down | . | Palauta tehdasasetukset | Returns every setting to its factory default | . | Tyhjennä NodeDB-tietokanta | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Varmuuskopiointi ja palautus . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Lisäasetukset . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Tyhjennä NodeDB-tietokanta . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Vianetsintäpaneeli . Avaa Paketit- ja Sovelluslokit-välilehdet diagnostiikkatietojen tarkastelua, suodatusta ja vientiä varten. Katso Virheenjäljityslokit, jossa on täydellinen käyttöohje. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Tietoja . Settings → About carries the app’s own identity rather than the node’s: . Kolme osiota: . | Mikä on Meshtastic? – lyhyt kuvaus projektista. | Sovellukset — avaa Tarvitsetko laitteiston? -näkymän, jossa on suosittujen laitteiden karuselli ja linkit niiden ostopaikkoihin. Siellä näytetään myös GitHub-tietovarasto, käytössä oleva sovellusversio ja Tekijätiedot (katso seuraava osio). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Kiitokset . Tietoja-kohdasta avattava näkymä, jossa luetellaan kaikki sovelluksen käyttämät avoimen lähdekoodin kirjastot lisensseineen. Luettelo luodaan käännöshetkellä AboutLibraries-kirjastolla. Tätä kutsuttiin aiemmin lisenssinäkymäksi. Troubleshooting remote admin . | Ei vastausta kohderadiolta — kohderadio voi olla kuuluvuusalueen ulkopuolella, poissa verkosta tai siinä voi olla eri ylläpitoavain. Varmista, että ylläpitoavain on sama molemmissa radioissa. | Muutokset eivät tule voimaan — jotkin asetukset edellyttävät uudelleenkäynnistystä ennen kuin ne astuvat voimaan. Kokeile Uudelleenkäynnistystä tallennuksen jälkeen. | Et näe etäasetuksia — varmista, että radiossasi on kohderadion ylläpitoavain. Ylläpitokanava määritetään automaattisesti, kun ylläpitoavain on asetettu. | . ",
"url": "/Meshtastic-Android/main/fi-rFI/user/settings-module-admin.html#yll%C3%A4pito",
"relUrl": "/fi-rFI/user/settings-module-admin.html#ylläpito"
@@ -32124,7 +32124,7 @@
},"4589": {
"doc": "Settings — Modules & Admin",
"title": "Administration",
- "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Endurræsa | Restarts the node | . | Slökkva | Powers the node down | . | Grunnstilla | Returns every setting to its factory default | . | Endurræsa NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Villuleitarborð . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Um smáforrit . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Endurræsa | Restarts the node | . | Slökkva | Powers the node down | . | Grunnstilla | Returns every setting to its factory default | . | Endurræsa NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Villuleitarborð . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Um smáforrit . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/is-rIS/user/settings-module-admin.html#administration",
"relUrl": "/is-rIS/user/settings-module-admin.html#administration"
@@ -32159,7 +32159,7 @@
},"4594": {
"doc": "Settings — Modules & Admin",
"title": "Administravimas",
- "content": "Nuotolinis administravimas . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Perkrauti | Restarts the node | . | Išjungti | Powers the node down | . | Gamyklinis atstatymas | Returns every setting to its factory default | . | NodeDB perkrauti | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Derinimo skydelis . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Apie . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Nuotolinis administravimas . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Perkrauti | Restarts the node | . | Išjungti | Powers the node down | . | Gamyklinis atstatymas | Returns every setting to its factory default | . | NodeDB perkrauti | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Derinimo skydelis . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Apie . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/lt-rLT/user/settings-module-admin.html#administravimas",
"relUrl": "/lt-rLT/user/settings-module-admin.html#administravimas"
@@ -32194,7 +32194,7 @@
},"4599": {
"doc": "Settings — Modules & Admin",
"title": "Administration",
- "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reiniciar | Restarts the node | . | Apagar | Powers the node down | . | Restablecemento de fábrica | Returns every setting to its factory default | . | Restablecer NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panel de depuración . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Acerca de . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reiniciar | Restarts the node | . | Apagar | Powers the node down | . | Restablecemento de fábrica | Returns every setting to its factory default | . | Restablecer NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panel de depuración . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Acerca de . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/gl-rES/user/settings-module-admin.html#administration",
"relUrl": "/gl-rES/user/settings-module-admin.html#administration"
@@ -32229,7 +32229,7 @@
},"4604": {
"doc": "設定：モジュールと管理",
"title": "管理",
- "content": "リモート管理 . 管理者鍵を共有しているノードをリモートで設定します： . | ノードリストで対象のノードを選択します。 | そのノードの「設定」に移動します。 | 設定を変更します。 | 「保存」をタップします。変更がメッシュ経由で送信されます。 | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | 操作 | 内容 | . | 時刻を設定 | Sends your phone’s clock to the node | . | 再起動 | Restarts the node | . | シャットダウン | Powers the node down | . | 出荷時にリセット | Returns every setting to its factory default | . | NodeDBをリセット | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. バックアップと復元 . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. 詳細設定 . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. ノードデータベースの整理 . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. デバッグ . 診断出力の表示・絞り込み・エクスポートを行う「パケット」タブと「アプリログ」タブを開きます。詳しい手順は、デバッグログ を参照してください。 . App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. 概要 . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. 謝辞 . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | 「対象ノードから応答がありません」：対象が圏外、オフライン、または管理者鍵が一致していない可能性があります。両方のノードで管理者鍵が一致しているか確認してください。 | 変更が適用されない：一部の設定は、反映に再起動が必要です。保存後に「再起動」を実行してみてください。 | リモートの設定が表示されない：自分のノードに、対象ノードの管理者鍵があることを確認してください。管理チャンネルは、管理者鍵を設定すると自動的に構成されます。 | . ",
+ "content": "リモート管理 . 管理者鍵を共有しているノードをリモートで設定します： . | ノードリストで対象のノードを選択します。 | そのノードの「設定」に移動します。 | 設定を変更します。 | 「保存」をタップします。変更がメッシュ経由で送信されます。 | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | 操作 | 内容 | . | 時刻を設定 | Sends your phone’s clock to the node | . | 再起動 | Restarts the node | . | シャットダウン | Powers the node down | . | 出荷時にリセット | Returns every setting to its factory default | . | NodeDBをリセット | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. バックアップと復元 . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. 詳細設定 . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. ノードデータベースの整理 . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. デバッグ . 診断出力の表示・絞り込み・エクスポートを行う「パケット」タブと「アプリログ」タブを開きます。詳しい手順は、デバッグログ を参照してください。 . App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. 概要 . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. 謝辞 . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | 「対象ノードから応答がありません」：対象が圏外、オフライン、または管理者鍵が一致していない可能性があります。両方のノードで管理者鍵が一致しているか確認してください。 | 変更が適用されない：一部の設定は、反映に再起動が必要です。保存後に「再起動」を実行してみてください。 | リモートの設定が表示されない：自分のノードに、対象ノードの管理者鍵があることを確認してください。管理チャンネルは、管理者鍵を設定すると自動的に構成されます。 | . ",
"url": "/Meshtastic-Android/main/ja-rJP/user/settings-module-admin.html#%E7%AE%A1%E7%90%86",
"relUrl": "/ja-rJP/user/settings-module-admin.html#管理"
@@ -32257,7 +32257,7 @@
},"4608": {
"doc": "Settings — Modules & Admin",
"title": "Einstellung",
- "content": "Ferneinstellung . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Neustart | Restarts the node | . | Herunterfahren | Powers the node down | . | Auf Werkseinstellungen zurücksetzen | Returns every setting to its factory default | . | Node-Datenbank zurücksetzen | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Sichern & Wiederherstellen . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Fortgeschritten . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Knotendatenbank leeren . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Debug-Ausgaben . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Einstellungen . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Über . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Danksagungen . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Ferneinstellung . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Neustart | Restarts the node | . | Herunterfahren | Powers the node down | . | Auf Werkseinstellungen zurücksetzen | Returns every setting to its factory default | . | Node-Datenbank zurücksetzen | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Sichern & Wiederherstellen . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Fortgeschritten . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Knotendatenbank leeren . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Debug-Ausgaben . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Einstellungen . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Über . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Danksagungen . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/de-rDE/user/settings-module-admin.html#einstellung",
"relUrl": "/de-rDE/user/settings-module-admin.html#einstellung"
@@ -32292,7 +32292,7 @@
},"4613": {
"doc": "Settings — Modules & Admin",
"title": "الإدارة",
- "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | إعادة التشغيل | Restarts the node | . | Shutdown | Powers the node down | . | Factory reset | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Debug Panel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. حول . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | إعادة التشغيل | Restarts the node | . | Shutdown | Powers the node down | . | Factory reset | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Debug Panel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. حول . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/ar-rSA/user/settings-module-admin.html#%D8%A7%D9%84%D8%A5%D8%AF%D8%A7%D8%B1%D8%A9",
"relUrl": "/ar-rSA/user/settings-module-admin.html#الإدارة"
@@ -32327,7 +32327,7 @@
},"4618": {
"doc": "Settings — Modules & Admin",
"title": "Administration",
- "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Ponovno pokreni | Restarts the node | . | Isključi | Powers the node down | . | Vraćanje na tvorničke postavke | Returns every setting to its factory default | . | Resetiraj NodeDB bazu | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Otklanjanje pogrešaka . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O programu . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Ponovno pokreni | Restarts the node | . | Isključi | Powers the node down | . | Vraćanje na tvorničke postavke | Returns every setting to its factory default | . | Resetiraj NodeDB bazu | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Otklanjanje pogrešaka . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O programu . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/hr-rHR/user/settings-module-admin.html#administration",
"relUrl": "/hr-rHR/user/settings-module-admin.html#administration"
@@ -32362,7 +32362,7 @@
},"4623": {
"doc": "Settings — Modules & Admin",
"title": "Administração",
- "content": "Administração Remota . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reiniciar | Restarts the node | . | Desligar | Powers the node down | . | Redefinição de fábrica | Returns every setting to its factory default | . | Redefinir NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restauro . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Painel de depuração . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Sobre . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Administração Remota . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reiniciar | Restarts the node | . | Desligar | Powers the node down | . | Redefinição de fábrica | Returns every setting to its factory default | . | Redefinir NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restauro . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Painel de depuração . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Sobre . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/pt-rPT/user/settings-module-admin.html#administra%C3%A7%C3%A3o",
"relUrl": "/pt-rPT/user/settings-module-admin.html#administração"
@@ -32397,7 +32397,7 @@
},"4628": {
"doc": "Settings — Modules & Admin",
"title": "Zarządzanie",
- "content": "Zdalne zarządzanie . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Uruchom ponownie | Restarts the node | . | Wyłącz | Powers the node down | . | Ustawienia fabryczne | Returns every setting to its factory default | . | Zresetuj NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Kopia zapasowa i przywracanie . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Zaawansowane . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Wyczyść bazę węzłów . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panel debugowania . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O aplikacji . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Potwierdzenia . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Zdalne zarządzanie . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Uruchom ponownie | Restarts the node | . | Wyłącz | Powers the node down | . | Ustawienia fabryczne | Returns every setting to its factory default | . | Zresetuj NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Kopia zapasowa i przywracanie . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Zaawansowane . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Wyczyść bazę węzłów . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panel debugowania . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O aplikacji . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Potwierdzenia . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/pl-rPL/user/settings-module-admin.html#zarz%C4%85dzanie",
"relUrl": "/pl-rPL/user/settings-module-admin.html#zarządzanie"
@@ -32432,7 +32432,7 @@
},"4633": {
"doc": "Settings — Modules & Admin",
"title": "管理员",
- "content": "远程管理 . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | 设置时间 | Sends your phone’s clock to the node | . | 重启 | Restarts the node | . | 关机 | Powers the node down | . | 恢复出厂设置 | Returns every setting to its factory default | . | 重置节点数据库 | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. 备份与恢复 . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. 高级 . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. 清理节点数据库 . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. 调试面板 . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App 设置 . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. 关于 . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. 开源 . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "远程管理 . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | 设置时间 | Sends your phone’s clock to the node | . | 重启 | Restarts the node | . | 关机 | Powers the node down | . | 恢复出厂设置 | Returns every setting to its factory default | . | 重置节点数据库 | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. 备份与恢复 . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. 高级 . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. 清理节点数据库 . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. 调试面板 . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App 设置 . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. 关于 . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. 开源 . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/zh-rCN/user/settings-module-admin.html#%E7%AE%A1%E7%90%86%E5%91%98",
"relUrl": "/zh-rCN/user/settings-module-admin.html#管理员"
@@ -32467,7 +32467,7 @@
},"4638": {
"doc": "Settings — Modules & Admin",
"title": "Administratë",
- "content": "Administratë e Largët . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Rindiz | Restarts the node | . | Fik | Powers the node down | . | Përditësim i fabrikës | Returns every setting to its factory default | . | Përditësimi i NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Paneli i debug-ut . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Rreth . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Administratë e Largët . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Rindiz | Restarts the node | . | Fik | Powers the node down | . | Përditësim i fabrikës | Returns every setting to its factory default | . | Përditësimi i NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Paneli i debug-ut . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Rreth . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/sq-rAL/user/settings-module-admin.html#administrat%C3%AB",
"relUrl": "/sq-rAL/user/settings-module-admin.html#administratë"
@@ -32502,7 +32502,7 @@
},"4643": {
"doc": "Settings — Modules & Admin",
"title": "管理",
- "content": "遠端管理 . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | 動作 | What it does | . | Set time | Sends your phone’s clock to the node | . | 重新開機 | Restarts the node | . | 關機 | Powers the node down | . | 恢復出廠設置 | Returns every setting to its factory default | . | 重設節點資料庫 | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. 備份與還原 . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. 進階 . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. 清除節點資料庫 . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. 偵錯面板 . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings 應用程式設定 . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. About（關於） . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. 致謝 . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "遠端管理 . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | 動作 | What it does | . | Set time | Sends your phone’s clock to the node | . | 重新開機 | Restarts the node | . | 關機 | Powers the node down | . | 恢復出廠設置 | Returns every setting to its factory default | . | 重設節點資料庫 | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. 備份與還原 . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. 進階 . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. 清除節點資料庫 . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. 偵錯面板 . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings 應用程式設定 . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. About（關於） . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. 致謝 . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/zh-rTW/user/settings-module-admin.html#%E7%AE%A1%E7%90%86",
"relUrl": "/zh-rTW/user/settings-module-admin.html#管理"
@@ -32537,7 +32537,7 @@
},"4648": {
"doc": "Sätted - moodulid & admin",
"title": "Haldus",
- "content": "Kaughaldus . Administraatori võtit jagavate sõlmede kaugkonfigureerimine: . | Vali sõlmede loendist sihtsõlm. | Mine selle sõlme Seadetesse. | Muuda seadistust. | Puuduta Salvesta – muudatused saadetakse kärgvõrgu kaudu. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Määra aeg | Sends your phone’s clock to the node | . | Taaskäivita | Restarts the node | . | Lülita välja | Powers the node down | . | Tehasesätted | Returns every setting to its factory default | . | NodeDB lähtestamine | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Varunda ja taasta . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Täpsem . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Tühjenda sõlmede andmebaas . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Arendaja paneel . Avab vahekaardid Paketid ja Rakenduse logid diagnostilise väljundi vaatamiseks, filtreerimiseks ja eksportimiseks. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Teave . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Tänusõnad . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “Sihtsõlmelt ei ole vastust” — sihtsõlm võib olla leviulatusest väljas, võrguühenduseta või sellel võib olla sobimatu administraatori võti. Veendu, et administraatori võti sobiks mõlemas sõlmele. | Muudatused ei rakendu — mõnede sätete jõustumiseks on vaja taaskäivitada. Pärast salvestamist proovi taaskäivitust. | Ei näe kaugseadeid — veendu, et sõlmel oleks sihtsõlme administraatori võti ja et administraatori kanal oleks turbekonfiguratsioonis lubatud. Administraatori kanal seadistatakse automaatselt, kui administraatori võti on määratud. | . ",
+ "content": "Kaughaldus . Administraatori võtit jagavate sõlmede kaugkonfigureerimine: . | Vali sõlmede loendist sihtsõlm. | Mine selle sõlme Seadetesse. | Muuda seadistust. | Puuduta Salvesta – muudatused saadetakse kärgvõrgu kaudu. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Määra aeg | Sends your phone’s clock to the node | . | Taaskäivita | Restarts the node | . | Lülita välja | Powers the node down | . | Tehasesätted | Returns every setting to its factory default | . | NodeDB lähtestamine | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Varunda ja taasta . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Täpsem . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Tühjenda sõlmede andmebaas . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Arendaja paneel . Avab vahekaardid Paketid ja Rakenduse logid diagnostilise väljundi vaatamiseks, filtreerimiseks ja eksportimiseks. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Teave . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Tänusõnad . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “Sihtsõlmelt ei ole vastust” — sihtsõlm võib olla leviulatusest väljas, võrguühenduseta või sellel võib olla sobimatu administraatori võti. Veendu, et administraatori võti sobiks mõlemas sõlmele. | Muudatused ei rakendu — mõnede sätete jõustumiseks on vaja taaskäivitada. Pärast salvestamist proovi taaskäivitust. | Ei näe kaugseadeid — veendu, et sõlmel oleks sihtsõlme administraatori võti ja et administraatori kanal oleks turbekonfiguratsioonis lubatud. Administraatori kanal seadistatakse automaatselt, kui administraatori võti on määratud. | . ",
"url": "/Meshtastic-Android/main/et-rEE/user/settings-module-admin.html#haldus",
"relUrl": "/et-rEE/user/settings-module-admin.html#haldus"
@@ -32572,7 +32572,7 @@
},"4653": {
"doc": "Settings — Modules & Admin",
"title": "Administration",
- "content": "Administration à distance . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Redémarrer | Restarts the node | . | Éteindre | Powers the node down | . | Réinitialisation d’usine | Returns every setting to its factory default | . | Reconfiguration de NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Sauvegarder & Restaurer . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avancé . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Nettoyer la base de données des nœuds . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panneau de débogage . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. A propros . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Remerciements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Administration à distance . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Redémarrer | Restarts the node | . | Éteindre | Powers the node down | . | Réinitialisation d’usine | Returns every setting to its factory default | . | Reconfiguration de NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Sauvegarder & Restaurer . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avancé . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Nettoyer la base de données des nœuds . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panneau de débogage . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. A propros . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Remerciements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/fr-rFR/user/settings-module-admin.html#administration",
"relUrl": "/fr-rFR/user/settings-module-admin.html#administration"
@@ -32607,7 +32607,7 @@
},"4658": {
"doc": "Settings — Modules & Admin",
"title": "Yönetim",
- "content": "Uzaktan Yönetim . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Yeniden başlat | Restarts the node | . | Kapat | Powers the node down | . | Fabrika ayarları | Returns every setting to its factory default | . | NodeDB sıfırla | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Yedekleme & Geri yükleme . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Gelişmiş . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Hata Ayıklama Paneli . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Hakkında . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Uzaktan Yönetim . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Yeniden başlat | Restarts the node | . | Kapat | Powers the node down | . | Fabrika ayarları | Returns every setting to its factory default | . | NodeDB sıfırla | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Yedekleme & Geri yükleme . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Gelişmiş . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Hata Ayıklama Paneli . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Hakkında . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/tr-rTR/user/settings-module-admin.html#y%C3%B6netim",
"relUrl": "/tr-rTR/user/settings-module-admin.html#yönetim"
@@ -32642,7 +32642,7 @@
},"4663": {
"doc": "Settings — Modules & Admin",
"title": "Διαχείριση",
- "content": "Απομακρυσμένη Διαχείριση . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Επανεκκίνηση | Restarts the node | . | Τερματισμός λειτουργίας | Powers the node down | . | Επαναφορά εργοστασιακών ρυθμίσεων | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Πίνακας αποσφαλμάτωσης . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Σχετικά . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Απομακρυσμένη Διαχείριση . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Επανεκκίνηση | Restarts the node | . | Τερματισμός λειτουργίας | Powers the node down | . | Επαναφορά εργοστασιακών ρυθμίσεων | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Πίνακας αποσφαλμάτωσης . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Σχετικά . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/el-rGR/user/settings-module-admin.html#%CE%B4%CE%B9%CE%B1%CF%87%CE%B5%CE%AF%CF%81%CE%B9%CF%83%CE%B7",
"relUrl": "/el-rGR/user/settings-module-admin.html#διαχείριση"
@@ -32677,7 +32677,7 @@
},"4668": {
"doc": "Settings — Modules & Admin",
"title": "Administrare",
- "content": "Administrare la distanță . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Restartează | Restarts the node | . | Oprire | Powers the node down | . | Resetare la setările din fabrică | Returns every setting to its factory default | . | Resetare NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Copie de rezervă și restaurare . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avansate . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Curăță baza de date a nodurilor . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panou de depanare . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Despre . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Mulțumiri . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Administrare la distanță . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Restartează | Restarts the node | . | Oprire | Powers the node down | . | Resetare la setările din fabrică | Returns every setting to its factory default | . | Resetare NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Copie de rezervă și restaurare . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avansate . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Curăță baza de date a nodurilor . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panou de depanare . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Despre . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Mulțumiri . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/ro-rRO/user/settings-module-admin.html#administrare",
"relUrl": "/ro-rRO/user/settings-module-admin.html#administrare"
@@ -32712,7 +32712,7 @@
},"4673": {
"doc": "Settings — Modules & Admin",
"title": "Administration",
- "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | אתחול מחדש | Restarts the node | . | כיבוי | Powers the node down | . | איפוס להגדרות היצרן | Returns every setting to its factory default | . | איפוס NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. פאנל דיבאג . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. אודות . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | אתחול מחדש | Restarts the node | . | כיבוי | Powers the node down | . | איפוס להגדרות היצרן | Returns every setting to its factory default | . | איפוס NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. פאנל דיבאג . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. אודות . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/iw-rIL/user/settings-module-admin.html#administration",
"relUrl": "/iw-rIL/user/settings-module-admin.html#administration"
@@ -32747,7 +32747,7 @@
},"4678": {
"doc": "Settings — Modules & Admin",
"title": "Administração",
- "content": "Administração Remota . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reiniciar | Restarts the node | . | Desligar | Powers the node down | . | Redefinição de fábrica | Returns every setting to its factory default | . | Redefinir NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup e Restaurar . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avançado . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Limpar Banco de Dados de Nó . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Painel de depuração . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Sobre . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Agradecimentos . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
+ "content": "Administração Remota . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reiniciar | Restarts the node | . | Desligar | Powers the node down | . | Redefinição de fábrica | Returns every setting to its factory default | . | Redefinir NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup e Restaurar . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avançado . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Limpar Banco de Dados de Nó . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Painel de depuração . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Sobre . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Agradecimentos . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
"url": "/Meshtastic-Android/main/pt-rBR/user/settings-module-admin.html#administra%C3%A7%C3%A3o",
"relUrl": "/pt-rBR/user/settings-module-admin.html#administração"
diff --git a/main/be-rBY/user/debug-logs.html b/main/be-rBY/user/debug-logs.html
index 2dbde9c566..2576676eb5 100644
--- a/main/be-rBY/user/debug-logs.html
+++ b/main/be-rBY/user/debug-logs.html
@@ -1 +1 @@
- Debug Logs | Meshtastic AndroidSkip to main content
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
Connections — if the problem is getting connected to your radio in the first place
diff --git a/main/be-rBY/user/onboarding.html b/main/be-rBY/user/onboarding.html
index 6eafb95c47..6f63cb6a6c 100644
--- a/main/be-rBY/user/onboarding.html
+++ b/main/be-rBY/user/onboarding.html
@@ -1 +1 @@
- Начало работы | Meshtastic AndroidSkip to main content
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Module configuration
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Апісанне
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Імя карыстальніка
Authentication username
Пароль
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Апісанне
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Апісанне
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Скончыўся час чакання
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Апісанне
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Апісанне
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Сервер
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Апісанне
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Апісанне
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Апісанне
Canned message enabled
⚠️ Deprecated in the protobuf schema
Паведамленні
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Апісанне
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Апісанне
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Апісанне
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Апісанне
LED state
Turn the LED on or off
3
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Апісанне
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Апісанне
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Remote Administration
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Перазагрузіць
Restarts the node
Shutdown
Powers the node down
Factory reset
Returns every setting to its factory default
NodeDB reset
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Панэль адладкі
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
О нас
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Module configuration
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Апісанне
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Імя карыстальніка
Authentication username
Пароль
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Апісанне
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Апісанне
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Скончыўся час чакання
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Апісанне
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Апісанне
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Сервер
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Апісанне
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Апісанне
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Апісанне
Canned message enabled
⚠️ Deprecated in the protobuf schema
Паведамленні
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Апісанне
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Апісанне
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Апісанне
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Апісанне
LED state
Turn the LED on or off
3
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Апісанне
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Апісанне
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Remote Administration
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Перазагрузіць
Restarts the node
Shutdown
Powers the node down
Factory reset
Returns every setting to its factory default
NodeDB reset
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Панэль адладкі
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
О нас
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Комуникирайте извън мрежата с вашите приятели и общността без клетъчна услуга.
Create Your Own Networks
Настройте лесно частни mesh мрежи за сигурна и надеждна комуникация в отдалечени райони.
Track and Share Locations
Споделяйте местоположението си в реално време и координирайте групата си с вградени GPS функции.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
Състояние
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Комуникирайте извън мрежата с вашите приятели и общността без клетъчна услуга.
Create Your Own Networks
Настройте лесно частни mesh мрежи за сигурна и надеждна комуникация в отдалечени райони.
Track and Share Locations
Споделяйте местоположението си в реално време и координирайте групата си с вградени GPS функции.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
Състояние
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Конфигуриране на модулите
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Настройка
Описание
MQTT е активиран
Toggle MQTT bridge
Адрес
MQTT broker address
Потребителско име
Authentication username
Парола
Authentication password
Криптирането е активирано
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS е активиран
Use secure connection
Root topic
Base MQTT topic path
Прокси към клиент е активиран
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Настройка
Описание
Съгласен съм.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Настройка
Описание
Серийната връзка е активирана
Activate serial communication
Echo е активирано
Echo received serial data back
Сериен режим
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Серийна скорост на предаване
Port speed
Timeout
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Настройка
Описание
Външните известия са активирани
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Използване на PWM зумер
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Тон на звънене
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Настройка
Описание
Съхраняване & препращане е активиран
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Брой записи
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Сървър
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Настройка
Описание
Тест на обхвата е активиран
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Запазване на .CSV в хранилище (само за ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Настройка
Описание
Изпращане на телеметрия на устройството
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Интервал на актуализиране на показателите на устройството
How often to report battery, uptime and channel utilization
Модулът за измерване на околната среда е активиран
Report the attached environment sensors
Интервал на актуализиране на показателите за средата
How often to report them
Показателите на околната среда на екрана са активирани
Also show these readings on the device’s own display
Показателите на околната среда използват Фаренхайт
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Модулът за показатели за качеството на въздуха е активиран
Report particulate and CO₂ sensor data
Интервал на актуализиране на показателите за качеството на въздуха
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Настройка
Описание
Canned message enabled
⚠️ Deprecated in the protobuf schema
Съобщения
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Ротационен енкодер #1 е активиран
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Настройка
Описание
CODEC 2 е активиран
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
Пин за РТТ
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Настройка
Описание
Отдалечен хардуер е активиран
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Налични пинове
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Настройка
Описание
Neighbor Info enabled
Activate neighbor broadcasting
Интервал на актуализиране
How often to broadcast neighbor list
Предаване през LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Настройка
Описание
LED за състояние
Turn the LED on or off
Текущ
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Настройка
Описание
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Използване на режим INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Приятелско име
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Настройка
Описание
Paxcounter е активиран
Activate people counting
Интервал на актуализиране
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Администриране
Отдалечено администриране
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Действие
Какво прави
Set time
Sends your phone’s clock to the node
Рестартиране
Restarts the node
Изключване
Powers the node down
Фабрично нулиране
Returns every setting to its factory default
Нулиране на базата данни с възли
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Архивиране & Възстановяване
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Разширени
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Почистване на базата данни с възлите
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Панел за отстраняване на грешки
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Мерни единици — метрични, имперски или според системата. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Относно
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Благодарности
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Конфигуриране на модулите
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Настройка
Описание
MQTT е активиран
Toggle MQTT bridge
Адрес
MQTT broker address
Потребителско име
Authentication username
Парола
Authentication password
Криптирането е активирано
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS е активиран
Use secure connection
Root topic
Base MQTT topic path
Прокси към клиент е активиран
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Настройка
Описание
Съгласен съм.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Настройка
Описание
Серийната връзка е активирана
Activate serial communication
Echo е активирано
Echo received serial data back
Сериен режим
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Серийна скорост на предаване
Port speed
Timeout
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Настройка
Описание
Външните известия са активирани
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Използване на PWM зумер
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Тон на звънене
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Настройка
Описание
Съхраняване & препращане е активиран
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Брой записи
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Сървър
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Настройка
Описание
Тест на обхвата е активиран
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Запазване на .CSV в хранилище (само за ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Настройка
Описание
Изпращане на телеметрия на устройството
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Интервал на актуализиране на показателите на устройството
How often to report battery, uptime and channel utilization
Модулът за измерване на околната среда е активиран
Report the attached environment sensors
Интервал на актуализиране на показателите за средата
How often to report them
Показателите на околната среда на екрана са активирани
Also show these readings on the device’s own display
Показателите на околната среда използват Фаренхайт
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Модулът за показатели за качеството на въздуха е активиран
Report particulate and CO₂ sensor data
Интервал на актуализиране на показателите за качеството на въздуха
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Настройка
Описание
Canned message enabled
⚠️ Deprecated in the protobuf schema
Съобщения
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Ротационен енкодер #1 е активиран
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Настройка
Описание
CODEC 2 е активиран
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
Пин за РТТ
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Настройка
Описание
Отдалечен хардуер е активиран
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Налични пинове
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Настройка
Описание
Neighbor Info enabled
Activate neighbor broadcasting
Интервал на актуализиране
How often to broadcast neighbor list
Предаване през LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Настройка
Описание
LED за състояние
Turn the LED on or off
Текущ
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Настройка
Описание
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Използване на режим INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Приятелско име
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Настройка
Описание
Paxcounter е активиран
Activate people counting
Интервал на актуализиране
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Администриране
Отдалечено администриране
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Действие
Какво прави
Set time
Sends your phone’s clock to the node
Рестартиране
Restarts the node
Изключване
Powers the node down
Фабрично нулиране
Returns every setting to its factory default
Нулиране на базата данни с възли
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Архивиране & Възстановяване
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Разширени
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Почистване на базата данни с възлите
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Панел за отстраняване на грешки
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Мерни единици — метрични, имперски или според системата. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Относно
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Благодарности
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Configuració de mòdul
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Descripció
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Descripció
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Descripció
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Temps esgotat
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Descripció
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Descripció
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Descripció
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Descripció
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Descripció
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Descripció
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Descripció
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Descripció
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Descripció
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Descripció
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Descripció
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Remote Administration
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Reiniciar
Restarts the node
Apagar
Powers the node down
Restauració dels paràmetres de fàbrica
Returns every setting to its factory default
Restablir NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panell de depuració
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Sobre
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Configuració de mòdul
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Descripció
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Descripció
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Descripció
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Temps esgotat
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Descripció
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Descripció
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Descripció
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Descripció
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Descripció
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Descripció
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Descripció
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Descripció
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Descripció
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Descripció
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Descripció
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Remote Administration
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Reiniciar
Restarts the node
Apagar
Powers the node down
Restauració dels paràmetres de fàbrica
Returns every setting to its factory default
Restablir NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panell de depuració
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Sobre
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Komunikujte off-the-grid s přáteli a komunitou bez mobilních služeb.
Create Your Own Networks
Jednoduché nastavení soukromých mesh sítí pro bezpečnou a spolehlivou komunikaci i v odlehlých místech.
Track and Share Locations
Sdílejte svou polohu v reálném čase a udržujte svou skupinu koordinovanou díky integrovaným funkcím GPS.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Komunikujte off-the-grid s přáteli a komunitou bez mobilních služeb.
Create Your Own Networks
Jednoduché nastavení soukromých mesh sítí pro bezpečnou a spolehlivou komunikaci i v odlehlých místech.
Track and Share Locations
Sdílejte svou polohu v reálném čase a udržujte svou skupinu koordinovanou díky integrovaným funkcím GPS.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Nastavení modulů
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Nastavení
Popis
MQTT povoleno
Toggle MQTT bridge
Adresa
MQTT broker address
Uživatelské jméno
Authentication username
Heslo
Authentication password
Šifrování povoleno
Encrypt MQTT payloads
JSON výstup povolen
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS povoleno
Use secure connection
Kořenové téma
Base MQTT topic path
Proxy na klienta povoleno
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Hlášení mapy
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Nastavení
Popis
Souhlasím.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Nastavení
Popis
Sériová komunikace povolena
Activate serial communication
Povolit echo
Echo received serial data back
Sériový režim
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Rychlost sériového přenosu
Port speed
Vypršel čas spojení
How long to wait before considering an incoming message complete
Přepsat sériový port komunikace
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Nastavení
Popis
Externí oznámení povoleno
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Výstupní LED (GPIO)
Pin the LED is wired to
Výstupní LED aktivní při HIGH
Whether the LED pin is active high or low
Výstupní pin bzučáku (GPIO)
Pin the buzzer is wired to
Výstupní pin vybračního motorku (GPIO)
Pin the vibration motor is wired to
Použít PWM bzučák
Drive the buzzer with PWM, which allows tones rather than a single pitch
Použít I2S jako bzučák
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Vyzváněcí tón
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Nastavení
Popis
Uložit a přeposlat povoleno
Activate store and forward
Pulzující LED
Periodically announce this node’s store-and-forward capability
Počet záznamů
Maximum stored messages
Max. počet záznamů historie
Max messages to replay
Časové okno historie
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Nastavení
Popis
Test pokrytí povolen
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Uložit .CSV do úložiště (pouze ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Nastavení
Popis
Odesílat telemetrii zařízení
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Interval aktualizace metrik zařízení
How often to report battery, uptime and channel utilization
Modul měření životního prostředí povolen
Report the attached environment sensors
Interval aktualizace měření životního prostředí
How often to report them
Zobrazení měření životního prostředí povoleno
Also show these readings on the device’s own display
Měření životního prostředí používá Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Modul měření kvality ovzduší povolen
Report particulate and CO₂ sensor data
Interval aktualizace měření kvality ovzduší
How often to report them
Modul měření spotřeby povolen
Report the per-channel voltage and current readings
Interval aktualizace měření napájení
How often to report them
Měření spotřeby na obrazovce povoleno
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Nastavení
Popis
Canned message enabled
⚠️ Deprecated in the protobuf schema
Zprávy
Newline-separated list of messages
Odeslat zvonek
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotační enkodér #1 povolen
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Vstup Nahoru/Dolů/Výběr povolen
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Nastavení
Popis
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S výběr slov
GPIO pin for I2S WS
I2S vstupní data
GPIO pin for I2S DIN
I2S výstupní data
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Nastavení
Popis
Vzdálený modul povolen
Activate remote GPIO access
Povolit přiřazení nedefinovaného pinu
Allow access to any GPIO pin (security risk)
Dostupné piny
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Nastavení
Popis
Informace o sousedech povoleny
Activate neighbor broadcasting
Interval aktualizace GPS
How often to broadcast neighbor list
Přenos přes LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Nastavení
Popis
Stav LED
Turn the LED on or off
Proud
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Nastavení
Popis
Detekční senzor povolen
Activate detection sensor
GPIO pin ke sledování
GPIO pin connected to sensor
Typ spouštění detekce
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Použít INPUT_PULLUP režim
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Poslat zvonek s výstražnou zprávou
Include bell character in alerts
Přezdívka
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Nastavení
Popis
Paxcounter povolen
Activate people counting
Interval aktualizace GPS
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administrace
Vzdálená administrace
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Nastavení času
Sends your phone’s clock to the node
Restartovat
Restarts the node
Vypnout
Powers the node down
Obnovení továrního nastavení
Returns every setting to its factory default
Reset NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Zálohování a obnovení
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Rozšířené
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Vyčistit databázi uzlů
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panel pro ladění
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
O aplikaci
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Poděkování
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Nastavení modulů
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Nastavení
Popis
MQTT povoleno
Toggle MQTT bridge
Adresa
MQTT broker address
Uživatelské jméno
Authentication username
Heslo
Authentication password
Šifrování povoleno
Encrypt MQTT payloads
JSON výstup povolen
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS povoleno
Use secure connection
Kořenové téma
Base MQTT topic path
Proxy na klienta povoleno
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Hlášení mapy
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Nastavení
Popis
Souhlasím.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Nastavení
Popis
Sériová komunikace povolena
Activate serial communication
Povolit echo
Echo received serial data back
Sériový režim
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Rychlost sériového přenosu
Port speed
Vypršel čas spojení
How long to wait before considering an incoming message complete
Přepsat sériový port komunikace
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Nastavení
Popis
Externí oznámení povoleno
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Výstupní LED (GPIO)
Pin the LED is wired to
Výstupní LED aktivní při HIGH
Whether the LED pin is active high or low
Výstupní pin bzučáku (GPIO)
Pin the buzzer is wired to
Výstupní pin vybračního motorku (GPIO)
Pin the vibration motor is wired to
Použít PWM bzučák
Drive the buzzer with PWM, which allows tones rather than a single pitch
Použít I2S jako bzučák
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Vyzváněcí tón
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Nastavení
Popis
Uložit a přeposlat povoleno
Activate store and forward
Pulzující LED
Periodically announce this node’s store-and-forward capability
Počet záznamů
Maximum stored messages
Max. počet záznamů historie
Max messages to replay
Časové okno historie
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Nastavení
Popis
Test pokrytí povolen
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Uložit .CSV do úložiště (pouze ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Nastavení
Popis
Odesílat telemetrii zařízení
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Interval aktualizace metrik zařízení
How often to report battery, uptime and channel utilization
Modul měření životního prostředí povolen
Report the attached environment sensors
Interval aktualizace měření životního prostředí
How often to report them
Zobrazení měření životního prostředí povoleno
Also show these readings on the device’s own display
Měření životního prostředí používá Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Modul měření kvality ovzduší povolen
Report particulate and CO₂ sensor data
Interval aktualizace měření kvality ovzduší
How often to report them
Modul měření spotřeby povolen
Report the per-channel voltage and current readings
Interval aktualizace měření napájení
How often to report them
Měření spotřeby na obrazovce povoleno
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Nastavení
Popis
Canned message enabled
⚠️ Deprecated in the protobuf schema
Zprávy
Newline-separated list of messages
Odeslat zvonek
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotační enkodér #1 povolen
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Vstup Nahoru/Dolů/Výběr povolen
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Nastavení
Popis
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S výběr slov
GPIO pin for I2S WS
I2S vstupní data
GPIO pin for I2S DIN
I2S výstupní data
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Nastavení
Popis
Vzdálený modul povolen
Activate remote GPIO access
Povolit přiřazení nedefinovaného pinu
Allow access to any GPIO pin (security risk)
Dostupné piny
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Nastavení
Popis
Informace o sousedech povoleny
Activate neighbor broadcasting
Interval aktualizace GPS
How often to broadcast neighbor list
Přenos přes LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Nastavení
Popis
Stav LED
Turn the LED on or off
Proud
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Nastavení
Popis
Detekční senzor povolen
Activate detection sensor
GPIO pin ke sledování
GPIO pin connected to sensor
Typ spouštění detekce
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Použít INPUT_PULLUP režim
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Poslat zvonek s výstražnou zprávou
Include bell character in alerts
Přezdívka
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Nastavení
Popis
Paxcounter povolen
Activate people counting
Interval aktualizace GPS
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administrace
Vzdálená administrace
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Nastavení času
Sends your phone’s clock to the node
Restartovat
Restarts the node
Vypnout
Powers the node down
Obnovení továrního nastavení
Returns every setting to its factory default
Reset NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Zálohování a obnovení
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Rozšířené
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Vyčistit databázi uzlů
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panel pro ladění
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
O aplikaci
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Poděkování
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Kommunizieren Sie außerhalb des Netzwerks mit Ihren Freunden und der Gemeinschaft ohne Mobilfunkdienst.
Create Your Own Networks
Leicht einzurichtende, private Netznetze für sichere und zuverlässige Kommunikation in entlegenen Gebieten.
Track and Share Locations
Teilen Sie Ihren Standort in Echtzeit und koordinieren Sie Ihre Gruppe mit integrierten GPS Funktionen.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
Status
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? Die Anleitung für den Einstieg auf meshtastic.org behandelt die Hardware-Auswahl, die anfängliche Funkkonfiguration und die Einrichtung deines ersten Mesh-Netzwerks.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Kommunizieren Sie außerhalb des Netzwerks mit Ihren Freunden und der Gemeinschaft ohne Mobilfunkdienst.
Create Your Own Networks
Leicht einzurichtende, private Netznetze für sichere und zuverlässige Kommunikation in entlegenen Gebieten.
Track and Share Locations
Teilen Sie Ihren Standort in Echtzeit und koordinieren Sie Ihre Gruppe mit integrierten GPS Funktionen.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
Status
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? Die Anleitung für den Einstieg auf meshtastic.org behandelt die Hardware-Auswahl, die anfängliche Funkkonfiguration und die Einrichtung deines ersten Mesh-Netzwerks.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Moduleinstellungen
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Einstellung
Beschreibung
MQTT aktiviert
Toggle MQTT bridge
Adresse
MQTT broker address
Benutzername
Authentication username
Passwort
Authentication password
Verschlüsselung aktiviert
Encrypt MQTT payloads
JSON-Ausgabe aktiviert
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS aktiviert
Use secure connection
Hauptthema
Base MQTT topic path
Proxy zu Client aktiviert
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Kartenberichte
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Einstellung
Beschreibung
Ich stimme zu.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Einstellung
Beschreibung
Serielle Schnittstelle aktiviert
Activate serial communication
Echo aktiviert
Echo received serial data back
Serieller Modus
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serielle Baudrate
Port speed
Zeitlimit erreicht
How long to wait before considering an incoming message complete
Seriellen Anschluss der Konsole überschreiben
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Einstellung
Beschreibung
Externe Benachrichtigungen aktiviert
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Ausgabe LED (GPIO)
Pin the LED is wired to
Ausgabe LED aktiv hoch
Whether the LED pin is active high or low
Ausgabe Summer (GPIO)
Pin the buzzer is wired to
Ausgabe Vibration (GPIO)
Pin the vibration motor is wired to
Benutze PWM Summer
Drive the buzzer with PWM, which allows tones rather than a single pitch
I2S als Buzzer verwenden
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nervige Verzögerung
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Klingelton
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Einstellung
Beschreibung
Speichern & Weiterleiten aktiviert
Activate store and forward
Puls
Periodically announce this node’s store-and-forward capability
Anzahl Einträge
Maximum stored messages
Verlauf Rückgabewert maximal
Max messages to replay
Zeitraum Rückgabewert
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Einstellung
Beschreibung
Reichweitentest aktiviert
Activate range testing
Sendeintervall
Time between test transmissions, chosen from a dropdown of fixed intervals
Speichere .CSV im Speicher (nur ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Einstellung
Beschreibung
Gerätetelemetrie senden
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Aktualisierungsintervall für Gerätedaten
How often to report battery, uptime and channel utilization
Modul Umweltdaten aktiviert
Report the attached environment sensors
Aktualisierungsintervall für Umweltdaten
How often to report them
Umweltdatenanzeige aktiviert
Also show these readings on the device’s own display
Umweltdaten in Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Modul Luftqualität aktiviert
Report particulate and CO₂ sensor data
Aktualisierungsintervall der Luftqualität
How often to report them
Modul Energiedaten aktiviert
Report the per-channel voltage and current readings
Aktualisierungsintervall für Energiedaten
How often to report them
Energiedatenanzeige aktiviert
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Einstellung
Beschreibung
Canned message enabled
⚠️ Deprecated in the protobuf schema
Nachrichten
Newline-separated list of messages
Glocke senden
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Drehencoder #1 aktiviert
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select Eingang aktiviert
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Einstellung
Beschreibung
CODEC 2 aktiviert
Activate audio module
CODEC2 Abtastrate
Audio quality/bandwidth tradeoff
GPIO Pin PTT
GPIO pin for the push-to-talk button
I2S Wortauswahl
GPIO pin for I2S WS
I2S Daten Eingang
GPIO pin for I2S DIN
I2S Daten Ausgang
GPIO pin for I2S DOUT
I2S Takt
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Einstellung
Beschreibung
Einstellung entfernte Hardware
Activate remote GPIO access
Erlaube undefinierten Pin-Zugriff
Allow access to any GPIO pin (security risk)
Verfügbare Pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Einstellung
Beschreibung
Nachbarinformationen aktiviert
Activate neighbor broadcasting
GPS Abfrageintervall
How often to broadcast neighbor list
Übertragen über LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Einstellung
Beschreibung
LED Zustand
Turn the LED on or off
Stromstärke
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Einstellung
Beschreibung
Erkennungssensor aktiviert
Activate detection sensor
Zu überwachender GPIO-Pin
GPIO pin connected to sensor
Typ der Erkennungsauslösung
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Eingang PULLUP Einstellung
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
Übertragungsintervall
Periodic state broadcast interval
Glocke mit Warnmeldung senden
Include bell character in alerts
Anzeigename
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Einstellung
Beschreibung
Besucherzähler aktiviert
Activate people counting
GPS Abfrageintervall
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Siehe TAK Integration für detaillierte Einrichtung und Nutzung.
Einstellung
Ferneinstellung
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Neustart
Restarts the node
Herunterfahren
Powers the node down
Auf Werkseinstellungen zurücksetzen
Returns every setting to its factory default
Node-Datenbank zurücksetzen
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Sichern & Wiederherstellen
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Fortgeschritten
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Knotendatenbank leeren
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Debug-Ausgaben
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Einstellungen
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Über
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Danksagungen
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Moduleinstellungen
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Einstellung
Beschreibung
MQTT aktiviert
Toggle MQTT bridge
Adresse
MQTT broker address
Benutzername
Authentication username
Passwort
Authentication password
Verschlüsselung aktiviert
Encrypt MQTT payloads
JSON-Ausgabe aktiviert
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS aktiviert
Use secure connection
Hauptthema
Base MQTT topic path
Proxy zu Client aktiviert
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Kartenberichte
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Einstellung
Beschreibung
Ich stimme zu.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Einstellung
Beschreibung
Serielle Schnittstelle aktiviert
Activate serial communication
Echo aktiviert
Echo received serial data back
Serieller Modus
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serielle Baudrate
Port speed
Zeitlimit erreicht
How long to wait before considering an incoming message complete
Seriellen Anschluss der Konsole überschreiben
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Einstellung
Beschreibung
Externe Benachrichtigungen aktiviert
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Ausgabe LED (GPIO)
Pin the LED is wired to
Ausgabe LED aktiv hoch
Whether the LED pin is active high or low
Ausgabe Summer (GPIO)
Pin the buzzer is wired to
Ausgabe Vibration (GPIO)
Pin the vibration motor is wired to
Benutze PWM Summer
Drive the buzzer with PWM, which allows tones rather than a single pitch
I2S als Buzzer verwenden
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nervige Verzögerung
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Klingelton
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Einstellung
Beschreibung
Speichern & Weiterleiten aktiviert
Activate store and forward
Puls
Periodically announce this node’s store-and-forward capability
Anzahl Einträge
Maximum stored messages
Verlauf Rückgabewert maximal
Max messages to replay
Zeitraum Rückgabewert
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Einstellung
Beschreibung
Reichweitentest aktiviert
Activate range testing
Sendeintervall
Time between test transmissions, chosen from a dropdown of fixed intervals
Speichere .CSV im Speicher (nur ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Einstellung
Beschreibung
Gerätetelemetrie senden
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Aktualisierungsintervall für Gerätedaten
How often to report battery, uptime and channel utilization
Modul Umweltdaten aktiviert
Report the attached environment sensors
Aktualisierungsintervall für Umweltdaten
How often to report them
Umweltdatenanzeige aktiviert
Also show these readings on the device’s own display
Umweltdaten in Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Modul Luftqualität aktiviert
Report particulate and CO₂ sensor data
Aktualisierungsintervall der Luftqualität
How often to report them
Modul Energiedaten aktiviert
Report the per-channel voltage and current readings
Aktualisierungsintervall für Energiedaten
How often to report them
Energiedatenanzeige aktiviert
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Einstellung
Beschreibung
Canned message enabled
⚠️ Deprecated in the protobuf schema
Nachrichten
Newline-separated list of messages
Glocke senden
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Drehencoder #1 aktiviert
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select Eingang aktiviert
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Einstellung
Beschreibung
CODEC 2 aktiviert
Activate audio module
CODEC2 Abtastrate
Audio quality/bandwidth tradeoff
GPIO Pin PTT
GPIO pin for the push-to-talk button
I2S Wortauswahl
GPIO pin for I2S WS
I2S Daten Eingang
GPIO pin for I2S DIN
I2S Daten Ausgang
GPIO pin for I2S DOUT
I2S Takt
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Einstellung
Beschreibung
Einstellung entfernte Hardware
Activate remote GPIO access
Erlaube undefinierten Pin-Zugriff
Allow access to any GPIO pin (security risk)
Verfügbare Pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Einstellung
Beschreibung
Nachbarinformationen aktiviert
Activate neighbor broadcasting
GPS Abfrageintervall
How often to broadcast neighbor list
Übertragen über LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Einstellung
Beschreibung
LED Zustand
Turn the LED on or off
Stromstärke
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Einstellung
Beschreibung
Erkennungssensor aktiviert
Activate detection sensor
Zu überwachender GPIO-Pin
GPIO pin connected to sensor
Typ der Erkennungsauslösung
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Eingang PULLUP Einstellung
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
Übertragungsintervall
Periodic state broadcast interval
Glocke mit Warnmeldung senden
Include bell character in alerts
Anzeigename
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Einstellung
Beschreibung
Besucherzähler aktiviert
Activate people counting
GPS Abfrageintervall
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Siehe TAK Integration für detaillierte Einrichtung und Nutzung.
Einstellung
Ferneinstellung
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Neustart
Restarts the node
Herunterfahren
Powers the node down
Auf Werkseinstellungen zurücksetzen
Returns every setting to its factory default
Node-Datenbank zurücksetzen
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Sichern & Wiederherstellen
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Fortgeschritten
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Knotendatenbank leeren
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Debug-Ausgaben
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Einstellungen
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Über
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Danksagungen
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Ρυθμίσεις πρόσθετου
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Περιγραφή
MQTT enabled
Toggle MQTT bridge
Διεύθυνση
MQTT broker address
Όνομα χρήστη
Authentication username
Κωδικός πρόσβασης
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Περιγραφή
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Περιγραφή
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Λήξη χρονικού ορίου
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Περιγραφή
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Περιγραφή
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Περιγραφή
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Περιγραφή
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Περιγραφή
Canned message enabled
⚠️ Deprecated in the protobuf schema
Μηνύματα
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Περιγραφή
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Περιγραφή
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Περιγραφή
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Περιγραφή
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Περιγραφή
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Περιγραφή
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Διαχείριση
Απομακρυσμένη Διαχείριση
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Επανεκκίνηση
Restarts the node
Τερματισμός λειτουργίας
Powers the node down
Επαναφορά εργοστασιακών ρυθμίσεων
Returns every setting to its factory default
NodeDB reset
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Πίνακας αποσφαλμάτωσης
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Σχετικά
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Ρυθμίσεις πρόσθετου
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Περιγραφή
MQTT enabled
Toggle MQTT bridge
Διεύθυνση
MQTT broker address
Όνομα χρήστη
Authentication username
Κωδικός πρόσβασης
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Περιγραφή
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Περιγραφή
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Λήξη χρονικού ορίου
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Περιγραφή
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Περιγραφή
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Περιγραφή
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Περιγραφή
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Περιγραφή
Canned message enabled
⚠️ Deprecated in the protobuf schema
Μηνύματα
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Περιγραφή
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Περιγραφή
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Περιγραφή
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Περιγραφή
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Περιγραφή
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Περιγραφή
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Διαχείριση
Απομακρυσμένη Διαχείριση
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Επανεκκίνηση
Restarts the node
Τερματισμός λειτουργίας
Powers the node down
Επαναφορά εργοστασιακών ρυθμίσεων
Returns every setting to its factory default
NodeDB reset
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Πίνακας αποσφαλμάτωσης
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Σχετικά
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Comparte tu ubicación en tiempo real y mantén tu grupo coordinado con las características integradas del GPS.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Comparte tu ubicación en tiempo real y mantén tu grupo coordinado con las características integradas del GPS.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Configuración de módulo
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Descripción
Activar el MQTT
Toggle MQTT bridge
Dirección del Servidor MQTT
MQTT broker address
Usuario
Authentication username
Contraseña
Authentication password
Permitir Encripción
Encrypt MQTT payloads
Salida JSON activada
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS activado
Use secure connection
Tema raíz
Base MQTT topic path
Compartir Internet a la Radio
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Reportar Posición
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Descripción
Estoy de acuerdo.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Descripción
Comunicación serial activada
Activate serial communication
Eco activado
Echo received serial data back
Modo serial
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Tasa de baudios por segundo
Port speed
Tiempo agotado
How long to wait before considering an incoming message complete
Sobreescribir el puerto serie de la consola
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Descripción
Notificaciones externas activadas
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Salida LED (pin GPIO)
Pin the LED is wired to
LED de salida activo en alto
Whether the LED pin is active high or low
Salida buzzer (pin GPIO)
Pin the buzzer is wired to
Salida vibratoria (pin GPIO)
Pin the vibration motor is wired to
Utilizar buzzer PWM
Drive the buzzer with PWM, which allows tones rather than a single pitch
Utilizar el Buzzer como uno I2S
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Tono de notificación
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Descripción
Descargar y reenviar activado
Activate store and forward
Pulso de vida
Periodically announce this node’s store-and-forward capability
Número de registros
Maximum stored messages
Historial máximo devuelto
Max messages to replay
History return window
Time window for replay
Servidor
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Descripción
Test de alcance activado
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Guardar el .CSV en el almacenamiento (Esp32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Descripción
Enviar telemetría del dispositivo
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervalo actualización de métricas del dispositivo
How often to report battery, uptime and channel utilization
Módulo para las medidas del entorno activado
Report the attached environment sensors
Intervalo actualización de métricas del entorno
How often to report them
Mostrar las medidas del entorno en la
Also show these readings on the device’s own display
Grados Fahrenheit para la temperatura ambiente
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Módulo para la medición de la calidad del aire activado
Report particulate and CO₂ sensor data
Intervalo actualización de métricas calidad del aire
How often to report them
Módulo de medidas eléctricas activado
Report the per-channel voltage and current readings
Intervalo de actualización de métricas de energía
How often to report them
Medidas eléctricas en pantalla
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Descripción
Canned message enabled
⚠️ Deprecated in the protobuf schema
Mensajes
Newline-separated list of messages
Mandar campana 🔔
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encoder Número 1 Activado
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Arriba/Abajo/Seleccionar Activado
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Descripción
CODEC 2 activado
Activate audio module
Frecuencia de Muestreo CODEC2
Audio quality/bandwidth tradeoff
Pin PTT
GPIO pin for the push-to-talk button
Selecionar palabras I2S
GPIO pin for I2S WS
Entrada de datos I2S
GPIO pin for I2S DIN
Salida de datos I2S
GPIO pin for I2S DOUT
Reloj del I2S
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Descripción
Hardware remoto activado
Activate remote GPIO access
Permitir el acceso sin un pin definido
Allow access to any GPIO pin (security risk)
Pines disponibles
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Descripción
Información de Vecinos
Activate neighbor broadcasting
Intervalo de actualización
How often to broadcast neighbor list
Transmitir en LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Descripción
Estado de led
Turn the LED on or off
Intensidad
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Descripción
Sensor detector activado
Activate detection sensor
Pin GPIO para monitorizar
GPIO pin connected to sensor
Tipo de detección para activar
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Utilizar el modo de entrada PULL_UP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Mandar la campana con el mensaje de alerta
Include bell character in alerts
Mote
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Descripción
Activar el Contador de Paquetes
Activate people counting
Intervalo de actualización
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administración
Administración remota
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Reiniciar
Restarts the node
Apagar
Powers the node down
Restablecer los valores de fábrica
Returns every setting to its factory default
Reinicio de NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Hacer copia de seguridad y restaurar
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Avanzado
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Limpiar nodos de la base de datos
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panel de depuración
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Acerca de
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Agradecimientos
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Configuración de módulo
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Descripción
Activar el MQTT
Toggle MQTT bridge
Dirección del Servidor MQTT
MQTT broker address
Usuario
Authentication username
Contraseña
Authentication password
Permitir Encripción
Encrypt MQTT payloads
Salida JSON activada
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS activado
Use secure connection
Tema raíz
Base MQTT topic path
Compartir Internet a la Radio
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Reportar Posición
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Descripción
Estoy de acuerdo.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Descripción
Comunicación serial activada
Activate serial communication
Eco activado
Echo received serial data back
Modo serial
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Tasa de baudios por segundo
Port speed
Tiempo agotado
How long to wait before considering an incoming message complete
Sobreescribir el puerto serie de la consola
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Descripción
Notificaciones externas activadas
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Salida LED (pin GPIO)
Pin the LED is wired to
LED de salida activo en alto
Whether the LED pin is active high or low
Salida buzzer (pin GPIO)
Pin the buzzer is wired to
Salida vibratoria (pin GPIO)
Pin the vibration motor is wired to
Utilizar buzzer PWM
Drive the buzzer with PWM, which allows tones rather than a single pitch
Utilizar el Buzzer como uno I2S
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Tono de notificación
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Descripción
Descargar y reenviar activado
Activate store and forward
Pulso de vida
Periodically announce this node’s store-and-forward capability
Número de registros
Maximum stored messages
Historial máximo devuelto
Max messages to replay
History return window
Time window for replay
Servidor
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Descripción
Test de alcance activado
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Guardar el .CSV en el almacenamiento (Esp32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Descripción
Enviar telemetría del dispositivo
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervalo actualización de métricas del dispositivo
How often to report battery, uptime and channel utilization
Módulo para las medidas del entorno activado
Report the attached environment sensors
Intervalo actualización de métricas del entorno
How often to report them
Mostrar las medidas del entorno en la
Also show these readings on the device’s own display
Grados Fahrenheit para la temperatura ambiente
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Módulo para la medición de la calidad del aire activado
Report particulate and CO₂ sensor data
Intervalo actualización de métricas calidad del aire
How often to report them
Módulo de medidas eléctricas activado
Report the per-channel voltage and current readings
Intervalo de actualización de métricas de energía
How often to report them
Medidas eléctricas en pantalla
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Descripción
Canned message enabled
⚠️ Deprecated in the protobuf schema
Mensajes
Newline-separated list of messages
Mandar campana 🔔
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encoder Número 1 Activado
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Arriba/Abajo/Seleccionar Activado
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Descripción
CODEC 2 activado
Activate audio module
Frecuencia de Muestreo CODEC2
Audio quality/bandwidth tradeoff
Pin PTT
GPIO pin for the push-to-talk button
Selecionar palabras I2S
GPIO pin for I2S WS
Entrada de datos I2S
GPIO pin for I2S DIN
Salida de datos I2S
GPIO pin for I2S DOUT
Reloj del I2S
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Descripción
Hardware remoto activado
Activate remote GPIO access
Permitir el acceso sin un pin definido
Allow access to any GPIO pin (security risk)
Pines disponibles
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Descripción
Información de Vecinos
Activate neighbor broadcasting
Intervalo de actualización
How often to broadcast neighbor list
Transmitir en LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Descripción
Estado de led
Turn the LED on or off
Intensidad
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Descripción
Sensor detector activado
Activate detection sensor
Pin GPIO para monitorizar
GPIO pin connected to sensor
Tipo de detección para activar
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Utilizar el modo de entrada PULL_UP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Mandar la campana con el mensaje de alerta
Include bell character in alerts
Mote
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Descripción
Activar el Contador de Paquetes
Activate people counting
Intervalo de actualización
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administración
Administración remota
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Reiniciar
Restarts the node
Apagar
Powers the node down
Restablecer los valores de fábrica
Returns every setting to its factory default
Reinicio de NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Hacer copia de seguridad y restaurar
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Avanzado
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Limpiar nodos de la base de datos
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panel de depuración
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Acerca de
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Agradecimientos
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Kui midagi töötab valesti, on rakenduse arendajalogid kõige kasulikum asi, mida saad veateatele lisada. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Ava Arendajapaneel, valides Seaded → Täpsemad → Arendajapaneel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
Arendajapaneelil on kaks vahekaarti:
Paketid – dekodeeritud võrguliiklus, mida raadio on saatnud ja vastu võtnud (protokollitasemel sõnumid). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Otsi – sisesta otsingukasti otsing, et filtreerida sobivate ridade hulgast.
Tasemefilter — V / D / I / W / E kiibid lülitavad sisse üksikasjaliku, arendaja-, teabe-, hoiatus- ja vearea. Tap a level to hide it; tap again to bring it back. Fataalseid jooni näidatakse alati.
Värskenda – värskendamise ikoon loeb uuesti viimased logid.
Error and warning lines are tinted so problems stand out.
Eksportimine
Praeguste logide faili salvestamiseks puuduta ikooni allalaadimine. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Töölaud
Töölauarakendusel puudub süsteemi logcat, seega kuvatakse vahekaardil Rakenduse logid rakenduse enda jäädvustatud logide väljundit. Otsimine, filtreerimine ja eksportimine toimivad samamoodi.
Kui midagi töötab valesti, on rakenduse arendajalogid kõige kasulikum asi, mida saad veateatele lisada. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Ava Arendajapaneel, valides Seaded → Täpsemad → Arendajapaneel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
Arendajapaneelil on kaks vahekaarti:
Paketid – dekodeeritud võrguliiklus, mida raadio on saatnud ja vastu võtnud (protokollitasemel sõnumid). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Otsi – sisesta otsingukasti otsing, et filtreerida sobivate ridade hulgast.
Tasemefilter — V / D / I / W / E kiibid lülitavad sisse üksikasjaliku, arendaja-, teabe-, hoiatus- ja vearea. Tap a level to hide it; tap again to bring it back. Fataalseid jooni näidatakse alati.
Värskenda – värskendamise ikoon loeb uuesti viimased logid.
Error and warning lines are tinted so problems stand out.
Eksportimine
Praeguste logide faili salvestamiseks puuduta ikooni allalaadimine. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Töölaud
Töölauarakendusel puudub süsteemi logcat, seega kuvatakse vahekaardil Rakenduse logid rakenduse enda jäädvustatud logide väljundit. Otsimine, filtreerimine ja eksportimine toimivad samamoodi. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Tervituskuva
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Saada sõnumeid sõpradele ja kommuunile ilma võrguühenduse või mobiilivõrguta.
Create Your Own Networks
Loo hõlpsalt privaatseid kärgvõrke turvaliseks ja usaldusväärseks suhtluseks asustamata piirkondades.
Track and Share Locations
Jaga reaalajas oma asukohta ja hoia oma grupp ühtsena integreeritud GPS funktsioonide abil.
Tap Get started to proceed through the setup flow.
Permissions
Rakendus küsib seadistamise ajal mitmeid lube. Igal neist on kindel eesmärk ja mõned on vajalikud põhifunktsioonide täitmiseks.
Sinihamba load
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Asukoha luba
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic kasutab sinu asukohta ka järgmiseks:
Kuvatakse asukoht kärgvõrgu kaardil
Calculating distances to other nodes
GPS koordinaatide jagamine teiste kärgvõrgu liikmetega (kui lubatud)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Märguannete load
Märguanded teavitavad teid järgmisest:
Sissetulevad sõnumid kanalitelt ja otsesõnumid
New nodes joining the mesh
Kaugsõlmel on aku tühjenenud
💡 Vihje: Teavituste eelistusi saab hiljem Androidi süsteemiseadetes täpsustada – rakendus loob iga kategooria kohta eraldi teavituskanali (lisaks mõned sisemised, näiteks taustateenus), nii et saad need eraldi lubada või vaigistada.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
Olek
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
Peale seadistamist
After you grant permissions, the app opens the main interface. Esimene samm peaks olema ühenduse loomine Meshtastic raadioga – üksikasjalike juhiste saamiseks vaata [Ühendused] (connections).
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
Kas oled Meshtasticus algaja? Meshtastic.org lehel olev alustusjuhend käsitleb riistvara valimist, raadio esialgset seadistamist ja esimest võrgu seadistamist.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Tervituskuva
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Saada sõnumeid sõpradele ja kommuunile ilma võrguühenduse või mobiilivõrguta.
Create Your Own Networks
Loo hõlpsalt privaatseid kärgvõrke turvaliseks ja usaldusväärseks suhtluseks asustamata piirkondades.
Track and Share Locations
Jaga reaalajas oma asukohta ja hoia oma grupp ühtsena integreeritud GPS funktsioonide abil.
Tap Get started to proceed through the setup flow.
Permissions
Rakendus küsib seadistamise ajal mitmeid lube. Igal neist on kindel eesmärk ja mõned on vajalikud põhifunktsioonide täitmiseks.
Sinihamba load
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Asukoha luba
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic kasutab sinu asukohta ka järgmiseks:
Kuvatakse asukoht kärgvõrgu kaardil
Calculating distances to other nodes
GPS koordinaatide jagamine teiste kärgvõrgu liikmetega (kui lubatud)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Märguannete load
Märguanded teavitavad teid järgmisest:
Sissetulevad sõnumid kanalitelt ja otsesõnumid
New nodes joining the mesh
Kaugsõlmel on aku tühjenenud
💡 Vihje: Teavituste eelistusi saab hiljem Androidi süsteemiseadetes täpsustada – rakendus loob iga kategooria kohta eraldi teavituskanali (lisaks mõned sisemised, näiteks taustateenus), nii et saad need eraldi lubada või vaigistada.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
Olek
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
Peale seadistamist
After you grant permissions, the app opens the main interface. Esimene samm peaks olema ühenduse loomine Meshtastic raadioga – üksikasjalike juhiste saamiseks vaata [Ühendused] (connections).
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
Kas oled Meshtasticus algaja? Meshtastic.org lehel olev alustusjuhend käsitleb riistvara valimist, raadio esialgset seadistamist ja esimest võrgu seadistamist.
Konfi valikulisi funktsioonimooduleid ja teosta seadme haldamist. Moodulid laiendavad Meshtasticut spetsiaalsete võimalustega – igaüht saab eraldi lubada või keelata.
💡 Vihje: Pead lubama ainult need moodulid, mida sa tegelikult kasutad. Kasutamata moodulite keelamine vähendab eetriaega, säästab akut ja lihtsustab seadistamist. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Mooduli seaded kasutavad kaardipõhist paigutust koos lülitite, rippmenüüde, tekstiväljade ja liuguritega:
Mooduli sätted
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Sildab võrgusõnumeid MQTT vahendajasse ja sealt internetiühenduse loomiseks. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Sätted
Kirjeldus
MQTT lubatud
Lükka MQTT sild sisse
Aadress
MQTT vahendaja aadress
Kasutajatunnus
Authentication username
Parool
Authentication password
Krüpteerimine lubatud
Krüpteeri MQTT kasutus
JSON väljund lubatud
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS lubatud
Use secure connection
Juurteema
Baas MQTT teema teekond
Kliendi proksi lubatud
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Kaardi raport
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Sätted
Kirjeldus
Nõustun.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
Vaata MQTT üksikasjalikumat kasutusjuhendit, mis sisaldab teavet krüpteerimise, privaatsuse ja vahendaja seadistamise kohta,.
Serial module
Võimaldab jadapordi sidet väliste seadmete integreerimiseks (GPS-moodulid, andurid või kohandatud riistvara). Kui lubatud, saab sõlme jadaühendus saata ja vastu võtta protobuf- või tekstiandmeid, võimaldades välistel mikrokontrolleritel või arvutitel võrguga suhelda.
Sätted
Kirjeldus
Jadaport lubatud
Aktiveeri jadapordi ühendus
Kaja lubatud
Kaja sai jadaandmed tagasi
Jadapordi režiim
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Jadapordi kiirus
Port speed
Aegunud
How long to wait before considering an incoming message complete
Konsooli jadapordi alistamine
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Kasulik seadmetele, mis peavad sõnumi saabumisest füüsiliselt märku andma – eriti kasulik järelevalveta või välistingimustes paigaldamise korral.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Sätted
Kirjeldus
Luba Välised teated
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Väljund LED (GPIO)
Pin the LED is wired to
Väljund LED aktiivne
Whether the LED pin is active high or low
Väljund summer (GPIO)
Pin the buzzer is wired to
Väljund värin (GPIO)
Pin the vibration motor is wired to
Kasuta PWM summerit
Drive the buzzer with PWM, which allows tones rather than a single pitch
Kasuta I2S summerina
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Helin
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Puhverdab ajutiselt võrguühenduseta olnud sõlmede sõnumeid ja esitab need uuesti, kui need sõlmed taasühenduvad. Hädavajalik kärgvõrgu jaoks, kus sõlmed regulaarselt levialasse lähevad ja levialast välja lähevad — tagab, et lühikeste katkestuste ajal sõnumid kaotsi ei lähe.
Sätted
Kirjeldus
Salvesta & Edasta lubatud
Aktiveeri salvesta ja saada
Südamelöögid
Periodically announce this node’s store-and-forward capability
Kirjete arv
Maximum stored messages
Ajalookirjete maksimaalne arv
Max messages to replay
Ajalookirjete aken
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Vihje: Salvesta ja edasta töötab kõige paremini rohke mäluga sõlmedes (ESP32 koos PSRAM-iga). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automatiseeritud vahemiku testimise tööriist sõlmede vahelise ühenduse kvaliteedi hindamiseks. Kui lubatud, edastab sõlm perioodiliselt testsõnumeid kasvavate loenduritega. Vastuvõtusõlm logib need sõnumid, võimaldades kõndida või minema sõita ning hiljem analüüsida, millisel kaugusel sõnumite saabumine lakkas.
Sätted
Kirjeldus
Ulatustest lubatud
Aktiveeri levi test
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Salvesta .CSV faili (ainult ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Juhib, milliseid telemeetriaandmeid sõlm võrguga jagab. Telemeetria sisaldab seadme tervist (aku, tööaeg) ja keskkonnaandurite andmeid (temperatuur, niiskus, rõhk).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Sätted
Kirjeldus
Saada seadme telemeetria
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Seadme mõõdikute värskendamise intervall
How often to report battery, uptime and channel utilization
Keskkonnamõõdikute lubamine
Report the attached environment sensors
Keskkonnamõõdikute värskendamise intervall
How often to report them
Keskkonnamõõdikute ekraanil kuvamine lubatud
Also show these readings on the device’s own display
Keskkonnamõõdikud kasutavad Fahrenheiti
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Õhukvaliteedi moodul on lubatud
Report particulate and CO₂ sensor data
Õhukvaliteedi näidikute värskendamise intervall
How often to report them
Toitemõõdiku moodul on lubatud
Report the per-channel voltage and current readings
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Määra nimekiri kiirsõnumitest, mida saab edastada ilma telefoni ühendamata – ideaalne välitöödeks.
Sätted
Kirjeldus
Canned message enabled
⚠️ Deprecated in the protobuf schema
Sõnumid
Reavahetusega eraldatud sõnumite loend
Saada Kõll
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Pöördvalik #1 lubatud
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Üles/Alla/Vali sisend lubatud
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. See on eksperimentaalne funktsioon, mis kodeerib hääle Codec2 koodeki abil väga väikesteks andmepakettideks.
Sätted
Kirjeldus
CODEC 2 lubatud
Aktiveeri audio moodul
CODEC2 test sagedus
Audio quality/bandwidth tradeoff
PTT klemm
GPIO pin for the push-to-talk button
I2S sõna valik
GPIO sisend I2S WS jaoks
I2S info sisse
GPIO sisend I2S DIN jaoks
I2S info välja
GPIO sisend I2S DOUT jaoks
I2S kell
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO juhtimine kärgvõrgu kaudu. Võimaldab kaugsõlmel lugeda või kirjutada GPIO sisendkontakte teisel sõlmel – kasulik releede aktiveerimiseks, lülitite lugemiseks või välise riistvara kaugjuhtimiseks.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Sätted
Kirjeldus
Kaug riistvara lubatud
Aktiveeri kaugjuurdepääs GPIO-le
Luba määratlemata klemmi juurdepääs
Luba juurdepääs mis tahes GPIO sisendile (turvarisk)
Saadaval klemmid
Kuni 4 GPIO sisendit, mida see sõlm kauglugemiseks/-kirjutamiseks avab
Neighbor Info module
Levitab teavet otse kuuldud naabrite kohta, võimaldades kärgvõrgu topoloogia kaardistamist. Iga lubatud sõlm jagab perioodiliselt nimekirja teistest sõlmedest, mida ta kuuleb ja nende signaali kvaliteedist.
Sätted
Kirjeldus
Naabruskonna teave lubatud
Aktiveeri naabrite leviring
GPS-i küsimise intervall
Kui tihti naabrite nimekirja levitada
Saada LoRa kaudu
Edasta naabriinfot ka LoRa kaudu, mitte ainult MQTT/telefoni kaudu. Vaikimisi võtit ja nime kasutavat kanalit pole saadaval
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Juhib toetatud riistvaral NeoPixeli või muid adresseeritavaid RGB LEDe. Saab kasutada visuaalsete olekuindikaatorite, märgutulede või dekoratiivsete efektide jaoks.
Sätted
Kirjeldus
LED olek
Turn the LED on or off
Pinge
LED current limit (0–31)
Punane / Roheline / Sinine
Individuaalsete värvikanalite väärtused (0–255)
Detection Sensor module
Muudab sõlme liikumis- või ukseanduri hoiatussüsteemiks. Kui GPIO sisend tuvastab oleku muutuse (liikumine tuvastatud, uks avatud), levitab sõlm kärgvõrgu kaudu hoiatusteate.
Sätted
Kirjeldus
Tuvastusandur lubatud
Aktiveeri tuvastusandur
GPIO klemmi jälgimine
GPIO sisend on anduriga ühendatud
Identifitseerimistüüp
Kuidas klemmi olek vastab tuvastussündmusele (nt aktiivne kõrge/madal, serva poolt käivitatav)
Kasuta INPUT_PULLUP režiimi
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimaalne aeg hoiatusteadete levitamisel
State Broadcast Interval
Perioodilise oleku levitamise intervall
Saada kõll koos hoiatussõnumiga
Lisa märguannetesse hoiatuskella sümbol
Kasutajasõbralik nimi
Selle anduri kohandatud nimi
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Loendab lähedalasuvaid seadmeid, kuulates passiivselt sondimistaotlusi, mida telefonid ja sülearvutid võrkude skannimisel edastavad. Available only on ESP32 devices.
Sätted
Kirjeldus
Paxcounter lubatud
Aktiveeri inimeste loendamine
GPS-i küsimise intervall
Kui tihti loendeid esitada
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Vihje: Paxloendur on kasulik jalakäijate liikluse hindamiseks matkaradade alguses, ürituste toimumiskohtades või muudes kohtades. Arvud on ligikaudsed – üks inimene võib kaasas kanda mitut seadet.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Meeskonna teadlikkuse komplekti integratsioon ATAKi ja WinTAKi koostalitlusvõime tagamiseks. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Vaata TAK Integration täpsema seadistamise ja kasutamise kohta.
Puuduta Salvesta – muudatused saadetakse kärgvõrgu kaudu.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Määra aeg
Sends your phone’s clock to the node
Taaskäivita
Restarts the node
Lülita välja
Powers the node down
Tehasesätted
Returns every setting to its factory default
NodeDB lähtestamine
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Varunda ja taasta
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Täpsem
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Tühjenda sõlmede andmebaas
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Arendaja paneel
Avab vahekaardid Paketid ja Rakenduse logid diagnostilise väljundi vaatamiseks, filtreerimiseks ja eksportimiseks. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Teave
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Tänusõnad
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“Sihtsõlmelt ei ole vastust” — sihtsõlm võib olla leviulatusest väljas, võrguühenduseta või sellel võib olla sobimatu administraatori võti. Veendu, et administraatori võti sobiks mõlemas sõlmele.
Muudatused ei rakendu — mõnede sätete jõustumiseks on vaja taaskäivitada. Pärast salvestamist proovi taaskäivitust.
Ei näe kaugseadeid — veendu, et sõlmel oleks sihtsõlme administraatori võti ja et administraatori kanal oleks turbekonfiguratsioonis lubatud. Administraatori kanal seadistatakse automaatselt, kui administraatori võti on määratud.
Konfi valikulisi funktsioonimooduleid ja teosta seadme haldamist. Moodulid laiendavad Meshtasticut spetsiaalsete võimalustega – igaüht saab eraldi lubada või keelata.
💡 Vihje: Pead lubama ainult need moodulid, mida sa tegelikult kasutad. Kasutamata moodulite keelamine vähendab eetriaega, säästab akut ja lihtsustab seadistamist. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Mooduli seaded kasutavad kaardipõhist paigutust koos lülitite, rippmenüüde, tekstiväljade ja liuguritega:
Mooduli sätted
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Sildab võrgusõnumeid MQTT vahendajasse ja sealt internetiühenduse loomiseks. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Sätted
Kirjeldus
MQTT lubatud
Lükka MQTT sild sisse
Aadress
MQTT vahendaja aadress
Kasutajatunnus
Authentication username
Parool
Authentication password
Krüpteerimine lubatud
Krüpteeri MQTT kasutus
JSON väljund lubatud
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS lubatud
Use secure connection
Juurteema
Baas MQTT teema teekond
Kliendi proksi lubatud
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Kaardi raport
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Sätted
Kirjeldus
Nõustun.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
Vaata MQTT üksikasjalikumat kasutusjuhendit, mis sisaldab teavet krüpteerimise, privaatsuse ja vahendaja seadistamise kohta,.
Serial module
Võimaldab jadapordi sidet väliste seadmete integreerimiseks (GPS-moodulid, andurid või kohandatud riistvara). Kui lubatud, saab sõlme jadaühendus saata ja vastu võtta protobuf- või tekstiandmeid, võimaldades välistel mikrokontrolleritel või arvutitel võrguga suhelda.
Sätted
Kirjeldus
Jadaport lubatud
Aktiveeri jadapordi ühendus
Kaja lubatud
Kaja sai jadaandmed tagasi
Jadapordi režiim
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Jadapordi kiirus
Port speed
Aegunud
How long to wait before considering an incoming message complete
Konsooli jadapordi alistamine
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Kasulik seadmetele, mis peavad sõnumi saabumisest füüsiliselt märku andma – eriti kasulik järelevalveta või välistingimustes paigaldamise korral.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Sätted
Kirjeldus
Luba Välised teated
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Väljund LED (GPIO)
Pin the LED is wired to
Väljund LED aktiivne
Whether the LED pin is active high or low
Väljund summer (GPIO)
Pin the buzzer is wired to
Väljund värin (GPIO)
Pin the vibration motor is wired to
Kasuta PWM summerit
Drive the buzzer with PWM, which allows tones rather than a single pitch
Kasuta I2S summerina
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Helin
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Puhverdab ajutiselt võrguühenduseta olnud sõlmede sõnumeid ja esitab need uuesti, kui need sõlmed taasühenduvad. Hädavajalik kärgvõrgu jaoks, kus sõlmed regulaarselt levialasse lähevad ja levialast välja lähevad — tagab, et lühikeste katkestuste ajal sõnumid kaotsi ei lähe.
Sätted
Kirjeldus
Salvesta & Edasta lubatud
Aktiveeri salvesta ja saada
Südamelöögid
Periodically announce this node’s store-and-forward capability
Kirjete arv
Maximum stored messages
Ajalookirjete maksimaalne arv
Max messages to replay
Ajalookirjete aken
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Vihje: Salvesta ja edasta töötab kõige paremini rohke mäluga sõlmedes (ESP32 koos PSRAM-iga). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automatiseeritud vahemiku testimise tööriist sõlmede vahelise ühenduse kvaliteedi hindamiseks. Kui lubatud, edastab sõlm perioodiliselt testsõnumeid kasvavate loenduritega. Vastuvõtusõlm logib need sõnumid, võimaldades kõndida või minema sõita ning hiljem analüüsida, millisel kaugusel sõnumite saabumine lakkas.
Sätted
Kirjeldus
Ulatustest lubatud
Aktiveeri levi test
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Salvesta .CSV faili (ainult ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Juhib, milliseid telemeetriaandmeid sõlm võrguga jagab. Telemeetria sisaldab seadme tervist (aku, tööaeg) ja keskkonnaandurite andmeid (temperatuur, niiskus, rõhk).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Sätted
Kirjeldus
Saada seadme telemeetria
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Seadme mõõdikute värskendamise intervall
How often to report battery, uptime and channel utilization
Keskkonnamõõdikute lubamine
Report the attached environment sensors
Keskkonnamõõdikute värskendamise intervall
How often to report them
Keskkonnamõõdikute ekraanil kuvamine lubatud
Also show these readings on the device’s own display
Keskkonnamõõdikud kasutavad Fahrenheiti
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Õhukvaliteedi moodul on lubatud
Report particulate and CO₂ sensor data
Õhukvaliteedi näidikute värskendamise intervall
How often to report them
Toitemõõdiku moodul on lubatud
Report the per-channel voltage and current readings
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Määra nimekiri kiirsõnumitest, mida saab edastada ilma telefoni ühendamata – ideaalne välitöödeks.
Sätted
Kirjeldus
Canned message enabled
⚠️ Deprecated in the protobuf schema
Sõnumid
Reavahetusega eraldatud sõnumite loend
Saada Kõll
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Pöördvalik #1 lubatud
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Üles/Alla/Vali sisend lubatud
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. See on eksperimentaalne funktsioon, mis kodeerib hääle Codec2 koodeki abil väga väikesteks andmepakettideks.
Sätted
Kirjeldus
CODEC 2 lubatud
Aktiveeri audio moodul
CODEC2 test sagedus
Audio quality/bandwidth tradeoff
PTT klemm
GPIO pin for the push-to-talk button
I2S sõna valik
GPIO sisend I2S WS jaoks
I2S info sisse
GPIO sisend I2S DIN jaoks
I2S info välja
GPIO sisend I2S DOUT jaoks
I2S kell
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO juhtimine kärgvõrgu kaudu. Võimaldab kaugsõlmel lugeda või kirjutada GPIO sisendkontakte teisel sõlmel – kasulik releede aktiveerimiseks, lülitite lugemiseks või välise riistvara kaugjuhtimiseks.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Sätted
Kirjeldus
Kaug riistvara lubatud
Aktiveeri kaugjuurdepääs GPIO-le
Luba määratlemata klemmi juurdepääs
Luba juurdepääs mis tahes GPIO sisendile (turvarisk)
Saadaval klemmid
Kuni 4 GPIO sisendit, mida see sõlm kauglugemiseks/-kirjutamiseks avab
Neighbor Info module
Levitab teavet otse kuuldud naabrite kohta, võimaldades kärgvõrgu topoloogia kaardistamist. Iga lubatud sõlm jagab perioodiliselt nimekirja teistest sõlmedest, mida ta kuuleb ja nende signaali kvaliteedist.
Sätted
Kirjeldus
Naabruskonna teave lubatud
Aktiveeri naabrite leviring
GPS-i küsimise intervall
Kui tihti naabrite nimekirja levitada
Saada LoRa kaudu
Edasta naabriinfot ka LoRa kaudu, mitte ainult MQTT/telefoni kaudu. Vaikimisi võtit ja nime kasutavat kanalit pole saadaval
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Juhib toetatud riistvaral NeoPixeli või muid adresseeritavaid RGB LEDe. Saab kasutada visuaalsete olekuindikaatorite, märgutulede või dekoratiivsete efektide jaoks.
Sätted
Kirjeldus
LED olek
Turn the LED on or off
Pinge
LED current limit (0–31)
Punane / Roheline / Sinine
Individuaalsete värvikanalite väärtused (0–255)
Detection Sensor module
Muudab sõlme liikumis- või ukseanduri hoiatussüsteemiks. Kui GPIO sisend tuvastab oleku muutuse (liikumine tuvastatud, uks avatud), levitab sõlm kärgvõrgu kaudu hoiatusteate.
Sätted
Kirjeldus
Tuvastusandur lubatud
Aktiveeri tuvastusandur
GPIO klemmi jälgimine
GPIO sisend on anduriga ühendatud
Identifitseerimistüüp
Kuidas klemmi olek vastab tuvastussündmusele (nt aktiivne kõrge/madal, serva poolt käivitatav)
Kasuta INPUT_PULLUP režiimi
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimaalne aeg hoiatusteadete levitamisel
State Broadcast Interval
Perioodilise oleku levitamise intervall
Saada kõll koos hoiatussõnumiga
Lisa märguannetesse hoiatuskella sümbol
Kasutajasõbralik nimi
Selle anduri kohandatud nimi
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Loendab lähedalasuvaid seadmeid, kuulates passiivselt sondimistaotlusi, mida telefonid ja sülearvutid võrkude skannimisel edastavad. Available only on ESP32 devices.
Sätted
Kirjeldus
Paxcounter lubatud
Aktiveeri inimeste loendamine
GPS-i küsimise intervall
Kui tihti loendeid esitada
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Vihje: Paxloendur on kasulik jalakäijate liikluse hindamiseks matkaradade alguses, ürituste toimumiskohtades või muudes kohtades. Arvud on ligikaudsed – üks inimene võib kaasas kanda mitut seadet.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Meeskonna teadlikkuse komplekti integratsioon ATAKi ja WinTAKi koostalitlusvõime tagamiseks. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Vaata TAK Integration täpsema seadistamise ja kasutamise kohta.
Puuduta Salvesta – muudatused saadetakse kärgvõrgu kaudu.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Määra aeg
Sends your phone’s clock to the node
Taaskäivita
Restarts the node
Lülita välja
Powers the node down
Tehasesätted
Returns every setting to its factory default
NodeDB lähtestamine
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Varunda ja taasta
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Täpsem
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Tühjenda sõlmede andmebaas
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Arendaja paneel
Avab vahekaardid Paketid ja Rakenduse logid diagnostilise väljundi vaatamiseks, filtreerimiseks ja eksportimiseks. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Teave
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Tänusõnad
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“Sihtsõlmelt ei ole vastust” — sihtsõlm võib olla leviulatusest väljas, võrguühenduseta või sellel võib olla sobimatu administraatori võti. Veendu, et administraatori võti sobiks mõlemas sõlmele.
Muudatused ei rakendu — mõnede sätete jõustumiseks on vaja taaskäivitada. Pärast salvestamist proovi taaskäivitust.
Ei näe kaugseadeid — veendu, et sõlmel oleks sihtsõlme administraatori võti ja et administraatori kanal oleks turbekonfiguratsioonis lubatud. Administraatori kanal seadistatakse automaatselt, kui administraatori võti on määratud.
Kun jokin toimii odottamattomasti, sovelluksen virheenjäljityslokitiedot ovat hyödyllisin liite vikaraporttiin. Meshtastic voi kerätä ne puolestasi suoraan sovelluksessa — niiden keräämiseen ei tarvita adb:tä eikä työpöydän työkaluja.
Jos teet vikailmoituksen, vie lokit (katso Lokien vieminen) ja liitä .txt-tiedosto raporttiisi Meshtastic-Androidin vikaseurannassa. Lokitietotallenne, joka kattaa hetken jolloin ongelma ilmeni, auttaa muuttamaan “ei toimi” -kuvauksen sellaiseksi, jonka kehittäjä pystyy oikeasti selvittämään.
Kaksi välilehteä
Virheenjäljityspaneelissa on kaksi välilehteä:
Paketit — radion lähettämä ja vastaanottama purettu mesh-liikenne (protokollatason viestit). Hyödyllinen mesh-verkon ja reitityksen toiminnan diagnosointiin.
Sovelluslokitiedot — sovelluksen oma diagnostiikkaloki (Androidin logcat), joka sisältää varoitukset, virheet ja pinoseurannat itse sovelluksesta. Tätä tarvitaan yleensä vikaraportissa.
Jokaisella välilehdellä on oma Vie-painikkeensa, ja kumpikin tuottaa oman tiedostonsa. Voit siis liittää raporttiin vain tarvittavan tiedoston tai molemmat.
Sovelluslokitietojen tarkastelu
Sovelluksen lokit -välilehdellä näkyvät tämän sovelluksen uusimmat lokirivit — ei koskaan muiden puhelimesi sovellusten.
Haku — kirjoita hakukenttään suodattaaksesi vastaavat lokirivit.
Tasosuodatin — V / D / I / W / E -painikkeilla voit näyttää tai piilottaa Verbose-, Debug-, Info-, Warn- ja Error-lokirivit. Piilota taso napauttamalla sitä. Napauta uudelleen, niin se tulee takaisin näkyviin. Vakavat virheet näytetään aina.
Päivitä — päivityskuvake lukee uusimmat lokitiedot uudelleen.
Virhe- ja varoitusrivit on korostettu, jotta ongelmat erottuvat paremmin.
Lokien vienti
Napauta latauskuvaketta tallentaaksesi nykyiset lokitiedot tiedostoon. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Liitä tämä tiedosto GitHub-vikaraporttiisi.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Työpöytä
Työpöytäsovelluksessa ei ole järjestelmän logcat-lokitietoa, joten Sovelluslokit-välilehti näyttää sen sijaan sovelluksen itse keräämät lokit. Haku, suodatus ja vienti toimivat samalla tavalla.
Kun jokin toimii odottamattomasti, sovelluksen virheenjäljityslokitiedot ovat hyödyllisin liite vikaraporttiin. Meshtastic voi kerätä ne puolestasi suoraan sovelluksessa — niiden keräämiseen ei tarvita adb:tä eikä työpöydän työkaluja.
Jos teet vikailmoituksen, vie lokit (katso Lokien vieminen) ja liitä .txt-tiedosto raporttiisi Meshtastic-Androidin vikaseurannassa. Lokitietotallenne, joka kattaa hetken jolloin ongelma ilmeni, auttaa muuttamaan “ei toimi” -kuvauksen sellaiseksi, jonka kehittäjä pystyy oikeasti selvittämään.
Kaksi välilehteä
Virheenjäljityspaneelissa on kaksi välilehteä:
Paketit — radion lähettämä ja vastaanottama purettu mesh-liikenne (protokollatason viestit). Hyödyllinen mesh-verkon ja reitityksen toiminnan diagnosointiin.
Sovelluslokitiedot — sovelluksen oma diagnostiikkaloki (Androidin logcat), joka sisältää varoitukset, virheet ja pinoseurannat itse sovelluksesta. Tätä tarvitaan yleensä vikaraportissa.
Jokaisella välilehdellä on oma Vie-painikkeensa, ja kumpikin tuottaa oman tiedostonsa. Voit siis liittää raporttiin vain tarvittavan tiedoston tai molemmat.
Sovelluslokitietojen tarkastelu
Sovelluksen lokit -välilehdellä näkyvät tämän sovelluksen uusimmat lokirivit — ei koskaan muiden puhelimesi sovellusten.
Haku — kirjoita hakukenttään suodattaaksesi vastaavat lokirivit.
Tasosuodatin — V / D / I / W / E -painikkeilla voit näyttää tai piilottaa Verbose-, Debug-, Info-, Warn- ja Error-lokirivit. Piilota taso napauttamalla sitä. Napauta uudelleen, niin se tulee takaisin näkyviin. Vakavat virheet näytetään aina.
Päivitä — päivityskuvake lukee uusimmat lokitiedot uudelleen.
Virhe- ja varoitusrivit on korostettu, jotta ongelmat erottuvat paremmin.
Lokien vienti
Napauta latauskuvaketta tallentaaksesi nykyiset lokitiedot tiedostoon. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Liitä tämä tiedosto GitHub-vikaraporttiisi.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Työpöytä
Työpöytäsovelluksessa ei ole järjestelmän logcat-lokitietoa, joten Sovelluslokit-välilehti näyttää sen sijaan sovelluksen itse keräämät lokit. Haku, suodatus ja vienti toimivat samalla tavalla. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
Tällä sivulla kerrotaan Meshtastic Android -sovelluksen ensimmäisen käynnistyksen käyttöönotosta, mitä kukin käyttöoikeus tarkoittaa ja miten niihin voi palata myöhemmin.
Ensimmäinen käynnistys
Kun avaat sovelluksen ensimmäisen kerran, se ohjaa sinut käyttöönottoon, jossa määritetään tarvittavat käyttöoikeudet ja asetukset. Suorita vaiheet järjestyksessä tai ohita ne — mikään täällä ei ole kertaluonteinen mahdollisuus. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Aloitusnäkymä
Tervetulonäkymä esittelee Meshtasticin kolmella ominaisuusrivillä:
Pysy yhteydessä kaikkialla
Viestitä ilman verkkoyhteyttä ystäviesi ja yhteisösi kanssa ilman matkapuhelinverkkoa.
Luo omat verkkosi
Luo vaivattomasti yksityisiä meshtastic verkkoja turvalliseen ja luotettavaan viestintään kaukana asutuista paikoista.
Seuraa ja jaa sijainteja
Jaa sijaintisi reaaliaikaisesti ja varmista ryhmäsi yhteistoiminta GPS-toimintojen avulla.
Napauta Aloita siirtyäksesi käyttöönottoon.
Käyttöoikeudet
Sovellus pyytää määrityksen aikana useita käyttöoikeuksia. Jokaisella niistä on oma tarkoituksensa, ja osa niistä on välttämättömiä perustoimintojen kannalta.
Bluetooth-käyttöoikeus
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Sijaintikäyttöoikeus
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Käyttöoikeuden pyytäminen kahdesti voisi johtaa tilanteeseen, jossa Android lakkaa näyttämästä valintaikkunaa kokonaan (toinen hylkäys Android 11:ssä, Älä kysy uudelleen -valintaruutu Android 10:ssä ja sitä vanhemmissa versioissa). Android 12:ssa ja uudemmissa versioissa nämä ovat erillisiä: “Lähistön laitteet” on määritelty asetuksella neverForLocation, eikä sijaintikäyttöoikeuden hylkääminen estä radion löytämistä tai siihen yhdistämistä.
Meshtastic käyttää sijaintiasi myös seuraaviin tarkoituksiin:
Sijaintisi näyttäminen mesh-kartalla
Etäisyyksien laskeminen muihin radioihin
GPS-koordinaattiesi jakaminen muiden verkon jäsenten kanssa (jos käytössä)
Myönnä Sovelluksen käytön aikana. Sovellus ei pyydä taustasijaintia — sen manifestissa ei ole ACCESS_BACKGROUND_LOCATION-oikeutta — joten Android ei tarjoa Aina-vaihtoehtoa, ja sijaintipäivitykset tapahtuvat sovelluksen ollessa etualalla tai sen suorittaessa taustapalvelua.
Sijaintikäyttöoikeuden hylkääminen ei estä sovelluksen muuta toimintaa. Android 12:ssa ja uudemmissa versioissa Bluetooth toimii edelleen, ja vain kartta, sijainnin näyttäminen ja sijainnin jakaminen poistuvat käytöstä. Android 11:ssä ja uudemmissa versioissa myös Bluetooth-skannaus estyy, koska Android liittää sen tähän käyttöoikeuteen — lisäksi järjestelmän Sijaintipalvelut on oltava käytössä, jotta skannaus palauttaa tuloksia.
Ilmoituskäyttöoikeus
Ilmoitukset kertovat sinulle:
Saapuvista viesteistä kanavilta ja yksityisviesteistä
Uusista mesh-verkkoon liittyvistä radioista
Etäradion akun vähäisestä virrasta
💡 Vinkki: Voit myöhemmin säätää ilmoitusasetuksia Androidin järjestelmäasetuksissa. Sovellus luo jokaiselle ilmoitusluokalle oman ilmoituskanavan (sekä muutamia sisäisiä kanavia, kuten taustapalvelulle), joten voit ottaa ne käyttöön tai mykistää ne yksitellen.
Kriittisten hälytysten käyttöoikeus
Kriittiset hälytykset ovat korkean prioriteetin ilmoituksia, jotka ohittavat Älä häiritse -tilan — niitä käytetään mesh-verkon hätähälytyksiin ja kiireellisiin viesteihin.
Tämä vaihe ei ole käyttöoikeuspyyntö. Hyväksy/hylkää-valintaikkunaa ei ole: painike avaa Androidin järjestelmäasetusten sivun sovelluksen Hälytykset-ilmoituskanavalle, jossa voit itse ottaa käyttöön Älä häiritse -tilan ohituksen. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Käyttöoikeuksien tarkistaminen myöhemmin
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
Tila
Mitä rivin napauttaminen tekee
Sallittu
Avaa järjestelmän sivun, jossa voit tarkistaa tai peruuttaa käyttöoikeuden
Ei kysytty vielä
Pyytää sitä
Estetty - napauta salliaksesi
Selittää, mihin käyttöoikeutta tarvitaan, ja pyytää sitä uudelleen, jos hyväksyt
Estetty - napauta avataksesi järjestelmäasetukset
Android ei enää näytä käyttöoikeusikkunaa, joten tämä avaa sivun, jossa voit ottaa käyttöoikeuden uudelleen käyttöön
Ei tarvita tässä Android-versiossa
Ei mitään – tätä käyttöoikeutta ei ole laitteessasi
Tämä koskee erityisesti ilmoituksia. Jos hylkäät ne käyttöönoton aikana, tämä rivi toimii paluutienä: Android lakkaa näyttämästä valintaikkunaa, kun olet hylännyt pyynnön lopullisesti (toinen hylkäys), jolloin tämän rivin tilaksi vaihtuu Estetty ja se avaa sen sijaan järjestelmäasetukset. Ilmoituskäyttöoikeutta pyydetään vain Android 13:ssa ja uudemmissa versioissa — vanhemmissa versioissa ilmoitukset ovat oletusarvoisesti käytössä ja niitä hallitaan Androidin omista asetuksista.
Määrityksen jälkeen
Kun olet myöntänyt käyttöoikeudet, sovellus avaa pääkäyttöliittymän. Ensimmäinen toimenpiteesi pitäisi olla yhteyden muodostaminen Meshtastic-radioon — katso Yhteydet yksityiskohtaisia ohjeita varten.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Kaikki käyttöaikaiset käyttöoikeudet näkyvät siellä nykyisessä tilassaan sekä linkkinä niiden hallintaan, mukaan lukien ilmoitukset, joita järjestelmä ei pyydä toista kertaa automaattisesti.
Sovelluksen toiminnot pyytävät käyttöoikeuksia myös tarpeen mukaan. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
Uusi Meshtasticissa? Aloitusopas meshtastic.org-sivustolla käsittelee laitteiston valintaa, radion alkuasetuksia ja ensimmäisen verkon käyttöönottoa.
Tällä sivulla kerrotaan Meshtastic Android -sovelluksen ensimmäisen käynnistyksen käyttöönotosta, mitä kukin käyttöoikeus tarkoittaa ja miten niihin voi palata myöhemmin.
Ensimmäinen käynnistys
Kun avaat sovelluksen ensimmäisen kerran, se ohjaa sinut käyttöönottoon, jossa määritetään tarvittavat käyttöoikeudet ja asetukset. Suorita vaiheet järjestyksessä tai ohita ne — mikään täällä ei ole kertaluonteinen mahdollisuus. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Aloitusnäkymä
Tervetulonäkymä esittelee Meshtasticin kolmella ominaisuusrivillä:
Pysy yhteydessä kaikkialla
Viestitä ilman verkkoyhteyttä ystäviesi ja yhteisösi kanssa ilman matkapuhelinverkkoa.
Luo omat verkkosi
Luo vaivattomasti yksityisiä meshtastic verkkoja turvalliseen ja luotettavaan viestintään kaukana asutuista paikoista.
Seuraa ja jaa sijainteja
Jaa sijaintisi reaaliaikaisesti ja varmista ryhmäsi yhteistoiminta GPS-toimintojen avulla.
Napauta Aloita siirtyäksesi käyttöönottoon.
Käyttöoikeudet
Sovellus pyytää määrityksen aikana useita käyttöoikeuksia. Jokaisella niistä on oma tarkoituksensa, ja osa niistä on välttämättömiä perustoimintojen kannalta.
Bluetooth-käyttöoikeus
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Sijaintikäyttöoikeus
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Käyttöoikeuden pyytäminen kahdesti voisi johtaa tilanteeseen, jossa Android lakkaa näyttämästä valintaikkunaa kokonaan (toinen hylkäys Android 11:ssä, Älä kysy uudelleen -valintaruutu Android 10:ssä ja sitä vanhemmissa versioissa). Android 12:ssa ja uudemmissa versioissa nämä ovat erillisiä: “Lähistön laitteet” on määritelty asetuksella neverForLocation, eikä sijaintikäyttöoikeuden hylkääminen estä radion löytämistä tai siihen yhdistämistä.
Meshtastic käyttää sijaintiasi myös seuraaviin tarkoituksiin:
Sijaintisi näyttäminen mesh-kartalla
Etäisyyksien laskeminen muihin radioihin
GPS-koordinaattiesi jakaminen muiden verkon jäsenten kanssa (jos käytössä)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Myönnä Sovelluksen käytön aikana. Sovellus ei pyydä taustasijaintia — sen manifestissa ei ole ACCESS_BACKGROUND_LOCATION-oikeutta — joten Android ei tarjoa Aina-vaihtoehtoa, ja sijaintipäivitykset tapahtuvat sovelluksen ollessa etualalla tai sen suorittaessa taustapalvelua.
Sijaintikäyttöoikeuden hylkääminen ei estä sovelluksen muuta toimintaa. Android 12:ssa ja uudemmissa versioissa Bluetooth toimii edelleen, ja vain kartta, sijainnin näyttäminen ja sijainnin jakaminen poistuvat käytöstä. Android 11:ssä ja uudemmissa versioissa myös Bluetooth-skannaus estyy, koska Android liittää sen tähän käyttöoikeuteen — lisäksi järjestelmän Sijaintipalvelut on oltava käytössä, jotta skannaus palauttaa tuloksia.
Ilmoituskäyttöoikeus
Ilmoitukset kertovat sinulle:
Saapuvista viesteistä kanavilta ja yksityisviesteistä
Uusista mesh-verkkoon liittyvistä radioista
Etäradion akun vähäisestä virrasta
💡 Vinkki: Voit myöhemmin säätää ilmoitusasetuksia Androidin järjestelmäasetuksissa. Sovellus luo jokaiselle ilmoitusluokalle oman ilmoituskanavan (sekä muutamia sisäisiä kanavia, kuten taustapalvelulle), joten voit ottaa ne käyttöön tai mykistää ne yksitellen.
Kriittisten hälytysten käyttöoikeus
Kriittiset hälytykset ovat korkean prioriteetin ilmoituksia, jotka ohittavat Älä häiritse -tilan — niitä käytetään mesh-verkon hätähälytyksiin ja kiireellisiin viesteihin.
Tämä vaihe ei ole käyttöoikeuspyyntö. Hyväksy/hylkää-valintaikkunaa ei ole: painike avaa Androidin järjestelmäasetusten sivun sovelluksen Hälytykset-ilmoituskanavalle, jossa voit itse ottaa käyttöön Älä häiritse -tilan ohituksen. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Käyttöoikeuksien tarkistaminen myöhemmin
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
Tila
Mitä rivin napauttaminen tekee
Sallittu
Avaa järjestelmän sivun, jossa voit tarkistaa tai peruuttaa käyttöoikeuden
Ei kysytty vielä
Pyytää sitä
Estetty - napauta salliaksesi
Selittää, mihin käyttöoikeutta tarvitaan, ja pyytää sitä uudelleen, jos hyväksyt
Estetty - napauta avataksesi järjestelmäasetukset
Android ei enää näytä käyttöoikeusikkunaa, joten tämä avaa sivun, jossa voit ottaa käyttöoikeuden uudelleen käyttöön
Ei tarvita tässä Android-versiossa
Ei mitään – tätä käyttöoikeutta ei ole laitteessasi
Tämä koskee erityisesti ilmoituksia. Jos hylkäät ne käyttöönoton aikana, tämä rivi toimii paluutienä: Android lakkaa näyttämästä valintaikkunaa, kun olet hylännyt pyynnön lopullisesti (toinen hylkäys), jolloin tämän rivin tilaksi vaihtuu Estetty ja se avaa sen sijaan järjestelmäasetukset. Ilmoituskäyttöoikeutta pyydetään vain Android 13:ssa ja uudemmissa versioissa — vanhemmissa versioissa ilmoitukset ovat oletusarvoisesti käytössä ja niitä hallitaan Androidin omista asetuksista.
Määrityksen jälkeen
Kun olet myöntänyt käyttöoikeudet, sovellus avaa pääkäyttöliittymän. Ensimmäinen toimenpiteesi pitäisi olla yhteyden muodostaminen Meshtastic-radioon — katso Yhteydet yksityiskohtaisia ohjeita varten.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Kaikki käyttöaikaiset käyttöoikeudet näkyvät siellä nykyisessä tilassaan sekä linkkinä niiden hallintaan, mukaan lukien ilmoitukset, joita järjestelmä ei pyydä toista kertaa automaattisesti.
Sovelluksen toiminnot pyytävät käyttöoikeuksia myös tarpeen mukaan. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
Uusi Meshtasticissa? Aloitusopas meshtastic.org-sivustolla käsittelee laitteiston valintaa, radion alkuasetuksia ja ensimmäisen verkon käyttöönottoa.
Määritä valinnaiset ominaisuusmoduulit ja suorita laitteen ylläpitotoimia. Moduulit laajentavat Meshtasticia erikoisominaisuuksilla — jokainen voidaan ottaa käyttöön tai poistaa käytöstä erikseen.
💡 Vinkki: Ota käyttöön vain ne moduulit, joita todella käytät. Käyttämättömien moduulien poistaminen käytöstä vähentää lähetyksen käyttöastetta, säästää akkua ja yksinkertaistaa määrityksiä. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Moduuliasetukset käyttävät korttipohjaista asettelua, jossa on kytkimiä, pudotusvalikoita, tekstikenttiä ja liukusäätimiä:
Moduulin asetukset
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Yhdistää verkon viestejä MQTT-välityspalvelimeen ja sieltä takaisin internet-yhteyksiä varten. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Asetus
Kuvaus
MQTT käytössä
Ota MQTT-välityspalvelin käyttöön
Osoite
MQTT-välityspalvelimen osoite
Käyttäjänimi
Todennuksen käyttäjätunnus
Salasana
Todennuksen salasana
Salaus käytössä
Salaa MQTT-viestisisällöt
JSON ulostulo käytössä
Julkaise ja vastaanota MQTT-viestejä JSON-muodossa. Merkitty protobuf-rakenteessa vanhentuneeksi, mutta tämä on edelleen ainoa asetus tähän toimintaan, ja laiteohjelmisto käyttää sitä yhä
TLS käytössä
Käytä suojattua yhteyttä
Palvelimen osoite (root topic)
MQTT:n perusaihepolku
Välityspalvelin käytössä
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. Katso MQTT
Karttaraportointi
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Asetus
Kuvaus
Hyväksyn.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
Kuinka usein sijainti julkaistaan. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
Katso MQTT saadaksesi yksityiskohtaisen käyttöoppaan, joka sisältää salauksen, tietosuojan ja välityspalvelimen määrityksen.
Serial module
Mahdollistaa sarjaporttiviestinnän ulkoisten laiteintegraatioiden kanssa (GPS-moduulit, anturit tai mukautettu laitteisto). Kun tämä on käytössä, radion sarjaportti voi lähettää ja vastaanottaa protobuf- tai tekstimuotoista dataa, jolloin ulkoiset mikrokontrollerit tai tietokoneet voivat olla vuorovaikutuksessa verkon kanssa.
Asetus
Kuvaus
Sarjaportti käytössä
Ota sarjaporttiviestintä käyttöön
Palautus päällä
Toista vastaanotettu sarjaporttidata takaisin
Sarjaportin tila
Portin käyttämä protokolla – Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, YE.Direct, MeshSolar config, Log tai Log (vain teksti)
Vastaanotto / lähetys
Sarjayhteyden GPIO-nastat
Sarjaportin nopeus
Portin nopeus
Aikakatkaisu
Kuinka kauan odotetaan ennen kuin saapuva viesti katsotaan kokonaiseksi
Korvaa konsolin sarjaportti
Ota käyttöön portti, jota virheenkorjauskonsoli normaalisti käyttää
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Hyödyllinen laitteille, joiden täytyy ilmoittaa fyysisesti viestin saapumisesta — erityisen hyödyllinen valvomattomissa tai ulkokäyttöön asennetuissa laitteissa.
Käynnistimiä on kaksi – saapuva viesti ja vastaanotettu BEL-ohjausmerkki – ja kumpikin voi ohjata LED-valoa, summeria ja värinämoottoria erikseen, joten käytettävissä on kuusi kytkintä.
Asetus
Kuvaus
Ulkoiset ilmoitukset käytössä
Moduulin pääkytkin
Hälytysviesti: LED / summeri / värinä
Mitkä lähdöt aktivoituvat saapuvasta viestistä
Hälytysmerkki: LED / summeri / värinä
Mitkä lähdöt aktivoituvat vastaanotetusta BEL-ohjausmerkistä
Ulostulon LED (GPIO)
LED on kytketty nastaan
Ulostulon LED aktiivinen
Onko LED-nasta aktiivinen korkealla vai matalalla tasolla
Ulostulon äänimerkki (GPIO)
Summeri on kytketty nastaan
Ulostulon värinä (GPIO)
Värinämoottori on kytketty nastaan
Käytä PWM-äänimerkkiä
Ohjaa summeria PWM:llä, jolloin voidaan toistaa ääniä yhden kiinteän taajuuden sijaan
Käytä I2S protokollaa äänimerkille
Lähetä hälytys sen sijaan I2S-äänilähdön kautta
GPIO Output Duration
Kuinka kauan yksittäinen hälytys kestää
Toistokehotuksen aikakatkaisu
Toista hälytystä tämän ajan, kunnes se kuitataan. 0 poistaa toistuvan muistutuksen käytöstä
Soittoääni
PWM-summerilla toistettava RTTTL-soittoääni. Voidaan tuoda tiedostosta
Store & Forward module
Puskuroi viestejä radioille, jotka ovat tilapäisesti poissa verkosta, ja toimittaa ne, kun nämä radiot yhdistyvät uudelleen. Välttämätön verkoissa, joissa radiot siirtyvät säännöllisesti kuuluvuusalueelle ja sen ulkopuolelle — varmistaa, etteivät viestit katoa lyhyiden yhteyskatkosten aikana.
Asetus
Kuvaus
Tallenna ja lähetä edelleen
Ota Varastoi & välitä käyttöön
Valvontasignaali
Ilmoita tämän radion varastoi & välitä -ominaisuudesta säännöllisesti
Kirjausten määrä
Tallennettujen viestien enimmäismäärä
Historian maksimimäärä
Toistettavien viestien enimmäismäärä
Historian aikamäärä
Aikaikkuna viestien toistolle
Palvelin
Toimi mesh-verkon varastoi & välitä -palvelimena (edellyttää riittävästi muistia, esimerkiksi ESP32 PSRAM:lla)
💡 Vinkki: Varastoi & välitä toimii parhaiten radioissa, joissa on runsaasti muistia (ESP32 ja PSRAM). Router-roolin radiot ovat ihanteellisia ehdokkaita, koska ne ovat yleensä jatkuvasti käynnissä.
Range Test module
⚠️ Varoitus: Kuuluvuustesti toimii vain suojatulla ensisijaisella kanavalla. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automaattinen kuuluvuustestityökalu radioiden välisen yhteyden laadun arviointiin. Kun toiminto on käytössä, radio lähettää säännöllisesti testiviestejä kasvavilla laskuriarvoilla. Vastaanottava radio kirjaa nämä viestit, jolloin voit myöhemmin kävellä tai ajaa pois ja analysoida, millä etäisyydellä viestien saapuminen loppui.
Asetus
Kuvaus
Kuuluvuustesti käytössä
Ota kuuluvuustesti käyttöön
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Tallenna .CSV (ESP32 ainoastaan)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Määrittää, mitä telemetriatietoja radiosi jakaa verkkoon. Telemetria sisältää laitteen kuntoon liittyviä tietoja (akun varaustaso, käyttöaika) sekä ympäristöanturien tietoja (lämpötila, kosteus, ilmanpaine).
Jokaisella neljällä mittausryhmällä on oma käyttöönottokytkin ja oma mittausväli, joten esimerkiksi akun tila voidaan raportoida usein ja anturitiedot harvemmin.
Asetus
Kuvaus
Lähetä laitteen telemetriatiedot
Laitemittausten pääkytkin. Näkyy vain laiteohjelmistoversiossa 2.7.12 ja uudemmissa
Laitemittareiden päivitysväli
How often to report battery, uptime and channel utilization
Ympäristötietojen moduuli käytössä
Raportoi liitettyjen ympäristöanturien tiedot
Ympäristömittareiden päivitysväli
Kuinka usein tiedot raportoidaan
Näytä ympäristötiedot näytöllä
Näytä nämä tiedot myös radion omalla näytöllä
Käytä Fahrenheit yksikköä
Käytä radion näytössä Fahrenheit-asteita. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Ilmanlaadun tietojen moduuli käytössä
Raportoi hiukkas- ja CO₂-anturin tiedot
Ilmanlaatumittareiden päivitysväli
Kuinka usein tiedot raportoidaan
Virrankulutuksen moduuli käytössä
Raportoi kanavakohtaiset jännite- ja virtamittaukset
Virtamittareiden päivitysväli
Kuinka usein tiedot raportoidaan
Virrankulutuksen näyttö käytössä
Näytä virtamittaukset myös radion omalla näytöllä
Katso Telemetria ja anturit saadaksesi tietoa tuetuista antureista ja määrityssuosituksista.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Määritä luettelo pikaviesteistä, jotka voidaan lähettää ilman yhdistettyä puhelinta — ihanteellinen kenttäkäyttöön.
Asetus
Kuvaus
Valmisviesti käytössä
⚠️ Vanhentunut protobuf-rakenteessa
Viestit
Rivinvaihdoilla eroteltu viestiluettelo
Lähetä äänimerkki
Lähetä viestin mukana BEL-ohjausmerkki, jotta vastaanottavan radion Ulkoiset ilmoitukset -moduuli voi antaa hälytyksen
Kiertovalitsin #1 käytössä
Käytä kiertokoodainta syöttölaitteena
GPIO pin for rotary encoder A / B / Press port
Kolme nastaa, joihin kiertokoodain on kytketty
Generate input event on Press / CW / CCW
Minkä näppäintapahtuman kukin kiertokoodaimen toiminto tuottaa
Ylös/Alas/Valitse syöte käytössä
Erillinen, yksinkertaisempi syöttötapa, jossa käytetään ylös-/alas-/valitse-painikkeita kiertokoodaimen sijaan
Salli syöttölähde
⚠️ Vanhentunut protobuf-rakenteessa
Audio module
Codec2-äänituki matalan kaistanleveyden puheviestintään verkossa. Tämä on kokeellinen ominaisuus, joka koodaa puheen erittäin pieniksi datapaketeiksi käyttäen Codec2-koodekkia.
Asetus
Kuvaus
CODEC 2 käytössä
Ota äänimoduuli käyttöön
CODEC2 näytteenottotaajuus
Äänenlaadun ja kaistanleveyden välinen kompromissi
PTT-pinni
PTT-painikkeen GPIO-nasta
I2S-sanan valinta
GPIO-pinni I2S WS:lle
I2S-datatulo
GPIO-nasta I2S DIN:lle
I2S-datalähtö
GPIO-pinni I2S DOUT:lle
I2S-kello
I2S-bittikellon GPIO-nasta
ℹ️ Huomautus: Ääniominaisuus edellyttää yhteensopivaa laitteistoa (I2S-mikrofoni ja -kaiutin). Äänenlaatu on hyvin matalakaistainen — ajattele “ymmärrettävää radiopuhetta”, ei puhelinlaatua.
Remote Hardware module
GPIO-ohjaus mesh-verkon kautta. Mahdollistaa etäradion lukea tai kirjoittaa GPIO-nastoja toisessa radiossa — hyödyllinen releiden aktivointiin, kytkimien lukemiseen tai ulkoisen laitteiston ohjaamiseen etäältä.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Asetus
Kuvaus
Etälaitteen ohjaus käytössä
Ota etä-GPIO-käyttö käyttöön
Salli määrittämättömän pinnin käyttö
Salli pääsy mihin tahansa GPIO-nastaan (tietoturvariski)
Käytettävissä olevat pinnit
Enintään 4 tämän radion etälukuun tai kirjoitukseen tarjoamaa GPIO-pinniä
Neighbor Info module
Lähettää tietoa suoraan kuulluista naapureista mahdollistaen verkon topologian kartoituksen. Jokainen käyttöön otettu radio jakaa säännöllisesti luettelon muista radioista, jotka se kuulee, sekä niiden signaalin laadun.
Asetus
Kuvaus
Naapuritiedot käytössä
Ota naapuritiedon lähetys käyttöön
GPS-kyselyn aikaväli
Kuinka usein naapuriluettelo lähetetään
Lähetä LoRa:n kautta
Lähetä myös naapuritiedot LoRa:n kautta, ei pelkästään MQTT:n tai puhelimen kautta. Ei käytettävissä kanavalla, joka käyttää oletusavainta ja nimeä
Katso Paikallinen mesh-haku, miten naapuritietoja käytetään mesh-verkon rakenteen tutkimiseen.
Ambient Lighting module
Ohjaa tuetuissa laitteissa olevaa NeoPixeliä tai muita osoitteellisia RGB-LEDejä. Voidaan käyttää visuaalisina tilailmaisimina, ilmoitusvaloina tai koriste-efekteinä.
Asetus
Kuvaus
LED-tila
Kytke LED päälle tai pois päältä
Virta
LED-virran rajoitus (0–31)
Punainen / vihreä / sininen
Yksittäisten värikanavien arvot (0–255)
Detection Sensor module
Muuttaa radiosi liike- tai ovitunnistimeen perustuvaksi hälytysjärjestelmäksi. Kun GPIO-pinni havaitsee tilamuutoksen (liike havaittu, ovi avattu), radio lähettää hälytysviestin verkkoon.
Asetus
Kuvaus
Tunnistinsensori käytössä
Ota tunnistusanturi käyttöön
GPIO-pinni valvontaa varten
Anturiin kytketty GPIO-pinni
Tunnistuksen tyyppi
Miten pinnin tila vastaa havaitsemistapahtumaa (esim. aktiivinen korkea/matala taso tai reunalaukaisu)
Käytä INPUT_PULLUP tilaa
Ota pinnin sisäinen ylösvetovastus käyttöön
Minimum time between detection broadcasts
Hälytyslähetysten vähimmäisaika
State Broadcast Interval
Tilatiedon lähetysväli
Lähetä äänimerkki hälytyssanoman kanssa
Sisällytä soittomerkkimerkki hälytyksiin
Käyttäjäystävällinen nimi
Tälle anturille määritetty nimi
Paxcounter module
Henkilöt, jotka lasketaan WiFi- ja BLE-hakukyselyiden perusteella. Laskee lähellä olevia laitteita kuuntelemalla passiivisesti koepyyntöjä, joita puhelimet ja kannettavat tietokoneet lähettävät etsiessään verkkoja. Saatavilla vain ESP32-laitteissa.
Asetus
Kuvaus
PAX-laskuri käytössä
Ota henkilölaskenta käyttöön
GPS-kyselyn aikaväli
Kuinka usein laskentatiedot raportoidaan
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
Sama raja-arvo BLE-mainospaketeille (oletus: -80 dBm)
💡 Vinkki: PAX-laskuri on hyödyllinen jalankulkijamäärien arviointiin retkeilyreittien lähtöpisteissä, tapahtumapaikoilla tai muissa kohteissa. Laskentatulokset ovat arvioita — yhdellä henkilöllä voi olla useita laitteita mukana.
Status Message module
Tilaviestillä ei ole omaa moduulinäkymää. Sitä muokataan yhdessä muiden radion tunnistetietojen kanssa kohdassa Asetukset → Radio ja käyttäjä.
Mesh Beacon module
Lähettää kutsun mesh-verkkoosi ja vastaanottaa muiden lähettämiä kutsuja. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit -integraatio yhteensopivuutta varten ATAK- ja WinTAK-järjestelmien kanssa. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Katso TAK-integraatio saadaksesi tarkemmat määritys- ja käyttöohjeet.
Ylläpito
Etähallinta
Määritä etänä radiot, jotka jakavat saman ylläpitoavaimen:
Valitse kohderadio radioluettelosta.
Siirry kyseisen radion Asetukset-kohtaan.
Muokkaa määrityksiä.
Napauta Tallenna — muutokset lähetetään verkon kautta.
⚠️ Tärkeää: Edellyttää, että järjestelmänvalvojan avain on määritetty sekä omassa radiossasi että kohderadiossa.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Toiminto
Mitä se tekee
Aseta aika
Sends your phone’s clock to the node
Käynnistä uudelleen
Restarts the node
Sammuta
Powers the node down
Palauta tehdasasetukset
Returns every setting to its factory default
Tyhjennä NodeDB-tietokanta
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Varmuuskopiointi ja palautus
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Lisäasetukset
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Tyhjennä NodeDB-tietokanta
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Vianetsintäpaneeli
Avaa Paketit- ja Sovelluslokit-välilehdet diagnostiikkatietojen tarkastelua, suodatusta ja vientiä varten. Katso Virheenjäljityslokit, jossa on täydellinen käyttöohje.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Tietoja
Settings → About carries the app’s own identity rather than the node’s:
Kolme osiota:
Mikä on Meshtastic? – lyhyt kuvaus projektista.
Sovellukset — avaa Tarvitsetko laitteiston? -näkymän, jossa on suosittujen laitteiden karuselli ja linkit niiden ostopaikkoihin. Siellä näytetään myös GitHub-tietovarasto, käytössä oleva sovellusversio ja Tekijätiedot (katso seuraava osio).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Kiitokset
Tietoja-kohdasta avattava näkymä, jossa luetellaan kaikki sovelluksen käyttämät avoimen lähdekoodin kirjastot lisensseineen. Luettelo luodaan käännöshetkellä AboutLibraries-kirjastolla. Tätä kutsuttiin aiemmin lisenssinäkymäksi.
Troubleshooting remote admin
Ei vastausta kohderadiolta — kohderadio voi olla kuuluvuusalueen ulkopuolella, poissa verkosta tai siinä voi olla eri ylläpitoavain. Varmista, että ylläpitoavain on sama molemmissa radioissa.
Muutokset eivät tule voimaan — jotkin asetukset edellyttävät uudelleenkäynnistystä ennen kuin ne astuvat voimaan. Kokeile Uudelleenkäynnistystä tallennuksen jälkeen.
Et näe etäasetuksia — varmista, että radiossasi on kohderadion ylläpitoavain. Ylläpitokanava määritetään automaattisesti, kun ylläpitoavain on asetettu.
Määritä valinnaiset ominaisuusmoduulit ja suorita laitteen ylläpitotoimia. Moduulit laajentavat Meshtasticia erikoisominaisuuksilla — jokainen voidaan ottaa käyttöön tai poistaa käytöstä erikseen.
💡 Vinkki: Ota käyttöön vain ne moduulit, joita todella käytät. Käyttämättömien moduulien poistaminen käytöstä vähentää lähetyksen käyttöastetta, säästää akkua ja yksinkertaistaa määrityksiä. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Moduuliasetukset käyttävät korttipohjaista asettelua, jossa on kytkimiä, pudotusvalikoita, tekstikenttiä ja liukusäätimiä:
Moduulin asetukset
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Yhdistää verkon viestejä MQTT-välityspalvelimeen ja sieltä takaisin internet-yhteyksiä varten. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Asetus
Kuvaus
MQTT käytössä
Ota MQTT-välityspalvelin käyttöön
Osoite
MQTT-välityspalvelimen osoite
Käyttäjänimi
Todennuksen käyttäjätunnus
Salasana
Todennuksen salasana
Salaus käytössä
Salaa MQTT-viestisisällöt
JSON ulostulo käytössä
Julkaise ja vastaanota MQTT-viestejä JSON-muodossa. Merkitty protobuf-rakenteessa vanhentuneeksi, mutta tämä on edelleen ainoa asetus tähän toimintaan, ja laiteohjelmisto käyttää sitä yhä
TLS käytössä
Käytä suojattua yhteyttä
Palvelimen osoite (root topic)
MQTT:n perusaihepolku
Välityspalvelin käytössä
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. Katso MQTT
Karttaraportointi
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Asetus
Kuvaus
Hyväksyn.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
Kuinka usein sijainti julkaistaan. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
Katso MQTT saadaksesi yksityiskohtaisen käyttöoppaan, joka sisältää salauksen, tietosuojan ja välityspalvelimen määrityksen.
Serial module
Mahdollistaa sarjaporttiviestinnän ulkoisten laiteintegraatioiden kanssa (GPS-moduulit, anturit tai mukautettu laitteisto). Kun tämä on käytössä, radion sarjaportti voi lähettää ja vastaanottaa protobuf- tai tekstimuotoista dataa, jolloin ulkoiset mikrokontrollerit tai tietokoneet voivat olla vuorovaikutuksessa verkon kanssa.
Asetus
Kuvaus
Sarjaportti käytössä
Ota sarjaporttiviestintä käyttöön
Palautus päällä
Toista vastaanotettu sarjaporttidata takaisin
Sarjaportin tila
Portin käyttämä protokolla – Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, YE.Direct, MeshSolar config, Log tai Log (vain teksti)
Vastaanotto / lähetys
Sarjayhteyden GPIO-nastat
Sarjaportin nopeus
Portin nopeus
Aikakatkaisu
Kuinka kauan odotetaan ennen kuin saapuva viesti katsotaan kokonaiseksi
Korvaa konsolin sarjaportti
Ota käyttöön portti, jota virheenkorjauskonsoli normaalisti käyttää
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Hyödyllinen laitteille, joiden täytyy ilmoittaa fyysisesti viestin saapumisesta — erityisen hyödyllinen valvomattomissa tai ulkokäyttöön asennetuissa laitteissa.
Käynnistimiä on kaksi – saapuva viesti ja vastaanotettu BEL-ohjausmerkki – ja kumpikin voi ohjata LED-valoa, summeria ja värinämoottoria erikseen, joten käytettävissä on kuusi kytkintä.
Asetus
Kuvaus
Ulkoiset ilmoitukset käytössä
Moduulin pääkytkin
Hälytysviesti: LED / summeri / värinä
Mitkä lähdöt aktivoituvat saapuvasta viestistä
Hälytysmerkki: LED / summeri / värinä
Mitkä lähdöt aktivoituvat vastaanotetusta BEL-ohjausmerkistä
Ulostulon LED (GPIO)
LED on kytketty nastaan
Ulostulon LED aktiivinen
Onko LED-nasta aktiivinen korkealla vai matalalla tasolla
Ulostulon äänimerkki (GPIO)
Summeri on kytketty nastaan
Ulostulon värinä (GPIO)
Värinämoottori on kytketty nastaan
Käytä PWM-äänimerkkiä
Ohjaa summeria PWM:llä, jolloin voidaan toistaa ääniä yhden kiinteän taajuuden sijaan
Käytä I2S protokollaa äänimerkille
Lähetä hälytys sen sijaan I2S-äänilähdön kautta
GPIO Output Duration
Kuinka kauan yksittäinen hälytys kestää
Toistokehotuksen aikakatkaisu
Toista hälytystä tämän ajan, kunnes se kuitataan. 0 poistaa toistuvan muistutuksen käytöstä
Soittoääni
PWM-summerilla toistettava RTTTL-soittoääni. Voidaan tuoda tiedostosta
Store & Forward module
Puskuroi viestejä radioille, jotka ovat tilapäisesti poissa verkosta, ja toimittaa ne, kun nämä radiot yhdistyvät uudelleen. Välttämätön verkoissa, joissa radiot siirtyvät säännöllisesti kuuluvuusalueelle ja sen ulkopuolelle — varmistaa, etteivät viestit katoa lyhyiden yhteyskatkosten aikana.
Asetus
Kuvaus
Tallenna ja lähetä edelleen
Ota Varastoi & välitä käyttöön
Valvontasignaali
Ilmoita tämän radion varastoi & välitä -ominaisuudesta säännöllisesti
Kirjausten määrä
Tallennettujen viestien enimmäismäärä
Historian maksimimäärä
Toistettavien viestien enimmäismäärä
Historian aikamäärä
Aikaikkuna viestien toistolle
Palvelin
Toimi mesh-verkon varastoi & välitä -palvelimena (edellyttää riittävästi muistia, esimerkiksi ESP32 PSRAM:lla)
💡 Vinkki: Varastoi & välitä toimii parhaiten radioissa, joissa on runsaasti muistia (ESP32 ja PSRAM). Router-roolin radiot ovat ihanteellisia ehdokkaita, koska ne ovat yleensä jatkuvasti käynnissä.
Range Test module
⚠️ Varoitus: Kuuluvuustesti toimii vain suojatulla ensisijaisella kanavalla. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automaattinen kuuluvuustestityökalu radioiden välisen yhteyden laadun arviointiin. Kun toiminto on käytössä, radio lähettää säännöllisesti testiviestejä kasvavilla laskuriarvoilla. Vastaanottava radio kirjaa nämä viestit, jolloin voit myöhemmin kävellä tai ajaa pois ja analysoida, millä etäisyydellä viestien saapuminen loppui.
Asetus
Kuvaus
Kuuluvuustesti käytössä
Ota kuuluvuustesti käyttöön
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Tallenna .CSV (ESP32 ainoastaan)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Määrittää, mitä telemetriatietoja radiosi jakaa verkkoon. Telemetria sisältää laitteen kuntoon liittyviä tietoja (akun varaustaso, käyttöaika) sekä ympäristöanturien tietoja (lämpötila, kosteus, ilmanpaine).
Jokaisella neljällä mittausryhmällä on oma käyttöönottokytkin ja oma mittausväli, joten esimerkiksi akun tila voidaan raportoida usein ja anturitiedot harvemmin.
Asetus
Kuvaus
Lähetä laitteen telemetriatiedot
Laitemittausten pääkytkin. Näkyy vain laiteohjelmistoversiossa 2.7.12 ja uudemmissa
Laitemittareiden päivitysväli
How often to report battery, uptime and channel utilization
Ympäristötietojen moduuli käytössä
Raportoi liitettyjen ympäristöanturien tiedot
Ympäristömittareiden päivitysväli
Kuinka usein tiedot raportoidaan
Näytä ympäristötiedot näytöllä
Näytä nämä tiedot myös radion omalla näytöllä
Käytä Fahrenheit yksikköä
Käytä radion näytössä Fahrenheit-asteita. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Ilmanlaadun tietojen moduuli käytössä
Raportoi hiukkas- ja CO₂-anturin tiedot
Ilmanlaatumittareiden päivitysväli
Kuinka usein tiedot raportoidaan
Virrankulutuksen moduuli käytössä
Raportoi kanavakohtaiset jännite- ja virtamittaukset
Virtamittareiden päivitysväli
Kuinka usein tiedot raportoidaan
Virrankulutuksen näyttö käytössä
Näytä virtamittaukset myös radion omalla näytöllä
Katso Telemetria ja anturit saadaksesi tietoa tuetuista antureista ja määrityssuosituksista.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Määritä luettelo pikaviesteistä, jotka voidaan lähettää ilman yhdistettyä puhelinta — ihanteellinen kenttäkäyttöön.
Asetus
Kuvaus
Valmisviesti käytössä
⚠️ Vanhentunut protobuf-rakenteessa
Viestit
Rivinvaihdoilla eroteltu viestiluettelo
Lähetä äänimerkki
Lähetä viestin mukana BEL-ohjausmerkki, jotta vastaanottavan radion Ulkoiset ilmoitukset -moduuli voi antaa hälytyksen
Kiertovalitsin #1 käytössä
Käytä kiertokoodainta syöttölaitteena
GPIO pin for rotary encoder A / B / Press port
Kolme nastaa, joihin kiertokoodain on kytketty
Generate input event on Press / CW / CCW
Minkä näppäintapahtuman kukin kiertokoodaimen toiminto tuottaa
Ylös/Alas/Valitse syöte käytössä
Erillinen, yksinkertaisempi syöttötapa, jossa käytetään ylös-/alas-/valitse-painikkeita kiertokoodaimen sijaan
Salli syöttölähde
⚠️ Vanhentunut protobuf-rakenteessa
Audio module
Codec2-äänituki matalan kaistanleveyden puheviestintään verkossa. Tämä on kokeellinen ominaisuus, joka koodaa puheen erittäin pieniksi datapaketeiksi käyttäen Codec2-koodekkia.
Asetus
Kuvaus
CODEC 2 käytössä
Ota äänimoduuli käyttöön
CODEC2 näytteenottotaajuus
Äänenlaadun ja kaistanleveyden välinen kompromissi
PTT-pinni
PTT-painikkeen GPIO-nasta
I2S-sanan valinta
GPIO-pinni I2S WS:lle
I2S-datatulo
GPIO-nasta I2S DIN:lle
I2S-datalähtö
GPIO-pinni I2S DOUT:lle
I2S-kello
I2S-bittikellon GPIO-nasta
ℹ️ Huomautus: Ääniominaisuus edellyttää yhteensopivaa laitteistoa (I2S-mikrofoni ja -kaiutin). Äänenlaatu on hyvin matalakaistainen — ajattele “ymmärrettävää radiopuhetta”, ei puhelinlaatua.
Remote Hardware module
GPIO-ohjaus mesh-verkon kautta. Mahdollistaa etäradion lukea tai kirjoittaa GPIO-nastoja toisessa radiossa — hyödyllinen releiden aktivointiin, kytkimien lukemiseen tai ulkoisen laitteiston ohjaamiseen etäältä.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Asetus
Kuvaus
Etälaitteen ohjaus käytössä
Ota etä-GPIO-käyttö käyttöön
Salli määrittämättömän pinnin käyttö
Salli pääsy mihin tahansa GPIO-nastaan (tietoturvariski)
Käytettävissä olevat pinnit
Enintään 4 tämän radion etälukuun tai kirjoitukseen tarjoamaa GPIO-pinniä
Neighbor Info module
Lähettää tietoa suoraan kuulluista naapureista mahdollistaen verkon topologian kartoituksen. Jokainen käyttöön otettu radio jakaa säännöllisesti luettelon muista radioista, jotka se kuulee, sekä niiden signaalin laadun.
Asetus
Kuvaus
Naapuritiedot käytössä
Ota naapuritiedon lähetys käyttöön
GPS-kyselyn aikaväli
Kuinka usein naapuriluettelo lähetetään
Lähetä LoRa:n kautta
Lähetä myös naapuritiedot LoRa:n kautta, ei pelkästään MQTT:n tai puhelimen kautta. Ei käytettävissä kanavalla, joka käyttää oletusavainta ja nimeä
Katso Paikallinen mesh-haku, miten naapuritietoja käytetään mesh-verkon rakenteen tutkimiseen.
Ambient Lighting module
Ohjaa tuetuissa laitteissa olevaa NeoPixeliä tai muita osoitteellisia RGB-LEDejä. Voidaan käyttää visuaalisina tilailmaisimina, ilmoitusvaloina tai koriste-efekteinä.
Asetus
Kuvaus
LED-tila
Kytke LED päälle tai pois päältä
Virta
LED-virran rajoitus (0–31)
Punainen / vihreä / sininen
Yksittäisten värikanavien arvot (0–255)
Detection Sensor module
Muuttaa radiosi liike- tai ovitunnistimeen perustuvaksi hälytysjärjestelmäksi. Kun GPIO-pinni havaitsee tilamuutoksen (liike havaittu, ovi avattu), radio lähettää hälytysviestin verkkoon.
Asetus
Kuvaus
Tunnistinsensori käytössä
Ota tunnistusanturi käyttöön
GPIO-pinni valvontaa varten
Anturiin kytketty GPIO-pinni
Tunnistuksen tyyppi
Miten pinnin tila vastaa havaitsemistapahtumaa (esim. aktiivinen korkea/matala taso tai reunalaukaisu)
Käytä INPUT_PULLUP tilaa
Ota pinnin sisäinen ylösvetovastus käyttöön
Minimum time between detection broadcasts
Hälytyslähetysten vähimmäisaika
State Broadcast Interval
Tilatiedon lähetysväli
Lähetä äänimerkki hälytyssanoman kanssa
Sisällytä soittomerkkimerkki hälytyksiin
Käyttäjäystävällinen nimi
Tälle anturille määritetty nimi
Paxcounter module
Henkilöt, jotka lasketaan WiFi- ja BLE-hakukyselyiden perusteella. Laskee lähellä olevia laitteita kuuntelemalla passiivisesti koepyyntöjä, joita puhelimet ja kannettavat tietokoneet lähettävät etsiessään verkkoja. Saatavilla vain ESP32-laitteissa.
Asetus
Kuvaus
PAX-laskuri käytössä
Ota henkilölaskenta käyttöön
GPS-kyselyn aikaväli
Kuinka usein laskentatiedot raportoidaan
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
Sama raja-arvo BLE-mainospaketeille (oletus: -80 dBm)
💡 Vinkki: PAX-laskuri on hyödyllinen jalankulkijamäärien arviointiin retkeilyreittien lähtöpisteissä, tapahtumapaikoilla tai muissa kohteissa. Laskentatulokset ovat arvioita — yhdellä henkilöllä voi olla useita laitteita mukana.
Status Message module
Tilaviestillä ei ole omaa moduulinäkymää. Sitä muokataan yhdessä muiden radion tunnistetietojen kanssa kohdassa Asetukset → Radio ja käyttäjä.
Mesh Beacon module
Lähettää kutsun mesh-verkkoosi ja vastaanottaa muiden lähettämiä kutsuja. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit -integraatio yhteensopivuutta varten ATAK- ja WinTAK-järjestelmien kanssa. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Katso TAK-integraatio saadaksesi tarkemmat määritys- ja käyttöohjeet.
Ylläpito
Etähallinta
Määritä etänä radiot, jotka jakavat saman ylläpitoavaimen:
Valitse kohderadio radioluettelosta.
Siirry kyseisen radion Asetukset-kohtaan.
Muokkaa määrityksiä.
Napauta Tallenna — muutokset lähetetään verkon kautta.
⚠️ Tärkeää: Edellyttää, että järjestelmänvalvojan avain on määritetty sekä omassa radiossasi että kohderadiossa.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Toiminto
Mitä se tekee
Aseta aika
Sends your phone’s clock to the node
Käynnistä uudelleen
Restarts the node
Sammuta
Powers the node down
Palauta tehdasasetukset
Returns every setting to its factory default
Tyhjennä NodeDB-tietokanta
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Varmuuskopiointi ja palautus
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Lisäasetukset
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Tyhjennä NodeDB-tietokanta
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Vianetsintäpaneeli
Avaa Paketit- ja Sovelluslokit-välilehdet diagnostiikkatietojen tarkastelua, suodatusta ja vientiä varten. Katso Virheenjäljityslokit, jossa on täydellinen käyttöohje.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Tietoja
Settings → About carries the app’s own identity rather than the node’s:
Kolme osiota:
Mikä on Meshtastic? – lyhyt kuvaus projektista.
Sovellukset — avaa Tarvitsetko laitteiston? -näkymän, jossa on suosittujen laitteiden karuselli ja linkit niiden ostopaikkoihin. Siellä näytetään myös GitHub-tietovarasto, käytössä oleva sovellusversio ja Tekijätiedot (katso seuraava osio).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Kiitokset
Tietoja-kohdasta avattava näkymä, jossa luetellaan kaikki sovelluksen käyttämät avoimen lähdekoodin kirjastot lisensseineen. Luettelo luodaan käännöshetkellä AboutLibraries-kirjastolla. Tätä kutsuttiin aiemmin lisenssinäkymäksi.
Troubleshooting remote admin
Ei vastausta kohderadiolta — kohderadio voi olla kuuluvuusalueen ulkopuolella, poissa verkosta tai siinä voi olla eri ylläpitoavain. Varmista, että ylläpitoavain on sama molemmissa radioissa.
Muutokset eivät tule voimaan — jotkin asetukset edellyttävät uudelleenkäynnistystä ennen kuin ne astuvat voimaan. Kokeile Uudelleenkäynnistystä tallennuksen jälkeen.
Et näe etäasetuksia — varmista, että radiossasi on kohderadion ylläpitoavain. Ylläpitokanava määritetään automaattisesti, kun ylläpitoavain on asetettu.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communiquez en dehors du réseau avec vos amis et votre communauté sans service cellulaire.
Create Your Own Networks
Installez facilement des réseaux de maillage privé pour une communication sûre et fiable dans les régions éloignées.
Track and Share Locations
Partagez votre position en temps réel et gardez votre groupe coordonné avec les fonctionnalités GPS intégrées.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communiquez en dehors du réseau avec vos amis et votre communauté sans service cellulaire.
Create Your Own Networks
Installez facilement des réseaux de maillage privé pour une communication sûre et fiable dans les régions éloignées.
Track and Share Locations
Partagez votre position en temps réel et gardez votre groupe coordonné avec les fonctionnalités GPS intégrées.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Réglages du module
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Description
MQTT activé
Toggle MQTT bridge
Adresse
MQTT broker address
Nom d’utilisateur
Authentication username
Mot de passe
Authentication password
Chiffrement activé
Encrypt MQTT payloads
Sortie JSON activée
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS activé
Use secure connection
Sujet principal
Base MQTT topic path
Proxy pour le client activé
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Rapport cartographique
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Description
J’accepte.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Description
Série activée
Activate serial communication
Écho activé
Echo received serial data back
Mode série
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Vitesse de transmission série
Port speed
Délai d’expiration
How long to wait before considering an incoming message complete
Outrepasser le port série de la console
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Description
Notifications externes activées
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
LED extérieure (GPIO)
Pin the LED is wired to
Sortie LED active à l’état haut
Whether the LED pin is active high or low
Buzzer extérieur (GPIO)
Pin the buzzer is wired to
Sortie vibreur (GPIO)
Pin the vibration motor is wired to
Utiliser le buzzer PWM
Drive the buzzer with PWM, which allows tones rather than a single pitch
Utiliser l’I2S comme buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Délai d’expiration du message
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Sonnerie
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Description
Stocker & Transférer activé
Activate store and forward
Battement de cœur (heartbeat)
Periodically announce this node’s store-and-forward capability
Nombre d’enregistrements
Maximum stored messages
Limite d’historique renvoyé
Max messages to replay
Fenêtre de retour d’historique
Time window for replay
Serveur
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Description
Test de portée activé
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Enregistrer .CSV dans le stockage (ESP32 seulement)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Description
Envoyer la télémétrie de l’appareil
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervalle de mise à jour des mesures
How often to report battery, uptime and channel utilization
Module de métriques de l’environnement activé
Report the attached environment sensors
Intervalle de mise à jour des mesures d’environnement
How often to report them
Mesures d’environnement à l’écran activées
Also show these readings on the device’s own display
Les mesures environnementales utilisent Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Module de mesure de la qualité de l’air activé
Report particulate and CO₂ sensor data
Intervalle de mise à jour des mesures de qualité d’air
How often to report them
Module de mesure de puissance activé
Report the per-channel voltage and current readings
Intervalle de mise à jour des mesures d’alimentation
How often to report them
Indicateurs d’alimentation à l’écran activés
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Description
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Envoyer une sonnerie
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encodeur rotatif #1 activé
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Entrée Haut/Bas/Select activée
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Description
CODEC 2 activé
Activate audio module
Taux d’échantillonnage CODEC2
Audio quality/bandwidth tradeoff
Broche PTT
GPIO pin for the push-to-talk button
Selection de mot I2S
GPIO pin for I2S WS
Données d’entrée I2S
GPIO pin for I2S DIN
Données de sortie I2S
GPIO pin for I2S DOUT
Horloge I2C
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Description
Matériel distant activé
Activate remote GPIO access
Autoriser l’accès non défini aux broches
Allow access to any GPIO pin (security risk)
Broches disponibles
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Description
Infos de voisinage activées
Activate neighbor broadcasting
Fréquence de récupération GPS
How often to broadcast neighbor list
Transmettre par LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Description
État de la LED
Turn the LED on or off
Actif
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Description
Capteur de détection activé
Activate detection sensor
Broche GPIO à surveiller
GPIO pin connected to sensor
Type du déclencheur de détection
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Utiliser le mode INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Envoyer une sonnerie avec un message d’alerte
Include bell character in alerts
Nom convivial
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Paramètre
Description
Paxcounter activé
Activate people counting
Fréquence de récupération GPS
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Administration à distance
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Redémarrer
Restarts the node
Éteindre
Powers the node down
Réinitialisation d’usine
Returns every setting to its factory default
Reconfiguration de NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Sauvegarder & Restaurer
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Avancé
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Nettoyer la base de données des nœuds
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panneau de débogage
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
A propros
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Remerciements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Réglages du module
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Description
MQTT activé
Toggle MQTT bridge
Adresse
MQTT broker address
Nom d’utilisateur
Authentication username
Mot de passe
Authentication password
Chiffrement activé
Encrypt MQTT payloads
Sortie JSON activée
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS activé
Use secure connection
Sujet principal
Base MQTT topic path
Proxy pour le client activé
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Rapport cartographique
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Description
J’accepte.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Description
Série activée
Activate serial communication
Écho activé
Echo received serial data back
Mode série
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Vitesse de transmission série
Port speed
Délai d’expiration
How long to wait before considering an incoming message complete
Outrepasser le port série de la console
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Description
Notifications externes activées
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
LED extérieure (GPIO)
Pin the LED is wired to
Sortie LED active à l’état haut
Whether the LED pin is active high or low
Buzzer extérieur (GPIO)
Pin the buzzer is wired to
Sortie vibreur (GPIO)
Pin the vibration motor is wired to
Utiliser le buzzer PWM
Drive the buzzer with PWM, which allows tones rather than a single pitch
Utiliser l’I2S comme buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Délai d’expiration du message
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Sonnerie
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Description
Stocker & Transférer activé
Activate store and forward
Battement de cœur (heartbeat)
Periodically announce this node’s store-and-forward capability
Nombre d’enregistrements
Maximum stored messages
Limite d’historique renvoyé
Max messages to replay
Fenêtre de retour d’historique
Time window for replay
Serveur
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Description
Test de portée activé
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Enregistrer .CSV dans le stockage (ESP32 seulement)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Description
Envoyer la télémétrie de l’appareil
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervalle de mise à jour des mesures
How often to report battery, uptime and channel utilization
Module de métriques de l’environnement activé
Report the attached environment sensors
Intervalle de mise à jour des mesures d’environnement
How often to report them
Mesures d’environnement à l’écran activées
Also show these readings on the device’s own display
Les mesures environnementales utilisent Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Module de mesure de la qualité de l’air activé
Report particulate and CO₂ sensor data
Intervalle de mise à jour des mesures de qualité d’air
How often to report them
Module de mesure de puissance activé
Report the per-channel voltage and current readings
Intervalle de mise à jour des mesures d’alimentation
How often to report them
Indicateurs d’alimentation à l’écran activés
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Description
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Envoyer une sonnerie
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encodeur rotatif #1 activé
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Entrée Haut/Bas/Select activée
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Description
CODEC 2 activé
Activate audio module
Taux d’échantillonnage CODEC2
Audio quality/bandwidth tradeoff
Broche PTT
GPIO pin for the push-to-talk button
Selection de mot I2S
GPIO pin for I2S WS
Données d’entrée I2S
GPIO pin for I2S DIN
Données de sortie I2S
GPIO pin for I2S DOUT
Horloge I2C
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Description
Matériel distant activé
Activate remote GPIO access
Autoriser l’accès non défini aux broches
Allow access to any GPIO pin (security risk)
Broches disponibles
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Description
Infos de voisinage activées
Activate neighbor broadcasting
Fréquence de récupération GPS
How often to broadcast neighbor list
Transmettre par LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Description
État de la LED
Turn the LED on or off
Actif
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Description
Capteur de détection activé
Activate detection sensor
Broche GPIO à surveiller
GPIO pin connected to sensor
Type du déclencheur de détection
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Utiliser le mode INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Envoyer une sonnerie avec un message d’alerte
Include bell character in alerts
Nom convivial
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Paramètre
Description
Paxcounter activé
Activate people counting
Fréquence de récupération GPS
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Administration à distance
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Redémarrer
Restarts the node
Éteindre
Powers the node down
Réinitialisation d’usine
Returns every setting to its factory default
Reconfiguration de NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Sauvegarder & Restaurer
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Avancé
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Nettoyer la base de données des nœuds
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panneau de débogage
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
A propros
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Remerciements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communiquez en dehors du réseau avec vos amis et votre communauté sans service cellulaire.
Create Your Own Networks
Installez facilement des réseaux de maillage privé pour une communication sûre et fiable dans les régions éloignées.
Track and Share Locations
Partagez votre position en temps réel et gardez votre groupe coordonné avec les fonctionnalités GPS intégrées.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communiquez en dehors du réseau avec vos amis et votre communauté sans service cellulaire.
Create Your Own Networks
Installez facilement des réseaux de maillage privé pour une communication sûre et fiable dans les régions éloignées.
Track and Share Locations
Partagez votre position en temps réel et gardez votre groupe coordonné avec les fonctionnalités GPS intégrées.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Réglages du module
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Description
MQTT activé
Toggle MQTT bridge
Adresse
MQTT broker address
Nom d’utilisateur
Authentication username
Mot de passe
Authentication password
Chiffrement activé
Encrypt MQTT payloads
Sortie JSON activée
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS activé
Use secure connection
Sujet principal
Base MQTT topic path
Proxy pour le client activé
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Rapport cartographique
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Description
J’accepte.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Description
Série activée
Activate serial communication
Écho activé
Echo received serial data back
Mode série
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Vitesse de transmission série
Port speed
Délai d’expiration
How long to wait before considering an incoming message complete
Outrepasser le port série de la console
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Description
Notifications externes activées
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
LED extérieure (GPIO)
Pin the LED is wired to
Sortie LED active à l’état haut
Whether the LED pin is active high or low
Buzzer extérieur (GPIO)
Pin the buzzer is wired to
Sortie vibreur (GPIO)
Pin the vibration motor is wired to
Utiliser le buzzer PWM
Drive the buzzer with PWM, which allows tones rather than a single pitch
Utiliser l’I2S comme buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Délai d’expiration du message
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Sonnerie
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Description
Stocker & Transférer activé
Activate store and forward
Battement de cœur (heartbeat)
Periodically announce this node’s store-and-forward capability
Nombre d’enregistrements
Maximum stored messages
Limite d’historique renvoyé
Max messages to replay
Fenêtre de retour d’historique
Time window for replay
Serveur
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Description
Test de portée activé
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Enregistrer .CSV dans le stockage (ESP32 seulement)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Description
Envoyer la télémétrie de l’appareil
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervalle de mise à jour des mesures
How often to report battery, uptime and channel utilization
Module de métriques de l’environnement activé
Report the attached environment sensors
Intervalle de mise à jour des mesures d’environnement
How often to report them
Mesures d’environnement à l’écran activées
Also show these readings on the device’s own display
Les mesures environnementales utilisent Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Module de mesure de la qualité de l’air activé
Report particulate and CO₂ sensor data
Intervalle de mise à jour des mesures de qualité d’air
How often to report them
Module de mesure de puissance activé
Report the per-channel voltage and current readings
Intervalle de mise à jour des mesures d’alimentation
How often to report them
Indicateurs d’alimentation à l’écran activés
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Description
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Envoyer une sonnerie
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encodeur rotatif #1 activé
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Entrée Haut/Bas/Select activée
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Description
CODEC 2 activé
Activate audio module
Taux d’échantillonnage CODEC2
Audio quality/bandwidth tradeoff
Broche PTT
GPIO pin for the push-to-talk button
Selection de mot I2S
GPIO pin for I2S WS
Données d’entrée I2S
GPIO pin for I2S DIN
Données de sortie I2S
GPIO pin for I2S DOUT
Horloge I2C
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Description
Matériel distant activé
Activate remote GPIO access
Autoriser l’accès non défini aux broches
Allow access to any GPIO pin (security risk)
Broches disponibles
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Description
Infos de voisinage activées
Activate neighbor broadcasting
Fréquence de récupération GPS
How often to broadcast neighbor list
Transmettre par LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Description
État de la LED
Turn the LED on or off
Actif
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Description
Capteur de détection activé
Activate detection sensor
Broche GPIO à surveiller
GPIO pin connected to sensor
Type du déclencheur de détection
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Utiliser le mode INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Envoyer une sonnerie avec un message d’alerte
Include bell character in alerts
Nom convivial
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Paramètre
Description
Paxcounter activé
Activate people counting
Fréquence de récupération GPS
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Administration à distance
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Redémarrer
Restarts the node
Éteindre
Powers the node down
Réinitialisation d’usine
Returns every setting to its factory default
Reconfiguration de NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Sauvegarder & Restaurer
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Avancé
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Nettoyer la base de données des nœuds
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panneau de débogage
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
A propros
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Remerciements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Réglages du module
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Description
MQTT activé
Toggle MQTT bridge
Adresse
MQTT broker address
Nom d’utilisateur
Authentication username
Mot de passe
Authentication password
Chiffrement activé
Encrypt MQTT payloads
Sortie JSON activée
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS activé
Use secure connection
Sujet principal
Base MQTT topic path
Proxy pour le client activé
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Rapport cartographique
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Description
J’accepte.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Description
Série activée
Activate serial communication
Écho activé
Echo received serial data back
Mode série
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Vitesse de transmission série
Port speed
Délai d’expiration
How long to wait before considering an incoming message complete
Outrepasser le port série de la console
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Description
Notifications externes activées
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
LED extérieure (GPIO)
Pin the LED is wired to
Sortie LED active à l’état haut
Whether the LED pin is active high or low
Buzzer extérieur (GPIO)
Pin the buzzer is wired to
Sortie vibreur (GPIO)
Pin the vibration motor is wired to
Utiliser le buzzer PWM
Drive the buzzer with PWM, which allows tones rather than a single pitch
Utiliser l’I2S comme buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Délai d’expiration du message
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Sonnerie
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Description
Stocker & Transférer activé
Activate store and forward
Battement de cœur (heartbeat)
Periodically announce this node’s store-and-forward capability
Nombre d’enregistrements
Maximum stored messages
Limite d’historique renvoyé
Max messages to replay
Fenêtre de retour d’historique
Time window for replay
Serveur
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Description
Test de portée activé
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Enregistrer .CSV dans le stockage (ESP32 seulement)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Description
Envoyer la télémétrie de l’appareil
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervalle de mise à jour des mesures
How often to report battery, uptime and channel utilization
Module de métriques de l’environnement activé
Report the attached environment sensors
Intervalle de mise à jour des mesures d’environnement
How often to report them
Mesures d’environnement à l’écran activées
Also show these readings on the device’s own display
Les mesures environnementales utilisent Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Module de mesure de la qualité de l’air activé
Report particulate and CO₂ sensor data
Intervalle de mise à jour des mesures de qualité d’air
How often to report them
Module de mesure de puissance activé
Report the per-channel voltage and current readings
Intervalle de mise à jour des mesures d’alimentation
How often to report them
Indicateurs d’alimentation à l’écran activés
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Description
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Envoyer une sonnerie
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encodeur rotatif #1 activé
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Entrée Haut/Bas/Select activée
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Description
CODEC 2 activé
Activate audio module
Taux d’échantillonnage CODEC2
Audio quality/bandwidth tradeoff
Broche PTT
GPIO pin for the push-to-talk button
Selection de mot I2S
GPIO pin for I2S WS
Données d’entrée I2S
GPIO pin for I2S DIN
Données de sortie I2S
GPIO pin for I2S DOUT
Horloge I2C
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Description
Matériel distant activé
Activate remote GPIO access
Autoriser l’accès non défini aux broches
Allow access to any GPIO pin (security risk)
Broches disponibles
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Description
Infos de voisinage activées
Activate neighbor broadcasting
Fréquence de récupération GPS
How often to broadcast neighbor list
Transmettre par LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Description
État de la LED
Turn the LED on or off
Actif
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Description
Capteur de détection activé
Activate detection sensor
Broche GPIO à surveiller
GPIO pin connected to sensor
Type du déclencheur de détection
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Utiliser le mode INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Envoyer une sonnerie avec un message d’alerte
Include bell character in alerts
Nom convivial
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Paramètre
Description
Paxcounter activé
Activate people counting
Fréquence de récupération GPS
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Administration à distance
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Redémarrer
Restarts the node
Éteindre
Powers the node down
Réinitialisation d’usine
Returns every setting to its factory default
Reconfiguration de NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Sauvegarder & Restaurer
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Avancé
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Nettoyer la base de données des nœuds
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panneau de débogage
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
A propros
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Remerciements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Cumraíocht an mhódule
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Cur síos
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Cur síos
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Cur síos
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Am tráth
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Cur síos
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Cur síos
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Cur síos
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Cur síos
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Cur síos
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Cur síos
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Cur síos
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Cur síos
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Cur síos
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Cur síos
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Cur síos
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Rialachas
Rialú iargúlta
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Athmhaoinigh
Restarts the node
Dún
Powers the node down
Athshocraigh an fhactaraí
Returns every setting to its factory default
Athshocraigh NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Painéal Laige
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Maidir le
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Cumraíocht an mhódule
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Cur síos
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Cur síos
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Cur síos
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Am tráth
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Cur síos
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Cur síos
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Cur síos
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Cur síos
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Cur síos
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Cur síos
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Cur síos
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Cur síos
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Cur síos
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Cur síos
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Cur síos
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Rialachas
Rialú iargúlta
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Athmhaoinigh
Restarts the node
Dún
Powers the node down
Athshocraigh an fhactaraí
Returns every setting to its factory default
Athshocraigh NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Painéal Laige
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Maidir le
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Configuración de módulo
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Descrición
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Descrición
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Descrición
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Timeout
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Descrición
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Descrición
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Descrición
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Descrición
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Descrición
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Descrición
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Descrición
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Descrición
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Descrición
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Descrición
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Descrición
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Remote Administration
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Reiniciar
Restarts the node
Apagar
Powers the node down
Restablecemento de fábrica
Returns every setting to its factory default
Restablecer NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panel de depuración
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Acerca de
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Configuración de módulo
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Descrición
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Descrición
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Descrición
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Timeout
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Descrición
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Descrición
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Descrición
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Descrición
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Descrición
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Descrición
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Descrición
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Descrición
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Descrición
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Descrición
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Descrición
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Remote Administration
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Reiniciar
Restarts the node
Apagar
Powers the node down
Restablecemento de fábrica
Returns every setting to its factory default
Restablecer NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panel de depuración
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Acerca de
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Konfiguracija modula
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Opis
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Opis
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Opis
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Timeout
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Opis
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Opis
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Opis
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Opis
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Opis
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Opis
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Opis
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Opis
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Opis
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Opis
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Opis
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Remote Administration
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Ponovno pokreni
Restarts the node
Isključi
Powers the node down
Vraćanje na tvorničke postavke
Returns every setting to its factory default
Resetiraj NodeDB bazu
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Otklanjanje pogrešaka
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
O programu
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Konfiguracija modula
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Opis
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Opis
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Opis
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Timeout
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Opis
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Opis
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Opis
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Opis
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Opis
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Opis
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Opis
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Opis
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Opis
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Opis
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Opis
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Remote Administration
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Ponovno pokreni
Restarts the node
Isključi
Powers the node down
Vraćanje na tvorničke postavke
Returns every setting to its factory default
Resetiraj NodeDB bazu
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Otklanjanje pogrešaka
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
O programu
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Konfigirasyon modil
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Deskripsyon
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Deskripsyon
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Deskripsyon
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Tan pase
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Deskripsyon
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Deskripsyon
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Deskripsyon
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Deskripsyon
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Deskripsyon
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Deskripsyon
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Deskripsyon
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Deskripsyon
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Deskripsyon
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Deskripsyon
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Deskripsyon
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administrasyon
Administrasyon Remote
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Rekòmanse
Restarts the node
Fèmen
Powers the node down
Reyajiste nan faktori
Returns every setting to its factory default
Reyajiste NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panno Debug
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Sou
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Konfigirasyon modil
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Deskripsyon
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Deskripsyon
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Deskripsyon
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Tan pase
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Deskripsyon
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Deskripsyon
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Deskripsyon
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Deskripsyon
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Deskripsyon
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Deskripsyon
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Deskripsyon
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Deskripsyon
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Deskripsyon
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Deskripsyon
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Deskripsyon
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administrasyon
Administrasyon Remote
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Rekòmanse
Restarts the node
Fèmen
Powers the node down
Reyajiste nan faktori
Returns every setting to its factory default
Reyajiste NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panno Debug
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Sou
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Kommunikálj a barátaiddal és a közösségeddel mobilhálózat nélkül, a hálózaton kívül is.
Create Your Own Networks
Egyszerűen állíts be privát mesh hálózatokat a biztonságos és megbízható kommunikáció érdekében távoli területeken.
Track and Share Locations
Oszd meg a helyzeted valós időben, és tartsd összehangoltan a csoportot a beépített GPS-funkciókkal.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Kommunikálj a barátaiddal és a közösségeddel mobilhálózat nélkül, a hálózaton kívül is.
Create Your Own Networks
Egyszerűen állíts be privát mesh hálózatokat a biztonságos és megbízható kommunikáció érdekében távoli területeken.
Track and Share Locations
Oszd meg a helyzeted valós időben, és tartsd összehangoltan a csoportot a beépített GPS-funkciókkal.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Modul beállítások
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Leírás
MQTT engedélyezve
Toggle MQTT bridge
Cím
MQTT broker address
Felhasználónév
Authentication username
Jelszó
Authentication password
Titkosítás engedélyezve
Encrypt MQTT payloads
JSON kimenet engedélyezve
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS engedélyezve
Use secure connection
Gyökér téma
Base MQTT topic path
Proxy kliens felé engedélyezve
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Térképadat-jelentés
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Leírás
Elfogadom.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Leírás
Soros engedélyezve
Activate serial communication
Echo engedélyezve
Echo received serial data back
Soros mód
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Soros baud ráta
Port speed
Időtúllépés
How long to wait before considering an incoming message complete
Konzol soros port felülbírálása
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Leírás
Külső értesítés engedélyezve
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Kimeneti LED (GPIO)
Pin the LED is wired to
Kimeneti LED aktív magas szint
Whether the LED pin is active high or low
Kimeneti csipogó (GPIO)
Pin the buzzer is wired to
Kimeneti rezgő (GPIO)
Pin the vibration motor is wired to
PWM csipogó használata
Drive the buzzer with PWM, which allows tones rather than a single pitch
I2S használata csipogóként
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Csengőhang
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Leírás
Tárolás és továbbítás engedélyezve
Activate store and forward
Heartbeat jel
Periodically announce this node’s store-and-forward capability
Rekordok száma
Maximum stored messages
Előzmény-visszaadás maximum
Max messages to replay
Előzmény-visszaadás időablak
Time window for replay
Szerver
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Leírás
Hatótáv-teszt engedélyezve
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
.CSV mentése a tárhelyre (csak ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Leírás
Eszköztelemetria küldése
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Eszközmetrikák frissítési időköze
How often to report battery, uptime and channel utilization
Környezeti metrika modul engedélyezve
Report the attached environment sensors
Környezeti metrikák frissítési időköze
How often to report them
Környezeti metrikák megjelenítése képernyőn
Also show these readings on the device’s own display
Környezeti metrikák Fahrenheit-ben
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Levegőminőség-metrika modul engedélyezve
Report particulate and CO₂ sensor data
Levegőminőségi metrikák frissítési időköze
How often to report them
Energia-metrika modul engedélyezve
Report the per-channel voltage and current readings
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Leírás
Canned message enabled
⚠️ Deprecated in the protobuf schema
Üzenetek
Newline-separated list of messages
Harangjel küldése
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
1. forgóenkóder engedélyezve
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Fel/Le/Kiválaszt gomb engedélyezve
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Leírás
CODEC 2 engedélyezve
Activate audio module
CODEC2 mintavételi ráta
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S szóválasztás
GPIO pin for I2S WS
I2S adat be
GPIO pin for I2S DIN
I2S adat ki
GPIO pin for I2S DOUT
I2S órajel
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Leírás
Távoli hardver engedélyezve
Activate remote GPIO access
Nem definiált pinek elérésének engedélyezése
Allow access to any GPIO pin (security risk)
Elérhető pinek
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Leírás
Szomszéd-információ engedélyezve
Activate neighbor broadcasting
Frissítési időköz
How often to broadcast neighbor list
Továbbítás LoRa-n keresztül
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Leírás
LED állapot
Turn the LED on or off
Áramerősség
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Leírás
Érzékelő szenzor engedélyezve
Activate detection sensor
Figyelt GPIO láb
GPIO pin connected to sensor
Érzékelési ravasztípus
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
INPUT_PULLUP mód használata
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Harangjel küldése riasztási üzenettel
Include bell character in alerts
Barátságos név
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Leírás
Paxcounter engedélyezve
Activate people counting
Frissítési időköz
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Adminisztráció
Távoli Adminisztráció
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Újraindítás
Restarts the node
Leállítás
Powers the node down
Gyári beállítások visszaállítása
Returns every setting to its factory default
NodeDB törlése
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Biztonsági mentés és visszaállítás
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Haladó
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Csomópont-adatbázis tisztítása
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Hibakereső panel
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
A programról
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Visszaigazolások (ACK-ek)
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Modul beállítások
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Leírás
MQTT engedélyezve
Toggle MQTT bridge
Cím
MQTT broker address
Felhasználónév
Authentication username
Jelszó
Authentication password
Titkosítás engedélyezve
Encrypt MQTT payloads
JSON kimenet engedélyezve
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS engedélyezve
Use secure connection
Gyökér téma
Base MQTT topic path
Proxy kliens felé engedélyezve
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Térképadat-jelentés
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Leírás
Elfogadom.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Leírás
Soros engedélyezve
Activate serial communication
Echo engedélyezve
Echo received serial data back
Soros mód
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Soros baud ráta
Port speed
Időtúllépés
How long to wait before considering an incoming message complete
Konzol soros port felülbírálása
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Leírás
Külső értesítés engedélyezve
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Kimeneti LED (GPIO)
Pin the LED is wired to
Kimeneti LED aktív magas szint
Whether the LED pin is active high or low
Kimeneti csipogó (GPIO)
Pin the buzzer is wired to
Kimeneti rezgő (GPIO)
Pin the vibration motor is wired to
PWM csipogó használata
Drive the buzzer with PWM, which allows tones rather than a single pitch
I2S használata csipogóként
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Csengőhang
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Leírás
Tárolás és továbbítás engedélyezve
Activate store and forward
Heartbeat jel
Periodically announce this node’s store-and-forward capability
Rekordok száma
Maximum stored messages
Előzmény-visszaadás maximum
Max messages to replay
Előzmény-visszaadás időablak
Time window for replay
Szerver
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Leírás
Hatótáv-teszt engedélyezve
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
.CSV mentése a tárhelyre (csak ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Leírás
Eszköztelemetria küldése
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Eszközmetrikák frissítési időköze
How often to report battery, uptime and channel utilization
Környezeti metrika modul engedélyezve
Report the attached environment sensors
Környezeti metrikák frissítési időköze
How often to report them
Környezeti metrikák megjelenítése képernyőn
Also show these readings on the device’s own display
Környezeti metrikák Fahrenheit-ben
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Levegőminőség-metrika modul engedélyezve
Report particulate and CO₂ sensor data
Levegőminőségi metrikák frissítési időköze
How often to report them
Energia-metrika modul engedélyezve
Report the per-channel voltage and current readings
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Leírás
Canned message enabled
⚠️ Deprecated in the protobuf schema
Üzenetek
Newline-separated list of messages
Harangjel küldése
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
1. forgóenkóder engedélyezve
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Fel/Le/Kiválaszt gomb engedélyezve
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Leírás
CODEC 2 engedélyezve
Activate audio module
CODEC2 mintavételi ráta
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S szóválasztás
GPIO pin for I2S WS
I2S adat be
GPIO pin for I2S DIN
I2S adat ki
GPIO pin for I2S DOUT
I2S órajel
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Leírás
Távoli hardver engedélyezve
Activate remote GPIO access
Nem definiált pinek elérésének engedélyezése
Allow access to any GPIO pin (security risk)
Elérhető pinek
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Leírás
Szomszéd-információ engedélyezve
Activate neighbor broadcasting
Frissítési időköz
How often to broadcast neighbor list
Továbbítás LoRa-n keresztül
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Leírás
LED állapot
Turn the LED on or off
Áramerősség
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Leírás
Érzékelő szenzor engedélyezve
Activate detection sensor
Figyelt GPIO láb
GPIO pin connected to sensor
Érzékelési ravasztípus
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
INPUT_PULLUP mód használata
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Harangjel küldése riasztási üzenettel
Include bell character in alerts
Barátságos név
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Leírás
Paxcounter engedélyezve
Activate people counting
Frissítési időköz
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Adminisztráció
Távoli Adminisztráció
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Újraindítás
Restarts the node
Leállítás
Powers the node down
Gyári beállítások visszaállítása
Returns every setting to its factory default
NodeDB törlése
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Biztonsági mentés és visszaállítás
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Haladó
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Csomópont-adatbázis tisztítása
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Hibakereső panel
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
A programról
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Visszaigazolások (ACK-ek)
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Stillingar aukaeininga
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Lýsing
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Lýsing
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Lýsing
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Timeout
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Lýsing
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Lýsing
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Lýsing
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Lýsing
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Lýsing
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Lýsing
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Lýsing
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Lýsing
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Lýsing
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Lýsing
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Lýsing
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Remote Administration
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Endurræsa
Restarts the node
Slökkva
Powers the node down
Grunnstilla
Returns every setting to its factory default
Endurræsa NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Villuleitarborð
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Um smáforrit
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Stillingar aukaeininga
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Lýsing
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Lýsing
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Lýsing
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Timeout
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Lýsing
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Lýsing
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Lýsing
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Lýsing
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Lýsing
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Lýsing
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Lýsing
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Lýsing
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Lýsing
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Lýsing
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Lýsing
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Remote Administration
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Endurræsa
Restarts the node
Slökkva
Powers the node down
Grunnstilla
Returns every setting to its factory default
Endurræsa NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Villuleitarborð
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Um smáforrit
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Comunica off-grid con i tuoi amici e la tua comunità senza la connessione cellulare.
Create Your Own Networks
Crea reti mesh private in modo semplice per connessioni sicure e affidabili in zone remote.
Track and Share Locations
Condividi la tua posizione in tempo reale e mantieni il tuo gruppo coordinato con le funzionalità GPS integrate.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Comunica off-grid con i tuoi amici e la tua comunità senza la connessione cellulare.
Create Your Own Networks
Crea reti mesh private in modo semplice per connessioni sicure e affidabili in zone remote.
Track and Share Locations
Condividi la tua posizione in tempo reale e mantieni il tuo gruppo coordinato con le funzionalità GPS integrate.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Impostazioni moduli
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Impostazione
Descrizione
MQTT abilitato
Toggle MQTT bridge
Indirizzo
MQTT broker address
Username
Authentication username
Password
Authentication password
Crittografia abilitata
Encrypt MQTT payloads
Output JSON abilitato
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS abilitato
Use secure connection
Root topic
Base MQTT topic path
Proxy to client attivato
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Segnalazione su mappa
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Impostazione
Descrizione
Sono d’accordo.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Impostazione
Descrizione
Seriale abilitata
Activate serial communication
Echo abilitato
Echo received serial data back
Modalità seriale
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Velocità della seriale
Port speed
Timeout
How long to wait before considering an incoming message complete
Sovrascrivi porta seriale della console
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Impostazione
Descrizione
Notifica esterna attivata
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
LED Output (GPIO)
Pin the LED is wired to
Output per LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibrazione (GPIO)
Pin the vibration motor is wired to
Usa buzzer PWM
Drive the buzzer with PWM, which allows tones rather than a single pitch
Usa I2S come buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Suoneria
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Impostazione
Descrizione
Store & Forward abilitato
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Numero di record
Maximum stored messages
Cronologia ritorno max
Max messages to replay
Finestra di ritorno cronologia
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Impostazione
Descrizione
Test distanza massima abilitato
Activate range testing
Intervallo Del Mittente
Time between test transmissions, chosen from a dropdown of fixed intervals
Salva .CSV nella memoria (solo ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Impostazione
Descrizione
Invia Telemetria Dispositivo
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervallo aggiornamento metriche dispositivo
How often to report battery, uptime and channel utilization
Modulo metriche ambientali abilitato
Report the attached environment sensors
Intervallo aggiornamento metriche ambientali
How often to report them
Metriche ambientali visualizzate su schermo
Also show these readings on the device’s own display
Usa i gradi Fahrenheit nelle metriche ambientali
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Modulo metriche della qualità dell’aria abilitato
Report particulate and CO₂ sensor data
Intervallo aggiornamento metriche qualità aria
How often to report them
Modulo metriche di alimentazione abilitato
Report the per-channel voltage and current readings
Intervallo aggiornamento metriche alimentazione
How often to report them
Metriche di alimentazione visualizzate su schermo
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Impostazione
Descrizione
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messaggi
Newline-separated list of messages
Invia campanella
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encoder rotativo #1 abilitato
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Input Su/Giu/Selezione abilitato
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Impostazione
Descrizione
CODEC 2 attivato
Activate audio module
Frequenza di campionamento CODEC2
Audio quality/bandwidth tradeoff
Pin PTT
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Impostazione
Descrizione
Hardware Remoto abilitato
Activate remote GPIO access
Consenti accesso a pin non definiti
Allow access to any GPIO pin (security risk)
Pin disponibili
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Impostazione
Descrizione
Info Nodi Vicini abilitato
Activate neighbor broadcasting
Intervallo Interrogazione GPS
How often to broadcast neighbor list
Trasmettere su LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Impostazione
Descrizione
LED di stato
Turn the LED on or off
Attuale
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Impostazione
Descrizione
Sensore Rilevamento attivo
Activate detection sensor
Pin GPIO da monitorare
GPIO pin connected to sensor
Tipo di trigger di rilevamento
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Usa modalità INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
Intervallo Di Trasmissione
Periodic state broadcast interval
Invia campanella con messaggio di avviso
Include bell character in alerts
Nome semplificato
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Impostazione
Descrizione
Paxcounter abilitato
Activate people counting
Intervallo Interrogazione GPS
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Amministrazione
Amministrazione Remota
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Imposta l’ora
Sends your phone’s clock to the node
Riavvia
Restarts the node
Spegni
Powers the node down
Ripristina impostazioni di fabbrica
Returns every setting to its factory default
NodeDB reset
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Ripristino
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Avanzate
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Azzera il database dei nodi
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Pannello Di Debug
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Informazioni
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Ringraziamenti
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Impostazioni moduli
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Impostazione
Descrizione
MQTT abilitato
Toggle MQTT bridge
Indirizzo
MQTT broker address
Username
Authentication username
Password
Authentication password
Crittografia abilitata
Encrypt MQTT payloads
Output JSON abilitato
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS abilitato
Use secure connection
Root topic
Base MQTT topic path
Proxy to client attivato
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Segnalazione su mappa
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Impostazione
Descrizione
Sono d’accordo.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Impostazione
Descrizione
Seriale abilitata
Activate serial communication
Echo abilitato
Echo received serial data back
Modalità seriale
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Velocità della seriale
Port speed
Timeout
How long to wait before considering an incoming message complete
Sovrascrivi porta seriale della console
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Impostazione
Descrizione
Notifica esterna attivata
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
LED Output (GPIO)
Pin the LED is wired to
Output per LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibrazione (GPIO)
Pin the vibration motor is wired to
Usa buzzer PWM
Drive the buzzer with PWM, which allows tones rather than a single pitch
Usa I2S come buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Suoneria
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Impostazione
Descrizione
Store & Forward abilitato
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Numero di record
Maximum stored messages
Cronologia ritorno max
Max messages to replay
Finestra di ritorno cronologia
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Impostazione
Descrizione
Test distanza massima abilitato
Activate range testing
Intervallo Del Mittente
Time between test transmissions, chosen from a dropdown of fixed intervals
Salva .CSV nella memoria (solo ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Impostazione
Descrizione
Invia Telemetria Dispositivo
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervallo aggiornamento metriche dispositivo
How often to report battery, uptime and channel utilization
Modulo metriche ambientali abilitato
Report the attached environment sensors
Intervallo aggiornamento metriche ambientali
How often to report them
Metriche ambientali visualizzate su schermo
Also show these readings on the device’s own display
Usa i gradi Fahrenheit nelle metriche ambientali
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Modulo metriche della qualità dell’aria abilitato
Report particulate and CO₂ sensor data
Intervallo aggiornamento metriche qualità aria
How often to report them
Modulo metriche di alimentazione abilitato
Report the per-channel voltage and current readings
Intervallo aggiornamento metriche alimentazione
How often to report them
Metriche di alimentazione visualizzate su schermo
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Impostazione
Descrizione
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messaggi
Newline-separated list of messages
Invia campanella
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encoder rotativo #1 abilitato
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Input Su/Giu/Selezione abilitato
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Impostazione
Descrizione
CODEC 2 attivato
Activate audio module
Frequenza di campionamento CODEC2
Audio quality/bandwidth tradeoff
Pin PTT
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Impostazione
Descrizione
Hardware Remoto abilitato
Activate remote GPIO access
Consenti accesso a pin non definiti
Allow access to any GPIO pin (security risk)
Pin disponibili
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Impostazione
Descrizione
Info Nodi Vicini abilitato
Activate neighbor broadcasting
Intervallo Interrogazione GPS
How often to broadcast neighbor list
Trasmettere su LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Impostazione
Descrizione
LED di stato
Turn the LED on or off
Attuale
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Impostazione
Descrizione
Sensore Rilevamento attivo
Activate detection sensor
Pin GPIO da monitorare
GPIO pin connected to sensor
Tipo di trigger di rilevamento
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Usa modalità INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
Intervallo Di Trasmissione
Periodic state broadcast interval
Invia campanella con messaggio di avviso
Include bell character in alerts
Nome semplificato
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Impostazione
Descrizione
Paxcounter abilitato
Activate people counting
Intervallo Interrogazione GPS
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Amministrazione
Amministrazione Remota
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Imposta l’ora
Sends your phone’s clock to the node
Riavvia
Restarts the node
Spegni
Powers the node down
Ripristina impostazioni di fabbrica
Returns every setting to its factory default
NodeDB reset
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Ripristino
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Avanzate
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Azzera il database dei nodi
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Pannello Di Debug
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Informazioni
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Ringraziamenti
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
הגדרות מודולות
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
תיאור
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
תיאור
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
תיאור
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Timeout
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
תיאור
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
תיאור
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
תיאור
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
תיאור
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
תיאור
Canned message enabled
⚠️ Deprecated in the protobuf schema
הודעות
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
תיאור
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
תיאור
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
תיאור
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
תיאור
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
תיאור
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
תיאור
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Remote Administration
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
אתחול מחדש
Restarts the node
כיבוי
Powers the node down
איפוס להגדרות היצרן
Returns every setting to its factory default
איפוס NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
פאנל דיבאג
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
אודות
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
הגדרות מודולות
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
תיאור
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
תיאור
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
תיאור
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Timeout
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
תיאור
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
תיאור
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
תיאור
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
תיאור
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
תיאור
Canned message enabled
⚠️ Deprecated in the protobuf schema
הודעות
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
תיאור
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
תיאור
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
תיאור
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
תיאור
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
תיאור
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
תיאור
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Remote Administration
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
אתחול מחדש
Restarts the node
כיבוי
Powers the node down
איפוס להגדרות היצרן
Returns every setting to its factory default
איפוס NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
פאנל דיבאג
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
אודות
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
何か不具合が起きたとき、アプリのデバッグログは、バグ報告に添付できる最も役立つものです。 Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
「設定 → 詳細設定 → デバッグパネル」から「デバッグパネル」を開きます。
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. 問題が起きた瞬間を含むログのキャプチャは、「動かない」という報告を、開発者が実際に追跡できるものに変えます。
ダウンロードアイコンをタップすると、現在のログをファイルに保存できます。 The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
そのファイルを GitHub の issue に添付してください。
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
何か不具合が起きたとき、アプリのデバッグログは、バグ報告に添付できる最も役立つものです。 Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
「設定 → 詳細設定 → デバッグパネル」から「デバッグパネル」を開きます。
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. 問題が起きた瞬間を含むログのキャプチャは、「動かない」という報告を、開発者が実際に追跡できるものに変えます。
ダウンロードアイコンをタップすると、現在のログをファイルに保存できます。 The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
そのファイルを GitHub の issue に添付してください。
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
デスクトップ
デスクトップアプリにはシステムの logcat がないため、「アプリログ」タブは代わりに、アプリ自身がキャプチャしたログ出力を表示します。検索、絞り込み、エクスポートは同じように機能します。 Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
初回起動
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
ようこそ画面
The welcome screen introduces Meshtastic with three feature rows:
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
位置情報の権限
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic は、次の目的でも位置情報を使用します：
メッシュマップ上に自分の位置を表示する
他のノードまでの距離を計算する
他のメッシュメンバーと GPS 座標を共有する（有効な場合）
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
状態
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
セットアップ後
After you grant permissions, the app opens the main interface. 最初に行うべきことは、Meshtastic 無線機への接続です。詳しい手順は接続を参照してください。
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
初回起動
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
ようこそ画面
The welcome screen introduces Meshtastic with three feature rows:
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
位置情報の権限
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic は、次の目的でも位置情報を使用します：
メッシュマップ上に自分の位置を表示する
他のノードまでの距離を計算する
他のメッシュメンバーと GPS 座標を共有する（有効な場合）
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
状態
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
セットアップ後
After you grant permissions, the app opens the main interface. 最初に行うべきことは、Meshtastic 無線機への接続です。詳しい手順は接続を参照してください。
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
💡 ヒント： 実際に使うモジュールだけを有効にすれば十分です。使わないモジュールを無効にすると、電波利用時間が減り、バッテリーを節約でき、設定もシンプルになります。 A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
インターネット接続のために、メッシュのメッセージを MQTT サーバーとの間で橋渡しします。 This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
設定項目
説明
MQTTを有効化
MQTT ブリッジを切り替え
アドレス
MQTT サーバーのアドレス
ユーザー名
認証用のユーザー名
パスワード
認証用のパスワード
暗号化の有効化
MQTT ペイロードを暗号化
JSON出力の有効化
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS の有効化
セキュアな接続を使用
ルート トピック
MQTT のベーストピックパス
クライアントへのプロキシの有効化
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
マップレポート
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
設定項目
説明
同意します。
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
シリアルボーレイト
Port speed
タイムアウト
How long to wait before considering an incoming message complete
コンソールのシリアルポートを上書き
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. メッセージ到着時に物理的に知らせる必要があるデバイスに便利です。特に無人設置や屋外設置で役立ちます。
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
設定項目
説明
外部通知を有効化
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
LED出力 (GPIO)
Pin the LED is wired to
LED出力 アクティブハイ
Whether the LED pin is active high or low
ブザー出力(GPIO)
Pin the buzzer is wired to
バイブレーション出力 (GPIO)
Pin the vibration motor is wired to
PWMブザーを使用
Drive the buzzer with PWM, which allows tones rather than a single pitch
I2Sをブザーとして使用
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
着信音
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). スマートフォンを接続していなくても送信できる、クイック送信メッセージのリストを定義します。フィールドでの使用に最適です。
設定項目
説明
Canned message enabled
⚠️ Deprecated in the protobuf schema
メッセージ
改行で区切ったメッセージのリスト
ベルを送信
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
ロータリーエンコーダ #1 を有効化
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
上下/選択入力を有効化
A separate, simpler input scheme using up/down/select buttons rather than an encoder
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
ATAK および WinTAK と相互運用するための、Team Awareness Kit 連携です。 Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. 詳しい設定と使い方は、TAK 連携 を参照してください。
管理
リモート管理
管理者鍵を共有しているノードをリモートで設定します：
ノードリストで対象のノードを選択します。
そのノードの「設定」に移動します。
設定を変更します。
「保存」をタップします。変更がメッシュ経由で送信されます。
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
操作
内容
時刻を設定
Sends your phone’s clock to the node
再起動
Restarts the node
シャットダウン
Powers the node down
出荷時にリセット
Returns every setting to its factory default
NodeDBをリセット
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
バックアップと復元
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
詳細設定
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
ノードデータベースの整理
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
概要
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
謝辞
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
💡 ヒント： 実際に使うモジュールだけを有効にすれば十分です。使わないモジュールを無効にすると、電波利用時間が減り、バッテリーを節約でき、設定もシンプルになります。 A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
インターネット接続のために、メッシュのメッセージを MQTT サーバーとの間で橋渡しします。 This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
設定項目
説明
MQTTを有効化
MQTT ブリッジを切り替え
アドレス
MQTT サーバーのアドレス
ユーザー名
認証用のユーザー名
パスワード
認証用のパスワード
暗号化の有効化
MQTT ペイロードを暗号化
JSON出力の有効化
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS の有効化
セキュアな接続を使用
ルート トピック
MQTT のベーストピックパス
クライアントへのプロキシの有効化
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
マップレポート
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
設定項目
説明
同意します。
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
シリアルボーレイト
Port speed
タイムアウト
How long to wait before considering an incoming message complete
コンソールのシリアルポートを上書き
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. メッセージ到着時に物理的に知らせる必要があるデバイスに便利です。特に無人設置や屋外設置で役立ちます。
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
設定項目
説明
外部通知を有効化
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
LED出力 (GPIO)
Pin the LED is wired to
LED出力 アクティブハイ
Whether the LED pin is active high or low
ブザー出力(GPIO)
Pin the buzzer is wired to
バイブレーション出力 (GPIO)
Pin the vibration motor is wired to
PWMブザーを使用
Drive the buzzer with PWM, which allows tones rather than a single pitch
I2Sをブザーとして使用
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
着信音
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). スマートフォンを接続していなくても送信できる、クイック送信メッセージのリストを定義します。フィールドでの使用に最適です。
設定項目
説明
Canned message enabled
⚠️ Deprecated in the protobuf schema
メッセージ
改行で区切ったメッセージのリスト
ベルを送信
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
ロータリーエンコーダ #1 を有効化
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
上下/選択入力を有効化
A separate, simpler input scheme using up/down/select buttons rather than an encoder
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
ATAK および WinTAK と相互運用するための、Team Awareness Kit 連携です。 Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. 詳しい設定と使い方は、TAK 連携 を参照してください。
管理
リモート管理
管理者鍵を共有しているノードをリモートで設定します：
ノードリストで対象のノードを選択します。
そのノードの「設定」に移動します。
設定を変更します。
「保存」をタップします。変更がメッシュ経由で送信されます。
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
操作
内容
時刻を設定
Sends your phone’s clock to the node
再起動
Restarts the node
シャットダウン
Powers the node down
出荷時にリセット
Returns every setting to its factory default
NodeDBをリセット
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
バックアップと復元
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
詳細設定
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
ノードデータベースの整理
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
概要
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
謝辞
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
모듈 설정
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
설명
MQTT 활성화
Toggle MQTT bridge
서버 주소
MQTT broker address
사용자명
Authentication username
비밀번호
Authentication password
암호화 사용
Encrypt MQTT payloads
JSON 사용
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS 사용
Use secure connection
Root topic
Base MQTT topic path
Proxy to client 사용
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
맵 보고
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
설명
동의합니다.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
설명
시리얼 활성화
Activate serial communication
에코 활성화
Echo received serial data back
시리얼 모드
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
시리얼 baud rate
Port speed
시간 초과
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
설명
외부 알림 활성화
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
LED 출력 (GPIO)
Pin the LED is wired to
LED 출력 active high
Whether the LED pin is active high or low
부저 출력 (GPIO)
Pin the buzzer is wired to
진동 출력 (GPIO)
Pin the vibration motor is wired to
PWM 부저 사용
Drive the buzzer with PWM, which allows tones rather than a single pitch
I2S 부저 사용
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
벨소리
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
설명
저장 및 전달 활성화
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
서버
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
설명
거리 테스트 활성화
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
.CSV 파일 저장 (EPS32만 동작)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
설명
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
환경 메트릭 모듈 사용
Report the attached environment sensors
Environment metrics update interval
How often to report them
환경 메트릭 화면 사용
Also show these readings on the device’s own display
환경 메트릭에서 화씨 사용
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
대기질 메트릭 모듈 사용
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
전력 메트릭 모듈 사용
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
전력 메트릭 화면 사용
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
설명
Canned message enabled
⚠️ Deprecated in the protobuf schema
메시지기기
Newline-separated list of messages
벨 전송
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
로터리 엔코더 #1 활성화
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
업/다운/선택 입력 활성화
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
설명
CODEC2 활성화
Activate audio module
CODEC2 샘플 레이트
Audio quality/bandwidth tradeoff
PTT 핀
GPIO pin for the push-to-talk button
I2S 단어 선택
GPIO pin for I2S WS
I2S 데이터 in
GPIO pin for I2S DIN
I2S 데이터 out
GPIO pin for I2S DOUT
I2S 시간
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
설명
원격 하드웨어 활성화
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
설명
이웃 정보 활성화
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
LoRa로 전송
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
설명
LED 상태
Turn the LED on or off
전류
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
설명
감지 센서 활성화
Activate detection sensor
상태 모니터링 GPIO 핀
GPIO pin connected to sensor
디텍션 트리거 타입
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
INPUT_PULLUP 모드 사용
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
알람 메시지와 벨 전송
Include bell character in alerts
식별 이름
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
설명
팍스카운터 활성화
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
관리
원격 설정
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
재부팅
Restarts the node
종료
Powers the node down
공장초기화
Returns every setting to its factory default
노드 목록 리셋
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
백업 & 복구
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
고급
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
디버그 패널
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
앱에 대하여
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
모듈 설정
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
설명
MQTT 활성화
Toggle MQTT bridge
서버 주소
MQTT broker address
사용자명
Authentication username
비밀번호
Authentication password
암호화 사용
Encrypt MQTT payloads
JSON 사용
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS 사용
Use secure connection
Root topic
Base MQTT topic path
Proxy to client 사용
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
맵 보고
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
설명
동의합니다.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
설명
시리얼 활성화
Activate serial communication
에코 활성화
Echo received serial data back
시리얼 모드
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
시리얼 baud rate
Port speed
시간 초과
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
설명
외부 알림 활성화
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
LED 출력 (GPIO)
Pin the LED is wired to
LED 출력 active high
Whether the LED pin is active high or low
부저 출력 (GPIO)
Pin the buzzer is wired to
진동 출력 (GPIO)
Pin the vibration motor is wired to
PWM 부저 사용
Drive the buzzer with PWM, which allows tones rather than a single pitch
I2S 부저 사용
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
벨소리
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
설명
저장 및 전달 활성화
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
서버
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
설명
거리 테스트 활성화
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
.CSV 파일 저장 (EPS32만 동작)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
설명
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
환경 메트릭 모듈 사용
Report the attached environment sensors
Environment metrics update interval
How often to report them
환경 메트릭 화면 사용
Also show these readings on the device’s own display
환경 메트릭에서 화씨 사용
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
대기질 메트릭 모듈 사용
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
전력 메트릭 모듈 사용
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
전력 메트릭 화면 사용
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
설명
Canned message enabled
⚠️ Deprecated in the protobuf schema
메시지기기
Newline-separated list of messages
벨 전송
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
로터리 엔코더 #1 활성화
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
업/다운/선택 입력 활성화
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
설명
CODEC2 활성화
Activate audio module
CODEC2 샘플 레이트
Audio quality/bandwidth tradeoff
PTT 핀
GPIO pin for the push-to-talk button
I2S 단어 선택
GPIO pin for I2S WS
I2S 데이터 in
GPIO pin for I2S DIN
I2S 데이터 out
GPIO pin for I2S DOUT
I2S 시간
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
설명
원격 하드웨어 활성화
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
설명
이웃 정보 활성화
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
LoRa로 전송
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
설명
LED 상태
Turn the LED on or off
전류
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
설명
감지 센서 활성화
Activate detection sensor
상태 모니터링 GPIO 핀
GPIO pin connected to sensor
디텍션 트리거 타입
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
INPUT_PULLUP 모드 사용
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
알람 메시지와 벨 전송
Include bell character in alerts
식별 이름
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
설명
팍스카운터 활성화
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
관리
원격 설정
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
재부팅
Restarts the node
종료
Powers the node down
공장초기화
Returns every setting to its factory default
노드 목록 리셋
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
백업 & 복구
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
고급
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
디버그 패널
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
앱에 대하여
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Modulio konfigūracija
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Aprašymas
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Aprašymas
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Aprašymas
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Baigėsi laikas
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Aprašymas
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Aprašymas
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Aprašymas
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Aprašymas
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Aprašymas
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Aprašymas
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Aprašymas
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Aprašymas
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Aprašymas
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Aprašymas
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Aprašymas
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administravimas
Nuotolinis administravimas
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Perkrauti
Restarts the node
Išjungti
Powers the node down
Gamyklinis atstatymas
Returns every setting to its factory default
NodeDB perkrauti
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Derinimo skydelis
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Apie
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Modulio konfigūracija
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Aprašymas
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Aprašymas
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Aprašymas
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Baigėsi laikas
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Aprašymas
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Aprašymas
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Aprašymas
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Aprašymas
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Aprašymas
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Aprašymas
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Aprašymas
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Aprašymas
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Aprašymas
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Aprašymas
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Aprašymas
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administravimas
Nuotolinis administravimas
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Perkrauti
Restarts the node
Išjungti
Powers the node down
Gamyklinis atstatymas
Returns every setting to its factory default
NodeDB perkrauti
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Derinimo skydelis
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Apie
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Module-configuratie
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Beschrijving
MQTT ingeschakeld
Toggle MQTT bridge
Adres
MQTT broker address
Gebruikersnaam
Authentication username
Wachtwoord
Authentication password
Encryptie ingeschakeld
Encrypt MQTT payloads
JSON uitvoer ingeschakeld
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS ingeschakeld
Use secure connection
Root topic
Base MQTT topic path
Proxy to client ingeschakeld
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Kaartrapportage
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Beschrijving
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Beschrijving
Serieel ingeschakeld
Activate serial communication
Echo ingeschakeld
Echo received serial data back
Seriële modus
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Time-Out
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Beschrijving
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Gebruik PWM zoemer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Beltoon
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Beschrijving
Store & Forward enabled
Activate store and forward
Hartslag
Periodically announce this node’s store-and-forward capability
Aantal records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Beschrijving
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Beschrijving
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Beschrijving
Canned message enabled
⚠️ Deprecated in the protobuf schema
Berichten
Newline-separated list of messages
Verstuur bel
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Beschrijving
CODEC 2 ingeschakeld
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S klok
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Beschrijving
Externe hardware ingeschakeld
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Beschikbare pinnen
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Beschrijving
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Zend over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Beschrijving
LED status
Turn the LED on or off
Huidige
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Beschrijving
Bewegingssensor Ingeschakeld
Activate detection sensor
GPIO pin om te monitoren
GPIO pin connected to sensor
Detectie trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Weergavenaam
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Beschrijving
Paxcounter ingeschakeld
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Beheer
Extern beheer
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Herstart
Restarts the node
Zet uit
Powers the node down
Reset naar fabrieksinstellingen
Returns every setting to its factory default
NodeDB reset
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Back-up & Herstellen
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Debug-paneel
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Over
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Module-configuratie
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Beschrijving
MQTT ingeschakeld
Toggle MQTT bridge
Adres
MQTT broker address
Gebruikersnaam
Authentication username
Wachtwoord
Authentication password
Encryptie ingeschakeld
Encrypt MQTT payloads
JSON uitvoer ingeschakeld
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS ingeschakeld
Use secure connection
Root topic
Base MQTT topic path
Proxy to client ingeschakeld
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Kaartrapportage
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Beschrijving
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Beschrijving
Serieel ingeschakeld
Activate serial communication
Echo ingeschakeld
Echo received serial data back
Seriële modus
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Time-Out
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Beschrijving
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Gebruik PWM zoemer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Beltoon
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Beschrijving
Store & Forward enabled
Activate store and forward
Hartslag
Periodically announce this node’s store-and-forward capability
Aantal records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Beschrijving
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Beschrijving
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Beschrijving
Canned message enabled
⚠️ Deprecated in the protobuf schema
Berichten
Newline-separated list of messages
Verstuur bel
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Beschrijving
CODEC 2 ingeschakeld
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S klok
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Beschrijving
Externe hardware ingeschakeld
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Beschikbare pinnen
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Beschrijving
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Zend over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Beschrijving
LED status
Turn the LED on or off
Huidige
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Beschrijving
Bewegingssensor Ingeschakeld
Activate detection sensor
GPIO pin om te monitoren
GPIO pin connected to sensor
Detectie trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Weergavenaam
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Beschrijving
Paxcounter ingeschakeld
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Beheer
Extern beheer
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Herstart
Restarts the node
Zet uit
Powers the node down
Reset naar fabrieksinstellingen
Returns every setting to its factory default
NodeDB reset
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Back-up & Herstellen
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Debug-paneel
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Over
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Modul konfigurasjon
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Beskrivelse
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Beskrivelse
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Beskrivelse
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Tidsavbrudd
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Beskrivelse
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Beskrivelse
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Beskrivelse
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Beskrivelse
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Beskrivelse
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Beskrivelse
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Beskrivelse
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Beskrivelse
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Beskrivelse
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Beskrivelse
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Beskrivelse
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administrasjon
Fjernadministrasjon
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Omstart
Restarts the node
Avslutt
Powers the node down
Tilbakestill til fabrikkstandard
Returns every setting to its factory default
NodeDB reset
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Feilsøkningspanel
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Om
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Modul konfigurasjon
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Beskrivelse
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Beskrivelse
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Beskrivelse
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Tidsavbrudd
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Beskrivelse
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Beskrivelse
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Beskrivelse
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Beskrivelse
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Beskrivelse
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Beskrivelse
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Beskrivelse
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Beskrivelse
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Beskrivelse
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Beskrivelse
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Beskrivelse
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administrasjon
Fjernadministrasjon
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Omstart
Restarts the node
Avslutt
Powers the node down
Tilbakestill til fabrikkstandard
Returns every setting to its factory default
NodeDB reset
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Feilsøkningspanel
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Om
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Udostępniaj swoją lokalizację w czasie rzeczywistym i koordynuj działania swojej grupy dzięki zintegrowanym funkcjom GPS.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Udostępniaj swoją lokalizację w czasie rzeczywistym i koordynuj działania swojej grupy dzięki zintegrowanym funkcjom GPS.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Ustawienia modułu
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Opis
Włącz MQTT
Toggle MQTT bridge
Adres
MQTT broker address
Nazwa użytkownika
Authentication username
Hasło
Authentication password
Szyfrowanie włączone
Encrypt MQTT payloads
Włącz wyjście JSON
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
Włącz TLS
Use secure connection
Główny wątek
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Raportowanie map
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Opis
Zgadzam się.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Opis
Włącz tryb serial
Activate serial communication
Włącz echo
Echo received serial data back
Tryb serial
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Prędkość transmisji
Port speed
Limit czasu
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Opis
Powiadomienia zewnętrzne włączone
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Wyjście LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Wyjście buzzera (GPIO)
Pin the buzzer is wired to
Wyjście silnika wibracyjnego (GPIO)
Pin the vibration motor is wired to
Użyj buzzer PWM
Drive the buzzer with PWM, which allows tones rather than a single pitch
Użyj I2S jako buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Czas przerwy
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Dzwonek
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Opis
Store & Forward enabled
Activate store and forward
Bicie serca
Periodically announce this node’s store-and-forward capability
Liczba rekordów
Maximum stored messages
Maks zwrotnej historii
Max messages to replay
Okno zwrotu historii
Time window for replay
Serwer
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Opis
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Opis
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Włącz moduł metryk jakości powietrza
Report particulate and CO₂ sensor data
Czas aktualizacji metryk jakości powietrza
How often to report them
Włącz moduł metryk zasilania
Report the per-channel voltage and current readings
Czas aktualizacji metryk zasilania
How often to report them
Wyświetlaj metryki zasilania na ekranie
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Opis
Canned message enabled
⚠️ Deprecated in the protobuf schema
Wiadomości
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Opis
CODEC 2 włączony
Activate audio module
Częstotliwość próbkowania CODEC2
Audio quality/bandwidth tradeoff
Pin PTT (Push-To-Talk)
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
Zegar I2S
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Opis
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Dostępne piny
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Opis
Włącz informacje o sąsiedzie
Activate neighbor broadcasting
Częstotliwość aktualizacji
How often to broadcast neighbor list
Nadaj przez LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Opis
Stan diody LED
Turn the LED on or off
Natężenie
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Opis
Czujnik detekcji włączony
Activate detection sensor
Pin GPIO do monitorowania
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Użyj trybu INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Przyjazna nazwa
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Opis
Paxcounter enabled
Activate people counting
Częstotliwość aktualizacji
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Zarządzanie
Zdalne zarządzanie
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Uruchom ponownie
Restarts the node
Wyłącz
Powers the node down
Ustawienia fabryczne
Returns every setting to its factory default
Zresetuj NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Kopia zapasowa i przywracanie
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Zaawansowane
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Wyczyść bazę węzłów
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panel debugowania
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
O aplikacji
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Potwierdzenia
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Ustawienia modułu
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Opis
Włącz MQTT
Toggle MQTT bridge
Adres
MQTT broker address
Nazwa użytkownika
Authentication username
Hasło
Authentication password
Szyfrowanie włączone
Encrypt MQTT payloads
Włącz wyjście JSON
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
Włącz TLS
Use secure connection
Główny wątek
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Raportowanie map
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Opis
Zgadzam się.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Opis
Włącz tryb serial
Activate serial communication
Włącz echo
Echo received serial data back
Tryb serial
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Prędkość transmisji
Port speed
Limit czasu
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Opis
Powiadomienia zewnętrzne włączone
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Wyjście LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Wyjście buzzera (GPIO)
Pin the buzzer is wired to
Wyjście silnika wibracyjnego (GPIO)
Pin the vibration motor is wired to
Użyj buzzer PWM
Drive the buzzer with PWM, which allows tones rather than a single pitch
Użyj I2S jako buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Czas przerwy
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Dzwonek
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Opis
Store & Forward enabled
Activate store and forward
Bicie serca
Periodically announce this node’s store-and-forward capability
Liczba rekordów
Maximum stored messages
Maks zwrotnej historii
Max messages to replay
Okno zwrotu historii
Time window for replay
Serwer
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Opis
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Opis
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Włącz moduł metryk jakości powietrza
Report particulate and CO₂ sensor data
Czas aktualizacji metryk jakości powietrza
How often to report them
Włącz moduł metryk zasilania
Report the per-channel voltage and current readings
Czas aktualizacji metryk zasilania
How often to report them
Wyświetlaj metryki zasilania na ekranie
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Opis
Canned message enabled
⚠️ Deprecated in the protobuf schema
Wiadomości
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Opis
CODEC 2 włączony
Activate audio module
Częstotliwość próbkowania CODEC2
Audio quality/bandwidth tradeoff
Pin PTT (Push-To-Talk)
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
Zegar I2S
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Opis
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Dostępne piny
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Opis
Włącz informacje o sąsiedzie
Activate neighbor broadcasting
Częstotliwość aktualizacji
How often to broadcast neighbor list
Nadaj przez LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Opis
Stan diody LED
Turn the LED on or off
Natężenie
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Opis
Czujnik detekcji włączony
Activate detection sensor
Pin GPIO do monitorowania
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Użyj trybu INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Przyjazna nazwa
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Opis
Paxcounter enabled
Activate people counting
Częstotliwość aktualizacji
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Zarządzanie
Zdalne zarządzanie
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Uruchom ponownie
Restarts the node
Wyłącz
Powers the node down
Ustawienia fabryczne
Returns every setting to its factory default
Zresetuj NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Kopia zapasowa i przywracanie
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Zaawansowane
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Wyczyść bazę węzłów
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panel debugowania
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
O aplikacji
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Potwierdzenia
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
🌐 Português (Brasil) — Community translation View in English
Debug Logs
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
🌐 Português (Brasil) — Community translation View in English
Debug Logs
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
🌐 Português (Brasil) — Community translation View in English
Getting Started
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Comunique-se off-grid com seus amigos e comunidades sem serviço de celular.
Create Your Own Networks
Configure facilmente redes de malha privada para uma comunicação segura e confiável em áreas remotas.
Track and Share Locations
Compartilhe sua localização em tempo real e mantenha seu grupo coordenado com recursos integrados de GPS.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
🌐 Português (Brasil) — Community translation View in English
Getting Started
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Comunique-se off-grid com seus amigos e comunidades sem serviço de celular.
Create Your Own Networks
Configure facilmente redes de malha privada para uma comunicação segura e confiável em áreas remotas.
Track and Share Locations
Compartilhe sua localização em tempo real e mantenha seu grupo coordenado com recursos integrados de GPS.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
🌐 Português (Brasil) — Community translation View in English
Settings — Modules & Admin
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Configuração de módulos
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Descrição
MQTT habilitado
Toggle MQTT bridge
Endereço
MQTT broker address
Nome de usuário
Authentication username
Senha
Authentication password
Criptografia ativada
Encrypt MQTT payloads
Saída JSON ativada
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS ativado
Use secure connection
Tópico principal
Base MQTT topic path
Proxy para cliente ativado
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Relatório de mapa
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Descrição
Eu concordo.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Descrição
Serial ativado
Activate serial communication
Eco habilitado
Echo received serial data back
Modo de série
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Taxa de transmissão série
Port speed
Tempo esgotado
How long to wait before considering an incoming message complete
Substituir porta série do console
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Descrição
Notificação Externa habilitada
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
LED de Saída (GPIO)
Pin the LED is wired to
LED de saída habilitado alto
Whether the LED pin is active high or low
Saída Campainha (GPIO)
Pin the buzzer is wired to
Vibra de saída (GPIO)
Pin the vibration motor is wired to
Usar uma campainha PWM
Drive the buzzer with PWM, which allows tones rather than a single pitch
Usar I2S como campainha
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Toque
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Descrição
Guardar e Encaminhar ativado
Activate store and forward
Batimento
Periodically announce this node’s store-and-forward capability
Número de registros
Maximum stored messages
Histórico de retorno máximo
Max messages to replay
Janela de retorno do histórico
Time window for replay
Servidor
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Descrição
Teste de distância ativado
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Salvar .CSV no armazenamento (apenas ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Descrição
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Módulo de métricas do ambiente ativado
Report the attached environment sensors
Environment metrics update interval
How often to report them
Métricas de ambiente na tela habilitado
Also show these readings on the device’s own display
Métricas de Ambiente usam Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Módulo de métricas de qualidade do ar habilitado
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Módulo de métricas de energia habilitado
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Métricas de ambiente na tela habilitado
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Descrição
Canned message enabled
⚠️ Deprecated in the protobuf schema
Mensagens
Newline-separated list of messages
Enviar sino
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Codificador rotativo #1 ativado
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Entrada Cima/Baixo/Selecionar ativada
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Descrição
CODEC 2 ativado
Activate audio module
Taxa de amostragem CODEC2
Audio quality/bandwidth tradeoff
Pino de PTT
GPIO pin for the push-to-talk button
CS I2S
GPIO pin for I2S WS
MOSI I2S
GPIO pin for I2S DIN
MISO I2S
GPIO pin for I2S DOUT
CLK I2S
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Descrição
Hardware Remoto ativado
Activate remote GPIO access
Permitir acesso indefinido ao pino
Allow access to any GPIO pin (security risk)
Pinos disponíveis
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Descrição
Informações do Vizinho ativado
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmitir por LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Descrição
Estado do LED
Turn the LED on or off
Atual
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Descrição
Sensor de Detecção ativado
Activate detection sensor
Pino GPIO para monitorar
GPIO pin connected to sensor
Tipo de gatilho de deteção
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Usar o modo INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Enviar sino com mensagem de alerta
Include bell character in alerts
Nome amigável
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Descrição
Contador de Pessoas ativado
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administração
Administração Remota
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Reiniciar
Restarts the node
Desligar
Powers the node down
Redefinição de fábrica
Returns every setting to its factory default
Redefinir NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup e Restaurar
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Avançado
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Limpar Banco de Dados de Nó
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Painel de depuração
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Sobre
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Agradecimentos
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
🌐 Português (Brasil) — Community translation View in English
Settings — Modules & Admin
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Configuração de módulos
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Descrição
MQTT habilitado
Toggle MQTT bridge
Endereço
MQTT broker address
Nome de usuário
Authentication username
Senha
Authentication password
Criptografia ativada
Encrypt MQTT payloads
Saída JSON ativada
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS ativado
Use secure connection
Tópico principal
Base MQTT topic path
Proxy para cliente ativado
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Relatório de mapa
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Descrição
Eu concordo.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Descrição
Serial ativado
Activate serial communication
Eco habilitado
Echo received serial data back
Modo de série
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Taxa de transmissão série
Port speed
Tempo esgotado
How long to wait before considering an incoming message complete
Substituir porta série do console
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Descrição
Notificação Externa habilitada
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
LED de Saída (GPIO)
Pin the LED is wired to
LED de saída habilitado alto
Whether the LED pin is active high or low
Saída Campainha (GPIO)
Pin the buzzer is wired to
Vibra de saída (GPIO)
Pin the vibration motor is wired to
Usar uma campainha PWM
Drive the buzzer with PWM, which allows tones rather than a single pitch
Usar I2S como campainha
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Toque
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Descrição
Guardar e Encaminhar ativado
Activate store and forward
Batimento
Periodically announce this node’s store-and-forward capability
Número de registros
Maximum stored messages
Histórico de retorno máximo
Max messages to replay
Janela de retorno do histórico
Time window for replay
Servidor
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Descrição
Teste de distância ativado
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Salvar .CSV no armazenamento (apenas ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Descrição
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Módulo de métricas do ambiente ativado
Report the attached environment sensors
Environment metrics update interval
How often to report them
Métricas de ambiente na tela habilitado
Also show these readings on the device’s own display
Métricas de Ambiente usam Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Módulo de métricas de qualidade do ar habilitado
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Módulo de métricas de energia habilitado
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Métricas de ambiente na tela habilitado
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Descrição
Canned message enabled
⚠️ Deprecated in the protobuf schema
Mensagens
Newline-separated list of messages
Enviar sino
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Codificador rotativo #1 ativado
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Entrada Cima/Baixo/Selecionar ativada
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Descrição
CODEC 2 ativado
Activate audio module
Taxa de amostragem CODEC2
Audio quality/bandwidth tradeoff
Pino de PTT
GPIO pin for the push-to-talk button
CS I2S
GPIO pin for I2S WS
MOSI I2S
GPIO pin for I2S DIN
MISO I2S
GPIO pin for I2S DOUT
CLK I2S
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Descrição
Hardware Remoto ativado
Activate remote GPIO access
Permitir acesso indefinido ao pino
Allow access to any GPIO pin (security risk)
Pinos disponíveis
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Descrição
Informações do Vizinho ativado
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmitir por LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Descrição
Estado do LED
Turn the LED on or off
Atual
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Descrição
Sensor de Detecção ativado
Activate detection sensor
Pino GPIO para monitorar
GPIO pin connected to sensor
Tipo de gatilho de deteção
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Usar o modo INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Enviar sino com mensagem de alerta
Include bell character in alerts
Nome amigável
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Descrição
Contador de Pessoas ativado
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administração
Administração Remota
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Reiniciar
Restarts the node
Desligar
Powers the node down
Redefinição de fábrica
Returns every setting to its factory default
Redefinir NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup e Restaurar
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Avançado
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Limpar Banco de Dados de Nó
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Painel de depuração
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Sobre
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Agradecimentos
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Configurações dos módulos
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Descrição
MQTT ativo
Toggle MQTT bridge
Endereço
MQTT broker address
Utilizador
Authentication username
Palavra-passe
Authentication password
Encriptação ativada
Encrypt MQTT payloads
Saída JSON ativada
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
Ativar TLS
Use secure connection
Tópico principal
Base MQTT topic path
Enviar através do cliente
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Enviar para o mapa
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Descrição
Estou de acordo.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Descrição
Série ativada
Activate serial communication
Eco ativado
Echo received serial data back
Modo de série
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Taxa de transmissão série
Port speed
Timeout
How long to wait before considering an incoming message complete
Substituir porta série do console
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Descrição
Ativar notificações externas
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
LED de Saída (GPIO)
Pin the LED is wired to
LED de saída ativo alto
Whether the LED pin is active high or low
Buzzer de saída (GPIO)
Pin the buzzer is wired to
Vibra de saída (GPIO)
Pin the vibration motor is wired to
Usar um buzzer PWM
Drive the buzzer with PWM, which allows tones rather than a single pitch
Usar I2S como buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Toque
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Descrição
Guardar & encaminhar ativo
Activate store and forward
Batimento
Periodically announce this node’s store-and-forward capability
Número de registos
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Servidor
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Descrição
Ativar Teste de alcance
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Guardar .CSV no armazenamento (apenas ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Descrição
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Módulo de métricas de ambiente ativado
Report the attached environment sensors
Environment metrics update interval
How often to report them
Mostrar métricas de ambiente no ecrã
Also show these readings on the device’s own display
Métricas de Ambiente usam Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Módulo de métricas de qualidade do ar ativado
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Módulo de métricas de energia ativado
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Mostrar métricas de energia no ecrã
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Descrição
Canned message enabled
⚠️ Deprecated in the protobuf schema
Mensagens
Newline-separated list of messages
Enviar sino
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Ativar Codificador rotativo #1
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Entrada Cima/Baixo/Selecionar ativa
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Descrição
CODEC 2 ativado
Activate audio module
Taxa de amostragem CODEC2
Audio quality/bandwidth tradeoff
Pin de PTT
GPIO pin for the push-to-talk button
Selecionar palavra I2S
GPIO pin for I2S WS
Entrada de dados I2S
GPIO pin for I2S DIN
Saída de dados I2S
GPIO pin for I2S DOUT
Relógio I2S
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Descrição
Hardware Remoto ativado
Activate remote GPIO access
Permitir acesso indefinido ao pin
Allow access to any GPIO pin (security risk)
Pins disponíveis
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Descrição
Enviar informações de vizinhos
Activate neighbor broadcasting
Intervalo de Atualização
How often to broadcast neighbor list
Enviar por LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Descrição
Estado do LED
Turn the LED on or off
Atual
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Descrição
Sensor de deteção ativado
Activate detection sensor
Pin GPIO para monitorizar
GPIO pin connected to sensor
Tipo de gatilho de deteção
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Usar o modo INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Enviar sino com mensagem de alerta
Include bell character in alerts
Nome amigável
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Descrição
Ativar contador de pessoas
Activate people counting
Intervalo de Atualização
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administração
Administração Remota
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Reiniciar
Restarts the node
Desligar
Powers the node down
Redefinição de fábrica
Returns every setting to its factory default
Redefinir NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restauro
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Painel de depuração
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Sobre
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Configurações dos módulos
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Descrição
MQTT ativo
Toggle MQTT bridge
Endereço
MQTT broker address
Utilizador
Authentication username
Palavra-passe
Authentication password
Encriptação ativada
Encrypt MQTT payloads
Saída JSON ativada
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
Ativar TLS
Use secure connection
Tópico principal
Base MQTT topic path
Enviar através do cliente
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Enviar para o mapa
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Descrição
Estou de acordo.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Descrição
Série ativada
Activate serial communication
Eco ativado
Echo received serial data back
Modo de série
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Taxa de transmissão série
Port speed
Timeout
How long to wait before considering an incoming message complete
Substituir porta série do console
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Descrição
Ativar notificações externas
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
LED de Saída (GPIO)
Pin the LED is wired to
LED de saída ativo alto
Whether the LED pin is active high or low
Buzzer de saída (GPIO)
Pin the buzzer is wired to
Vibra de saída (GPIO)
Pin the vibration motor is wired to
Usar um buzzer PWM
Drive the buzzer with PWM, which allows tones rather than a single pitch
Usar I2S como buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Toque
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Descrição
Guardar & encaminhar ativo
Activate store and forward
Batimento
Periodically announce this node’s store-and-forward capability
Número de registos
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Servidor
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Descrição
Ativar Teste de alcance
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Guardar .CSV no armazenamento (apenas ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Descrição
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Módulo de métricas de ambiente ativado
Report the attached environment sensors
Environment metrics update interval
How often to report them
Mostrar métricas de ambiente no ecrã
Also show these readings on the device’s own display
Métricas de Ambiente usam Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Módulo de métricas de qualidade do ar ativado
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Módulo de métricas de energia ativado
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Mostrar métricas de energia no ecrã
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Descrição
Canned message enabled
⚠️ Deprecated in the protobuf schema
Mensagens
Newline-separated list of messages
Enviar sino
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Ativar Codificador rotativo #1
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Entrada Cima/Baixo/Selecionar ativa
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Descrição
CODEC 2 ativado
Activate audio module
Taxa de amostragem CODEC2
Audio quality/bandwidth tradeoff
Pin de PTT
GPIO pin for the push-to-talk button
Selecionar palavra I2S
GPIO pin for I2S WS
Entrada de dados I2S
GPIO pin for I2S DIN
Saída de dados I2S
GPIO pin for I2S DOUT
Relógio I2S
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Descrição
Hardware Remoto ativado
Activate remote GPIO access
Permitir acesso indefinido ao pin
Allow access to any GPIO pin (security risk)
Pins disponíveis
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Descrição
Enviar informações de vizinhos
Activate neighbor broadcasting
Intervalo de Atualização
How often to broadcast neighbor list
Enviar por LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Descrição
Estado do LED
Turn the LED on or off
Atual
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Descrição
Sensor de deteção ativado
Activate detection sensor
Pin GPIO para monitorizar
GPIO pin connected to sensor
Tipo de gatilho de deteção
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Usar o modo INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Enviar sino com mensagem de alerta
Include bell character in alerts
Nome amigável
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Descrição
Ativar contador de pessoas
Activate people counting
Intervalo de Atualização
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administração
Administração Remota
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Reiniciar
Restarts the node
Desligar
Powers the node down
Redefinição de fábrica
Returns every setting to its factory default
Redefinir NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restauro
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Painel de depuração
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Sobre
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Comunicați în afara grilei cu prietenii și comunitatea dvs. fără serviciu celular.
Create Your Own Networks
Înființarea cu ușurință a rețelelor private de plasare pentru comunicații sigure și fiabile în zonele îndepărtate;
Track and Share Locations
Partajați-vă locația în timp real și păstrați grupul coordonat cu funcții GPS integrate.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Comunicați în afara grilei cu prietenii și comunitatea dvs. fără serviciu celular.
Create Your Own Networks
Înființarea cu ușurință a rețelelor private de plasare pentru comunicații sigure și fiabile în zonele îndepărtate;
Track and Share Locations
Partajați-vă locația în timp real și păstrați grupul coordonat cu funcții GPS integrate.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Configurare modul
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Descriere
MQTT activat
Toggle MQTT bridge
Adresă
MQTT broker address
Nume de utilizator
Authentication username
Parolă
Authentication password
Criptare activată
Encrypt MQTT payloads
Ieșire JSON activată
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS activat
Use secure connection
Temă rădăcină
Base MQTT topic path
Proxy-ul pentru client activat
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Raportarea hărții
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Descriere
Sunt de acord
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Descriere
Serial activat
Activate serial communication
Echo activat
Echo received serial data back
Mod serial
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Rata baud-ului serial
Port speed
Expirat
How long to wait before considering an incoming message complete
Suprascrie portul serial al consolei
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Descriere
Notificare externă activată
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
LED ieșire (GPIO)
Pin the LED is wired to
LED de ieșire activ ridicat
Whether the LED pin is active high or low
Buzzer ieșire (GPIO)
Pin the buzzer is wired to
Ieșire vibrație (GPIO)
Pin the vibration motor is wired to
Utilizează buzzer PWM
Drive the buzzer with PWM, which allows tones rather than a single pitch
Utilizează I2S ca buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Sonerie
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Descriere
Reținere și redirecționare activată
Activate store and forward
Puls
Periodically announce this node’s store-and-forward capability
Numarul de inregistrari
Maximum stored messages
istoric număr maxim de retur
Max messages to replay
Fereastra de returnare a istoricului
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Descriere
Testul de gamă activat
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Salvați .CSV doar în memorie (ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Descriere
Trimite telemetrie dispozitiv
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervalul de actualizare a parametrilor dispozitivului
How often to report battery, uptime and channel utilization
Modul de măsurare mediu activat
Report the attached environment sensors
Interval actualizare valori mediu
How often to report them
Valorile de mediu pe ecran sunt activate
Also show these readings on the device’s own display
Valorile de mediu utilizează Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Interval actualizare măsurători de calitate a aerului
How often to report them
Modul de măsurare putere activat
Report the per-channel voltage and current readings
Interval actualizare măsurători de putere
How often to report them
Valori pe ecran activate
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Descriere
Canned message enabled
⚠️ Deprecated in the protobuf schema
Mesaje
Newline-separated list of messages
Trimite clopoțel
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encoder rotativ #1 activat
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Intrare sus/jos/selectare activată
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Descriere
CODEC 2 activat
Activate audio module
Rată de eșantionare CODEC2
Audio quality/bandwidth tradeoff
Pin PTT
GPIO pin for the push-to-talk button
Selectare cuvânt I2S
GPIO pin for I2S WS
Intrare date I2S
GPIO pin for I2S DIN
Ieșire date I2S
GPIO pin for I2S DOUT
Ceas I2S
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Descriere
Hardware extern activat
Activate remote GPIO access
Permite acces Pin nedefinit
Allow access to any GPIO pin (security risk)
Pin-uri disponibile
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Descriere
Info vecin activat
Activate neighbor broadcasting
Interval de actualizare GPS
How often to broadcast neighbor list
Transmite peste LoRA
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Descriere
Stare LED
Turn the LED on or off
Actual
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Descriere
Senzor detectare activat
Activate detection sensor
Pin GPIO de monitorizat
GPIO pin connected to sensor
Tip declanșator detectare
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Folosește modul INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Trimite clopoțelul cu mesaj de alertă
Include bell character in alerts
Nume comun
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Descriere
Paxcounter activat
Activate people counting
Interval de actualizare GPS
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administrare
Administrare la distanță
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Restartează
Restarts the node
Oprire
Powers the node down
Resetare la setările din fabrică
Returns every setting to its factory default
Resetare NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Copie de rezervă și restaurare
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Avansate
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Curăță baza de date a nodurilor
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panou de depanare
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Despre
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Mulțumiri
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Configurare modul
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Descriere
MQTT activat
Toggle MQTT bridge
Adresă
MQTT broker address
Nume de utilizator
Authentication username
Parolă
Authentication password
Criptare activată
Encrypt MQTT payloads
Ieșire JSON activată
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS activat
Use secure connection
Temă rădăcină
Base MQTT topic path
Proxy-ul pentru client activat
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Raportarea hărții
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Descriere
Sunt de acord
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Descriere
Serial activat
Activate serial communication
Echo activat
Echo received serial data back
Mod serial
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Rata baud-ului serial
Port speed
Expirat
How long to wait before considering an incoming message complete
Suprascrie portul serial al consolei
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Descriere
Notificare externă activată
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
LED ieșire (GPIO)
Pin the LED is wired to
LED de ieșire activ ridicat
Whether the LED pin is active high or low
Buzzer ieșire (GPIO)
Pin the buzzer is wired to
Ieșire vibrație (GPIO)
Pin the vibration motor is wired to
Utilizează buzzer PWM
Drive the buzzer with PWM, which allows tones rather than a single pitch
Utilizează I2S ca buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Sonerie
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Descriere
Reținere și redirecționare activată
Activate store and forward
Puls
Periodically announce this node’s store-and-forward capability
Numarul de inregistrari
Maximum stored messages
istoric număr maxim de retur
Max messages to replay
Fereastra de returnare a istoricului
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Descriere
Testul de gamă activat
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Salvați .CSV doar în memorie (ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Descriere
Trimite telemetrie dispozitiv
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Intervalul de actualizare a parametrilor dispozitivului
How often to report battery, uptime and channel utilization
Modul de măsurare mediu activat
Report the attached environment sensors
Interval actualizare valori mediu
How often to report them
Valorile de mediu pe ecran sunt activate
Also show these readings on the device’s own display
Valorile de mediu utilizează Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Interval actualizare măsurători de calitate a aerului
How often to report them
Modul de măsurare putere activat
Report the per-channel voltage and current readings
Interval actualizare măsurători de putere
How often to report them
Valori pe ecran activate
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Descriere
Canned message enabled
⚠️ Deprecated in the protobuf schema
Mesaje
Newline-separated list of messages
Trimite clopoțel
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Encoder rotativ #1 activat
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Intrare sus/jos/selectare activată
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Descriere
CODEC 2 activat
Activate audio module
Rată de eșantionare CODEC2
Audio quality/bandwidth tradeoff
Pin PTT
GPIO pin for the push-to-talk button
Selectare cuvânt I2S
GPIO pin for I2S WS
Intrare date I2S
GPIO pin for I2S DIN
Ieșire date I2S
GPIO pin for I2S DOUT
Ceas I2S
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Descriere
Hardware extern activat
Activate remote GPIO access
Permite acces Pin nedefinit
Allow access to any GPIO pin (security risk)
Pin-uri disponibile
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Descriere
Info vecin activat
Activate neighbor broadcasting
Interval de actualizare GPS
How often to broadcast neighbor list
Transmite peste LoRA
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Descriere
Stare LED
Turn the LED on or off
Actual
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Descriere
Senzor detectare activat
Activate detection sensor
Pin GPIO de monitorizat
GPIO pin connected to sensor
Tip declanșator detectare
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Folosește modul INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Trimite clopoțelul cu mesaj de alertă
Include bell character in alerts
Nume comun
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Descriere
Paxcounter activat
Activate people counting
Interval de actualizare GPS
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administrare
Administrare la distanță
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Restartează
Restarts the node
Oprire
Powers the node down
Resetare la setările din fabrică
Returns every setting to its factory default
Resetare NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Copie de rezervă și restaurare
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Avansate
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Curăță baza de date a nodurilor
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panou de depanare
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Despre
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Mulțumiri
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Когда что-то работает неправильно, отладочные журналы приложения — это самое полезное, что вы можете приложить к отчёту об ошибке. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Откройте Панель отладки через Настройки → Дополнительно → Панель отладки.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. Захват журнала, охватывающий момент возникновения проблемы, превращает «это не работает» в то, что разработчик действительно может отследить.
Две вкладки
Панель отладки содержит две вкладки:
Пакеты — декодированный трафик mesh-сети, который ваше радио отправило и получило (сообщения уровня протокола). Полезно для диагностики поведения mesh-сети и маршрутизации.
Журналы приложения — собственный диагностический журнал приложения (Android logcat), включая предупреждения, ошибки и трассировки стека самого приложения. Обычно именно это требуется для отчёта об ошибке.
Каждая вкладка имеет собственную кнопку экспорта и создаёт отдельный файл, поэтому вы можете сохранить тот, который нужен — или сразу оба.
Просмотр журналов приложения
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Поиск — введите текст в поле поиска, чтобы отфильтровать строки по совпадению.
Фильтр по уровню — кнопки V / D / I / W / E переключают отображение строк с уровнями Verbose (Подробный), Debug (Отладка), Info (Информация), Warn (Предупреждение) и Error (Ошибка). Нажмите на уровень, чтобы скрыть его; нажмите ещё раз, чтобы вернуть обратно. Строки с фатальными ошибками отображаются всегда.
Обновить — значок обновления заново считывает последние записи журнала.
Строки с ошибками и предупреждениями подсвечиваются цветом, чтобы проблемы выделялись.
Экспорт
Нажмите на значок загрузки, чтобы сохранить текущие журналы в файл. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Прикрепите этот файл к своей задаче на GitHub.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
У компьютерного приложения нет системного logcat, поэтому вкладка Журналы приложения вместо этого показывает собственный захваченный вывод журнала приложения. Поиск, фильтрация и экспорт работают точно так же.
Когда что-то работает неправильно, отладочные журналы приложения — это самое полезное, что вы можете приложить к отчёту об ошибке. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Откройте Панель отладки через Настройки → Дополнительно → Панель отладки.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. Захват журнала, охватывающий момент возникновения проблемы, превращает «это не работает» в то, что разработчик действительно может отследить.
Две вкладки
Панель отладки содержит две вкладки:
Пакеты — декодированный трафик mesh-сети, который ваше радио отправило и получило (сообщения уровня протокола). Полезно для диагностики поведения mesh-сети и маршрутизации.
Журналы приложения — собственный диагностический журнал приложения (Android logcat), включая предупреждения, ошибки и трассировки стека самого приложения. Обычно именно это требуется для отчёта об ошибке.
Каждая вкладка имеет собственную кнопку экспорта и создаёт отдельный файл, поэтому вы можете сохранить тот, который нужен — или сразу оба.
Просмотр журналов приложения
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Поиск — введите текст в поле поиска, чтобы отфильтровать строки по совпадению.
Фильтр по уровню — кнопки V / D / I / W / E переключают отображение строк с уровнями Verbose (Подробный), Debug (Отладка), Info (Информация), Warn (Предупреждение) и Error (Ошибка). Нажмите на уровень, чтобы скрыть его; нажмите ещё раз, чтобы вернуть обратно. Строки с фатальными ошибками отображаются всегда.
Обновить — значок обновления заново считывает последние записи журнала.
Строки с ошибками и предупреждениями подсвечиваются цветом, чтобы проблемы выделялись.
Экспорт
Нажмите на значок загрузки, чтобы сохранить текущие журналы в файл. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Прикрепите этот файл к своей задаче на GitHub.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
У компьютерного приложения нет системного logcat, поэтому вкладка Журналы приложения вместо этого показывает собственный захваченный вывод журнала приложения. Поиск, фильтрация и экспорт работают точно так же. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
Подключения — если проблема в первую очередь связана с подключением к вашему радио
diff --git a/main/ru-rRU/user/onboarding.html b/main/ru-rRU/user/onboarding.html
index 088e6d76ea..862a6e6d27 100644
--- a/main/ru-rRU/user/onboarding.html
+++ b/main/ru-rRU/user/onboarding.html
@@ -1 +1 @@
- Начало работы | Meshtastic AndroidSkip to main content
На этой странице рассказывается о процессе первого запуска приложения Meshtastic для Android, для чего нужно каждое разрешение и как вернуться к нему позже.
Первый запуск
Когда ты открываешь приложение впервые, оно проводит тебя через вводный процесс, который настраивает необходимые разрешения и параметры. Выполни каждый шаг по порядку или пропусти — здесь ничто не является одноразовым предложением. Каждое разрешение можно просмотреть и выдать позже в разделе Разрешения в Настройках внутри приложения.
Экран приветствия
Экран приветствия знакомит с Meshtastic с тремя рядами функций:
Будь на связи везде
Общайтесь вне сети со своими друзьями и сообществом без использования сотовой связи.
Создавай свои собственные сети
Легко создать частные сети для защищённой и надежной связи в удаленных районах.
Отслеживай и делись местоположением
Делитесь своим местоположением в режиме реального времени и поддерживайте работу группы с функциями GPS.
Нажми Начать, чтобы пройти процесс настройки.
Разрешения
Приложение запрашивает несколько разрешений во время настройки. Каждое из них служит определенной цели, и некоторые необходимы для основной функциональности.
Разрешения Bluetooth
Bluetooth — это основной способ подключения твоего телефона к радиостанции Meshtastic. Экран Bluetooth показывает, что даёт тебе это разрешение:
Обнаружение — найди и определи устройства Meshtastic рядом с тобой.
Настройки — управляйте параметрами устройства и каналами по беспроводной сети.
На Android 12 и новее система спрашивает один раз про ближайшие устройства, и это разрешение покрывает и сканирование, и подключение. Без него придётся использовать USB или TCP-соединения.
Разрешение на доступ к местоположению
ℹ️ Примечание: Для Bluetooth на Android 12 и выше местоположение не требуется. Android 11 и старше показывают один шаг для местоположения на экране Bluetooth, а не два — эти версии рассматривают сканирование Bluetooth как функцию определения местоположения, поэтому приложение запрашивает доступ к Местоположению вместо “Ближайшие устройства”. Если спросить дважды, это приведёт к тому, что Android вообще перестанет показывать диалог (второй отказ на Android 11; галочка “Больше не спрашивать” на Android 10 и старее). На Android 12 и новее это два разных момента: “Ближайшие устройства” объявлены как neverForLocation, и отказ от доступа к местоположению не мешает находить или подключаться к радио.
Meshtastic также использует местоположение для:
Показ вашего положения на карте
Вычисление расстояний до других нод
Обмен GPS-координатами с другими участниками сети (если включено)
Предоставьте “При использовании приложения”. Приложение не запрашивает фоновое определение местоположения — в его манифесте нет параметра ACCESS_BACKGROUND_LOCATION — поэтому Android не предлагает опцию “Всегда”, и обновление местоположения происходит, когда приложение находится на переднем плане или выполняет функцию службы переднего плана.
При отключении остальная часть приложения продолжает работать: на Android 12 и более новых версиях Bluetooth не затрагивается, отключаются только отображение местоположения на карте и обмен данными о местоположении. На Android 11 и более ранних версиях сканирование Bluetooth также прекращается, поскольку для этого требуется разрешение, которое Android блокирует. Кроме того, для получения каких-либо результатов сканирования необходимо включить системные службы определения местоположения.
Разрешение на уведомления
Уведомления оповещают тебя о:
Входящие сообщения из каналов и личных сообщений
Новые ноды, присоединившиеся к сети
Низкий заряд на удаленной ноде
💡 Совет: Ты можешь тонко настроить уведомления позже в настройках системы — приложение создает отдельный канал уведомлений по категориям (плюс несколько внутренних, как фоновая служба), поэтому ты можешь включить или заглушить их по отдельности.
Разрешение на критические уведомления
Критические оповещения — это уведомления с высоким приоритетом, которые проходят через режим «Не беспокоить» и предназначены для экстренных вызовов и срочных сообщений.
Этот шаг не является запросом на разрешение запуска. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Пересмотреть разрешения позже
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
Состояние
What tapping the row does
Разрешено
Открывает страницу системы, на которой можно просмотреть или отозвать запрос
Ещё не спрашивали
Запросить
Отклонено — нажми для разрешения
Объясняет, для чего нужно разрешение, а затем снова спрашивает, согласен ли ты.
Заблокировано — нажми, чтобы открыть системные настройки
Android больше не будет отображать диалоговое окно, поэтому откроется страница, на которой можно снова его включить
Не требуется для данной версии Android
Ничего — разрешения на твоём устройстве нет
Это больше всего важно для уведомлений. Если вы отклонил их во время настройки, эта строка станет обратной: Android перестанет показывать диалоговое окно, как только ты решительно откажешься (повторный отказ), после чего эта строка переключится на ** Заблокировано ** и вместо этого отправит тебя на страницу настроек системы. Подсказка уведомлений есть только на Android 13 и новее — на более старых версиях уведомления включены по умолчанию и ими управляют через настройки самого Android.
После настройки
После предоставления разрешений, приложение открывает основной интерфейс. Ваше первое действие должно заключаться в подключении к радиостанции Meshtastic — см. Подключения для подробных инструкций.
💡 Совет: Если ты пропустил какие-либо разрешения при настройке, открой раздел Разрешения в Настройках приложения. Там перечислены все разрешения во время работы с их текущим состоянием и возможностью вернуться к ним — включая уведомления, на которые система сама больше не будет выдавать запрос второй раз.
Возможности также спрашивают в контексте. На вкладке Подключение карточка над списком устройств объясняет, для чего нужен доступ к Bluetooth, и предлагает Предоставить доступ; как только Android перестанет показывать подсказки, эта кнопка станет Открыть настройки.
Новичок в Meshtastic? Руководство по началу работы на meshtastic.org охватывает выбор оборудования, начальную настройку радиостанции и первую установку сети.
Связанные темы
Подключения — подключи своё первое радиоустройство
На этой странице рассказывается о процессе первого запуска приложения Meshtastic для Android, для чего нужно каждое разрешение и как вернуться к нему позже.
Первый запуск
Когда ты открываешь приложение впервые, оно проводит тебя через вводный процесс, который настраивает необходимые разрешения и параметры. Выполни каждый шаг по порядку или пропусти — здесь ничто не является одноразовым предложением. Каждое разрешение можно просмотреть и выдать позже в разделе Разрешения в Настройках внутри приложения.
Экран приветствия
Экран приветствия знакомит с Meshtastic с тремя рядами функций:
Будь на связи везде
Общайтесь вне сети со своими друзьями и сообществом без использования сотовой связи.
Создавай свои собственные сети
Легко создать частные сети для защищённой и надежной связи в удаленных районах.
Отслеживай и делись местоположением
Делитесь своим местоположением в режиме реального времени и поддерживайте работу группы с функциями GPS.
Нажми Начать, чтобы пройти процесс настройки.
Разрешения
Приложение запрашивает несколько разрешений во время настройки. Каждое из них служит определенной цели, и некоторые необходимы для основной функциональности.
Разрешения Bluetooth
Bluetooth — это основной способ подключения твоего телефона к радиостанции Meshtastic. Экран Bluetooth показывает, что даёт тебе это разрешение:
Обнаружение — найди и определи устройства Meshtastic рядом с тобой.
Настройки — управляйте параметрами устройства и каналами по беспроводной сети.
На Android 12 и новее система спрашивает один раз про ближайшие устройства, и это разрешение покрывает и сканирование, и подключение. Без него придётся использовать USB или TCP-соединения.
Разрешение на доступ к местоположению
ℹ️ Примечание: Для Bluetooth на Android 12 и выше местоположение не требуется. Android 11 и старше показывают один шаг для местоположения на экране Bluetooth, а не два — эти версии рассматривают сканирование Bluetooth как функцию определения местоположения, поэтому приложение запрашивает доступ к Местоположению вместо “Ближайшие устройства”. Если спросить дважды, это приведёт к тому, что Android вообще перестанет показывать диалог (второй отказ на Android 11; галочка “Больше не спрашивать” на Android 10 и старее). На Android 12 и новее это два разных момента: “Ближайшие устройства” объявлены как neverForLocation, и отказ от доступа к местоположению не мешает находить или подключаться к радио.
Meshtastic также использует местоположение для:
Показ вашего положения на карте
Вычисление расстояний до других нод
Обмен GPS-координатами с другими участниками сети (если включено)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Предоставьте “При использовании приложения”. Приложение не запрашивает фоновое определение местоположения — в его манифесте нет параметра ACCESS_BACKGROUND_LOCATION — поэтому Android не предлагает опцию “Всегда”, и обновление местоположения происходит, когда приложение находится на переднем плане или выполняет функцию службы переднего плана.
При отключении остальная часть приложения продолжает работать: на Android 12 и более новых версиях Bluetooth не затрагивается, отключаются только отображение местоположения на карте и обмен данными о местоположении. На Android 11 и более ранних версиях сканирование Bluetooth также прекращается, поскольку для этого требуется разрешение, которое Android блокирует. Кроме того, для получения каких-либо результатов сканирования необходимо включить системные службы определения местоположения.
Разрешение на уведомления
Уведомления оповещают тебя о:
Входящие сообщения из каналов и личных сообщений
Новые ноды, присоединившиеся к сети
Низкий заряд на удаленной ноде
💡 Совет: Ты можешь тонко настроить уведомления позже в настройках системы — приложение создает отдельный канал уведомлений по категориям (плюс несколько внутренних, как фоновая служба), поэтому ты можешь включить или заглушить их по отдельности.
Разрешение на критические уведомления
Критические оповещения — это уведомления с высоким приоритетом, которые проходят через режим «Не беспокоить» и предназначены для экстренных вызовов и срочных сообщений.
Этот шаг не является запросом на разрешение запуска. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Пересмотреть разрешения позже
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
Состояние
What tapping the row does
Разрешено
Открывает страницу системы, на которой можно просмотреть или отозвать запрос
Ещё не спрашивали
Запросить
Отклонено — нажми для разрешения
Объясняет, для чего нужно разрешение, а затем снова спрашивает, согласен ли ты.
Заблокировано — нажми, чтобы открыть системные настройки
Android больше не будет отображать диалоговое окно, поэтому откроется страница, на которой можно снова его включить
Не требуется для данной версии Android
Ничего — разрешения на твоём устройстве нет
Это больше всего важно для уведомлений. Если вы отклонил их во время настройки, эта строка станет обратной: Android перестанет показывать диалоговое окно, как только ты решительно откажешься (повторный отказ), после чего эта строка переключится на ** Заблокировано ** и вместо этого отправит тебя на страницу настроек системы. Подсказка уведомлений есть только на Android 13 и новее — на более старых версиях уведомления включены по умолчанию и ими управляют через настройки самого Android.
После настройки
После предоставления разрешений, приложение открывает основной интерфейс. Ваше первое действие должно заключаться в подключении к радиостанции Meshtastic — см. Подключения для подробных инструкций.
💡 Совет: Если ты пропустил какие-либо разрешения при настройке, открой раздел Разрешения в Настройках приложения. Там перечислены все разрешения во время работы с их текущим состоянием и возможностью вернуться к ним — включая уведомления, на которые система сама больше не будет выдавать запрос второй раз.
Возможности также спрашивают в контексте. На вкладке Подключение карточка над списком устройств объясняет, для чего нужен доступ к Bluetooth, и предлагает Предоставить доступ; как только Android перестанет показывать подсказки, эта кнопка станет Открыть настройки.
Новичок в Meshtastic? Руководство по началу работы на meshtastic.org охватывает выбор оборудования, начальную настройку радиостанции и первую установку сети.
Связанные темы
Подключения — подключи своё первое радиоустройство
Настрой дополнительные функциональные модули и выполняй управление устройством. Модули расширяют Meshtastic с помощью специализированных возможностей — каждый из них можно включать или отключать отдельно.
💡 Совет: Тебе нужно включать только те модули, которые действительно используешь. Отключение неиспользуемых модулей снижает время передачи, экономит батарею и упрощает конфигурацию. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Настройки модулей используют макет на основе карточек с переключателями, выпадающими списками, текстовыми полями и ползунками:
Настройки модуля
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Мосты передают сообщения туда и обратно от брокера MQTT для подключения к интернету. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Настройка
Описание
MQTT включен
Переключить MQTT мост
Адрес
Адрес MQTT брокера
Имя пользователя
Имя пользователя для аутентификации
Пароль
Пароль аутентификации
Шифрование включено
Зашифровать MQTT-пейлоады
Вывод JSON включен
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS включен
Использовать защищённое соединение
Корневая тема
Базовый путь темы MQTT
Прокси клиенту включен
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Отчёты по карте
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Настройка
Описание
Я согласен.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
См. MQTT для подробного руководства по использованию, включая шифрование, конфиденциальность и настройку брокера.
Serial module
Позволяет общаться через последовательный порт с внешними устройствами (GPS-модулями, датчиками или собственной техникой). Когда включено, последовательный порт ноды может отправлять и получать данные в формате protobuf или текст, что позволяет внешним микроконтроллерам или компьютерам взаимодействовать с сетью.
Настройка
Описание
COM-порт включен
Включить последовательное соединение
Echo включен
Echo получил обратно последовательные данные
Режим COM-порта
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Скорость COM-порта
Port speed
Время ожидания истекло
How long to wait before considering an incoming message complete
Переопределить COM-порт консоли
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Полезно для устройств, которым нужно физически сигнализировать о приходе сообщения — особенно удобно для неоснащенных персоналом или уличных установок.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Настройка
Описание
Внешние уведомления включены
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Выход LED (GPIO)
Pin the LED is wired to
Вывод светодиода активный высокий
Whether the LED pin is active high or low
Выход Буззера (GPIO)
Pin the buzzer is wired to
Вибросигнал (GPIO)
Pin the vibration motor is wired to
Использовать PWM-звукоизлучатель
Drive the buzzer with PWM, which allows tones rather than a single pitch
Использовать I2S как буззер
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Интервал повтора
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Рингтон
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Буферизирует сообщения для узлов, которые временно были недоступны, а затем ретранслирует их, когда эти узлы переподключаются. Важное значение для сеток, где узлы входят и выходят вне диапазона регулярно - обеспечивает отсутствие потери сообщений при коротких разъединениях.
Настройка
Описание
Store & Forward включен
Активировать режим хранения и пересылки
Heartbeat
Периодически объявлять о наличии функции хранения и пересылки у этого узла
Количество записей
Максимальное количество сохраненных сообщений
Макс возврат истории
Максимум сообщений для повтора
Окно возврата истории
Окно времени для повтора
Сервер
Действовать как сервер хранения и пересылки для mesh-сети (требуется большой объем памяти, например, ESP32 с PSRAM)
💡 Совет: Хранение и пересылка лучше всего работает на узлах с достаточной памятью (ESP32 с PSRAM). Узлы маршрутизатора являются идеальными кандидатами, так как они обычно всегда включены.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Автоматизированный инструмент для проверки дальности и оценки качества связи между нодами. Когда включено, нода периодически отправляет сообщения с увеличивающимся счетчиком. Приёмная нода записывает эти сообщения, что позволяет тебе уйти пешком или уехать на машине, а потом проанализировать, на каком расстоянии сообщения перестали приходить.
Настройка
Описание
Проверка дальности включена
Активировать проверку дальности
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Сохранить .CSV в хранилище (только ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Контролирует какими телеметрическими данными ваш узел делится с сеткой. Телеметрия включает данные о состоянии устройства (заряд батареи, время работы) и данные с датчиков окружающей среды (температура, влажность, давление).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Настройка
Описание
Отправлять телеметрию устройства
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Интервал обновления метрик устройства
How often to report battery, uptime and channel utilization
Модуль метрик окружения включен
Report the attached environment sensors
Интервал обновления метрик среды
How often to report them
Показатели окружения на экране включены
Also show these readings on the device’s own display
Использовать метрику окружения в Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Модуль измерения качества воздуха включен
Report particulate and CO₂ sensor data
Интервал обновления данных качества воздуха
How often to report them
Модуль метрик питания включен
Report the per-channel voltage and current readings
Интервал обновления метрик электропитания
How often to report them
Включить метрики питания на экране
Also show power readings on the device’s display
Посмотрите Телеметрия и датчики — для получения информации о поддерживаемых датчиках и рекомендациях по настройке.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Определите список быстрых сообщений, которые могут быть переданы без подключённого телефона — идеально подходит для использования в поле.
Настройка
Описание
Canned message enabled
⚠️ Deprecated in the protobuf schema
Сообщения
Список сообщений, разделённых новой строкой
Отправить колокольчик
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Поворотный энкодер #1 включен
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Вверх/Вниз/Выбирать включён
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Поддержка аудио Codec2 для низкополосной голосовой связи через сетку. Это экспериментальная функция, которая кодирует голос в очень маленькие пакеты данных с помощью кодека Codec2.
Настройка
Описание
CODEC 2 включен
Активировать модуль аудио
Частота дискретизации CODEC2
Компромисс между качеством звука и полосой пропускания
Контакт PTT
GPIO pin for the push-to-talk button
I2S Word Select
GPIO контакт для I2S WS
I2S Data In
Пин GPIO для I2S DIN
I2S Data Out
Пин GPIO для I2S DOUT
I2S Clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Качество голоса очень низкополосное — представьте себе «разборчивую радиосвязь», а не качество телефонного звонка.
Remote Hardware module
Управление GPIO через mesh-сеть. Позволяет удалённому узлу читать и записывать состояния выводов GPIO на другом узле — полезно для активации реле, опроса переключателей или удалённого управления внешним оборудованием.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Настройка
Описание
Удаленное оборудование включено
Активировать удаленный GPIO доступ
Разрешить неопределённый контакт
Разрешить доступ к любому GPIO-пину (риск для безопасности)
Доступные контакты
До 4 пинов GPIO, которые этот узел предоставляет для удалённого чтения и записи
Neighbor Info module
Транслирует информацию о доступных услышанных соседей, включив ячейку сеточной топологии. Каждый включенный узел периодически делится списком других узлов которые он может слышать и их качество сигнала.
Настройка
Описание
Информация о соседях включена
Включить трансляцию соседей
Интервал опроса GPS
Как часто транслировать список соседей
Передать через LoRa
Также транслировать информацию соседей по LoRa, а не только MQTT/телефон. Недоступно на канале используя ключ по умолчанию и имя
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Управляет встроенными светодиодами NeoPixel или другими адресуемыми RGB-светодиодами на поддерживаемом оборудовании. Может использоваться для визуальных статусовых индикаторов, световых уведомлений, или декоративных эффектов.
Настройка
Описание
Состояние LED
Включить или выключить светодиод
Ток
Текущий лимит светодиодов (0–31)
Красный / Зеленый / Синий
Индивидуальные значения цветов канала (0–255)
Detection Sensor module
Превращает ваш узел в систему сигнализации на основе датчика движения или открытия двери. При обнаружении изменения состояния на выводе GPIO (например, сработал датчик движения или открылась дверь) узел отправляет по меш-сети оповещение.
Настройка
Описание
Датчик определения включен
Активировать датчик обнаружения
GPIO контакт для мониторинга
Пин GPIO, подключенный к датчику
Тип триггера обнаружения
Как состояние пина интерпретируется как событие обнаружения (например, активный высокий/низкий уровень, срабатывание по фронту)
Использовать режим INPUT_PULLUP
Включить внутренний подтягивающий резистор пина
Minimum time between detection broadcasts
Минимальный интервал между оповещениями
State Broadcast Interval
Интервал периодической отправки состояния
Отправить колокол с уведомлением
Включать символ колокола в оповещения
Понятное имя
Пользовательское имя для этого датчика
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Засчитывает ближайшие устройства, пассивно прослушивая зондирующие запросы, чтобы телефоны и ноутбуки излучали при сканировании сетей. Доступно только на устройствах ESP32.
Настройка
Описание
Paxcounter включен
Активировать подсчет людей
Интервал опроса GPS
Как часто сообщать подсчитывания
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Совет: Paxcounter полезен для приблизительной оценки пешеходного потока в местах начала маршрутов, на мероприятийных площадках или в других локациях. Счетчики приблизительны — один человек может иметь несколько устройств.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Интеграция Team Awareness Kit для совместимости с ATAK и WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. См. TAK Integration для детальной настройки и использования.
Администрирование
Удаленное администрирование
Удалённо настраивай ноды, которые используют твой ключ администрирования:
Выбери целевую ноду в списке нод.
Перейди в Настройки этой ноды.
Измени конфигурацию.
Нажми Сохранить — изменения отправляются через сеть.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Действие
Что она делает
Установить время
Sends your phone’s clock to the node
Перезагрузка
Restarts the node
Выключение
Powers the node down
Сброс до заводских настроек
Returns every setting to its factory default
Очистка списка нод сети
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Бэкап & Восстановление
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Расширенные
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Очистить базу данных нод
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Панель отладки
Открывает вкладки Пакет и Журналы приложений для просмотра, фильтрации и экспорта диагностических выходов. См. Отладочные журналы для полного прохождения.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
О приложении
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Благодарности
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“Нет ответа от целевого узла” — цель может находиться вне диапазона, в автономном режиме или иметь несоответствующий ключ администратора. Проверьте соответствие ключа администратора на обоих узлах.
Изменения не применены — чтобы некоторые настройки вступили в силу, нужно перезагрузить устройство. Попробуй перезагрузить после сохранения.
Не видны настройки удалённой ноды — убедись, что твоя нода имеет админ-ключ для целевой ноды. Админ-канал настраивается автоматически, когда задан ключ администратора.
Настрой дополнительные функциональные модули и выполняй управление устройством. Модули расширяют Meshtastic с помощью специализированных возможностей — каждый из них можно включать или отключать отдельно.
💡 Совет: Тебе нужно включать только те модули, которые действительно используешь. Отключение неиспользуемых модулей снижает время передачи, экономит батарею и упрощает конфигурацию. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Настройки модулей используют макет на основе карточек с переключателями, выпадающими списками, текстовыми полями и ползунками:
Настройки модуля
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Мосты передают сообщения туда и обратно от брокера MQTT для подключения к интернету. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Настройка
Описание
MQTT включен
Переключить MQTT мост
Адрес
Адрес MQTT брокера
Имя пользователя
Имя пользователя для аутентификации
Пароль
Пароль аутентификации
Шифрование включено
Зашифровать MQTT-пейлоады
Вывод JSON включен
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS включен
Использовать защищённое соединение
Корневая тема
Базовый путь темы MQTT
Прокси клиенту включен
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Отчёты по карте
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Настройка
Описание
Я согласен.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
См. MQTT для подробного руководства по использованию, включая шифрование, конфиденциальность и настройку брокера.
Serial module
Позволяет общаться через последовательный порт с внешними устройствами (GPS-модулями, датчиками или собственной техникой). Когда включено, последовательный порт ноды может отправлять и получать данные в формате protobuf или текст, что позволяет внешним микроконтроллерам или компьютерам взаимодействовать с сетью.
Настройка
Описание
COM-порт включен
Включить последовательное соединение
Echo включен
Echo получил обратно последовательные данные
Режим COM-порта
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Скорость COM-порта
Port speed
Время ожидания истекло
How long to wait before considering an incoming message complete
Переопределить COM-порт консоли
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Полезно для устройств, которым нужно физически сигнализировать о приходе сообщения — особенно удобно для неоснащенных персоналом или уличных установок.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Настройка
Описание
Внешние уведомления включены
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Выход LED (GPIO)
Pin the LED is wired to
Вывод светодиода активный высокий
Whether the LED pin is active high or low
Выход Буззера (GPIO)
Pin the buzzer is wired to
Вибросигнал (GPIO)
Pin the vibration motor is wired to
Использовать PWM-звукоизлучатель
Drive the buzzer with PWM, which allows tones rather than a single pitch
Использовать I2S как буззер
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Интервал повтора
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Рингтон
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Буферизирует сообщения для узлов, которые временно были недоступны, а затем ретранслирует их, когда эти узлы переподключаются. Важное значение для сеток, где узлы входят и выходят вне диапазона регулярно - обеспечивает отсутствие потери сообщений при коротких разъединениях.
Настройка
Описание
Store & Forward включен
Активировать режим хранения и пересылки
Heartbeat
Периодически объявлять о наличии функции хранения и пересылки у этого узла
Количество записей
Максимальное количество сохраненных сообщений
Макс возврат истории
Максимум сообщений для повтора
Окно возврата истории
Окно времени для повтора
Сервер
Действовать как сервер хранения и пересылки для mesh-сети (требуется большой объем памяти, например, ESP32 с PSRAM)
💡 Совет: Хранение и пересылка лучше всего работает на узлах с достаточной памятью (ESP32 с PSRAM). Узлы маршрутизатора являются идеальными кандидатами, так как они обычно всегда включены.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Автоматизированный инструмент для проверки дальности и оценки качества связи между нодами. Когда включено, нода периодически отправляет сообщения с увеличивающимся счетчиком. Приёмная нода записывает эти сообщения, что позволяет тебе уйти пешком или уехать на машине, а потом проанализировать, на каком расстоянии сообщения перестали приходить.
Настройка
Описание
Проверка дальности включена
Активировать проверку дальности
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Сохранить .CSV в хранилище (только ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Контролирует какими телеметрическими данными ваш узел делится с сеткой. Телеметрия включает данные о состоянии устройства (заряд батареи, время работы) и данные с датчиков окружающей среды (температура, влажность, давление).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Настройка
Описание
Отправлять телеметрию устройства
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Интервал обновления метрик устройства
How often to report battery, uptime and channel utilization
Модуль метрик окружения включен
Report the attached environment sensors
Интервал обновления метрик среды
How often to report them
Показатели окружения на экране включены
Also show these readings on the device’s own display
Использовать метрику окружения в Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Модуль измерения качества воздуха включен
Report particulate and CO₂ sensor data
Интервал обновления данных качества воздуха
How often to report them
Модуль метрик питания включен
Report the per-channel voltage and current readings
Интервал обновления метрик электропитания
How often to report them
Включить метрики питания на экране
Also show power readings on the device’s display
Посмотрите Телеметрия и датчики — для получения информации о поддерживаемых датчиках и рекомендациях по настройке.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Определите список быстрых сообщений, которые могут быть переданы без подключённого телефона — идеально подходит для использования в поле.
Настройка
Описание
Canned message enabled
⚠️ Deprecated in the protobuf schema
Сообщения
Список сообщений, разделённых новой строкой
Отправить колокольчик
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Поворотный энкодер #1 включен
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Вверх/Вниз/Выбирать включён
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Поддержка аудио Codec2 для низкополосной голосовой связи через сетку. Это экспериментальная функция, которая кодирует голос в очень маленькие пакеты данных с помощью кодека Codec2.
Настройка
Описание
CODEC 2 включен
Активировать модуль аудио
Частота дискретизации CODEC2
Компромисс между качеством звука и полосой пропускания
Контакт PTT
GPIO pin for the push-to-talk button
I2S Word Select
GPIO контакт для I2S WS
I2S Data In
Пин GPIO для I2S DIN
I2S Data Out
Пин GPIO для I2S DOUT
I2S Clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Качество голоса очень низкополосное — представьте себе «разборчивую радиосвязь», а не качество телефонного звонка.
Remote Hardware module
Управление GPIO через mesh-сеть. Позволяет удалённому узлу читать и записывать состояния выводов GPIO на другом узле — полезно для активации реле, опроса переключателей или удалённого управления внешним оборудованием.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Настройка
Описание
Удаленное оборудование включено
Активировать удаленный GPIO доступ
Разрешить неопределённый контакт
Разрешить доступ к любому GPIO-пину (риск для безопасности)
Доступные контакты
До 4 пинов GPIO, которые этот узел предоставляет для удалённого чтения и записи
Neighbor Info module
Транслирует информацию о доступных услышанных соседей, включив ячейку сеточной топологии. Каждый включенный узел периодически делится списком других узлов которые он может слышать и их качество сигнала.
Настройка
Описание
Информация о соседях включена
Включить трансляцию соседей
Интервал опроса GPS
Как часто транслировать список соседей
Передать через LoRa
Также транслировать информацию соседей по LoRa, а не только MQTT/телефон. Недоступно на канале используя ключ по умолчанию и имя
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Управляет встроенными светодиодами NeoPixel или другими адресуемыми RGB-светодиодами на поддерживаемом оборудовании. Может использоваться для визуальных статусовых индикаторов, световых уведомлений, или декоративных эффектов.
Настройка
Описание
Состояние LED
Включить или выключить светодиод
Ток
Текущий лимит светодиодов (0–31)
Красный / Зеленый / Синий
Индивидуальные значения цветов канала (0–255)
Detection Sensor module
Превращает ваш узел в систему сигнализации на основе датчика движения или открытия двери. При обнаружении изменения состояния на выводе GPIO (например, сработал датчик движения или открылась дверь) узел отправляет по меш-сети оповещение.
Настройка
Описание
Датчик определения включен
Активировать датчик обнаружения
GPIO контакт для мониторинга
Пин GPIO, подключенный к датчику
Тип триггера обнаружения
Как состояние пина интерпретируется как событие обнаружения (например, активный высокий/низкий уровень, срабатывание по фронту)
Использовать режим INPUT_PULLUP
Включить внутренний подтягивающий резистор пина
Minimum time between detection broadcasts
Минимальный интервал между оповещениями
State Broadcast Interval
Интервал периодической отправки состояния
Отправить колокол с уведомлением
Включать символ колокола в оповещения
Понятное имя
Пользовательское имя для этого датчика
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Засчитывает ближайшие устройства, пассивно прослушивая зондирующие запросы, чтобы телефоны и ноутбуки излучали при сканировании сетей. Доступно только на устройствах ESP32.
Настройка
Описание
Paxcounter включен
Активировать подсчет людей
Интервал опроса GPS
Как часто сообщать подсчитывания
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Совет: Paxcounter полезен для приблизительной оценки пешеходного потока в местах начала маршрутов, на мероприятийных площадках или в других локациях. Счетчики приблизительны — один человек может иметь несколько устройств.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Интеграция Team Awareness Kit для совместимости с ATAK и WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. См. TAK Integration для детальной настройки и использования.
Администрирование
Удаленное администрирование
Удалённо настраивай ноды, которые используют твой ключ администрирования:
Выбери целевую ноду в списке нод.
Перейди в Настройки этой ноды.
Измени конфигурацию.
Нажми Сохранить — изменения отправляются через сеть.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Действие
Что она делает
Установить время
Sends your phone’s clock to the node
Перезагрузка
Restarts the node
Выключение
Powers the node down
Сброс до заводских настроек
Returns every setting to its factory default
Очистка списка нод сети
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Бэкап & Восстановление
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Расширенные
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Очистить базу данных нод
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Панель отладки
Открывает вкладки Пакет и Журналы приложений для просмотра, фильтрации и экспорта диагностических выходов. См. Отладочные журналы для полного прохождения.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
О приложении
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Благодарности
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“Нет ответа от целевого узла” — цель может находиться вне диапазона, в автономном режиме или иметь несоответствующий ключ администратора. Проверьте соответствие ключа администратора на обоих узлах.
Изменения не применены — чтобы некоторые настройки вступили в силу, нужно перезагрузить устройство. Попробуй перезагрузить после сохранения.
Не видны настройки удалённой ноды — убедись, что твоя нода имеет админ-ключ для целевой ноды. Админ-канал настраивается автоматически, когда задан ключ администратора.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Konfigurácia modulu
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Popis
MQTT enabled
Toggle MQTT bridge
Adresa
MQTT broker address
Používateľské meno
Authentication username
Heslo
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Popis
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Popis
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Časový limit
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Popis
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Zvonenie
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Popis
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Popis
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Popis
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Popis
Canned message enabled
⚠️ Deprecated in the protobuf schema
Správy
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Enkóder #1 aktivovaný
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Popis
CODEC 2 zapnutý
Activate audio module
CODEC2 vzorkovacia frekvencia
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2C výber slova
GPIO pin for I2S WS
I2S vstup dát
GPIO pin for I2S DIN
I2S výstup dát
GPIO pin for I2S DOUT
I2S čas
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Popis
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Popis
Neighbor Info enabled
Activate neighbor broadcasting
Aktualizačný interval
How often to broadcast neighbor list
Vysielať cez sieť LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Popis
Stav LED
Turn the LED on or off
Prúd
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Popis
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Popis
Paxcounter enabled
Activate people counting
Aktualizačný interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administrácia
Administrácia na diaľku
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Reštartovať
Restarts the node
Vypnúť
Powers the node down
Obnova do výrobných nastavení
Returns every setting to its factory default
Reset databázy uzlov
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Zálohovanie a Obnovenie
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Debug okno
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
O aplikácii
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Konfigurácia modulu
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Popis
MQTT enabled
Toggle MQTT bridge
Adresa
MQTT broker address
Používateľské meno
Authentication username
Heslo
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Popis
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Popis
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Časový limit
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Popis
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Zvonenie
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Popis
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Popis
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Popis
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Popis
Canned message enabled
⚠️ Deprecated in the protobuf schema
Správy
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Enkóder #1 aktivovaný
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Popis
CODEC 2 zapnutý
Activate audio module
CODEC2 vzorkovacia frekvencia
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2C výber slova
GPIO pin for I2S WS
I2S vstup dát
GPIO pin for I2S DIN
I2S výstup dát
GPIO pin for I2S DOUT
I2S čas
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Popis
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Popis
Neighbor Info enabled
Activate neighbor broadcasting
Aktualizačný interval
How often to broadcast neighbor list
Vysielať cez sieť LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Popis
Stav LED
Turn the LED on or off
Prúd
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Popis
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Popis
Paxcounter enabled
Activate people counting
Aktualizačný interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administrácia
Administrácia na diaľku
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Reštartovať
Restarts the node
Vypnúť
Powers the node down
Obnova do výrobných nastavení
Returns every setting to its factory default
Reset databázy uzlov
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Zálohovanie a Obnovenie
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Debug okno
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
O aplikácii
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Nastavitev modula
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Opis
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Opis
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Opis
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Časovna omejitev
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Opis
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Opis
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Opis
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Opis
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Opis
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Opis
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Opis
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Opis
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Opis
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Opis
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Opis
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administracija
Administracija na daljavo
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Ponovni zagon
Restarts the node
Ugasni
Powers the node down
Povrnitev tovarniških nastavitev
Returns every setting to its factory default
Ponastavi NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Plošča za odpravljanje napak
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
O programu
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Nastavitev modula
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Opis
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Opis
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Opis
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Časovna omejitev
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Opis
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Opis
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Opis
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Opis
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Opis
Canned message enabled
⚠️ Deprecated in the protobuf schema
Messages
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Opis
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Opis
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Opis
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Opis
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Opis
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Opis
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administracija
Administracija na daljavo
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Ponovni zagon
Restarts the node
Ugasni
Powers the node down
Povrnitev tovarniških nastavitev
Returns every setting to its factory default
Ponastavi NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Plošča za odpravljanje napak
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
O programu
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Konfigurimi i modulit
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Përshkrimi
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Përshkrimi
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Përshkrimi
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Koha e skaduar
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Përshkrimi
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Përshkrimi
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Përshkrimi
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Përshkrimi
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Përshkrimi
Canned message enabled
⚠️ Deprecated in the protobuf schema
訊息
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Përshkrimi
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Përshkrimi
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Përshkrimi
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Përshkrimi
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Përshkrimi
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Përshkrimi
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administratë
Administratë e Largët
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Rindiz
Restarts the node
Fik
Powers the node down
Përditësim i fabrikës
Returns every setting to its factory default
Përditësimi i NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Paneli i debug-ut
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Rreth
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Konfigurimi i modulit
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Përshkrimi
MQTT enabled
Toggle MQTT bridge
Address
MQTT broker address
Username
Authentication username
Password
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Përshkrimi
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Përshkrimi
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Koha e skaduar
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Përshkrimi
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringtone
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Përshkrimi
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Number of records
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Përshkrimi
Range test enabled
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Përshkrimi
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Përshkrimi
Canned message enabled
⚠️ Deprecated in the protobuf schema
訊息
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Përshkrimi
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Përshkrimi
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Përshkrimi
Neighbor Info enabled
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Përshkrimi
LED state
Turn the LED on or off
Current
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Përshkrimi
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Friendly name
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Përshkrimi
Paxcounter enabled
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administratë
Administratë e Largët
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Rindiz
Restarts the node
Fik
Powers the node down
Përditësim i fabrikës
Returns every setting to its factory default
Përditësimi i NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advanced
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Paneli i debug-ut
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Rreth
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Конфигурација модула
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Опис
MQTT enabled
Toggle MQTT bridge
Адреса
MQTT broker address
Корисничко име
Authentication username
Лозинка
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Опис
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Интервал објављивања мапе
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Опис
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Isteklo vreme
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Опис
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
Трајање GPIO излаза
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Мелодија звона
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Опис
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Број записа
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Сервер
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Опис
Range test enabled
Activate range testing
Инерварл пошиљаоца
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Опис
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Опис
Canned message enabled
⚠️ Deprecated in the protobuf schema
Поруке
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Опис
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Опис
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Опис
Neighbor Info enabled
Activate neighbor broadcasting
Интервал ажурирања
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Опис
LED state
Turn the LED on or off
Струја
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Опис
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Минимално време између емитовања детекције
Minimum time between alert broadcasts
Интервал емитовања стања
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Пријатељски назив
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Опис
Paxcounter enabled
Activate people counting
Интервал ажурирања
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administracija
Udaljena administracija
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Поново покрени
Restarts the node
Искључи
Powers the node down
Рестартовање на фабричка подешавања
Returns every setting to its factory default
Ресетовање базе чворова
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Напредно
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panel za otklanjanje grešaka
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
Подешавања апликације
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
O nama
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Конфигурација модула
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Опис
MQTT enabled
Toggle MQTT bridge
Адреса
MQTT broker address
Корисничко име
Authentication username
Лозинка
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Опис
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Интервал објављивања мапе
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Опис
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Isteklo vreme
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Опис
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
Трајање GPIO излаза
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Мелодија звона
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Опис
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Број записа
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Сервер
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Опис
Range test enabled
Activate range testing
Инерварл пошиљаоца
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Опис
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Опис
Canned message enabled
⚠️ Deprecated in the protobuf schema
Поруке
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Опис
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Опис
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Опис
Neighbor Info enabled
Activate neighbor broadcasting
Интервал ажурирања
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Опис
LED state
Turn the LED on or off
Струја
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Опис
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Минимално време између емитовања детекције
Minimum time between alert broadcasts
Интервал емитовања стања
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Пријатељски назив
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Опис
Paxcounter enabled
Activate people counting
Интервал ажурирања
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administracija
Udaljena administracija
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Поново покрени
Restarts the node
Искључи
Powers the node down
Рестартовање на фабричка подешавања
Returns every setting to its factory default
Ресетовање базе чворова
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Напредно
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Panel za otklanjanje grešaka
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
Подешавања апликације
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
O nama
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Конфигурација модула
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Опис
MQTT enabled
Toggle MQTT bridge
Адреса
MQTT broker address
Корисничко име
Authentication username
Лозинка
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Опис
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Интервал објављивања мапе
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Опис
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Временско ограничење
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Опис
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
Трајање GPIO излаза
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Мелодија звона
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Опис
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Број записа
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Сервер
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Опис
Range test enabled
Activate range testing
Инерварл пошиљаоца
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Опис
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Опис
Canned message enabled
⚠️ Deprecated in the protobuf schema
Поруке
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Опис
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Опис
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Опис
Neighbor Info enabled
Activate neighbor broadcasting
Интервал ажурирања
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Опис
LED state
Turn the LED on or off
Струја
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Опис
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Минимално време између емитовања детекције
Minimum time between alert broadcasts
Интервал емитовања стања
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Пријатељски назив
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Опис
Paxcounter enabled
Activate people counting
Интервал ажурирања
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Администрација
Удаљена администрација
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Поновно покретање
Restarts the node
Искључи
Powers the node down
Рестартовање на фабричка подешавања
Returns every setting to its factory default
Ресетовање базе чворова
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Напредно
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Панел за отклањање грешака
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
Подешавања апликације
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
О
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Конфигурација модула
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Опис
MQTT enabled
Toggle MQTT bridge
Адреса
MQTT broker address
Корисничко име
Authentication username
Лозинка
Authentication password
Encryption enabled
Encrypt MQTT payloads
JSON output enabled
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS enabled
Use secure connection
Root topic
Base MQTT topic path
Proxy to client enabled
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Опис
I agree.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Интервал објављивања мапе
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Опис
Serial enabled
Activate serial communication
Echo enabled
Echo received serial data back
Serial mode
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Serial baud rate
Port speed
Временско ограничење
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Опис
External notification enabled
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Output LED (GPIO)
Pin the LED is wired to
Output LED active high
Whether the LED pin is active high or low
Output buzzer (GPIO)
Pin the buzzer is wired to
Output vibra (GPIO)
Pin the vibration motor is wired to
Use PWM buzzer
Drive the buzzer with PWM, which allows tones rather than a single pitch
Use I2S as buzzer
Send the alert through an I2S audio output instead
Трајање GPIO излаза
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Мелодија звона
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Опис
Store & Forward enabled
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
Број записа
Maximum stored messages
History return max
Max messages to replay
History return window
Time window for replay
Сервер
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Опис
Range test enabled
Activate range testing
Инерварл пошиљаоца
Time between test transmissions, chosen from a dropdown of fixed intervals
Save .CSV in storage (ESP32 only)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Опис
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Environment metrics module enabled
Report the attached environment sensors
Environment metrics update interval
How often to report them
Environment metrics on-screen enabled
Also show these readings on the device’s own display
Environment metrics use Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Air quality metrics module enabled
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Power metrics module enabled
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Power metrics on-screen enabled
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Опис
Canned message enabled
⚠️ Deprecated in the protobuf schema
Поруке
Newline-separated list of messages
Send bell
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Опис
CODEC 2 enabled
Activate audio module
CODEC2 sample rate
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S word select
GPIO pin for I2S WS
I2S data in
GPIO pin for I2S DIN
I2S data out
GPIO pin for I2S DOUT
I2S clock
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Опис
Remote Hardware enabled
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Available pins
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Опис
Neighbor Info enabled
Activate neighbor broadcasting
Интервал ажурирања
How often to broadcast neighbor list
Transmit over LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Опис
LED state
Turn the LED on or off
Струја
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Опис
Detection Sensor enabled
Activate detection sensor
GPIO pin to monitor
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Use INPUT_PULLUP mode
Enable the pin’s internal pull-up resistor
Минимално време између емитовања детекције
Minimum time between alert broadcasts
Интервал емитовања стања
Periodic state broadcast interval
Send bell with alert message
Include bell character in alerts
Пријатељски назив
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Опис
Paxcounter enabled
Activate people counting
Интервал ажурирања
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Администрација
Удаљена администрација
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Поновно покретање
Restarts the node
Искључи
Powers the node down
Рестартовање на фабричка подешавања
Returns every setting to its factory default
Ресетовање базе чворова
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Backup & Restore
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Напредно
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Панел за отклањање грешака
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
Подешавања апликације
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
О
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Kommunicera med din släkt och dina vänner utan online- och mobiltjänster.
Create Your Own Networks
Konfigurera enkelt privata nätverk för säker och tillförlitlig kommunikation i avlägsna områden.
Track and Share Locations
Dela din plats i realtid och håll din grupp samordnad med integrerade GPS-funktioner.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Kommunicera med din släkt och dina vänner utan online- och mobiltjänster.
Create Your Own Networks
Konfigurera enkelt privata nätverk för säker och tillförlitlig kommunikation i avlägsna områden.
Track and Share Locations
Dela din plats i realtid och håll din grupp samordnad med integrerade GPS-funktioner.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Modul konfiguration
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Beskrivning
MQTT är aktiverat
Toggle MQTT bridge
Adress
MQTT broker address
Användarnamn
Authentication username
Lösenord
Authentication password
Kryptering aktiverad
Encrypt MQTT payloads
JSON-utdata aktiverad
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS är aktiverat
Use secure connection
Rotämne (root topic)
Base MQTT topic path
Proxy till klient aktiverad
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Beskrivning
Jag godkänner.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Beskrivning
Seriell aktiverad
Activate serial communication
Eko aktiverad
Echo received serial data back
Seriellt läge
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Den seriella kommunikationens hastighet
Port speed
Timeout
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Beskrivning
Externa aviseringar aktiverad
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Utmatning LED (GPIO)
Pin the LED is wired to
Utmatnings-LED aktiv hög
Whether the LED pin is active high or low
Utmatning summer (GPIO)
Pin the buzzer is wired to
Utmatning vibration (GPIO)
Pin the vibration motor is wired to
Använd PWM-summern
Drive the buzzer with PWM, which allows tones rather than a single pitch
Använd I2S som summer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Time-out för påminnelse
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringsignal
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Beskrivning
Lagra & vidarebefordra är aktiverad
Activate store and forward
Pulsera
Periodically announce this node’s store-and-forward capability
Antal poster
Maximum stored messages
Maxstorlek för historik
Max messages to replay
Returfönstrets storlek för historik
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Beskrivning
Räckvidstest aktiverat
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Spara .CSV i enheten (endast ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Beskrivning
Skicka enhetstelemetri
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Uppdateringsintervall för enhetsdata
How often to report battery, uptime and channel utilization
Mätmodul för miljö aktiverad
Report the attached environment sensors
Uppdateringsintervall för miljödata
How often to report them
Visning av miljödata på skärm är aktiverad
Also show these readings on the device’s own display
Miljömätvärden använder Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Luftkvalitetsmätarmodul aktiverad
Report particulate and CO₂ sensor data
Uppdateringsintervall för luftkvalitet
How often to report them
Strömmätarmodul aktiverad
Report the per-channel voltage and current readings
Uppdateringsintervall för strömmätare
How often to report them
Visning av strömvärden på skärm är aktiverad
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Beskrivning
Canned message enabled
⚠️ Deprecated in the protobuf schema
Meddelanden
Newline-separated list of messages
Skicka ljudavisering
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Beskrivning
CODEC 2 aktiverat
Activate audio module
CODEC2 samplingshastighet
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S ordval
GPIO pin for I2S WS
I2S-data in
GPIO pin for I2S DIN
I2S-data ut
GPIO pin for I2S DOUT
I2S-klocka
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Beskrivning
Fjärrhårdvara aktiverad
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Tillgängliga pin
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Beskrivning
Grannskapsinformation aktiverat
Activate neighbor broadcasting
Intervall för hämtning av GPS-position
How often to broadcast neighbor list
Skicka över LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Beskrivning
LED-läge
Turn the LED on or off
Ström
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Beskrivning
Detektionssensor aktiverad
Activate detection sensor
GPIO-pin att övervaka
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Använd INPUT_PULLUP-läge
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Skicka ljudavisering med larmmeddelande
Include bell character in alerts
Visningsnamn
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Beskrivning
PAX-räknare aktiverad
Activate people counting
Intervall för hämtning av GPS-position
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Fjärradministration
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Ställ in tid
Sends your phone’s clock to the node
Starta om
Restarts the node
Stäng av
Powers the node down
Återställ till standardinställningar
Returns every setting to its factory default
Nollställ NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Säkerhetskopiering och återställning
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advancerat
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Rensa noddatabas
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Felsökningspanel
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Om
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Bekräftelser
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Modul konfiguration
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Beskrivning
MQTT är aktiverat
Toggle MQTT bridge
Adress
MQTT broker address
Användarnamn
Authentication username
Lösenord
Authentication password
Kryptering aktiverad
Encrypt MQTT payloads
JSON-utdata aktiverad
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS är aktiverat
Use secure connection
Rotämne (root topic)
Base MQTT topic path
Proxy till klient aktiverad
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Map reporting
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Beskrivning
Jag godkänner.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Beskrivning
Seriell aktiverad
Activate serial communication
Eko aktiverad
Echo received serial data back
Seriellt läge
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Den seriella kommunikationens hastighet
Port speed
Timeout
How long to wait before considering an incoming message complete
Override console serial port
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Beskrivning
Externa aviseringar aktiverad
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Utmatning LED (GPIO)
Pin the LED is wired to
Utmatnings-LED aktiv hög
Whether the LED pin is active high or low
Utmatning summer (GPIO)
Pin the buzzer is wired to
Utmatning vibration (GPIO)
Pin the vibration motor is wired to
Använd PWM-summern
Drive the buzzer with PWM, which allows tones rather than a single pitch
Använd I2S som summer
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Time-out för påminnelse
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Ringsignal
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Beskrivning
Lagra & vidarebefordra är aktiverad
Activate store and forward
Pulsera
Periodically announce this node’s store-and-forward capability
Antal poster
Maximum stored messages
Maxstorlek för historik
Max messages to replay
Returfönstrets storlek för historik
Time window for replay
Server
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Beskrivning
Räckvidstest aktiverat
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Spara .CSV i enheten (endast ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Beskrivning
Skicka enhetstelemetri
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Uppdateringsintervall för enhetsdata
How often to report battery, uptime and channel utilization
Mätmodul för miljö aktiverad
Report the attached environment sensors
Uppdateringsintervall för miljödata
How often to report them
Visning av miljödata på skärm är aktiverad
Also show these readings on the device’s own display
Miljömätvärden använder Fahrenheit
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Luftkvalitetsmätarmodul aktiverad
Report particulate and CO₂ sensor data
Uppdateringsintervall för luftkvalitet
How often to report them
Strömmätarmodul aktiverad
Report the per-channel voltage and current readings
Uppdateringsintervall för strömmätare
How often to report them
Visning av strömvärden på skärm är aktiverad
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Beskrivning
Canned message enabled
⚠️ Deprecated in the protobuf schema
Meddelanden
Newline-separated list of messages
Skicka ljudavisering
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Rotary encoder #1 enabled
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Up/Down/Select input enabled
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Beskrivning
CODEC 2 aktiverat
Activate audio module
CODEC2 samplingshastighet
Audio quality/bandwidth tradeoff
PTT pin
GPIO pin for the push-to-talk button
I2S ordval
GPIO pin for I2S WS
I2S-data in
GPIO pin for I2S DIN
I2S-data ut
GPIO pin for I2S DOUT
I2S-klocka
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Beskrivning
Fjärrhårdvara aktiverad
Activate remote GPIO access
Allow undefined pin access
Allow access to any GPIO pin (security risk)
Tillgängliga pin
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Beskrivning
Grannskapsinformation aktiverat
Activate neighbor broadcasting
Intervall för hämtning av GPS-position
How often to broadcast neighbor list
Skicka över LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Beskrivning
LED-läge
Turn the LED on or off
Ström
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Beskrivning
Detektionssensor aktiverad
Activate detection sensor
GPIO-pin att övervaka
GPIO pin connected to sensor
Detection trigger type
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Använd INPUT_PULLUP-läge
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Skicka ljudavisering med larmmeddelande
Include bell character in alerts
Visningsnamn
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Beskrivning
PAX-räknare aktiverad
Activate people counting
Intervall för hämtning av GPS-position
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Administration
Fjärradministration
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Ställ in tid
Sends your phone’s clock to the node
Starta om
Restarts the node
Stäng av
Powers the node down
Återställ till standardinställningar
Returns every setting to its factory default
Nollställ NodeDB
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Säkerhetskopiering och återställning
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Advancerat
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Rensa noddatabas
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Felsökningspanel
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Om
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Bekräftelser
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Communicate off-the-grid with your friends and community without cell service.
Create Your Own Networks
Easily set up private mesh networks for secure and reliable communication in remote areas.
Track and Share Locations
Share your location in real-time and keep your group coordinated with integrated GPS features.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Modül ayarları
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Açıklaması
MQTT etkin
Toggle MQTT bridge
Adres
MQTT broker address
Kullanıcı adı
Authentication username
Şifre
Authentication password
Şifreleme etkin
Encrypt MQTT payloads
JSON çıktısı etkin
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS etkin
Use secure connection
Ana konu
Base MQTT topic path
Vekilden istemciye etkin
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Harita raporlama
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Açıklaması
Katılıyorum.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Açıklaması
Seri etkin
Activate serial communication
Eko etkin
Echo received serial data back
Seri modu
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Seri baud hızı
Port speed
Zaman Aşımı
How long to wait before considering an incoming message complete
Konsol seri portunu geçersiz kıl
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Açıklaması
Harici bildirim etkin
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Çıktı LED (GPIO)
Pin the LED is wired to
Çıktı LED aktif yüksek
Whether the LED pin is active high or low
Çıktı zırnı (GPIO)
Pin the buzzer is wired to
Çıktı titreşim (GPIO)
Pin the vibration motor is wired to
PWM zırnı kullan
Drive the buzzer with PWM, which allows tones rather than a single pitch
I2S’yi zırnı olarak kullan
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Zil tipi
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Açıklaması
Kaydet & Yönlendir etkin
Activate store and forward
Kalp atışı
Periodically announce this node’s store-and-forward capability
Kayıt sayısı
Maximum stored messages
Geçmiş geri dönüş maksimum
Max messages to replay
Geçmiş geri dönüş penceresi
Time window for replay
Sunucu
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Açıklaması
Menzi testi etkin
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
.CSV’yi depolamada kaydet (sadece ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Açıklaması
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Çevre metrikleri modülü etkin
Report the attached environment sensors
Environment metrics update interval
How often to report them
Çevre metrikleri ekran üzerinde etkin
Also show these readings on the device’s own display
Çevre metrikleri Fahrenheit kullan
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Hava kalitesi metrikleri modülü etkin
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Güç metrikleri modülü etkin
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Güç metrikleri ekran üzerinde etkin
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Açıklaması
Canned message enabled
⚠️ Deprecated in the protobuf schema
Mesajlar
Newline-separated list of messages
Zil gönder
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Dönen kodlayıcı #1 etkinleştirildi
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Yukarı/Aşağı/Seçme girişi etkinleştirildi
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Açıklaması
CODEC 2 etkinleştirildi
Activate audio module
CODEC2 örnekleme hızı
Audio quality/bandwidth tradeoff
PTT pini
GPIO pin for the push-to-talk button
I2S kelime seçimi
GPIO pin for I2S WS
I2S veri girişi
GPIO pin for I2S DIN
I2S veri çıkışı
GPIO pin for I2S DOUT
I2S saati
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Açıklaması
Uzak Donanım etkin
Activate remote GPIO access
Tanımlanmamış pin erişimine izin ver
Allow access to any GPIO pin (security risk)
Mevcut pinler
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Açıklaması
Komşu Bilgisi etkin
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
LoRa üzerinden ilet
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Açıklaması
LED durumu
Turn the LED on or off
Akım
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Açıklaması
Algılama Sensörü etkinleştirildi
Activate detection sensor
İzlenecek GPIO pini
GPIO pin connected to sensor
Algılama tetikleme türü
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
INPUT_PULLUP modu kullan
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Uyarı mesajı ile zil gönder
Include bell character in alerts
Arkadaşça isim
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Açıklaması
Pax sayacı etkin
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Yönetim
Uzaktan Yönetim
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Yeniden başlat
Restarts the node
Kapat
Powers the node down
Fabrika ayarları
Returns every setting to its factory default
NodeDB sıfırla
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Yedekleme & Geri yükleme
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Gelişmiş
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Hata Ayıklama Paneli
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Hakkında
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Modül ayarları
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Açıklaması
MQTT etkin
Toggle MQTT bridge
Adres
MQTT broker address
Kullanıcı adı
Authentication username
Şifre
Authentication password
Şifreleme etkin
Encrypt MQTT payloads
JSON çıktısı etkin
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS etkin
Use secure connection
Ana konu
Base MQTT topic path
Vekilden istemciye etkin
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Harita raporlama
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Açıklaması
Katılıyorum.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Açıklaması
Seri etkin
Activate serial communication
Eko etkin
Echo received serial data back
Seri modu
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Seri baud hızı
Port speed
Zaman Aşımı
How long to wait before considering an incoming message complete
Konsol seri portunu geçersiz kıl
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Açıklaması
Harici bildirim etkin
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Çıktı LED (GPIO)
Pin the LED is wired to
Çıktı LED aktif yüksek
Whether the LED pin is active high or low
Çıktı zırnı (GPIO)
Pin the buzzer is wired to
Çıktı titreşim (GPIO)
Pin the vibration motor is wired to
PWM zırnı kullan
Drive the buzzer with PWM, which allows tones rather than a single pitch
I2S’yi zırnı olarak kullan
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Zil tipi
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Açıklaması
Kaydet & Yönlendir etkin
Activate store and forward
Kalp atışı
Periodically announce this node’s store-and-forward capability
Kayıt sayısı
Maximum stored messages
Geçmiş geri dönüş maksimum
Max messages to replay
Geçmiş geri dönüş penceresi
Time window for replay
Sunucu
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Açıklaması
Menzi testi etkin
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
.CSV’yi depolamada kaydet (sadece ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Açıklaması
Send Device Telemetry
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Device metrics update interval
How often to report battery, uptime and channel utilization
Çevre metrikleri modülü etkin
Report the attached environment sensors
Environment metrics update interval
How often to report them
Çevre metrikleri ekran üzerinde etkin
Also show these readings on the device’s own display
Çevre metrikleri Fahrenheit kullan
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Hava kalitesi metrikleri modülü etkin
Report particulate and CO₂ sensor data
Air quality metrics update interval
How often to report them
Güç metrikleri modülü etkin
Report the per-channel voltage and current readings
Power metrics update interval
How often to report them
Güç metrikleri ekran üzerinde etkin
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Açıklaması
Canned message enabled
⚠️ Deprecated in the protobuf schema
Mesajlar
Newline-separated list of messages
Zil gönder
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Dönen kodlayıcı #1 etkinleştirildi
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Yukarı/Aşağı/Seçme girişi etkinleştirildi
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Açıklaması
CODEC 2 etkinleştirildi
Activate audio module
CODEC2 örnekleme hızı
Audio quality/bandwidth tradeoff
PTT pini
GPIO pin for the push-to-talk button
I2S kelime seçimi
GPIO pin for I2S WS
I2S veri girişi
GPIO pin for I2S DIN
I2S veri çıkışı
GPIO pin for I2S DOUT
I2S saati
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Açıklaması
Uzak Donanım etkin
Activate remote GPIO access
Tanımlanmamış pin erişimine izin ver
Allow access to any GPIO pin (security risk)
Mevcut pinler
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Açıklaması
Komşu Bilgisi etkin
Activate neighbor broadcasting
Update Interval
How often to broadcast neighbor list
LoRa üzerinden ilet
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Açıklaması
LED durumu
Turn the LED on or off
Akım
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Açıklaması
Algılama Sensörü etkinleştirildi
Activate detection sensor
İzlenecek GPIO pini
GPIO pin connected to sensor
Algılama tetikleme türü
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
INPUT_PULLUP modu kullan
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Uyarı mesajı ile zil gönder
Include bell character in alerts
Arkadaşça isim
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Açıklaması
Pax sayacı etkin
Activate people counting
Update Interval
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Yönetim
Uzaktan Yönetim
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Set time
Sends your phone’s clock to the node
Yeniden başlat
Restarts the node
Kapat
Powers the node down
Fabrika ayarları
Returns every setting to its factory default
NodeDB sıfırla
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Yedekleme & Geri yükleme
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Gelişmiş
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Clean Node Database
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Hata Ayıklama Paneli
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Hakkında
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Acknowledgements
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Спілкуйтеся з друзями та спільнотою поза мережею, навіть без мобільного зв’язку.
Create Your Own Networks
Легко налаштовуйте приватні mesh-мережі для безпечного та надійного зв’язку у віддалених районах.
Track and Share Locations
Діліться своїм місцезнаходженням у реальному часі та координуйте групу завдяки вбудованим функціям GPS.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
Спілкуйтеся з друзями та спільнотою поза мережею, навіть без мобільного зв’язку.
Create Your Own Networks
Легко налаштовуйте приватні mesh-мережі для безпечного та надійного зв’язку у віддалених районах.
Track and Share Locations
Діліться своїм місцезнаходженням у реальному часі та координуйте групу завдяки вбудованим функціям GPS.
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Налаштування модуля
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Опис
MQTT увімкнений
Toggle MQTT bridge
Адреса
MQTT broker address
Ім’я користувача
Authentication username
Пароль
Authentication password
Шифрування увімкнено
Encrypt MQTT payloads
Вивід JSON увімкнено
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS увімкнений
Use secure connection
Кореневий чат
Base MQTT topic path
Проксі для клієнта увімкнуто
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Відображення на мапі
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Опис
Погоджуюся.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Опис
Послідовний порт увімкнено
Activate serial communication
Відлуння активоване
Echo received serial data back
Послідовний режим
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Швидкість послідовного порту
Port speed
Таймаут
How long to wait before considering an incoming message complete
Перевизначити послідовний порт
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Опис
Зовнішні сповіщення увімкнено
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Вихідний LED (GPIO)
Pin the LED is wired to
Активний високий рівень світлодіода
Whether the LED pin is active high or low
Вихідний гудок (GPIO)
Pin the buzzer is wired to
Вихід вібросигналу (GPIO)
Pin the vibration motor is wired to
Використовувати зумер із ШІМ-керуванням
Drive the buzzer with PWM, which allows tones rather than a single pitch
Використовувати I2S як гудок
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Мелодія
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Опис
Збереження та перенаправлення увімкнено
Activate store and forward
Пульсація
Periodically announce this node’s store-and-forward capability
Кількість записів
Maximum stored messages
Максимальний обсяг історії
Max messages to replay
Максимальне вікно історії
Time window for replay
Сервер
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Опис
Тест на відстань увімкнений
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Зберегти .CSV у сховищі (лише ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Опис
Надсилати телеметрію пристрою
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Інтервал оновлення показників пристрою
How often to report battery, uptime and channel utilization
Модуль екологічних показників увімкнено
Report the attached environment sensors
Інтервал оновлення екологічних показників
How often to report them
Екологічні показники на екрані увімкнено
Also show these readings on the device’s own display
Екологічні показники використовують шкалу Фаренгейта
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Модуль показників якості повітря увімкнено
Report particulate and CO₂ sensor data
Інтервал оновлення показників якості повітря
How often to report them
Модуль показників потужності ввімкнено
Report the per-channel voltage and current readings
Інтервал оновлення показників потужності
How often to report them
Показники потужності на екрані ввімкнено
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Опис
Canned message enabled
⚠️ Deprecated in the protobuf schema
Повідомлення
Newline-separated list of messages
Надіслати дзвіночок
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Енкодер #1 активований
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Увімкнути керування Вгору/Вниз/Вибір
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Опис
CODEC 2 увімкнено
Activate audio module
Частота дискретизації CODEC2
Audio quality/bandwidth tradeoff
PTT контакт
GPIO pin for the push-to-talk button
Вибір слова I2S
GPIO pin for I2S WS
Вибір входу I2S
GPIO pin for I2S DIN
Вибір виходу I2S
GPIO pin for I2S DOUT
I2S тактування
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Опис
Конфігурація віддаленого пристрою активована
Activate remote GPIO access
Дозволити доступ до невизначених пінів
Allow access to any GPIO pin (security risk)
Доступні піни
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Опис
Інформацію про сусідів увімкнено
Activate neighbor broadcasting
Інтервал опитування GPS
How often to broadcast neighbor list
Передавати через LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Опис
Стан світлодіоду
Turn the LED on or off
Поточний
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Опис
Датчик виявлення увімкнено
Activate detection sensor
GPIO контакт для моніторингу
GPIO pin connected to sensor
Тип тригера виявлення
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Використовувати режим INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Надсилати дзвіночок з тривожним повідомленням
Include bell character in alerts
Дружня назва
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Опис
Лічильник пристроїв активований
Activate people counting
Інтервал опитування GPS
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Адміністрування
Віддалене керування
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Встановити час
Sends your phone’s clock to the node
Перевантажити
Restarts the node
Вимкнути
Powers the node down
Скинути до заводських налаштувань
Returns every setting to its factory default
Очищення бази вузлів
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Резервна копія & Відновлення
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Розширені
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Очистити базу даних вузлів
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Панель налагодження
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Про
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Подяки
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
Налаштування модуля
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
Опис
MQTT увімкнений
Toggle MQTT bridge
Адреса
MQTT broker address
Ім’я користувача
Authentication username
Пароль
Authentication password
Шифрування увімкнено
Encrypt MQTT payloads
Вивід JSON увімкнено
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS увімкнений
Use secure connection
Кореневий чат
Base MQTT topic path
Проксі для клієнта увімкнуто
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
Відображення на мапі
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
Опис
Погоджуюся.
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
Опис
Послідовний порт увімкнено
Activate serial communication
Відлуння активоване
Echo received serial data back
Послідовний режим
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
Швидкість послідовного порту
Port speed
Таймаут
How long to wait before considering an incoming message complete
Перевизначити послідовний порт
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
Опис
Зовнішні сповіщення увімкнено
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
Вихідний LED (GPIO)
Pin the LED is wired to
Активний високий рівень світлодіода
Whether the LED pin is active high or low
Вихідний гудок (GPIO)
Pin the buzzer is wired to
Вихід вібросигналу (GPIO)
Pin the vibration motor is wired to
Використовувати зумер із ШІМ-керуванням
Drive the buzzer with PWM, which allows tones rather than a single pitch
Використовувати I2S як гудок
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
Nag Timeout
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
Мелодія
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
Опис
Збереження та перенаправлення увімкнено
Activate store and forward
Пульсація
Periodically announce this node’s store-and-forward capability
Кількість записів
Maximum stored messages
Максимальний обсяг історії
Max messages to replay
Максимальне вікно історії
Time window for replay
Сервер
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
Опис
Тест на відстань увімкнений
Activate range testing
Sender Interval
Time between test transmissions, chosen from a dropdown of fixed intervals
Зберегти .CSV у сховищі (лише ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
Опис
Надсилати телеметрію пристрою
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
Інтервал оновлення показників пристрою
How often to report battery, uptime and channel utilization
Модуль екологічних показників увімкнено
Report the attached environment sensors
Інтервал оновлення екологічних показників
How often to report them
Екологічні показники на екрані увімкнено
Also show these readings on the device’s own display
Екологічні показники використовують шкалу Фаренгейта
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
Модуль показників якості повітря увімкнено
Report particulate and CO₂ sensor data
Інтервал оновлення показників якості повітря
How often to report them
Модуль показників потужності ввімкнено
Report the per-channel voltage and current readings
Інтервал оновлення показників потужності
How often to report them
Показники потужності на екрані ввімкнено
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
Опис
Canned message enabled
⚠️ Deprecated in the protobuf schema
Повідомлення
Newline-separated list of messages
Надіслати дзвіночок
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
Енкодер #1 активований
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
Увімкнути керування Вгору/Вниз/Вибір
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
Опис
CODEC 2 увімкнено
Activate audio module
Частота дискретизації CODEC2
Audio quality/bandwidth tradeoff
PTT контакт
GPIO pin for the push-to-talk button
Вибір слова I2S
GPIO pin for I2S WS
Вибір входу I2S
GPIO pin for I2S DIN
Вибір виходу I2S
GPIO pin for I2S DOUT
I2S тактування
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
Опис
Конфігурація віддаленого пристрою активована
Activate remote GPIO access
Дозволити доступ до невизначених пінів
Allow access to any GPIO pin (security risk)
Доступні піни
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
Опис
Інформацію про сусідів увімкнено
Activate neighbor broadcasting
Інтервал опитування GPS
How often to broadcast neighbor list
Передавати через LoRa
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
Опис
Стан світлодіоду
Turn the LED on or off
Поточний
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
Опис
Датчик виявлення увімкнено
Activate detection sensor
GPIO контакт для моніторингу
GPIO pin connected to sensor
Тип тригера виявлення
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
Використовувати режим INPUT_PULLUP
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
Надсилати дзвіночок з тривожним повідомленням
Include bell character in alerts
Дружня назва
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
Опис
Лічильник пристроїв активований
Activate people counting
Інтервал опитування GPS
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
Адміністрування
Віддалене керування
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
Встановити час
Sends your phone’s clock to the node
Перевантажити
Restarts the node
Вимкнути
Powers the node down
Скинути до заводських налаштувань
Returns every setting to its factory default
Очищення бази вузлів
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
Резервна копія & Відновлення
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
Розширені
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
Очистити базу даних вузлів
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
Панель налагодження
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
Про
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
Подяки
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
Desktop
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
在没有手机服务的情况下与您的朋友和社区进行网外通信。
Create Your Own Networks
轻松建立私人网格网络，以便在偏远地区进行安全和可靠的通信。
Track and Share Locations
实时分享您的位置，并通过集成的GPS功能保持团队的协调一致。
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
在没有手机服务的情况下与您的朋友和社区进行网外通信。
Create Your Own Networks
轻松建立私人网格网络，以便在偏远地区进行安全和可靠的通信。
Track and Share Locations
实时分享您的位置，并通过集成的GPS功能保持团队的协调一致。
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
State
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
模块设定
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
说明
启用MQTT
Toggle MQTT bridge
地址
MQTT broker address
用户名称
Authentication username
密码
Authentication password
启用加密
Encrypt MQTT payloads
启用JSON输出
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
启用TLS
Use secure connection
根主题
Base MQTT topic path
启用客户端代理
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
地图报告
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
说明
我同意。
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
地图发布间隔
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
说明
启用串口
Activate serial communication
启用Echo
Echo received serial data back
串口模式
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
串口波特率
Port speed
超时
How long to wait before considering an incoming message complete
覆盖控制台串口端口
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
说明
启用外部通知
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
输出 LED (GPIO)
Pin the LED is wired to
输出 LED 活动高
Whether the LED pin is active high or low
输出震动(GPIO)
Pin the buzzer is wired to
输出振动 (GPIO)
Pin the vibration motor is wired to
使用 PWM 蜂鸣器
Drive the buzzer with PWM, which allows tones rather than a single pitch
使用 I2S 作为蜂鸣器
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
超时提醒
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
铃声
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
说明
启用存储和转发
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
记录数
Maximum stored messages
历史记录最大返回值
Max messages to replay
历史记录返回窗口
Time window for replay
服务器
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
说明
启用范围测试
Activate range testing
发送间隔
Time between test transmissions, chosen from a dropdown of fixed intervals
保存 CSV 到存储 (仅ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
说明
发送设备远程数据
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
设备计量更新间隔
How often to report battery, uptime and channel utilization
启用环境计量模块
Report the attached environment sensors
环境计量更新间隔
How often to report them
屏幕显示环境指标
Also show these readings on the device’s own display
环境测量值使用华氏度
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
启用空气质量计量模块
Report particulate and CO₂ sensor data
空气质量计量更新间隔
How often to report them
启用电源计量模块
Report the per-channel voltage and current readings
电量计更新间隔
How often to report them
在屏幕上启用电源指标
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
说明
Canned message enabled
⚠️ Deprecated in the protobuf schema
消息
Newline-separated list of messages
发送响铃
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
启用旋转编码器 #1
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
启用Up/Down/select 输入
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
说明
启用CODEC2
Activate audio module
CODEC2 采样率
Audio quality/bandwidth tradeoff
PTT 引脚
GPIO pin for the push-to-talk button
I2S 字选择
GPIO pin for I2S WS
I2S 数据 IN
GPIO pin for I2S DIN
I2S 数据 OUT
GPIO pin for I2S DOUT
I2S 时钟
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
说明
启用远程硬件
Activate remote GPIO access
允许未定义的引脚访问
Allow access to any GPIO pin (security risk)
可用引脚
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
说明
启用邻居信息
Activate neighbor broadcasting
GPS 轮询间隔
How often to broadcast neighbor list
通过 LoRa 传输
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
说明
LED 状态
Turn the LED on or off
电流
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
说明
启用检测传感器
Activate detection sensor
显示器的 GPIO 引脚
GPIO pin connected to sensor
检测触发器类型
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
使用 输入上拉 模式
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
发送带有警报消息的响铃声
Include bell character in alerts
友好名称
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
说明
启用 Paxcount
Activate people counting
GPS 轮询间隔
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
管理员
远程管理
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
设置时间
Sends your phone’s clock to the node
重启
Restarts the node
关机
Powers the node down
恢复出厂设置
Returns every setting to its factory default
重置节点数据库
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
备份与恢复
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
高级
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
清理节点数据库
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
调试面板
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App 设置
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
关于
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
开源
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
模块设定
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
Setting
说明
启用MQTT
Toggle MQTT bridge
地址
MQTT broker address
用户名称
Authentication username
密码
Authentication password
启用加密
Encrypt MQTT payloads
启用JSON输出
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
启用TLS
Use secure connection
根主题
Base MQTT topic path
启用客户端代理
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
地图报告
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
Setting
说明
我同意。
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
地图发布间隔
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
Setting
说明
启用串口
Activate serial communication
启用Echo
Echo received serial data back
串口模式
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
串口波特率
Port speed
超时
How long to wait before considering an incoming message complete
覆盖控制台串口端口
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
Setting
说明
启用外部通知
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
输出 LED (GPIO)
Pin the LED is wired to
输出 LED 活动高
Whether the LED pin is active high or low
输出震动(GPIO)
Pin the buzzer is wired to
输出振动 (GPIO)
Pin the vibration motor is wired to
使用 PWM 蜂鸣器
Drive the buzzer with PWM, which allows tones rather than a single pitch
使用 I2S 作为蜂鸣器
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
超时提醒
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
铃声
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
Setting
说明
启用存储和转发
Activate store and forward
Heartbeat
Periodically announce this node’s store-and-forward capability
记录数
Maximum stored messages
历史记录最大返回值
Max messages to replay
历史记录返回窗口
Time window for replay
服务器
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
Setting
说明
启用范围测试
Activate range testing
发送间隔
Time between test transmissions, chosen from a dropdown of fixed intervals
保存 CSV 到存储 (仅ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
Setting
说明
发送设备远程数据
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
设备计量更新间隔
How often to report battery, uptime and channel utilization
启用环境计量模块
Report the attached environment sensors
环境计量更新间隔
How often to report them
屏幕显示环境指标
Also show these readings on the device’s own display
环境测量值使用华氏度
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
启用空气质量计量模块
Report particulate and CO₂ sensor data
空气质量计量更新间隔
How often to report them
启用电源计量模块
Report the per-channel voltage and current readings
电量计更新间隔
How often to report them
在屏幕上启用电源指标
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
Setting
说明
Canned message enabled
⚠️ Deprecated in the protobuf schema
消息
Newline-separated list of messages
发送响铃
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
启用旋转编码器 #1
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
启用Up/Down/select 输入
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
Setting
说明
启用CODEC2
Activate audio module
CODEC2 采样率
Audio quality/bandwidth tradeoff
PTT 引脚
GPIO pin for the push-to-talk button
I2S 字选择
GPIO pin for I2S WS
I2S 数据 IN
GPIO pin for I2S DIN
I2S 数据 OUT
GPIO pin for I2S DOUT
I2S 时钟
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
Setting
说明
启用远程硬件
Activate remote GPIO access
允许未定义的引脚访问
Allow access to any GPIO pin (security risk)
可用引脚
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
Setting
说明
启用邻居信息
Activate neighbor broadcasting
GPS 轮询间隔
How often to broadcast neighbor list
通过 LoRa 传输
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
Setting
说明
LED 状态
Turn the LED on or off
电流
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
Setting
说明
启用检测传感器
Activate detection sensor
显示器的 GPIO 引脚
GPIO pin connected to sensor
检测触发器类型
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
使用 输入上拉 模式
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
State Broadcast Interval
Periodic state broadcast interval
发送带有警报消息的响铃声
Include bell character in alerts
友好名称
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
Setting
说明
启用 Paxcount
Activate people counting
GPS 轮询间隔
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
管理员
远程管理
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
Action
What it does
设置时间
Sends your phone’s clock to the node
重启
Restarts the node
关机
Powers the node down
恢复出厂设置
Returns every setting to its factory default
重置节点数据库
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
备份与恢复
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
高级
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
清理节点数据库
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
调试面板
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App 设置
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
关于
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
开源
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
桌面版
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way.
When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them.
Open the Debug Panel from Settings → Advanced → Debug Panel.
If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down.
The two tabs
The Debug Panel has two tabs:
Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior.
App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs.
Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both.
Viewing app logs
The App logs tab shows the most recent log lines from this app only — never other apps on your phone.
Search — type in the search box to filter to matching lines.
Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown.
Refresh — the refresh icon re-reads the latest logs.
Error and warning lines are tinted so problems stand out.
Exporting
Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export.
Attach that file to your GitHub issue.
🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt.
桌面版
The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. Release builds capture Info, Warn, and Error lines; Verbose and Debug lines appear only in development builds.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
無需手機訊號，也能與您的朋友和社群離線通訊。
Create Your Own Networks
輕鬆設定私有網狀網絡，以實現偏遠地區安全可靠的通訊。
Track and Share Locations
透過整合的 GPS 功能，即時分享你的位置，並保持團隊協調一致。
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
狀態
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later.
First Launch
When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app.
Welcome Screen
The welcome screen introduces Meshtastic with three feature rows:
Stay Connected Anywhere
無需手機訊號，也能與您的朋友和社群離線通訊。
Create Your Own Networks
輕鬆設定私有網狀網絡，以實現偏遠地區安全可靠的通訊。
Track and Share Locations
透過整合的 GPS 功能，即時分享你的位置，並保持團隊協調一致。
Tap Get started to proceed through the setup flow.
Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you:
Discovery — find and identify Meshtastic devices near you.
Configuration — wirelessly manage your device settings and channels.
On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead.
Location Permission
ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio.
Meshtastic also uses your location for:
Showing your position on the mesh map
Calculating distances to other nodes
Sharing your GPS coordinates with other mesh members (if enabled)
On Android 12 and newer, choose Precise to share your position with the mesh: an approximate grant still shows you on the map, but position sharing needs precise location.
Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service.
Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything.
Notifications Permission
Notifications alert you to:
Incoming messages from channels and direct messages
New nodes joining the mesh
Low battery on a remote node
💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually.
Critical Alerts Permission
Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages.
This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there.
Reviewing permissions later
The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them.
The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time:
狀態
What tapping the row does
Allowed
Opens the system page, so you can review or revoke it
Not asked yet
Requests it
Denied — tap to allow
Explains what the permission is for, then asks again if you agree
Blocked — tap to open system settings
Android will no longer show its dialog, so this opens the page where you can turn it back on
Not required on this version of Android
Nothing — the permission does not exist on your device
This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings.
After Setup
After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions.
💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own.
Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings.
New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
模組設定
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
設定
描述說明
啟用MQTT服務器
Toggle MQTT bridge
地址
MQTT broker address
使用者名稱
Authentication username
密碼
Authentication password
加密已啟用
Encrypt MQTT payloads
JSON輸出已啟用
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS已啟用
Use secure connection
根話題
Base MQTT topic path
啟用對客戶端的代理
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
地圖報告
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
設定
描述說明
我同意。
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
設定
描述說明
啟用序列埠
Activate serial communication
啟用 Echo
Echo received serial data back
序列埠模式
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
序列埠鮑率
Port speed
Timeout - 超時
How long to wait before considering an incoming message complete
覆蓋控制台序列埠
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
設定
描述說明
啟用外部通知
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
輸出LED（GPIO）
Pin the LED is wired to
輸出LED 高電平觸發
Whether the LED pin is active high or low
輸出蜂鳴（GPIO）
Pin the buzzer is wired to
輸出振動（GPIO）
Pin the vibration motor is wired to
使用PWM調製的蜂鳴
Drive the buzzer with PWM, which allows tones rather than a single pitch
使用 I2S 控制蜂鳴器
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
持續提醒逾時
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
鈴聲
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
設定
描述說明
啟用儲存並轉發
Activate store and forward
心跳
Periodically announce this node’s store-and-forward capability
紀錄數目
Maximum stored messages
歴史紀錄最大返回值
Max messages to replay
歴史紀錄返回視窗
Time window for replay
伺服器
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
設定
描述說明
啟用範圍測試
Activate range testing
傳送間隔
Time between test transmissions, chosen from a dropdown of fixed intervals
將 .CSV 保存到內部儲存空間(僅限ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
設定
描述說明
傳送裝置遙測資料
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
裝置資訊更新間隔
How often to report battery, uptime and channel utilization
啟用環境資訊模組
Report the attached environment sensors
環境資訊更新間隔
How often to report them
在螢幕上顯示環境資訊
Also show these readings on the device’s own display
環境指標以華氏溫度顯示
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
啟用空氣品質模組
Report particulate and CO₂ sensor data
空氣品質資訊更新間隔
How often to report them
啟用電池資訊模組
Report the per-channel voltage and current readings
電源資訊更新間隔
How often to report them
在螢幕上顯示電量資訊
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
設定
描述說明
Canned message enabled
⚠️ Deprecated in the protobuf schema
訊息
Newline-separated list of messages
發送振鈴
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
啟用旋轉編碼器#1
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
啟用上下選擇輸入
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
設定
描述說明
啟用 CODEC 2
Activate audio module
CODEC2 取樣率
Audio quality/bandwidth tradeoff
PTT針腳
GPIO pin for the push-to-talk button
I2S WS 訊號選擇
GPIO pin for I2S WS
I2S 數據輸入
GPIO pin for I2S DIN
I2S 數據輸出
GPIO pin for I2S DOUT
I2S 時鐘
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
設定
描述說明
啟動遠端硬體
Activate remote GPIO access
允許未定義腳位連接
Allow access to any GPIO pin (security risk)
可用腳位
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
設定
描述說明
啟用鄰居資訊
Activate neighbor broadcasting
GPS 輪詢間隔
How often to broadcast neighbor list
通過Lora無線電傳輸
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
設定
描述說明
LED狀態
Turn the LED on or off
目前
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
設定
描述說明
啟用偵測感測器
Activate detection sensor
螢幕的 GPIO 腳位
GPIO pin connected to sensor
偵測觸發類型
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
使用輸入上拉模式
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
狀態廣播間隔
Periodic state broadcast interval
告警訊息發送提示音
Include bell character in alerts
顯示名稱
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
設定
描述說明
已啟用人流計數（Paxcount）
Activate people counting
GPS 輪詢間隔
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
管理
遠端管理
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
動作
What it does
Set time
Sends your phone’s clock to the node
重新開機
Restarts the node
關機
Powers the node down
恢復出廠設置
Returns every setting to its factory default
重設節點資料庫
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
備份與還原
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
進階
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
清除節點資料庫
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
偵錯面板
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings 應用程式設定
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
About（關於）
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
致謝
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
模組設定
Every module lives under Settings → Module configuration.
⚠️ Important: Saving a module screen restarts the node: the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save. External Notification may still restart the node for some changes, while a Mesh Beacon change applies without a restart.
MQTT module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems.
設定
描述說明
啟用MQTT服務器
Toggle MQTT bridge
地址
MQTT broker address
使用者名稱
Authentication username
密碼
Authentication password
加密已啟用
Encrypt MQTT payloads
JSON輸出已啟用
Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it
TLS已啟用
Use secure connection
根話題
Base MQTT topic path
啟用對客戶端的代理
Let the connected app carry the node’s MQTT traffic, instead of the node reaching the broker itself
MQTT proxy in this app
The app-side half of Proxy to client enabled: whether this app acts as that relay. See MQTT
地圖報告
Publish position to the public map — see the Map reporting group that follows
Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree:
設定
描述說明
我同意。
Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it
Precision slider
The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units
Map Publish Interval
How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered
See MQTT for a detailed usage guide including encryption, privacy, and broker setup.
Serial module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
設定
描述說明
啟用序列埠
Activate serial communication
啟用 Echo
Echo received serial data back
序列埠模式
Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only)
RX / TX
GPIO pins for the serial connection
序列埠鮑率
Port speed
Timeout - 超時
How long to wait before considering an incoming message complete
覆蓋控制台序列埠
Take over the port the debug console normally uses
External Notification module
Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
設定
描述說明
啟用外部通知
Master toggle for the module
Alert message LED / buzzer / vibra
Which outputs fire on an incoming message
Alert bell LED / buzzer / vibra
Which outputs fire on a received bell character
輸出LED（GPIO）
Pin the LED is wired to
輸出LED 高電平觸發
Whether the LED pin is active high or low
輸出蜂鳴（GPIO）
Pin the buzzer is wired to
輸出振動（GPIO）
Pin the vibration motor is wired to
使用PWM調製的蜂鳴
Drive the buzzer with PWM, which allows tones rather than a single pitch
使用 I2S 控制蜂鳴器
Send the alert through an I2S audio output instead
GPIO Output Duration
How long a single alert lasts
持續提醒逾時
Keep repeating the alert for this long until it is acknowledged. 0 disables nagging
鈴聲
The tone played on a PWM buzzer, in RTTTL. Can be imported from a file
Store & Forward module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections.
設定
描述說明
啟用儲存並轉發
Activate store and forward
心跳
Periodically announce this node’s store-and-forward capability
紀錄數目
Maximum stored messages
歴史紀錄最大返回值
Max messages to replay
歴史紀錄返回視窗
Time window for replay
伺服器
Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM)
💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on.
Range Test module
⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public.
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
設定
描述說明
啟用範圍測試
Activate range testing
傳送間隔
Time between test transmissions, chosen from a dropdown of fixed intervals
將 .CSV 保存到內部儲存空間(僅限ESP32)
Log received test data to the node’s own filesystem. ESP32 hardware only
Telemetry module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely.
設定
描述說明
傳送裝置遙測資料
Master toggle for device metrics. Only shown on firmware 2.7.12 and newer
裝置資訊更新間隔
How often to report battery, uptime and channel utilization
啟用環境資訊模組
Report the attached environment sensors
環境資訊更新間隔
How often to report them
在螢幕上顯示環境資訊
Also show these readings on the device’s own display
環境指標以華氏溫度顯示
Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale
啟用空氣品質模組
Report particulate and CO₂ sensor data
空氣品質資訊更新間隔
How often to report them
啟用電池資訊模組
Report the per-channel voltage and current readings
電源資訊更新間隔
How often to report them
在螢幕上顯示電量資訊
Also show power readings on the device’s display
See Telemetry & Sensors for supported sensors and configuration recommendations.
Canned Message module
Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
設定
描述說明
Canned message enabled
⚠️ Deprecated in the protobuf schema
訊息
Newline-separated list of messages
發送振鈴
Send a bell character alongside the message, so a receiving node’s External Notification module can sound
啟用旋轉編碼器#1
Use a rotary encoder as the input device
GPIO pin for rotary encoder A / B / Press port
The three pins the encoder is wired to
Generate input event on Press / CW / CCW
Which key event each encoder action produces
啟用上下選擇輸入
A separate, simpler input scheme using up/down/select buttons rather than an encoder
Allow input source
⚠️ Deprecated in the protobuf schema
Audio module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.
設定
描述說明
啟用 CODEC 2
Activate audio module
CODEC2 取樣率
Audio quality/bandwidth tradeoff
PTT針腳
GPIO pin for the push-to-talk button
I2S WS 訊號選擇
GPIO pin for I2S WS
I2S 數據輸入
GPIO pin for I2S DIN
I2S 數據輸出
GPIO pin for I2S DOUT
I2S 時鐘
GPIO pin for the I2S bit clock
ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality.
Remote Hardware module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes.
設定
描述說明
啟動遠端硬體
Activate remote GPIO access
允許未定義腳位連接
Allow access to any GPIO pin (security risk)
可用腳位
Up to 4 GPIO pins this node exposes for remote read/write
Neighbor Info module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
設定
描述說明
啟用鄰居資訊
Activate neighbor broadcasting
GPS 輪詢間隔
How often to broadcast neighbor list
通過Lora無線電傳輸
Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name
See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.
Ambient Lighting module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
設定
描述說明
LED狀態
Turn the LED on or off
目前
LED current limit (0–31)
Red / Green / Blue
Individual color channel values (0–255)
Detection Sensor module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
設定
描述說明
啟用偵測感測器
Activate detection sensor
螢幕的 GPIO 腳位
GPIO pin connected to sensor
偵測觸發類型
How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered)
使用輸入上拉模式
Enable the pin’s internal pull-up resistor
Minimum time between detection broadcasts
Minimum time between alert broadcasts
狀態廣播間隔
Periodic state broadcast interval
告警訊息發送提示音
Include bell character in alerts
顯示名稱
Custom name for this sensor
Paxcounter module
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
設定
描述說明
已啟用人流計數（Paxcount）
Activate people counting
GPS 輪詢間隔
How often to report counts
WiFi Threshold (dBm)
Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm)
BLE Threshold (dBm)
The same cut-off for BLE advertisements (defaults to −80 dBm)
💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
Status Message module
The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User.
Mesh Beacon module
Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough.
TAK module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage.
管理
遠端管理
Remotely configure nodes that share your admin key:
Select the target node in the node list.
Navigate to Settings for that node.
Modify configuration.
Tap Save — changes are sent over the mesh.
⚠️ Important: Requires an admin key configured on both your node and the target node.
Device Actions
Settings → Administration holds five one-shot actions, each behind a confirmation dialog:
動作
What it does
Set time
Sends your phone’s clock to the node
重新開機
Restarts the node
關機
Powers the node down
恢復出廠設置
Returns every setting to its factory default
重設節點資料庫
Clears the node database. This dialog carries a Preserve Favorites? switch
⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards.
備份與還原
Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Traffic Management settings are exported but not applied on import. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin.
進階
Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel.
清除節點資料庫
Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive.
Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.
Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it.
The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect.
偵錯面板
Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.
App Settings 應用程式設定
The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat:
Privacy
Allow analytics and crash reporting — opt in or out of diagnostics.
Provide phone location to mesh — share this phone’s position when the node has no GPS fix. It needs precise location: with approximate location allowed, turning it on asks for precise.
Homoglyph encoding — how look-alike characters in names are handled.
Appearance
Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to.
Theme and Language.
Show full message timestamps.
Persistence
A cache limit for how much history is kept.
Export rangetest packets, Export all packets and Export node database.
On their own
Node Layout — how much detail each row of the node list shows.
Wi-Fi Provisioning for mPWRD-OS — see Connections.
Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing.
System AI — appears only where app functions are available; see App Functions.
A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below.
About（關於）
Settings → About carries the app’s own identity rather than the node’s:
Three sections:
What is Meshtastic? — a short description of the project.
Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section).
Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under.
The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license.
致謝
Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen.
Troubleshooting remote admin
“No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.
Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
