From 5b1dcdd95d6ec565c825b37e8b2012cbb5583d80 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 10 Sep 2026 21:22:31 +0000 Subject: [PATCH] docs: publish channels: main api --- .../-robolectric-ble-bonding/index.html | 2 +- .../-meshtastic-dialog.html | 2 +- main/ar-rSA/user/node-metrics.html | 2 +- main/ar-rSA/user/nodes.html | 2 +- main/ar-rSA/user/settings-radio-user.html | 2 +- main/ar-rSA/user/signal-meter.html | 2 +- main/assets/css/just-the-docs-dark.css.map | 2 +- main/assets/css/just-the-docs-default.css.map | 2 +- main/assets/css/just-the-docs-light.css.map | 2 +- .../css/just-the-docs-meshtastic-dark.css.map | 2 +- .../css/just-the-docs-meshtastic.css.map | 2 +- main/assets/js/search-data.json | 322 +++++++++--------- main/be-rBY/user/node-metrics.html | 2 +- main/be-rBY/user/nodes.html | 2 +- main/be-rBY/user/settings-radio-user.html | 2 +- main/be-rBY/user/signal-meter.html | 2 +- main/bg-rBG/user/node-metrics.html | 2 +- main/bg-rBG/user/nodes.html | 2 +- main/bg-rBG/user/settings-radio-user.html | 2 +- main/bg-rBG/user/signal-meter.html | 2 +- main/bg-rBG/user/telemetry-and-sensors.html | 2 +- main/ca-rES/user/node-metrics.html | 2 +- main/ca-rES/user/nodes.html | 2 +- main/ca-rES/user/settings-radio-user.html | 2 +- main/ca-rES/user/signal-meter.html | 2 +- main/cs-rCZ/user/node-metrics.html | 2 +- main/cs-rCZ/user/nodes.html | 2 +- main/cs-rCZ/user/settings-radio-user.html | 2 +- main/cs-rCZ/user/signal-meter.html | 2 +- main/de-rDE/user/node-metrics.html | 2 +- main/de-rDE/user/nodes.html | 2 +- main/de-rDE/user/settings-radio-user.html | 2 +- main/de-rDE/user/signal-meter.html | 2 +- main/docs/ar-rSA/user/node-metrics.html | 2 +- main/docs/ar-rSA/user/nodes.html | 2 + .../docs/ar-rSA/user/settings-radio-user.html | 6 +- main/docs/ar-rSA/user/signal-meter.html | 4 +- main/docs/be-rBY/user/node-metrics.html | 2 +- main/docs/be-rBY/user/nodes.html | 2 + .../docs/be-rBY/user/settings-radio-user.html | 6 +- main/docs/be-rBY/user/signal-meter.html | 4 +- main/docs/bg-rBG/user/node-metrics.html | 2 +- main/docs/bg-rBG/user/nodes.html | 2 + .../docs/bg-rBG/user/settings-radio-user.html | 6 +- main/docs/bg-rBG/user/signal-meter.html | 4 +- .../bg-rBG/user/telemetry-and-sensors.html | 10 +- main/docs/ca-rES/user/node-metrics.html | 2 +- main/docs/ca-rES/user/nodes.html | 2 + .../docs/ca-rES/user/settings-radio-user.html | 6 +- main/docs/ca-rES/user/signal-meter.html | 4 +- main/docs/cs-rCZ/user/node-metrics.html | 2 +- main/docs/cs-rCZ/user/nodes.html | 2 + .../docs/cs-rCZ/user/settings-radio-user.html | 6 +- main/docs/cs-rCZ/user/signal-meter.html | 4 +- main/docs/de-rDE/user/node-metrics.html | 2 +- main/docs/de-rDE/user/nodes.html | 2 + .../docs/de-rDE/user/settings-radio-user.html | 6 +- main/docs/de-rDE/user/signal-meter.html | 4 +- main/docs/el-rGR/user/node-metrics.html | 2 +- main/docs/el-rGR/user/nodes.html | 2 + .../docs/el-rGR/user/settings-radio-user.html | 6 +- main/docs/el-rGR/user/signal-meter.html | 4 +- main/docs/es-rES/user/node-metrics.html | 2 +- main/docs/es-rES/user/nodes.html | 2 + .../docs/es-rES/user/settings-radio-user.html | 6 +- main/docs/es-rES/user/signal-meter.html | 4 +- main/docs/et-rEE/user/node-metrics.html | 2 +- main/docs/et-rEE/user/nodes.html | 2 + .../docs/et-rEE/user/settings-radio-user.html | 6 +- main/docs/et-rEE/user/signal-meter.html | 4 +- main/docs/fi-rFI/user/node-metrics.html | 2 +- main/docs/fi-rFI/user/nodes.html | 2 + .../docs/fi-rFI/user/settings-radio-user.html | 6 +- main/docs/fi-rFI/user/signal-meter.html | 4 +- main/docs/fr-rCA/user/node-metrics.html | 2 +- main/docs/fr-rCA/user/nodes.html | 2 + .../docs/fr-rCA/user/settings-radio-user.html | 6 +- main/docs/fr-rCA/user/signal-meter.html | 4 +- main/docs/fr-rFR/user/node-metrics.html | 2 +- main/docs/fr-rFR/user/nodes.html | 2 + .../docs/fr-rFR/user/settings-radio-user.html | 6 +- main/docs/fr-rFR/user/signal-meter.html | 4 +- main/docs/ga-rIE/user/node-metrics.html | 2 +- main/docs/ga-rIE/user/nodes.html | 2 + .../docs/ga-rIE/user/settings-radio-user.html | 6 +- main/docs/ga-rIE/user/signal-meter.html | 4 +- main/docs/gl-rES/user/node-metrics.html | 2 +- main/docs/gl-rES/user/nodes.html | 2 + .../docs/gl-rES/user/settings-radio-user.html | 6 +- main/docs/gl-rES/user/signal-meter.html | 4 +- main/docs/hr-rHR/user/node-metrics.html | 2 +- main/docs/hr-rHR/user/nodes.html | 2 + .../docs/hr-rHR/user/settings-radio-user.html | 6 +- main/docs/hr-rHR/user/signal-meter.html | 4 +- main/docs/ht-rHT/user/node-metrics.html | 2 +- main/docs/ht-rHT/user/nodes.html | 2 + .../docs/ht-rHT/user/settings-radio-user.html | 6 +- main/docs/ht-rHT/user/signal-meter.html | 4 +- main/docs/hu-rHU/user/node-metrics.html | 2 +- main/docs/hu-rHU/user/nodes.html | 2 + .../docs/hu-rHU/user/settings-radio-user.html | 6 +- main/docs/hu-rHU/user/signal-meter.html | 4 +- main/docs/is-rIS/user/node-metrics.html | 2 +- main/docs/is-rIS/user/nodes.html | 2 + .../docs/is-rIS/user/settings-radio-user.html | 6 +- main/docs/is-rIS/user/signal-meter.html | 4 +- main/docs/it-rIT/user/node-metrics.html | 2 +- main/docs/it-rIT/user/nodes.html | 2 + .../docs/it-rIT/user/settings-radio-user.html | 6 +- main/docs/it-rIT/user/signal-meter.html | 4 +- main/docs/iw-rIL/user/node-metrics.html | 2 +- main/docs/iw-rIL/user/nodes.html | 2 + .../docs/iw-rIL/user/settings-radio-user.html | 6 +- main/docs/iw-rIL/user/signal-meter.html | 4 +- main/docs/ja-rJP/user/node-metrics.html | 2 +- main/docs/ja-rJP/user/nodes.html | 2 + .../docs/ja-rJP/user/settings-radio-user.html | 6 +- main/docs/ja-rJP/user/signal-meter.html | 4 +- main/docs/ko-rKR/user/node-metrics.html | 2 +- main/docs/ko-rKR/user/nodes.html | 2 + .../docs/ko-rKR/user/settings-radio-user.html | 6 +- main/docs/ko-rKR/user/signal-meter.html | 4 +- main/docs/lt-rLT/user/node-metrics.html | 2 +- main/docs/lt-rLT/user/nodes.html | 2 + .../docs/lt-rLT/user/settings-radio-user.html | 6 +- main/docs/lt-rLT/user/signal-meter.html | 4 +- main/docs/nl-rNL/user/node-metrics.html | 2 +- main/docs/nl-rNL/user/nodes.html | 2 + .../docs/nl-rNL/user/settings-radio-user.html | 6 +- main/docs/nl-rNL/user/signal-meter.html | 4 +- main/docs/no-rNO/user/node-metrics.html | 2 +- main/docs/no-rNO/user/nodes.html | 2 + .../docs/no-rNO/user/settings-radio-user.html | 6 +- main/docs/no-rNO/user/signal-meter.html | 4 +- main/docs/pl-rPL/user/node-metrics.html | 2 +- main/docs/pl-rPL/user/nodes.html | 2 + .../docs/pl-rPL/user/settings-radio-user.html | 6 +- main/docs/pl-rPL/user/signal-meter.html | 4 +- main/docs/pt-rBR/user/node-metrics.html | 2 +- main/docs/pt-rBR/user/nodes.html | 2 + .../docs/pt-rBR/user/settings-radio-user.html | 6 +- main/docs/pt-rBR/user/signal-meter.html | 4 +- main/docs/pt-rPT/user/node-metrics.html | 2 +- main/docs/pt-rPT/user/nodes.html | 2 + .../docs/pt-rPT/user/settings-radio-user.html | 6 +- main/docs/pt-rPT/user/signal-meter.html | 4 +- main/docs/ro-rRO/user/node-metrics.html | 2 +- main/docs/ro-rRO/user/nodes.html | 2 + .../docs/ro-rRO/user/settings-radio-user.html | 6 +- main/docs/ro-rRO/user/signal-meter.html | 4 +- main/docs/ru-rRU/user/node-metrics.html | 2 +- main/docs/ru-rRU/user/nodes.html | 2 + .../docs/ru-rRU/user/settings-radio-user.html | 6 +- main/docs/ru-rRU/user/signal-meter.html | 4 +- main/docs/sk-rSK/user/node-metrics.html | 2 +- main/docs/sk-rSK/user/nodes.html | 2 + .../docs/sk-rSK/user/settings-radio-user.html | 6 +- main/docs/sk-rSK/user/signal-meter.html | 4 +- main/docs/sl-rSI/user/node-metrics.html | 2 +- main/docs/sl-rSI/user/nodes.html | 2 + .../docs/sl-rSI/user/settings-radio-user.html | 6 +- main/docs/sl-rSI/user/signal-meter.html | 4 +- main/docs/sq-rAL/user/node-metrics.html | 2 +- main/docs/sq-rAL/user/nodes.html | 2 + .../docs/sq-rAL/user/settings-radio-user.html | 6 +- main/docs/sq-rAL/user/signal-meter.html | 4 +- main/docs/srp/user/node-metrics.html | 2 +- main/docs/srp/user/nodes.html | 2 + main/docs/srp/user/settings-radio-user.html | 6 +- main/docs/srp/user/signal-meter.html | 4 +- main/docs/sv-rSE/user/node-metrics.html | 2 +- main/docs/sv-rSE/user/nodes.html | 2 + .../docs/sv-rSE/user/settings-radio-user.html | 6 +- main/docs/sv-rSE/user/signal-meter.html | 4 +- main/docs/tr-rTR/user/node-metrics.html | 2 +- main/docs/tr-rTR/user/nodes.html | 2 + .../docs/tr-rTR/user/settings-radio-user.html | 6 +- main/docs/tr-rTR/user/signal-meter.html | 4 +- main/docs/uk-rUA/user/node-metrics.html | 2 +- main/docs/uk-rUA/user/nodes.html | 2 + .../docs/uk-rUA/user/settings-radio-user.html | 6 +- main/docs/uk-rUA/user/signal-meter.html | 4 +- main/docs/zh-rCN/user/node-metrics.html | 2 +- main/docs/zh-rCN/user/nodes.html | 2 + .../docs/zh-rCN/user/settings-radio-user.html | 6 +- main/docs/zh-rCN/user/signal-meter.html | 4 +- main/docs/zh-rTW/user/node-metrics.html | 2 +- main/docs/zh-rTW/user/nodes.html | 2 + .../docs/zh-rTW/user/settings-radio-user.html | 6 +- main/docs/zh-rTW/user/signal-meter.html | 4 +- main/el-rGR/user/node-metrics.html | 2 +- main/el-rGR/user/nodes.html | 2 +- main/el-rGR/user/settings-radio-user.html | 2 +- main/el-rGR/user/signal-meter.html | 2 +- main/es-rES/user/node-metrics.html | 2 +- main/es-rES/user/nodes.html | 2 +- main/es-rES/user/settings-radio-user.html | 2 +- main/es-rES/user/signal-meter.html | 2 +- main/et-rEE/user/node-metrics.html | 2 +- main/et-rEE/user/nodes.html | 2 +- main/et-rEE/user/settings-radio-user.html | 2 +- main/et-rEE/user/signal-meter.html | 2 +- main/fi-rFI/user/node-metrics.html | 2 +- main/fi-rFI/user/nodes.html | 2 +- main/fi-rFI/user/settings-radio-user.html | 2 +- main/fi-rFI/user/signal-meter.html | 2 +- main/fr-rCA/user/node-metrics.html | 2 +- main/fr-rCA/user/nodes.html | 2 + main/fr-rCA/user/settings-radio-user.html | 6 +- main/fr-rCA/user/signal-meter.html | 4 +- main/fr-rFR/user/node-metrics.html | 2 +- main/fr-rFR/user/nodes.html | 2 +- main/fr-rFR/user/settings-radio-user.html | 2 +- main/fr-rFR/user/signal-meter.html | 2 +- main/ga-rIE/user/node-metrics.html | 2 +- main/ga-rIE/user/nodes.html | 2 +- main/ga-rIE/user/settings-radio-user.html | 2 +- main/ga-rIE/user/signal-meter.html | 2 +- main/gl-rES/user/node-metrics.html | 2 +- main/gl-rES/user/nodes.html | 2 +- main/gl-rES/user/settings-radio-user.html | 2 +- main/gl-rES/user/signal-meter.html | 2 +- main/hr-rHR/user/node-metrics.html | 2 +- main/hr-rHR/user/nodes.html | 2 +- main/hr-rHR/user/settings-radio-user.html | 2 +- main/hr-rHR/user/signal-meter.html | 2 +- main/ht-rHT/user/node-metrics.html | 2 +- main/ht-rHT/user/nodes.html | 2 +- main/ht-rHT/user/settings-radio-user.html | 2 +- main/ht-rHT/user/signal-meter.html | 2 +- main/hu-rHU/user/node-metrics.html | 2 +- main/hu-rHU/user/nodes.html | 2 +- main/hu-rHU/user/settings-radio-user.html | 2 +- main/hu-rHU/user/signal-meter.html | 2 +- main/index.json | 238 ++++++------- main/is-rIS/user/node-metrics.html | 2 +- main/is-rIS/user/nodes.html | 2 +- main/is-rIS/user/settings-radio-user.html | 2 +- main/is-rIS/user/signal-meter.html | 2 +- main/it-rIT/user/node-metrics.html | 2 +- main/it-rIT/user/nodes.html | 2 +- main/it-rIT/user/settings-radio-user.html | 2 +- main/it-rIT/user/signal-meter.html | 2 +- main/iw-rIL/user/node-metrics.html | 2 +- main/iw-rIL/user/nodes.html | 2 +- main/iw-rIL/user/settings-radio-user.html | 2 +- main/iw-rIL/user/signal-meter.html | 2 +- main/ja-rJP/user/node-metrics.html | 2 +- main/ja-rJP/user/nodes.html | 2 +- main/ja-rJP/user/settings-radio-user.html | 2 +- main/ja-rJP/user/signal-meter.html | 2 +- main/ko-rKR/user/node-metrics.html | 2 +- main/ko-rKR/user/nodes.html | 2 +- main/ko-rKR/user/settings-radio-user.html | 2 +- main/ko-rKR/user/signal-meter.html | 2 +- main/lt-rLT/user/node-metrics.html | 2 +- main/lt-rLT/user/nodes.html | 2 +- main/lt-rLT/user/settings-radio-user.html | 2 +- main/lt-rLT/user/signal-meter.html | 2 +- main/nl-rNL/user/node-metrics.html | 2 +- main/nl-rNL/user/nodes.html | 2 +- main/nl-rNL/user/settings-radio-user.html | 2 +- main/nl-rNL/user/signal-meter.html | 2 +- main/no-rNO/user/node-metrics.html | 2 +- main/no-rNO/user/nodes.html | 2 +- main/no-rNO/user/settings-radio-user.html | 2 +- main/no-rNO/user/signal-meter.html | 2 +- main/pl-rPL/user/node-metrics.html | 2 +- main/pl-rPL/user/nodes.html | 2 +- main/pl-rPL/user/settings-radio-user.html | 2 +- main/pl-rPL/user/signal-meter.html | 2 +- main/pt-rBR/user/node-metrics.html | 2 +- main/pt-rBR/user/nodes.html | 2 +- main/pt-rBR/user/settings-radio-user.html | 2 +- main/pt-rBR/user/signal-meter.html | 2 +- main/pt-rPT/user/node-metrics.html | 2 +- main/pt-rPT/user/nodes.html | 2 +- main/pt-rPT/user/settings-radio-user.html | 2 +- main/pt-rPT/user/signal-meter.html | 2 +- main/ro-rRO/user/node-metrics.html | 2 +- main/ro-rRO/user/nodes.html | 2 +- main/ro-rRO/user/settings-radio-user.html | 2 +- main/ro-rRO/user/signal-meter.html | 2 +- main/ru-rRU/user/node-metrics.html | 2 +- main/ru-rRU/user/nodes.html | 2 +- main/ru-rRU/user/settings-radio-user.html | 2 +- main/ru-rRU/user/signal-meter.html | 2 +- main/sk-rSK/user/node-metrics.html | 2 +- main/sk-rSK/user/nodes.html | 2 +- main/sk-rSK/user/settings-radio-user.html | 2 +- main/sk-rSK/user/signal-meter.html | 2 +- main/sl-rSI/user/node-metrics.html | 2 +- main/sl-rSI/user/nodes.html | 2 +- main/sl-rSI/user/settings-radio-user.html | 2 +- main/sl-rSI/user/signal-meter.html | 2 +- main/sq-rAL/user/node-metrics.html | 2 +- main/sq-rAL/user/nodes.html | 2 +- main/sq-rAL/user/settings-radio-user.html | 2 +- main/sq-rAL/user/signal-meter.html | 2 +- main/sr-rLatn/user/node-metrics.html | 2 +- main/sr-rLatn/user/nodes.html | 2 +- main/sr-rLatn/user/settings-radio-user.html | 2 +- main/sr-rLatn/user/signal-meter.html | 2 +- main/srp/user/node-metrics.html | 2 +- main/srp/user/nodes.html | 2 +- main/srp/user/settings-radio-user.html | 2 +- main/srp/user/signal-meter.html | 2 +- main/sv-rSE/user/node-metrics.html | 2 +- main/sv-rSE/user/nodes.html | 2 +- main/sv-rSE/user/settings-radio-user.html | 2 +- main/sv-rSE/user/signal-meter.html | 2 +- main/tr-rTR/user/node-metrics.html | 2 +- main/tr-rTR/user/nodes.html | 2 +- main/tr-rTR/user/settings-radio-user.html | 2 +- main/tr-rTR/user/signal-meter.html | 2 +- main/uk-rUA/user/node-metrics.html | 2 +- main/uk-rUA/user/nodes.html | 2 +- main/uk-rUA/user/settings-radio-user.html | 2 +- main/uk-rUA/user/signal-meter.html | 2 +- main/zh-rCN/user/node-metrics.html | 2 +- main/zh-rCN/user/nodes.html | 2 +- main/zh-rCN/user/settings-radio-user.html | 2 +- main/zh-rCN/user/signal-meter.html | 2 +- main/zh-rTW/user/node-metrics.html | 2 +- main/zh-rTW/user/nodes.html | 2 +- main/zh-rTW/user/settings-radio-user.html | 2 +- main/zh-rTW/user/signal-meter.html | 4 +- 327 files changed, 770 insertions(+), 690 deletions(-) diff --git a/api/core/testing/org.meshtastic.core.testing/-robolectric-ble-bonding/index.html b/api/core/testing/org.meshtastic.core.testing/-robolectric-ble-bonding/index.html index 05a39fafc3..465f6f34cd 100644 --- a/api/core/testing/org.meshtastic.core.testing/-robolectric-ble-bonding/index.html +++ b/api/core/testing/org.meshtastic.core.testing/-robolectric-ble-bonding/index.html @@ -95,7 +95,7 @@

RobolectricBleBonding

-

Reusable Robolectric helpers for driving Android Bluetooth bonding logic in androidHostTest source sets.

These let a unit test exercise the real AndroidBluetoothRepository.bond() (and any future BLE bonding code) without an emulator and without a production seam. They rely on two Robolectric behaviors (verified against Robolectric 4.16.x):

Isolation note: because the device cache is static and survives across tests in the same JVM, give each test a distinct MAC so bond-state cannot bleed between tests.

+
object RobolectricBleBonding(source)

Reusable Robolectric helpers for driving Android Bluetooth bonding logic in androidHostTest source sets.

These let a unit test exercise the real AndroidBluetoothRepository.bond() (and any future BLE bonding code) without an emulator and without a production seam. They rely on two Robolectric behaviors (verified against Robolectric 4.16.x):

Isolation note: because the device cache is static and survives across tests in the same JVM, give each test a distinct MAC so bond-state cannot bleed between tests.

diff --git a/api/core/ui/org.meshtastic.core.ui.component/-meshtastic-dialog.html b/api/core/ui/org.meshtastic.core.ui.component/-meshtastic-dialog.html index 52f56bad50..bd2c3c40eb 100644 --- a/api/core/ui/org.meshtastic.core.ui.component/-meshtastic-dialog.html +++ b/api/core/ui/org.meshtastic.core.ui.component/-meshtastic-dialog.html @@ -94,7 +94,7 @@

MeshtasticDialog

-
fun MeshtasticDialog(modifier: Modifier = Modifier, title: String? = null, titleRes: StringResource? = null, message: String? = null, messageRes: StringResource? = null, messageColor: Color = Color.Unspecified, html: String? = null, icon: ImageVector? = null, text: @Composable () -> Unit? = null, confirmText: String? = null, confirmTextRes: StringResource? = null, onConfirm: () -> Unit? = null, dismissText: String? = null, dismissTextRes: StringResource? = null, onDismiss: () -> Unit? = null, choices: Map<String, () -> Unit> = emptyMap(), dismissable: Boolean = true)(source)

A comprehensive and flexible dialog component for the Meshtastic application.

Parameters

modifier

Modifier for the dialog.

title

The title text of the dialog.

titleRes

The title string resource of the dialog.

message

Optional plain text message.

messageRes

Optional string resource message.

messageColor

Optional color for the plain text message; Color.Unspecified uses the default text color.

html

Optional HTML formatted message.

icon

Optional leading icon.

text

Optional custom composable content for the body.

confirmText

Text for the confirmation button.

confirmTextRes

String resource for the confirmation button.

onConfirm

Callback for the confirmation button.

dismissText

Text for the dismiss button.

dismissTextRes

String resource for the dismiss button.

onDismiss

Callback for when the dialog is dismissed or the dismiss button is clicked.

choices

If provided, displays a list of buttons instead of the standard confirm/dismiss actions.

dismissable

Whether the dialog can be dismissed by clicking outside or pressing back.

+
fun MeshtasticDialog(modifier: Modifier = Modifier, title: String? = null, titleRes: StringResource? = null, message: String? = null, messageRes: StringResource? = null, messageColor: Color = Color.Unspecified, html: String? = null, icon: ImageVector? = null, text: @Composable () -> Unit? = null, confirmText: String? = null, confirmTextRes: StringResource? = null, onConfirm: () -> Unit? = null, dismissText: String? = null, dismissTextRes: StringResource? = null, onDismiss: () -> Unit? = null, choices: Map<String, () -> Unit> = emptyMap(), dismissable: Boolean = true)(source)

A comprehensive and flexible dialog component for the Meshtastic application.

Parameters

modifier

Modifier for the dialog.

title

The title text of the dialog.

titleRes

The title string resource of the dialog.

message

Optional plain text message.

messageRes

Optional string resource message.

messageColor

Optional color for the plain text message; Color.Unspecified uses the default text color.

html

Optional HTML formatted message.

icon

Optional leading icon.

text

Optional custom composable content for the body.

confirmText

Text for the confirmation button.

confirmTextRes

String resource for the confirmation button.

onConfirm

Callback for the confirmation button.

dismissText

Text for the dismiss button.

dismissTextRes

String resource for the dismiss button.

onDismiss

Callback for when the dialog is dismissed or the dismiss button is clicked.

choices

If provided, displays a list of buttons instead of the standard confirm/dismiss actions.

dismissable

Whether the dialog can be dismissed by clicking outside or pressing back.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Français
Meshtastic Docs ↗

🌐 Français — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Métriques de l’appareil

Basic operating information reported by each node:

Metric Description
Niveau de batterie Current battery percentage
Tension Battery voltage reading
UtilCanal Percentage of local airtime in use
UtilAir Percentage of the last hour this node spent transmitting
Durée de fonctionnement Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Métriques d’environnement

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Température BME280, BME680, SHT31
Humidité BME280, BME680, SHT31
Pression Barométrique BME280, BMP280
Résistance au gaz BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Description
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Bon < 1000 Vert
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Rouge
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Qualité du signal

Radio signal quality information:

Metric Description
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Bon SNR above the preset’s limit
Passable less than 5.5 dB below the limit
Mauvais 5.5 dB to 7.5 dB below the limit
Aucun more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Métriques d’alimentation

Power management telemetry (requires INA sensor or compatible hardware):

Metric Description
Tension Per-channel voltage reading
Actif Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Journal des positions

Historical position data for nodes that share their location:

  • Coordonnées GPS
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Informations sur les voisins

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Métriques de l’hôte

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

Métriques de PAX

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/fr-rFR/user/nodes.html b/main/fr-rFR/user/nodes.html index 3169cb96de..3c1a4b7fe6 100644 --- a/main/fr-rFR/user/nodes.html +++ b/main/fr-rFR/user/nodes.html @@ -1 +1 @@ - Nœuds | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Français
Meshtastic Docs ↗

🌐 Français — Community translation View in English

Nœuds

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Rôle Description
Client Standard end-user node
Base Client Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client muet Receives but doesn’t retransmit
Client masqué Like Client Mute, plus hides from node list
Routeur Prioritizes message forwarding; stays awake to relay
Routeur avec retard Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Traqueur Optimized for position reporting at regular intervals
Capteur Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
Traqueur TAK TAK position reporting only
Objets trouvés Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Supprimer

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtre Description
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Description
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Niveau de batterie Battery
Hop count Hops
Dernière écoute Last heard
Distance Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nœuds | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Français
Meshtastic Docs ↗

🌐 Français — Community translation View in English

Nœuds

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Rôle Description
Client Standard end-user node
Base Client Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client muet Receives but doesn’t retransmit
Client masqué Like Client Mute, plus hides from node list
Routeur Prioritizes message forwarding; stays awake to relay
Routeur avec retard Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Traqueur Optimized for position reporting at regular intervals
Capteur Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
Traqueur TAK TAK position reporting only
Objets trouvés Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Supprimer

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtre Description
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Description
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Niveau de batterie Battery
Hop count Hops
Dernière écoute Last heard
Distance Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/fr-rFR/user/settings-radio-user.html b/main/fr-rFR/user/settings-radio-user.html index 24ffce7cac..5a3c979fdc 100644 --- a/main/fr-rFR/user/settings-radio-user.html +++ b/main/fr-rFR/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Français
Meshtastic Docs ↗

🌐 Français — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Paramètres utilisateur

User Profile

On Settings → User.

Setting Description
Nom long Your display name (up to 39 characters)
Nom court 4-character abbreviated name
Statut du message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Non joignable par message Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Radioamateur licencié (RA) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Configuration de l’appareil

On Settings → Device configuration → Device.

Setting Description Par défaut
Rôle de l’appareil Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Mode de réémission How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Intervalle de diffusion des infos nœud How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double clic comme appui sur le bouton Treat a double tap as a button press Désactivé
Triple clic pour faire un ping Ad Hoc Send an ad-hoc position ping on a triple click Désactivé
LED de vérification de fonctionnement (heartbeat) Blink the status LED periodically Activé
Fuseau horaire POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

Configuration LoRa

On Settings → LoRa.

Setting Description Par défaut
Région Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Préréglages Speed/range tradeoff LongFast
Nombre de sauts Maximum retransmit hops 3
Puissance d’émission Transmission power (dBm); 0 = max allowed for region 0 (region max)
Remplacer la fréquence Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Utiliser un préréglage On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Facteur de propagation Manual mode only: 7–12. Higher spreads further but slower From preset
Taux de codage Manual mode only: 5–8. More redundancy costs airtime From preset
Bande Passante Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Slot de fréquence Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmission activée Turning this off makes the node receive-only On
Autoriser le dépassement du temps d’émission autorisé par heure Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Éteint
Ignorer MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Transmission des paquets vers MQTT Allow your packets to be forwarded to MQTT by gateways Éteint
Gain RX Boosté Extra receive gain on SX126x radios; costs a little current Éteint
Ventilateur PA désactivé Turn off the power-amplifier fan on hardware that has one Éteint

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Vitesse SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configuration de l’écran

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Description
Écran allumé pour How long the display stays lit before sleeping
Intervalle du carrousel How often the radio cycles between screens on its own
Mode d’affichage Screen layout/density used by the firmware
Unités d’affichage Metric or Imperial on the radio’s screen
Utiliser le format horaire 12h Show the radio’s clock as 12-hour rather than 24-hour
Titre en gras Draw the screen’s heading text in bold
Inverser l’écran Rotate the display 180° for an inverted mounting
Type d’OLED Auto, SSD1306, SH1106, SH1107
Réveil par appui ou mouvement Light the screen when the radio is tapped or moved
Orientation de la boussole Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Toujours pointer vers le nord Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configuration de la position

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Description
Mode GPS (matériel physique) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Fréquence de récupération GPS How often the radio asks its GPS for a fix
Intervalle de diffusion How often the position is shared with the mesh
Position Intelligente Broadcast based on movement rather than purely on the clock
Intervalle intelligent With Smart Position on, the shortest gap between broadcasts
Distance intelligente With Smart Position on, how far you must move before broadcasting
Position fixe Use a manually entered latitude, longitude and altitude instead of the GPS
Champs de position A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configuration de l’alimentation

On Settings → Device configuration → Power.

Setting Description
Activer le mode économie d’énergie Let the radio sleep aggressively between activity
Arrêt en cas de perte d’alimentation Power the device down after external power disappears
Durée du sommeil extra profond How long the deepest sleep state lasts
Durée minimale de réveil The shortest time the radio stays awake once woken
Durée d’attente max du Bluetooth How long to wait for a phone to connect before sleeping
Remplacer le multiplicateur ADC Turn on a manual correction for battery-voltage readings
Facteur de remplacement du multiplicateur ADC The correction factor itself, used only when the override is on
Adresse I2C de la batterie INA_2XX Address of an external INA-series power sensor, if fitted

Configuration du réseau

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Description
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Mot de passe Mot de passe du réseau
Ethernet activé Use a wired connection on hardware that has one
Mode IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Serveur NTP Time synchronization server
Serveur Rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configuration Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Description
Bluetooth activé Enable/disable BLE radio
Mode d’appariement Fixed PIN, Random PIN, or No PIN
Code PIN fixe PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configuration de sécurité

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Description
Clé publique Your node’s public key (read-only)
Clé Admin Keys permitted to administer this node remotely — up to three
Clé privée Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Régénérer la clé privée Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Console série Serial console over the Stream API
API de journalisation de débogage activée Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Mode géré Restrict non-admin channel changes. Only selectable once an Admin Key is set
Sauvegarder les clés Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Heures jusqu’à expiration Wall-clock lifetime of the unlocked state
Limite de sessions (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Français
Meshtastic Docs ↗

🌐 Français — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Paramètres utilisateur

User Profile

On Settings → User.

Setting Description
Nom long Your display name (up to 39 characters)
Nom court 4-character abbreviated name
Statut du message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Non joignable par message Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Radioamateur licencié (RA) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Configuration de l’appareil

On Settings → Device configuration → Device.

Setting Description Par défaut
Rôle de l’appareil Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Mode de réémission How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Intervalle de diffusion des infos nœud How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double clic comme appui sur le bouton Treat a double tap as a button press Désactivé
Triple clic pour faire un ping Ad Hoc Send an ad-hoc position ping on a triple click Désactivé
LED de vérification de fonctionnement (heartbeat) Blink the status LED periodically Activé
Fuseau horaire POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

Configuration LoRa

On Settings → LoRa.

Setting Description Par défaut
Région Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Préréglages Speed/range tradeoff LongFast
Nombre de sauts Maximum retransmit hops 3
Puissance d’émission Transmission power (dBm); 0 = max allowed for region 0 (region max)
Remplacer la fréquence Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Utiliser un préréglage On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Facteur de propagation Manual mode only: 7–12. Higher spreads further but slower From preset
Taux de codage Manual mode only: 5–8. More redundancy costs airtime From preset
Bande Passante Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Slot de fréquence Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmission activée Turning this off makes the node receive-only On
Autoriser le dépassement du temps d’émission autorisé par heure Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Éteint
Ignorer MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Transmission des paquets vers MQTT Allow your packets to be forwarded to MQTT by gateways Éteint
Gain RX Boosté Extra receive gain on SX126x radios; costs a little current Éteint
Ventilateur PA désactivé Turn off the power-amplifier fan on hardware that has one Éteint

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Vitesse SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configuration de l’écran

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Description
Écran allumé pour How long the display stays lit before sleeping
Intervalle du carrousel How often the radio cycles between screens on its own
Mode d’affichage Screen layout/density used by the firmware
Unités d’affichage Metric or Imperial on the radio’s screen
Utiliser le format horaire 12h Show the radio’s clock as 12-hour rather than 24-hour
Titre en gras Draw the screen’s heading text in bold
Inverser l’écran Rotate the display 180° for an inverted mounting
Type d’OLED Auto, SSD1306, SH1106, SH1107
Réveil par appui ou mouvement Light the screen when the radio is tapped or moved
Orientation de la boussole Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Toujours pointer vers le nord Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configuration de la position

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Description
Mode GPS (matériel physique) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Fréquence de récupération GPS How often the radio asks its GPS for a fix
Intervalle de diffusion How often the position is shared with the mesh
Position Intelligente Broadcast based on movement rather than purely on the clock
Intervalle intelligent With Smart Position on, the shortest gap between broadcasts
Distance intelligente With Smart Position on, how far you must move before broadcasting
Position fixe Use a manually entered latitude, longitude and altitude instead of the GPS
Champs de position A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configuration de l’alimentation

On Settings → Device configuration → Power.

Setting Description
Activer le mode économie d’énergie Let the radio sleep aggressively between activity
Arrêt en cas de perte d’alimentation Power the device down after external power disappears
Durée du sommeil extra profond How long the deepest sleep state lasts
Durée minimale de réveil The shortest time the radio stays awake once woken
Durée d’attente max du Bluetooth How long to wait for a phone to connect before sleeping
Remplacer le multiplicateur ADC Turn on a manual correction for battery-voltage readings
Facteur de remplacement du multiplicateur ADC The correction factor itself, used only when the override is on
Adresse I2C de la batterie INA_2XX Address of an external INA-series power sensor, if fitted

Configuration du réseau

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Description
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Mot de passe Mot de passe du réseau
Ethernet activé Use a wired connection on hardware that has one
Mode IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Serveur NTP Time synchronization server
Serveur Rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configuration Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Description
Bluetooth activé Enable/disable BLE radio
Mode d’appariement Fixed PIN, Random PIN, or No PIN
Code PIN fixe PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configuration de sécurité

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Description
Clé publique Your node’s public key (read-only)
Clé Admin Keys permitted to administer this node remotely — up to three
Clé privée Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Régénérer la clé privée Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Console série Serial console over the Stream API
API de journalisation de débogage activée Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Mode géré Restrict non-admin channel changes. Only selectable once an Admin Key is set
Sauvegarder les clés Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Heures jusqu’à expiration Wall-clock lifetime of the unlocked state
Limite de sessions (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/fr-rFR/user/signal-meter.html b/main/fr-rFR/user/signal-meter.html index 3012fbe750..fe85a76e8b 100644 --- a/main/fr-rFR/user/signal-meter.html +++ b/main/fr-rFR/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Français
Meshtastic Docs ↗

🌐 Français — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Bon Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Passable 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Mauvais 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Aucun 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Français
Meshtastic Docs ↗

🌐 Français — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Bon Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Passable 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Mauvais 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Aucun 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/ga-rIE/user/node-metrics.html b/main/ga-rIE/user/node-metrics.html index 34c1bd6703..6a5cce753a 100644 --- a/main/ga-rIE/user/node-metrics.html +++ b/main/ga-rIE/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Gaeilge
Meshtastic Docs ↗

🌐 Gaeilge — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Cur síos
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Teocht BME280, BME680, SHT31
Laige BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Cur síos
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Maith < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Cáilíocht na Sígneal

Radio signal quality information:

Metric Cur síos
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Maith SNR above the preset’s limit
Ceart go leor less than 5.5 dB below the limit
Go dona 5.5 dB to 7.5 dB below the limit
Ní dhéanfaidh sé more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Cur síos
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Céim rianadóireachta

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Lógáil Seirbhís

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Gaeilge
Meshtastic Docs ↗

🌐 Gaeilge — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Cur síos
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Teocht BME280, BME680, SHT31
Laige BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Cur síos
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Maith < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Cáilíocht na Sígneal

Radio signal quality information:

Metric Cur síos
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Maith SNR above the preset’s limit
Ceart go leor less than 5.5 dB below the limit
Go dona 5.5 dB to 7.5 dB below the limit
Ní dhéanfaidh sé more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Cur síos
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Céim rianadóireachta

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Lógáil Seirbhís

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/ga-rIE/user/nodes.html b/main/ga-rIE/user/nodes.html index 989031881f..ced61c9006 100644 --- a/main/ga-rIE/user/nodes.html +++ b/main/ga-rIE/user/nodes.html @@ -1 +1 @@ - Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Gaeilge
Meshtastic Docs ↗

🌐 Gaeilge — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Cur síos
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Bain

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Scagaire Cur síos
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Cur síos
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Deiridh chluinmhu Last heard
Sáth Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Gaeilge
Meshtastic Docs ↗

🌐 Gaeilge — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Cur síos
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Bain

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Scagaire Cur síos
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Cur síos
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Deiridh chluinmhu Last heard
Sáth Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/ga-rIE/user/settings-radio-user.html b/main/ga-rIE/user/settings-radio-user.html index 3851b60954..3403c72c62 100644 --- a/main/ga-rIE/user/settings-radio-user.html +++ b/main/ga-rIE/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Gaeilge
Meshtastic Docs ↗

🌐 Gaeilge — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Cur síos
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Cur síos Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Cur síos Default
Réigiún Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Cur síos
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Cur síos
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Cur síos
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Cur síos
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Cur síos
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Cur síos
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Gaeilge
Meshtastic Docs ↗

🌐 Gaeilge — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Cur síos
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Cur síos Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Cur síos Default
Réigiún Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Cur síos
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Cur síos
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Cur síos
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Cur síos
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Cur síos
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Cur síos
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/ga-rIE/user/signal-meter.html b/main/ga-rIE/user/signal-meter.html index 6dccb190ad..d1c8da806e 100644 --- a/main/ga-rIE/user/signal-meter.html +++ b/main/ga-rIE/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Gaeilge
Meshtastic Docs ↗

🌐 Gaeilge — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Maith Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Ceart go leor 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Go dona 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Ní dhéanfaidh sé 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Gaeilge
Meshtastic Docs ↗

🌐 Gaeilge — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Maith Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Ceart go leor 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Go dona 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Ní dhéanfaidh sé 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/gl-rES/user/node-metrics.html b/main/gl-rES/user/node-metrics.html index c4f4946cf4..44db9bbfdd 100644 --- a/main/gl-rES/user/node-metrics.html +++ b/main/gl-rES/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Galego
Meshtastic Docs ↗

🌐 Galego — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Descrición
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperature BME280, BME680, SHT31
Humidity BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Descrición
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Good < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Signal Quality

Radio signal quality information:

Metric Descrición
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Good SNR above the preset’s limit
Fair less than 5.5 dB below the limit
Bad 5.5 dB to 7.5 dB below the limit
None more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Descrición
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traza-ruta

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Position Log

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Galego
Meshtastic Docs ↗

🌐 Galego — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Descrición
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperature BME280, BME680, SHT31
Humidity BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Descrición
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Good < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Signal Quality

Radio signal quality information:

Metric Descrición
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Good SNR above the preset’s limit
Fair less than 5.5 dB below the limit
Bad 5.5 dB to 7.5 dB below the limit
None more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Descrición
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traza-ruta

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Position Log

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/gl-rES/user/nodes.html b/main/gl-rES/user/nodes.html index 5b7df9a338..ce3974f220 100644 --- a/main/gl-rES/user/nodes.html +++ b/main/gl-rES/user/nodes.html @@ -1 +1 @@ - Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Galego
Meshtastic Docs ↗

🌐 Galego — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Descrición
Cliente Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Eliminar

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtro Descrición
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Descrición
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Última escoita Last heard
Distancia Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Galego
Meshtastic Docs ↗

🌐 Galego — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Descrición
Cliente Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Eliminar

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtro Descrición
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Descrición
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Última escoita Last heard
Distancia Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/gl-rES/user/settings-radio-user.html b/main/gl-rES/user/settings-radio-user.html index cc2b694acc..42c8fcb92b 100644 --- a/main/gl-rES/user/settings-radio-user.html +++ b/main/gl-rES/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Galego
Meshtastic Docs ↗

🌐 Galego — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descrición
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Descrición Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Descrición Default
Rexión Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Descrición
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrición
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Descrición
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Descrición
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrición
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrición
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Galego
Meshtastic Docs ↗

🌐 Galego — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descrición
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Descrición Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Descrición Default
Rexión Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Descrición
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrición
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Descrición
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Descrición
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrición
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrición
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/gl-rES/user/signal-meter.html b/main/gl-rES/user/signal-meter.html index 6d2e6af596..90bd3fab7b 100644 --- a/main/gl-rES/user/signal-meter.html +++ b/main/gl-rES/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Galego
Meshtastic Docs ↗

🌐 Galego — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Good Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Fair 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Bad 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
None 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Galego
Meshtastic Docs ↗

🌐 Galego — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Good Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Fair 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Bad 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
None 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/hr-rHR/user/node-metrics.html b/main/hr-rHR/user/node-metrics.html index 2d3746a791..d8be56ac6a 100644 --- a/main/hr-rHR/user/node-metrics.html +++ b/main/hr-rHR/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Hrvatski
Meshtastic Docs ↗

🌐 Hrvatski — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Opis
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperature BME280, BME680, SHT31
Humidity BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Opis
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Good < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Crveno
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Signal Quality

Radio signal quality information:

Metric Opis
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Good SNR above the preset’s limit
Fair less than 5.5 dB below the limit
Bad 5.5 dB to 7.5 dB below the limit
None more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Opis
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Position Log

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Hrvatski
Meshtastic Docs ↗

🌐 Hrvatski — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Opis
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperature BME280, BME680, SHT31
Humidity BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Opis
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Good < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Crveno
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Signal Quality

Radio signal quality information:

Metric Opis
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Good SNR above the preset’s limit
Fair less than 5.5 dB below the limit
Bad 5.5 dB to 7.5 dB below the limit
None more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Opis
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Position Log

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/hr-rHR/user/nodes.html b/main/hr-rHR/user/nodes.html index 2dcf4917d7..3384685cde 100644 --- a/main/hr-rHR/user/nodes.html +++ b/main/hr-rHR/user/nodes.html @@ -1 +1 @@ - Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Hrvatski
Meshtastic Docs ↗

🌐 Hrvatski — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Opis
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Ukloni

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtriraj Opis
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Opis
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Posljednje čuo Last heard
Udaljenost Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Hrvatski
Meshtastic Docs ↗

🌐 Hrvatski — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Opis
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Ukloni

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtriraj Opis
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Opis
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Posljednje čuo Last heard
Udaljenost Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/hr-rHR/user/settings-radio-user.html b/main/hr-rHR/user/settings-radio-user.html index 6e7ecedc59..5185df1dc7 100644 --- a/main/hr-rHR/user/settings-radio-user.html +++ b/main/hr-rHR/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Hrvatski
Meshtastic Docs ↗

🌐 Hrvatski — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Opis
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Opis Zadano
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Opis Zadano
Regija Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Opis
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Opis
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Opis
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Postavke Bluetootha

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Hrvatski
Meshtastic Docs ↗

🌐 Hrvatski — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Opis
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Opis Zadano
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Opis Zadano
Regija Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Opis
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Opis
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Opis
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Postavke Bluetootha

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/hr-rHR/user/signal-meter.html b/main/hr-rHR/user/signal-meter.html index 390120b6f9..6b801ed9af 100644 --- a/main/hr-rHR/user/signal-meter.html +++ b/main/hr-rHR/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Hrvatski
Meshtastic Docs ↗

🌐 Hrvatski — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Good Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Fair 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Bad 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
None 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Hrvatski
Meshtastic Docs ↗

🌐 Hrvatski — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Good Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Fair 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Bad 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
None 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/ht-rHT/user/node-metrics.html b/main/ht-rHT/user/node-metrics.html index 01b7b2cf47..b403016208 100644 --- a/main/ht-rHT/user/node-metrics.html +++ b/main/ht-rHT/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Kreyòl Ayisyen
Meshtastic Docs ↗

🌐 Kreyòl Ayisyen — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Deskripsyon
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Tanperati BME280, BME680, SHT31
Imidite BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Deskripsyon
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Bon < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Kalite Siynal

Radio signal quality information:

Metric Deskripsyon
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Bon SNR above the preset’s limit
Mwayen less than 5.5 dB below the limit
Move 5.5 dB to 7.5 dB below the limit
Pa gen more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Deskripsyon
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Jounal Pozisyon

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Kreyòl Ayisyen
Meshtastic Docs ↗

🌐 Kreyòl Ayisyen — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Deskripsyon
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Tanperati BME280, BME680, SHT31
Imidite BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Deskripsyon
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Bon < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Kalite Siynal

Radio signal quality information:

Metric Deskripsyon
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Bon SNR above the preset’s limit
Mwayen less than 5.5 dB below the limit
Move 5.5 dB to 7.5 dB below the limit
Pa gen more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Deskripsyon
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Jounal Pozisyon

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/ht-rHT/user/nodes.html b/main/ht-rHT/user/nodes.html index eb626a5c3a..25b561a093 100644 --- a/main/ht-rHT/user/nodes.html +++ b/main/ht-rHT/user/nodes.html @@ -1 +1 @@ - Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Kreyòl Ayisyen
Meshtastic Docs ↗

🌐 Kreyòl Ayisyen — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Deskripsyon
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Retire

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtre Deskripsyon
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Deskripsyon
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Dènye fwa li tande Last heard
Distans Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Kreyòl Ayisyen
Meshtastic Docs ↗

🌐 Kreyòl Ayisyen — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Deskripsyon
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Retire

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtre Deskripsyon
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Deskripsyon
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Dènye fwa li tande Last heard
Distans Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/ht-rHT/user/settings-radio-user.html b/main/ht-rHT/user/settings-radio-user.html index 6337bb346d..e51b69cd75 100644 --- a/main/ht-rHT/user/settings-radio-user.html +++ b/main/ht-rHT/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Kreyòl Ayisyen
Meshtastic Docs ↗

🌐 Kreyòl Ayisyen — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Deskripsyon
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Deskripsyon Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Deskripsyon Default
Rejyon Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Deskripsyon
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Deskripsyon
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Deskripsyon
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Deskripsyon
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Deskripsyon
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Deskripsyon
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Kreyòl Ayisyen
Meshtastic Docs ↗

🌐 Kreyòl Ayisyen — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Deskripsyon
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Deskripsyon Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Deskripsyon Default
Rejyon Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Deskripsyon
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Deskripsyon
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Deskripsyon
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Deskripsyon
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Deskripsyon
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Deskripsyon
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/ht-rHT/user/signal-meter.html b/main/ht-rHT/user/signal-meter.html index 12749d9df9..2023439755 100644 --- a/main/ht-rHT/user/signal-meter.html +++ b/main/ht-rHT/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Kreyòl Ayisyen
Meshtastic Docs ↗

🌐 Kreyòl Ayisyen — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Bon Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Mwayen 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Move 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Pa gen 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Kreyòl Ayisyen
Meshtastic Docs ↗

🌐 Kreyòl Ayisyen — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Bon Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Mwayen 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Move 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Pa gen 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/hu-rHU/user/node-metrics.html b/main/hu-rHU/user/node-metrics.html index 0e979c437f..bba5b9bb9f 100644 --- a/main/hu-rHU/user/node-metrics.html +++ b/main/hu-rHU/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Magyar
Meshtastic Docs ↗

🌐 Magyar — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Eszközmetrikák

Basic operating information reported by each node:

Metric Leírás
Battery Level Current battery percentage
Feszültség Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Működési idő Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Környezeti metrikák

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Hőmérséklet BME280, BME680, SHT31
Páratartalom BME280, BME680, SHT31
Légnyomás BME280, BMP280
Gázellenállás BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Leírás
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
< 1000 Zöld
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Piros
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Jelminőség

Radio signal quality information:

Metric Leírás
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
SNR above the preset’s limit
Megfelelő less than 5.5 dB below the limit
Rossz 5.5 dB to 7.5 dB below the limit
Semmi more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Tápellátási metrikák

Power management telemetry (requires INA sensor or compatible hardware):

Metric Leírás
Feszültség Per-channel voltage reading
Áramerősség Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Pozíciónapló

Historical position data for nodes that share their location:

  • GPS coordinates
  • Magasság
  • Speed (if moving)
  • Timestamp for each position report

Szomszéd-információ

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Magyar
Meshtastic Docs ↗

🌐 Magyar — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Eszközmetrikák

Basic operating information reported by each node:

Metric Leírás
Battery Level Current battery percentage
Feszültség Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Működési idő Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Környezeti metrikák

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Hőmérséklet BME280, BME680, SHT31
Páratartalom BME280, BME680, SHT31
Légnyomás BME280, BMP280
Gázellenállás BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Leírás
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
< 1000 Zöld
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Piros
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Jelminőség

Radio signal quality information:

Metric Leírás
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
SNR above the preset’s limit
Megfelelő less than 5.5 dB below the limit
Rossz 5.5 dB to 7.5 dB below the limit
Semmi more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Tápellátási metrikák

Power management telemetry (requires INA sensor or compatible hardware):

Metric Leírás
Feszültség Per-channel voltage reading
Áramerősség Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Pozíciónapló

Historical position data for nodes that share their location:

  • GPS coordinates
  • Magasság
  • Speed (if moving)
  • Timestamp for each position report

Szomszéd-információ

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/hu-rHU/user/nodes.html b/main/hu-rHU/user/nodes.html index c3c42b6f75..b971885593 100644 --- a/main/hu-rHU/user/nodes.html +++ b/main/hu-rHU/user/nodes.html @@ -1 +1 @@ - Csomópontok | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Magyar
Meshtastic Docs ↗

🌐 Magyar — Community translation View in English

Csomópontok

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Szerepkör Leírás
Kliens Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Néma Kliens Receives but doesn’t retransmit
Rejtett Kliens Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Késő Router Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Szenzor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Elveszett és Megkerült Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Törlés

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filter Leírás
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Leírás
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Utoljára hallott Last heard
Távolság Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Csomópontok | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Magyar
Meshtastic Docs ↗

🌐 Magyar — Community translation View in English

Csomópontok

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Szerepkör Leírás
Kliens Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Néma Kliens Receives but doesn’t retransmit
Rejtett Kliens Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Késő Router Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Szenzor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Elveszett és Megkerült Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Törlés

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filter Leírás
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Leírás
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Utoljára hallott Last heard
Távolság Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/hu-rHU/user/settings-radio-user.html b/main/hu-rHU/user/settings-radio-user.html index 84e4a4773b..4289eca5f2 100644 --- a/main/hu-rHU/user/settings-radio-user.html +++ b/main/hu-rHU/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Magyar
Meshtastic Docs ↗

🌐 Magyar — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Leírás
Hosszú név Your display name (up to 39 characters)
Rövid név 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Nem üzenetképes Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Eszközbeállítások

On Settings → Device configuration → Device.

Setting Leírás Alapértelmezett
Eszköz szerepköre Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Újrasugárzási mód How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Csomópont-információ sugárzási időköze How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Dupla koppintás mint gomb Treat a double tap as a button press Disabled
Háromszori kattintás – ad hoc ping Send an ad-hoc position ping on a triple click Disabled
LED ütemjelzés Blink the status LED periodically Engedélyezve
Időzóna POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa beállítások

On Settings → LoRa.

Setting Leírás Alapértelmezett
Régió Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Előbeállítások Speed/range tradeoff LongFast
Ugrások száma Maximum retransmit hops 3
Adásteljesítmény Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frekvencia felülbírálása Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Előbeállítás használata On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Szórási Faktor Manual mode only: 7–12. Higher spreads further but slower From preset
Kódolási ráta Manual mode only: 5–8. More redundancy costs airtime From preset
Sávszélesség Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frekvencia sáv Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Adás engedélyezve Turning this off makes the node receive-only On
Duty Cycle felülbírálása Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
MQTT figyelmen kívül hagyása Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
MQTT-re továbbítható Allow your packets to be forwarded to MQTT by gateways Off
RX fokozott erősítés Extra receive gain on SX126x radios; costs a little current Off
PA ventilátor letiltva Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Sebesség SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Kijelző beállítások

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Leírás
Kijelző bekapcsolva ennyi ideig How long the display stays lit before sleeping
Karusszel időköz How often the radio cycles between screens on its own
Kijelző mód Screen layout/density used by the firmware
Mértékegységek megjelenítése Metric or Imperial on the radio’s screen
12 órás időformátum használata Show the radio’s clock as 12-hour rather than 24-hour
Félkövér címsor Draw the screen’s heading text in bold
Kijelző megfordítása Rotate the display 180° for an inverted mounting
OLED típus Auto, SSD1306, SH1106, SH1107
Érintésre vagy mozgásra ébresztés Light the screen when the radio is tapped or moved
Iránytű tájolás Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Mindig észak felé mutasson Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Pozíció beállítások

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Leírás
GPS mód (fizikai hardver) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Sugárzási időköz How often the position is shared with the mesh
Intelligens pozíció Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Rögzített pozíció Use a manually entered latitude, longitude and altitude instead of the GPS
Pozíció jelzők (flags) A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Energia-beállítások

On Settings → Device configuration → Power.

Setting Leírás
Energiatakarékos mód engedélyezése Let the radio sleep aggressively between activity
Leállítás áramszünet esetén Power the device down after external power disappears
Szuper mélyalvás időtartama How long the deepest sleep state lasts
Minimális ébrenléti idő The shortest time the radio stays awake once woken
Bluetooth-várakozás időtartama How long to wait for a phone to connect before sleeping
ADC szorzó felülbírálása Turn on a manual correction for battery-voltage readings
ADC szorzó felülbírálási arány The correction factor itself, used only when the override is on
Akkumulátor INA_2XX I2C-cím Address of an external INA-series power sensor, if fitted

Hálózati beállítások

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Leírás
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Jelszó Network password
Ethernet engedélyezve Use a wired connection on hardware that has one
IPv4 mód DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP szerver Time synchronization server
rsyslog szerver Remote logging server

Network Config with a static IPv4 address entered

Bluetooth beállítások

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Leírás
Bluetooth engedélyezve Enable/disable BLE radio
Párosítási mód Fixed PIN, Random PIN, or No PIN
Rögzített PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Biztonsági beállítások

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Leírás
Nyilvános kulcs Your node’s public key (read-only)
Admin kulcs Keys permitted to administer this node remotely — up to three
Privát kulcs Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Privát kulcs újragenerálása Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Soros konzol Serial console over the Stream API
Hibakeresési napló API engedélyezve Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Felügyelt mód Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Magyar
Meshtastic Docs ↗

🌐 Magyar — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Leírás
Hosszú név Your display name (up to 39 characters)
Rövid név 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Nem üzenetképes Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Eszközbeállítások

On Settings → Device configuration → Device.

Setting Leírás Alapértelmezett
Eszköz szerepköre Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Újrasugárzási mód How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Csomópont-információ sugárzási időköze How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Dupla koppintás mint gomb Treat a double tap as a button press Disabled
Háromszori kattintás – ad hoc ping Send an ad-hoc position ping on a triple click Disabled
LED ütemjelzés Blink the status LED periodically Engedélyezve
Időzóna POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa beállítások

On Settings → LoRa.

Setting Leírás Alapértelmezett
Régió Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Előbeállítások Speed/range tradeoff LongFast
Ugrások száma Maximum retransmit hops 3
Adásteljesítmény Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frekvencia felülbírálása Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Előbeállítás használata On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Szórási Faktor Manual mode only: 7–12. Higher spreads further but slower From preset
Kódolási ráta Manual mode only: 5–8. More redundancy costs airtime From preset
Sávszélesség Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frekvencia sáv Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Adás engedélyezve Turning this off makes the node receive-only On
Duty Cycle felülbírálása Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
MQTT figyelmen kívül hagyása Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
MQTT-re továbbítható Allow your packets to be forwarded to MQTT by gateways Off
RX fokozott erősítés Extra receive gain on SX126x radios; costs a little current Off
PA ventilátor letiltva Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Sebesség SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Kijelző beállítások

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Leírás
Kijelző bekapcsolva ennyi ideig How long the display stays lit before sleeping
Karusszel időköz How often the radio cycles between screens on its own
Kijelző mód Screen layout/density used by the firmware
Mértékegységek megjelenítése Metric or Imperial on the radio’s screen
12 órás időformátum használata Show the radio’s clock as 12-hour rather than 24-hour
Félkövér címsor Draw the screen’s heading text in bold
Kijelző megfordítása Rotate the display 180° for an inverted mounting
OLED típus Auto, SSD1306, SH1106, SH1107
Érintésre vagy mozgásra ébresztés Light the screen when the radio is tapped or moved
Iránytű tájolás Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Mindig észak felé mutasson Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Pozíció beállítások

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Leírás
GPS mód (fizikai hardver) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Sugárzási időköz How often the position is shared with the mesh
Intelligens pozíció Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Rögzített pozíció Use a manually entered latitude, longitude and altitude instead of the GPS
Pozíció jelzők (flags) A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Energia-beállítások

On Settings → Device configuration → Power.

Setting Leírás
Energiatakarékos mód engedélyezése Let the radio sleep aggressively between activity
Leállítás áramszünet esetén Power the device down after external power disappears
Szuper mélyalvás időtartama How long the deepest sleep state lasts
Minimális ébrenléti idő The shortest time the radio stays awake once woken
Bluetooth-várakozás időtartama How long to wait for a phone to connect before sleeping
ADC szorzó felülbírálása Turn on a manual correction for battery-voltage readings
ADC szorzó felülbírálási arány The correction factor itself, used only when the override is on
Akkumulátor INA_2XX I2C-cím Address of an external INA-series power sensor, if fitted

Hálózati beállítások

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Leírás
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Jelszó Network password
Ethernet engedélyezve Use a wired connection on hardware that has one
IPv4 mód DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP szerver Time synchronization server
rsyslog szerver Remote logging server

Network Config with a static IPv4 address entered

Bluetooth beállítások

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Leírás
Bluetooth engedélyezve Enable/disable BLE radio
Párosítási mód Fixed PIN, Random PIN, or No PIN
Rögzített PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Biztonsági beállítások

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Leírás
Nyilvános kulcs Your node’s public key (read-only)
Admin kulcs Keys permitted to administer this node remotely — up to three
Privát kulcs Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Privát kulcs újragenerálása Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Soros konzol Serial console over the Stream API
Hibakeresési napló API engedélyezve Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Felügyelt mód Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/hu-rHU/user/signal-meter.html b/main/hu-rHU/user/signal-meter.html index 36c9c1d0c9..eda3c4395d 100644 --- a/main/hu-rHU/user/signal-meter.html +++ b/main/hu-rHU/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Magyar
Meshtastic Docs ↗

🌐 Magyar — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Megfelelő 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Rossz 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Semmi 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Magyar
Meshtastic Docs ↗

🌐 Magyar — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Megfelelő 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Rossz 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Semmi 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/index.json b/main/index.json index a504077933..4bfb8277b8 100644 --- a/main/index.json +++ b/main/index.json @@ -41,12 +41,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22696}, {"id":"mqtt","title":"MQTT","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "traceroute", "reading", "results", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12460}, - {"id":"nodes","title":"Nodes","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15388}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "traceroute", "reading", "results", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12592}, + {"id":"nodes","title":"Nodes","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15695}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32238}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["الإعدادات", "radio-config", "user-config", "lora"],"charCount":41242}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5196}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5245}, {"id":"tak","title":"TAK Integration","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10567}, {"id":"translate","title":"Translate the App","section":"user","locale":"ar-rSA","resourcePath":"docs/ar-rSA/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -62,12 +62,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22695}, {"id":"mqtt","title":"MQTT","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/mqtt.html","navOrder":11,"keywords":["mqtt", "how", "works", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting", "messages", "bridging"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12368}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "traceroute", "reading", "results", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12471}, - {"id":"nodes","title":"Nodes","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15411}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "traceroute", "reading", "results", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12603}, + {"id":"nodes","title":"Nodes","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15718}, {"id":"onboarding","title":"Начало работы","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/onboarding.html","navOrder":1,"keywords":["first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8457}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32250}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41240}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5190}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5239}, {"id":"tak","title":"TAK Integration","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/tak.html","navOrder":10,"keywords":["tak", "integration", "setup", "prerequisites", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10681}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10618}, {"id":"translate","title":"Translate the App","section":"user","locale":"be-rBY","resourcePath":"docs/be-rBY/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -83,14 +83,14 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13895}, {"id":"messages-and-channels","title":"Съобщения & Канали","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/messages-and-channels.html","navOrder":3,"keywords":["default", "channel", "adding", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "messages", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest", "actions", "priority"],"aliases":["канали", "direct-messages", "messaging", "conversations"],"charCount":22887}, {"id":"mqtt","title":"MQTT","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/mqtt.html","navOrder":11,"keywords":["mqtt", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "not", "connecting", "messages", "bridging"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12421}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "air", "quality", "signal", "reference", "reading", "traceroute", "results", "neighbor", "info", "host", "pax"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12638}, - {"id":"nodes","title":"Възли","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/nodes.html","navOrder":4,"keywords":["choosing", "what", "the", "list", "shows", "node", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15460}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "air", "quality", "signal", "reference", "reading", "traceroute", "results", "neighbor", "info", "host", "pax"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12770}, + {"id":"nodes","title":"Възли","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/nodes.html","navOrder":4,"keywords":["choosing", "what", "the", "list", "shows", "node", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15767}, {"id":"onboarding","title":"Първи стъпки","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/onboarding.html","navOrder":1,"keywords":["first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup"],"aliases":["first-launch", "setup", "intro"],"charCount":8480}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "module-config", "administration"],"charCount":33271}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "lora", "modem", "presets", "bluetooth", "related", "topics"],"aliases":["настройки", "radio-config", "user-config", "lora"],"charCount":42258}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5248}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5297}, {"id":"tak","title":"TAK Integration","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/tak.html","navOrder":10,"keywords":["tak", "integration", "setup", "prerequisites", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10721}, - {"id":"telemetry-and-sensors","title":"Телеметрия & Сензори","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/telemetry-and-sensors.html","navOrder":9,"keywords":["device", "telemetry", "soil", "weather", "and", "other", "readings", "configuring", "choosing", "interval", "air", "quality", "metrics", "viewing", "related", "topics"],"aliases":["сензори", "околна среда", "времето", "power-metrics"],"charCount":10912}, + {"id":"telemetry-and-sensors","title":"Телеметрия & Сензори","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/telemetry-and-sensors.html","navOrder":9,"keywords":["device", "telemetry", "weather", "and", "other", "readings", "configuring", "choosing", "interval", "air", "quality", "metrics", "viewing", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10984}, {"id":"translate","title":"Translate the App","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "adding", "new", "language", "how", "translations", "are", "organized", "translation", "guidelines"],"aliases":["translate", "crowdin", "localization"],"charCount":5425}, {"id":"units-and-locale","title":"Units, Measurement & Locale","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/units-and-locale.html","navOrder":16,"keywords":["units", "measurement", "locale", "the", "radio", "own", "screen", "separate", "distance", "altitude", "where", "these", "appear", "rainfall", "that", "never", "change", "date", "time", "changing", "your", "system", "overriding", "app"],"aliases":["measurement", "units", "locale", "metric", "imperial"],"charCount":9919}, {"id":"widget","title":"Home Screen Widget","section":"user","locale":"bg-rBG","resourcePath":"docs/bg-rBG/user/widget.html","navOrder":20,"keywords":["home", "screen", "widget", "what", "shows", "adding", "the", "related", "topics"],"aliases":["widget", "home-screen-widget", "local-stats-widget"],"charCount":2646}, @@ -104,12 +104,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22697}, {"id":"mqtt","title":"MQTT","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "tra", "ruta", "reading", "traceroute", "results", "position", "log", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12411}, - {"id":"nodes","title":"Nodes","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15390}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "tra", "ruta", "reading", "traceroute", "results", "position", "log", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12543}, + {"id":"nodes","title":"Nodes","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15697}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32430}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41241}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5184}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10590}, {"id":"translate","title":"Translate the App","section":"user","locale":"ca-rES","resourcePath":"docs/ca-rES/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -125,12 +125,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "mapov", "vrstvy", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13868}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "kan", "default", "channel", "zabezpe", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22816}, {"id":"mqtt","title":"MQTT","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "nastaven", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12368}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "metriky", "zen", "prost", "air", "quality", "kvalita", "sign", "signal", "reference", "nap", "jen", "traceroute", "reading", "results", "protokol", "pozic", "informace", "sousedech", "hostitele", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12436}, - {"id":"nodes","title":"Uzly","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/nodes.html","navOrder":4,"keywords":["uzly", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15403}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "metriky", "zen", "prost", "air", "quality", "kvalita", "sign", "signal", "reference", "nap", "jen", "traceroute", "reading", "results", "protokol", "pozic", "informace", "sousedech", "hostitele", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12568}, + {"id":"nodes","title":"Uzly","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/nodes.html","navOrder":4,"keywords":["uzly", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15710}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8511}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32804}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "nastaven", "zen", "lora", "modem", "presets", "zobrazen", "pozice", "nap", "jen", "bluetooth", "zabezpe", "related", "topics"],"aliases":["nastavení", "radio-config", "user-config", "lora"],"charCount":42155}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5190}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5239}, {"id":"tak","title":"TAK Integration","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "nastaven", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10681}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "metriky", "nap", "jen", "configuring", "choosing", "interval", "metrics", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10534}, {"id":"translate","title":"Translate the App","section":"user","locale":"cs-rCZ","resourcePath":"docs/cs-rCZ/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "jak", "isp", "adding", "new", "language", "how", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5421}, @@ -146,12 +146,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "kartensteuerung", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "kartenebenen", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13946}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "kan", "default", "channel", "kanalsicherheit", "adding", "direktnachrichten", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22944}, {"id":"mqtt","title":"MQTT","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/mqtt.html","navOrder":11,"keywords":["mqtt", "bersicht", "funktioniert", "einstellungen", "aktivieren", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "bew", "hrte", "praktiken", "fehlerbehebung", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12383}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "ger", "tedaten", "umweltdaten", "air", "quality", "signalqualit", "signal", "reference", "energiedaten", "traceroute", "reading", "results", "standortprotokoll", "nachbarinformation", "host", "kennzahlen", "benutzerz", "hlerdaten", "verwandte", "themen"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12844}, - {"id":"nodes","title":"Knoten","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/nodes.html","navOrder":4,"keywords":["knoten", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15668}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "ger", "tedaten", "umweltdaten", "air", "quality", "signalqualit", "signal", "reference", "energiedaten", "traceroute", "reading", "results", "standortprotokoll", "nachbarinformation", "host", "kennzahlen", "benutzerz", "hlerdaten", "verwandte", "themen"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12976}, + {"id":"nodes","title":"Knoten","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/nodes.html","navOrder":4,"keywords":["knoten", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15975}, {"id":"onboarding","title":"Erste Schritte","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/onboarding.html","navOrder":1,"keywords":["erste", "schritte", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "verwandte", "themen"],"aliases":["first-launch", "setup", "intro"],"charCount":8565}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "moduleinstellungen", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":33041}, - {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "benutzereinstellungen", "profile", "applying", "changes", "einstellungen", "ger", "teeinstellungen", "lora", "modem", "presets", "anzeigeeinstellungen", "standorteinstellungen", "energie", "netzwerkeinstellungen", "bluetooth", "sicherheitseinstellungen", "related", "topics"],"aliases":["Einstellungen", "radio-config", "user-config", "lora"],"charCount":41985}, - {"id":"signal-meter","title":"Wie das Meshtastic Signal Meter funktioniert","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/signal-meter.html","navOrder":15,"keywords":["wie", "das", "meshtastic", "signal", "meter", "funktioniert", "rssi", "and", "snr", "decoding", "below", "the", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["Signal", "Signal-Meter", "snr", "rssi"],"charCount":5329}, + {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "benutzereinstellungen", "profile", "applying", "changes", "einstellungen", "ger", "teeinstellungen", "lora", "modem", "presets", "anzeigeeinstellungen", "standorteinstellungen", "energie", "netzwerkeinstellungen", "bluetooth", "sicherheitseinstellungen", "related", "topics"],"aliases":["Einstellungen", "radio-config", "user-config", "lora"],"charCount":42001}, + {"id":"signal-meter","title":"Wie das Meshtastic Signal Meter funktioniert","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/signal-meter.html","navOrder":15,"keywords":["wie", "das", "meshtastic", "signal", "meter", "funktioniert", "rssi", "and", "snr", "decoding", "below", "the", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["Signal", "Signal-Meter", "snr", "rssi"],"charCount":5378}, {"id":"tak","title":"TAK Integration","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/tak.html","navOrder":10,"keywords":["tak", "integration", "bersicht", "einstellungen", "voraussetzungen", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "fehlerbehebung", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10707}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "ger", "tetelemetrie", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "energiedaten", "configuring", "choosing", "interval", "metrics", "viewing", "fehlerbehebung", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10678}, {"id":"translate","title":"Translate the App","section":"user","locale":"de-rDE","resourcePath":"docs/de-rDE/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "wie", "man", "beitragen", "kann", "adding", "new", "language", "how", "translations", "are", "organized", "translation", "guidelines", "questions", "verwandte", "themen"],"aliases":["translate", "crowdin", "localization"],"charCount":5452}, @@ -167,12 +167,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22696}, {"id":"mqtt","title":"MQTT","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "traceroute", "reading", "results", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12426}, - {"id":"nodes","title":"Nodes","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15390}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "traceroute", "reading", "results", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12558}, + {"id":"nodes","title":"Nodes","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15697}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32399}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["ρυθμίσεις", "radio-config", "user-config", "lora"],"charCount":41245}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5184}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10583}, {"id":"translate","title":"Translate the App","section":"user","locale":"el-rGR","resourcePath":"docs/el-rGR/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -188,12 +188,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "capas", "del", "mapa", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13877}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "canales", "default", "channel", "seguridad", "del", "canal", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22699}, {"id":"mqtt","title":"MQTT","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/mqtt.html","navOrder":11,"keywords":["mqtt", "visi", "general", "how", "works", "configuraci", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12378}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "tricas", "dispositivo", "entorno", "air", "quality", "calidad", "signal", "reference", "energ", "traceroute", "reading", "results", "registro", "posiciones", "informaci", "vecinos", "del", "anfitri", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12484}, - {"id":"nodes","title":"Nodos","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/nodes.html","navOrder":4,"keywords":["nodos", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15433}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "tricas", "dispositivo", "entorno", "air", "quality", "calidad", "signal", "reference", "energ", "traceroute", "reading", "results", "registro", "posiciones", "informaci", "vecinos", "del", "anfitri", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12616}, + {"id":"nodes","title":"Nodos","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/nodes.html","navOrder":4,"keywords":["nodos", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15740}, {"id":"onboarding","title":"Primeros Pasos","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/onboarding.html","navOrder":1,"keywords":["primeros", "pasos", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8534}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":33468}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuraci", "del", "dispositivo", "lora", "modem", "presets", "pantalla", "posici", "elecenerg", "red", "bluetooth", "seguridad", "related", "topics"],"aliases":["ajustes", "radio-config", "user-config", "lora"],"charCount":42531}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5208}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5257}, {"id":"tak","title":"TAK Integration","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/tak.html","navOrder":10,"keywords":["tak", "integration", "visi", "general", "setup", "prerequisites", "configuraci", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10691}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "tricas", "energ", "configuring", "choosing", "interval", "metrics", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10718}, {"id":"translate","title":"Translate the App","section":"user","locale":"es-rES","resourcePath":"docs/es-rES/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -209,12 +209,12 @@ {"id":"map-and-waypoints","title":"Kaart ja teekonnapunktid","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/map-and-waypoints.html","navOrder":6,"keywords":["kaart", "teekonnapunktid", "kaardi", "vaade", "node", "markers", "juhtnupud", "filtering", "the", "map", "teekonnapunkt", "loo", "waypoint", "properties", "expiration", "teekonnapunktide", "geopiirded", "managing", "waypoints", "kaardikihid", "saidi", "planeerija", "position", "sharing", "enabling", "privacy", "considerations", "allikad", "adding", "your"],"aliases":["kaart", "teekonnapunkt", "gps", "asukoht", "saidi planeerija", "kaardi-kihid", "geojson", "kml"],"charCount":14056}, {"id":"messages-and-channels","title":"Sõnumid ja kanalid","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/messages-and-channels.html","navOrder":3,"keywords":["numid", "kanalid", "kanal", "vaikekanal", "kanali", "turvalisus", "lisa", "otses", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "numi", "olek", "delivery", "errors", "omadused", "kiirvestlus", "otsin", "numeid", "numimullid", "teksti", "vormindamine", "mainimine", "reaktsioonid", "replying"],"aliases":["kanalid", "otsesõnumid", "messaging", "conversations"],"charCount":22872}, {"id":"mqtt","title":"MQTT","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/mqtt.html","navOrder":11,"keywords":["mqtt", "levaade", "kuidas", "see", "toimib", "tted", "luba", "connection", "status", "and", "test", "puhverserver", "sellel", "telefonil", "meshtastic", "vaikemaakler", "private", "broker", "kaardiaruannete", "koostamine", "leslink", "allalink", "numivormingud", "encryption", "privacy", "parimad", "tavad", "veaotsing", "hendu", "messages"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12403}, - {"id":"node-metrics","title":"Sõlme mõõdikud","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/node-metrics.html","navOrder":5,"keywords":["lme", "dikud", "viewing", "metrics", "seadme", "keskkonnam", "air", "quality", "levi", "kvaliteet", "signal", "reference", "imsusn", "itajad", "marsruudi", "traceroute", "tulemuste", "lugemine", "asukoha", "logi", "naabruse", "teave", "hosti", "dik", "pax", "diku", "seotud", "teemad"],"aliases":["meetriline", "telemeetria", "sõlme-mõõdikud", "signaal"],"charCount":12669}, - {"id":"nodes","title":"Sõlmed","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/nodes.html","navOrder":4,"keywords":["lmed", "lmede", "loend", "choosing", "what", "the", "list", "shows", "lme", "oleku", "indikaatorid", "node", "roles", "role", "encryption", "indicators", "quick", "actions", "sharing", "contact", "filtering", "sorting", "teksti", "otsing", "filter", "toggles", "sorteerimisvalikud", "ppe", "kohta", "detail"],"aliases":["sõlmede loend", "mesh-nodes", "eakaaslased", "hop-histogram"],"charCount":15956}, + {"id":"node-metrics","title":"Sõlme mõõdikud","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/node-metrics.html","navOrder":5,"keywords":["lme", "dikud", "viewing", "metrics", "seadme", "keskkonnam", "air", "quality", "levi", "kvaliteet", "signal", "reference", "imsusn", "itajad", "marsruudi", "traceroute", "tulemuste", "lugemine", "asukoha", "logi", "naabruse", "teave", "hosti", "dik", "pax", "diku", "seotud", "teemad"],"aliases":["meetriline", "telemeetria", "sõlme-mõõdikud", "signaal"],"charCount":12798}, + {"id":"nodes","title":"Sõlmed","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/nodes.html","navOrder":4,"keywords":["lmed", "lmede", "loend", "choosing", "what", "the", "list", "shows", "lme", "oleku", "indikaatorid", "node", "roles", "role", "encryption", "indicators", "quick", "actions", "sharing", "contact", "filtering", "sorting", "teksti", "otsing", "filter", "toggles", "sorteerimisvalikud", "ppe", "kohta", "detail"],"aliases":["sõlmede loend", "mesh-nodes", "eakaaslased", "hop-histogram"],"charCount":16263}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "tervituskuva", "permissions", "sinihamba", "load", "asukoha", "luba", "rguannete", "critical", "alerts", "permission", "reviewing", "later", "peale", "seadistamist", "seotud", "teemad"],"aliases":["first-launch", "seadistamine", "sissejuhatus"],"charCount":8529}, {"id":"settings-module-admin","title":"Sätted - moodulid & admin","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/settings-module-admin.html","navOrder":8,"keywords":["tted", "moodulid", "admin", "mooduli", "konf", "mqtt", "moodul", "jadapordi", "lise", "teavitusmoodul", "salvesta", "edasta", "kaugustesti", "telemeetria", "eelsalvestatud", "numi", "audio", "kaugriistvara", "naabriinfo", "ambientvalguse", "tuvastusanduri", "paxloenduri", "status", "message", "module", "mesh", "beacon", "tak", "haldus", "kaughaldus"],"aliases":["moodul", "mooduli sätted", "administratsioon"],"charCount":33029}, {"id":"settings-radio-user","title":"Seaded — raadio ja kasutaja","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/settings-radio-user.html","navOrder":7,"keywords":["seaded", "raadio", "kasutaja", "how", "these", "screens", "work", "kasutajaprofiil", "applying", "changes", "tted", "seadme", "lora", "modem", "presets", "ekraani", "asukoha", "toite", "rgu", "sinihamba", "turva", "seotud", "teemad"],"aliases":["sätted", "raadio-sätted", "kasutaja-sätted", "lora"],"charCount":41625}, - {"id":"signal-meter","title":"Kuidas Meshtastic signaalimõõtur töötab","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/signal-meter.html","navOrder":15,"keywords":["kuidas", "meshtastic", "signaalim", "tur", "tab", "rssi", "and", "snr", "decoding", "below", "the", "noise", "floor", "rating", "signal", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "seotud", "teemad"],"aliases":["signaal", "signaali-mõõtur", "snr", "rssi"],"charCount":5242}, + {"id":"signal-meter","title":"Kuidas Meshtastic signaalimõõtur töötab","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/signal-meter.html","navOrder":15,"keywords":["kuidas", "meshtastic", "signaalim", "tur", "tab", "rssi", "and", "snr", "decoding", "below", "the", "noise", "floor", "rating", "signal", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "seotud", "teemad"],"aliases":["signaal", "signaali-mõõtur", "snr", "rssi"],"charCount":5291}, {"id":"tak","title":"TAK integratsioon","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/tak.html","navOrder":10,"keywords":["tak", "integratsioon", "levaade", "seadistamine", "prerequisites", "tted", "lokaalne", "server", "rollid", "cot", "cursor", "target", "vorming", "numivorming", "kasutamine", "koos", "atakiga", "veaotsing", "security", "considerations", "seotud", "teemad"],"aliases":["tak", "atak", "meeskonna teadlikkuse komplekt"],"charCount":11096}, {"id":"telemetry-and-sensors","title":"Telemeetria & Sensorid","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemeetria", "sensorid", "telemetria", "device", "telemetry", "environment", "sensors", "temperature", "humidity", "air", "quality", "soil", "valgus", "weather", "and", "other", "readings", "imsusn", "itajad", "configuring", "choosing", "interval", "metrics", "viewing", "veaotsing", "seotud", "teemad"],"aliases":["sensorid", "environment", "ilm", "power-metrics"],"charCount":10499}, {"id":"translate","title":"Tõlgi rakendus","section":"user","locale":"et-rEE","resourcePath":"docs/et-rEE/user/translate.html","navOrder":17,"keywords":["lgi", "rakendus", "mida", "lgitakse", "how", "contribute", "lisa", "uus", "keel", "translations", "are", "organized", "translation", "guidelines", "simusi", "seotud", "teemad"],"aliases":["tõlgi", "crowdin", "localization"],"charCount":5354}, @@ -230,12 +230,12 @@ {"id":"map-and-waypoints","title":"Kartta ja reittipisteet","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/map-and-waypoints.html","navOrder":6,"keywords":["kartta", "reittipisteet", "karttan", "kym", "radioiden", "merkinn", "kartan", "hallinta", "filtering", "the", "map", "reittipisteen", "luominen", "ominaisuudet", "vanheneminen", "reittipisteiden", "aluerajaukset", "karttatasot", "site", "planner", "sijainnin", "jakaminen", "jakamisen", "ytt", "notto", "tietosuoja", "karttal", "hteet", "oman", "karttatiilipalvelun"],"aliases":["kartta", "reittipisteet", "gps", "sijainti", "site-planner", "karttatasot", "geojson", "kml"],"charCount":15092}, {"id":"messages-and-channels","title":"Viestit ja kanavat","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/messages-and-channels.html","navOrder":3,"keywords":["viestit", "kanavat", "oletuskanava", "kanavan", "turvallisuus", "lis", "minen", "yksityisviestit", "yksityisviestin", "hett", "keskusteluluettelon", "hallinta", "keskustelukuplat", "viestin", "tilat", "toimitusvirheet", "viestiominaisuudet", "pikachatti", "viestien", "haku", "viestikuplat", "tekstin", "muotoilu", "maininnat", "reaktiot", "vastaaminen", "erottimet", "siirry", "viimeisimpiin", "viestitoiminnot"],"aliases":["kanavat", "yksityisviestit", "viestit", "keskustelut"],"charCount":24669}, {"id":"mqtt","title":"MQTT","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/mqtt.html","navOrder":11,"keywords":["mqtt", "yleiskatsaus", "kuinka", "toimii", "asetukset", "ytt", "notto", "yhteyden", "tila", "testaa", "yhteys", "lityspalvelin", "puhelimessa", "oletus", "meshtastic", "oma", "karttaraportointi", "hetys", "vastaanotto", "viestiformaatit", "salaus", "yksityisyys", "parhaat", "vianetsint", "yhdist", "viestit", "eiv", "lity", "aiheeseen", "liittyv"],"aliases":["mqtt", "internet-silta", "välityspalvelin"],"charCount":13491}, - {"id":"node-metrics","title":"Radion mittarit","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/node-metrics.html","navOrder":5,"keywords":["radion", "mittarit", "mittareiden", "tarkastelu", "laitteen", "mittausloki", "ymp", "rist", "arvot", "ilmanlaatumittarit", "signaalin", "laatu", "laadun", "viitearvot", "virranhallinnan", "reitinselvitys", "reitinselvityksen", "tulosten", "lukeminen", "sijainnin", "loki", "naapuritieto", "mittausarvot", "pax", "aiheeseen", "liittyv", "aiheet"],"aliases":["mittarit", "telemetria", "laitteen mittarit", "signaali"],"charCount":13967}, - {"id":"nodes","title":"Laitteet","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/nodes.html","navOrder":4,"keywords":["laitteet", "radiolista", "choosing", "what", "the", "list", "shows", "radion", "tilailmaisimet", "roolit", "roolin", "valitseminen", "salausilmaisimet", "pikatoiminnot", "sharing", "contact", "suodatus", "lajittelu", "tekstihaku", "suodatusvalinnat", "lajitteluvaihtoehdot", "radiot", "hyppym", "mukaan", "tiedot", "laite", "linkit", "haluan", "sellaisen", "when"],"aliases":["radiolista", "mesh-radiot", "vertaisradiot", "Hyppymääräjakauma"],"charCount":17154}, + {"id":"node-metrics","title":"Radion mittarit","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/node-metrics.html","navOrder":5,"keywords":["radion", "mittarit", "mittareiden", "tarkastelu", "laitteen", "mittausloki", "ymp", "rist", "arvot", "ilmanlaatumittarit", "signaalin", "laatu", "laadun", "viitearvot", "virranhallinnan", "reitinselvitys", "reitinselvityksen", "tulosten", "lukeminen", "sijainnin", "loki", "naapuritieto", "mittausarvot", "pax", "aiheeseen", "liittyv", "aiheet"],"aliases":["mittarit", "telemetria", "laitteen mittarit", "signaali"],"charCount":14092}, + {"id":"nodes","title":"Laitteet","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/nodes.html","navOrder":4,"keywords":["laitteet", "radiolista", "choosing", "what", "the", "list", "shows", "radion", "tilailmaisimet", "roolit", "roolin", "valitseminen", "salausilmaisimet", "pikatoiminnot", "sharing", "contact", "suodatus", "lajittelu", "tekstihaku", "suodatusvalinnat", "lajitteluvaihtoehdot", "radiot", "hyppym", "mukaan", "tiedot", "laite", "linkit", "haluan", "sellaisen", "when"],"aliases":["radiolista", "mesh-radiot", "vertaisradiot", "Hyppymääräjakauma"],"charCount":17461}, {"id":"onboarding","title":"Aloittaminen","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/onboarding.html","navOrder":1,"keywords":["aloittaminen", "ensimm", "inen", "ynnistys", "aloitusn", "kym", "ytt", "oikeudet", "bluetooth", "oikeus", "sijaintik", "ilmoitusk", "kriittisten", "lytysten", "oikeuksien", "tarkistaminen", "hemmin", "rityksen", "lkeen", "aiheeseen", "liittyv", "aiheet"],"aliases":["ensimmäinen käynnistys", "asetukset", "esittely"],"charCount":9481}, {"id":"settings-module-admin","title":"Asetukset — Moduulit ja ylläpito","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/settings-module-admin.html","navOrder":8,"keywords":["asetukset", "moduulit", "yll", "pito", "moduulin", "ritys", "mqtt", "moduuli", "sarjaporttimoduuli", "ulkoisten", "ilmoitusten", "varastoi", "lit", "kuuluvuustesti", "telemetriamoduuli", "valmiiden", "viestien", "nimoduuli", "laitteiston", "naapuritieto", "ymp", "rist", "valaistusmoduuli", "tunnistusanturimoduuli", "pax", "laskurimoduuli", "tilaviestimoduuli", "mesh", "beacon", "tak"],"aliases":["moduulit", "moduulin asetukset", "ylläpito"],"charCount":35065}, {"id":"settings-radio-user","title":"Asetukset — Radio ja käyttäjä","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/settings-radio-user.html","navOrder":7,"keywords":["asetukset", "radio", "ytt", "how", "these", "screens", "work", "profiili", "muutosten", "notto", "laitteen", "lora", "esiasetukset", "sijainnin", "virran", "verkon", "bluetooth", "turvallisuusasetukset", "aiheeseen", "liittyv", "aiheet"],"aliases":["asetukset", "radion asetukset", "käyttäjän asetukset", "lora"],"charCount":44198}, - {"id":"signal-meter","title":"Kuinka Meshtastic-signaalimittari toimii","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/signal-meter.html","navOrder":15,"keywords":["kuinka", "meshtastic", "signaalimittari", "toimii", "rssi", "snr", "vastaanotto", "kohinatason", "alapuolelta", "signaalin", "laadun", "arviointi", "paikallisten", "iri", "iden", "tunnistaminen", "miss", "signaalitieto", "kyy", "aiheeseen", "liittyv", "aiheet"],"aliases":["signaali", "signaalimittari", "snr", "rssi"],"charCount":5771}, + {"id":"signal-meter","title":"Kuinka Meshtastic-signaalimittari toimii","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/signal-meter.html","navOrder":15,"keywords":["kuinka", "meshtastic", "signaalimittari", "toimii", "rssi", "snr", "vastaanotto", "kohinatason", "alapuolelta", "signaalin", "laadun", "arviointi", "paikallisten", "iri", "iden", "tunnistaminen", "miss", "signaalitieto", "kyy", "aiheeseen", "liittyv", "aiheet"],"aliases":["signaali", "signaalimittari", "snr", "rssi"],"charCount":5753}, {"id":"tak","title":"TAK-integraatio","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/tak.html","navOrder":10,"keywords":["tak", "integraatio", "yleiskatsaus", "asetukset", "edellytykset", "paikallinen", "palvelin", "roolit", "cot", "cursor", "target", "muoto", "wire", "format", "ytt", "atak", "kanssa", "vianetsint", "tietoturvahuomiot", "aiheeseen", "liittyv", "aiheet"],"aliases":["tak", "atak", "team awareness kit"],"charCount":11772}, {"id":"telemetry-and-sensors","title":"Telemetria ja anturit","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetria", "anturit", "laitteen", "telemetriatiedot", "ymp", "rist", "tila", "kosteus", "ilmanlaatu", "maaper", "valo", "weather", "and", "other", "readings", "virranhallinnan", "arvot", "telemetrian", "ritt", "minen", "mittausv", "lin", "valitseminen", "ilmanlaatumittarit", "tarkastelu", "vianetsint", "aiheeseen", "liittyv", "aiheet"],"aliases":["sensorit", "ympäristö", "sää", "virtamittarit"],"charCount":11297}, {"id":"translate","title":"Käännä sovellus","section":"user","locale":"fi-rFI","resourcePath":"docs/fi-rFI/user/translate.html","navOrder":17,"keywords":["sovellus", "mit", "nnet", "kuinka", "voi", "osallistua", "uuden", "kielen", "lis", "minen", "kset", "rjestetty", "sohjeet", "kysytt", "aiheeseen", "liittyv", "aiheet"],"aliases":["käännä", "crowdin", "lokalisointi"],"charCount":5707}, @@ -251,12 +251,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "couches", "cartographiques", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13886}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "canaux", "default", "channel", "curit", "canal", "adding", "directs", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22697}, {"id":"mqtt","title":"MQTT","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "triques", "appareil", "environnement", "air", "quality", "qualit", "signal", "reference", "alimentation", "traceroute", "reading", "results", "journal", "des", "positions", "informations", "sur", "les", "voisins", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12551}, - {"id":"nodes","title":"Nœuds","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/nodes.html","navOrder":4,"keywords":["uds", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15449}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "triques", "appareil", "environnement", "air", "quality", "qualit", "signal", "reference", "alimentation", "traceroute", "reading", "results", "journal", "des", "positions", "informations", "sur", "les", "voisins", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12683}, + {"id":"nodes","title":"Nœuds","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/nodes.html","navOrder":4,"keywords":["uds", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15756}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8571}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "configuration", "module", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":33427}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "param", "tres", "utilisateur", "profile", "applying", "changes", "configuration", "appareil", "lora", "modem", "presets", "cran", "position", "alimentation", "seau", "bluetooth", "curit", "related", "topics"],"aliases":["paramètres", "radio-config", "user-config", "lora"],"charCount":42971}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5202}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5251}, {"id":"tak","title":"TAK Integration","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10717}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "triques", "alimentation", "configuring", "choosing", "interval", "metrics", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10667}, {"id":"translate","title":"Translate the App","section":"user","locale":"fr-rCA","resourcePath":"docs/fr-rCA/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "qui", "est", "traduit", "comment", "contribuer", "ajouter", "une", "nouvelle", "langue", "sont", "organis", "les", "traductions", "directives", "traduction", "des", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5760}, @@ -272,12 +272,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "couches", "cartographiques", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13886}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "canaux", "default", "channel", "curit", "canal", "adding", "directs", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22697}, {"id":"mqtt","title":"MQTT","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "triques", "appareil", "environnement", "air", "quality", "qualit", "signal", "reference", "alimentation", "traceroute", "reading", "results", "journal", "des", "positions", "informations", "sur", "les", "voisins", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12551}, - {"id":"nodes","title":"Nœuds","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/nodes.html","navOrder":4,"keywords":["uds", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15449}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "triques", "appareil", "environnement", "air", "quality", "qualit", "signal", "reference", "alimentation", "traceroute", "reading", "results", "journal", "des", "positions", "informations", "sur", "les", "voisins", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12683}, + {"id":"nodes","title":"Nœuds","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/nodes.html","navOrder":4,"keywords":["uds", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15756}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8571}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "configuration", "module", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":33427}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "param", "tres", "utilisateur", "profile", "applying", "changes", "configuration", "appareil", "lora", "modem", "presets", "cran", "position", "alimentation", "seau", "bluetooth", "curit", "related", "topics"],"aliases":["paramètres", "radio-config", "user-config", "lora"],"charCount":42971}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5202}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5251}, {"id":"tak","title":"TAK Integration","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10717}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "triques", "alimentation", "configuring", "choosing", "interval", "metrics", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10667}, {"id":"translate","title":"Translate the App","section":"user","locale":"fr-rFR","resourcePath":"docs/fr-rFR/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "qui", "est", "traduit", "comment", "contribuer", "ajouter", "une", "nouvelle", "langue", "sont", "organis", "les", "traductions", "directives", "traduction", "des", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5760}, @@ -293,12 +293,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22697}, {"id":"mqtt","title":"MQTT","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "ocht", "gneal", "signal", "reference", "power", "rianad", "ireachta", "reading", "traceroute", "results", "seirbh", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12483}, - {"id":"nodes","title":"Nodes","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15407}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "ocht", "gneal", "signal", "reference", "power", "rianad", "ireachta", "reading", "traceroute", "results", "seirbh", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12615}, + {"id":"nodes","title":"Nodes","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15714}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32325}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41241}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5250}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5299}, {"id":"tak","title":"TAK Integration","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10534}, {"id":"translate","title":"Translate the App","section":"user","locale":"ga-rIE","resourcePath":"docs/ga-rIE/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -314,12 +314,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22697}, {"id":"mqtt","title":"MQTT","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "traza", "ruta", "reading", "traceroute", "results", "position", "log", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12410}, - {"id":"nodes","title":"Nodes","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15390}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "traza", "ruta", "reading", "traceroute", "results", "position", "log", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12542}, + {"id":"nodes","title":"Nodes","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15697}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32350}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41241}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5184}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10590}, {"id":"translate","title":"Translate the App","section":"user","locale":"gl-rES","resourcePath":"docs/gl-rES/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -335,12 +335,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22697}, {"id":"mqtt","title":"MQTT","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "traceroute", "reading", "results", "position", "log", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12410}, - {"id":"nodes","title":"Nodes","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15388}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "traceroute", "reading", "results", "position", "log", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12542}, + {"id":"nodes","title":"Nodes","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15695}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32381}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "postavke", "bluetootha", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41244}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5184}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10590}, {"id":"translate","title":"Translate the App","section":"user","locale":"hr-rHR","resourcePath":"docs/hr-rHR/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -356,12 +356,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13873}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22697}, {"id":"mqtt","title":"MQTT","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "kalite", "siynal", "signal", "reference", "power", "traceroute", "reading", "results", "jounal", "pozisyon", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12412}, - {"id":"nodes","title":"Nodes","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15416}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "kalite", "siynal", "signal", "reference", "power", "traceroute", "reading", "results", "jounal", "pozisyon", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12544}, + {"id":"nodes","title":"Nodes","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15723}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32301}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41241}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5190}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5239}, {"id":"tak","title":"TAK Integration","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10569}, {"id":"translate","title":"Translate the App","section":"user","locale":"ht-rHT","resourcePath":"docs/ht-rHT/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -377,12 +377,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "tegek", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13868}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "csatorn", "default", "channel", "csatorna", "biztons", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22700}, {"id":"mqtt","title":"MQTT","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "eszk", "zmetrik", "rnyezeti", "metrik", "air", "quality", "jelmin", "signal", "reference", "pell", "traceroute", "reading", "results", "poz", "napl", "szomsz", "inform", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12447}, - {"id":"nodes","title":"Csomópontok","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/nodes.html","navOrder":4,"keywords":["csom", "pontok", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15489}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "eszk", "zmetrik", "rnyezeti", "metrik", "air", "quality", "jelmin", "signal", "reference", "pell", "traceroute", "reading", "results", "poz", "napl", "szomsz", "inform", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12579}, + {"id":"nodes","title":"Csomópontok","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/nodes.html","navOrder":4,"keywords":["csom", "pontok", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15796}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8566}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":33222}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "eszk", "zbe", "sok", "lora", "modem", "presets", "kijelz", "poz", "energia", "zati", "bluetooth", "biztons", "related", "topics"],"aliases":["beállítások", "radio-config", "user-config", "lora"],"charCount":41888}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5208}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5257}, {"id":"tak","title":"TAK Integration","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "pell", "metrik", "configuring", "choosing", "interval", "metrics", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10627}, {"id":"translate","title":"Translate the App","section":"user","locale":"hu-rHU","resourcePath":"docs/hu-rHU/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -398,12 +398,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22697}, {"id":"mqtt","title":"MQTT","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "ferilk", "nnun", "reading", "traceroute", "results", "position", "log", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12411}, - {"id":"nodes","title":"Nodes","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15388}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "ferilk", "nnun", "reading", "traceroute", "results", "position", "log", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12543}, + {"id":"nodes","title":"Nodes","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15695}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32279}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41241}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5184}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10590}, {"id":"translate","title":"Translate the App","section":"user","locale":"is-rIS","resourcePath":"docs/is-rIS/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -419,12 +419,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "livelli", "della", "mappa", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13882}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "canali", "default", "channel", "sicurezza", "del", "canale", "adding", "messaggi", "diretti", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22955}, {"id":"mqtt","title":"MQTT","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/mqtt.html","navOrder":11,"keywords":["mqtt", "panoramica", "come", "funziona", "configurazione", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "buone", "pratiche", "risoluzione", "problemi", "not"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12381}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "metriche", "dispositivo", "ambientali", "air", "quality", "qualit", "segnale", "signal", "reference", "alimentazione", "traceroute", "reading", "results", "registro", "posizione", "informazioni", "vicinato", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12494}, - {"id":"nodes","title":"Nodi","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/nodes.html","navOrder":4,"keywords":["nodi", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15450}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "metriche", "dispositivo", "ambientali", "air", "quality", "qualit", "segnale", "signal", "reference", "alimentazione", "traceroute", "reading", "results", "registro", "posizione", "informazioni", "vicinato", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12626}, + {"id":"nodes","title":"Nodi","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/nodes.html","navOrder":4,"keywords":["nodi", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15757}, {"id":"onboarding","title":"Come iniziare","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/onboarding.html","navOrder":1,"keywords":["come", "iniziare", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8547}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "configurazione", "modulo", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":33207}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "impostazioni", "utente", "profile", "applying", "changes", "configurazione", "dispositivo", "lora", "modem", "presets", "schermo", "posizione", "alimentazione", "della", "rete", "bluetooth", "sicurezza", "related", "topics"],"aliases":["impostazioni", "radio-config", "user-config", "lora"],"charCount":42166}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5202}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5251}, {"id":"tak","title":"TAK Integration","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/tak.html","navOrder":10,"keywords":["tak", "integration", "panoramica", "configurazione", "prerequisiti", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "risoluzione", "problemi", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "telemetria", "dispositivo", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "metriche", "alimentazione", "configuring", "choosing", "interval", "metrics", "viewing", "risoluzione", "problemi", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10686}, {"id":"translate","title":"Translate the App","section":"user","locale":"it-rIT","resourcePath":"docs/it-rIT/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -440,12 +440,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22697}, {"id":"mqtt","title":"MQTT","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "reading", "traceroute", "results", "position", "log", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12411}, - {"id":"nodes","title":"Nodes","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15388}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "reading", "traceroute", "results", "position", "log", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12543}, + {"id":"nodes","title":"Nodes","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15695}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32288}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["הגדרות", "radio-config", "user-config", "lora"],"charCount":41239}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5184}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10590}, {"id":"translate","title":"Translate the App","section":"user","locale":"iw-rIL","resourcePath":"docs/iw-rIL/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -461,12 +461,12 @@ {"id":"map-and-waypoints","title":"マップとウェイポイント","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/map-and-waypoints.html","navOrder":6,"keywords":["filtering", "the", "map", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":12308}, {"id":"messages-and-channels","title":"メッセージとチャンネル","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/messages-and-channels.html","navOrder":3,"keywords":["managing", "the", "conversation", "list", "bubbles", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":20550}, {"id":"mqtt","title":"MQTT","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/mqtt.html","navOrder":11,"keywords":["mqtt", "connection", "status", "and", "test", "meshtastic"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":11198}, - {"id":"node-metrics","title":"ノードメトリクス","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/node-metrics.html","navOrder":5,"keywords":["pax"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":9858}, - {"id":"nodes","title":"ノード","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/nodes.html","navOrder":4,"keywords":["choosing", "what", "the", "list", "shows", "sharing", "contact", "when", "nodes", "appear"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":13015}, + {"id":"node-metrics","title":"ノードメトリクス","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/node-metrics.html","navOrder":5,"keywords":["pax"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":10009}, + {"id":"nodes","title":"ノード","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/nodes.html","navOrder":4,"keywords":["choosing", "what", "the", "list", "shows", "sharing", "contact", "when", "nodes", "appear"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":13322}, {"id":"onboarding","title":"はじめに","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/onboarding.html","navOrder":1,"keywords":["bluetooth", "reviewing", "permissions", "later"],"aliases":["初回起動", "セットアップ", "概要"],"charCount":7547}, {"id":"settings-module-admin","title":"設定:モジュールと管理","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/settings-module-admin.html","navOrder":8,"keywords":["mqtt", "store", "forward", "paxcounter", "status", "message", "module", "mesh", "beacon", "tak", "device", "actions", "app", "settings"],"aliases":["modules", "module-config", "administration"],"charCount":26660}, {"id":"settings-radio-user","title":"設定:無線機とユーザー","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/settings-radio-user.html","navOrder":7,"keywords":["how", "these", "screens", "work", "lora", "bluetooth"],"aliases":["設定", "radio-config", "user-config", "lora"],"charCount":39550}, - {"id":"signal-meter","title":"Meshtastic の信号メーターの仕組み","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/signal-meter.html","navOrder":15,"keywords":["meshtastic", "rssi", "and", "snr", "decoding", "below", "the", "noise", "floor", "rating", "signal", "quality", "diagnosing", "local", "interference"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":4931}, + {"id":"signal-meter","title":"Meshtastic の信号メーターの仕組み","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/signal-meter.html","navOrder":15,"keywords":["meshtastic", "rssi", "and", "snr", "decoding", "below", "the", "noise", "floor", "rating", "signal", "quality", "diagnosing", "local", "interference"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":4980}, {"id":"tak","title":"TAK 連携","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/tak.html","navOrder":10,"keywords":["tak", "cot", "cursor", "target", "atak"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":8473}, {"id":"telemetry-and-sensors","title":"テレメトリとセンサー","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/telemetry-and-sensors.html","navOrder":9,"keywords":["soil", "weather", "and", "other", "readings", "choosing", "interval"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":9214}, {"id":"translate","title":"アプリを翻訳する","section":"user","locale":"ja-rJP","resourcePath":"docs/ja-rJP/user/translate.html","navOrder":17,"keywords":[],"aliases":["translate", "crowdin", "localization"],"charCount":4506}, @@ -482,12 +482,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22691}, {"id":"mqtt","title":"MQTT","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting", "messages"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12361}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "reading", "traceroute", "results", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12377}, - {"id":"nodes","title":"노드","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15379}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signal", "reference", "power", "reading", "traceroute", "results", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12509}, + {"id":"nodes","title":"노드","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15686}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":31344}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "lora", "modem", "presets", "related", "topics"],"aliases":["설정", "radio-config", "user-config", "lora"],"charCount":41057}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5184}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10674}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10439}, {"id":"translate","title":"Translate the App","section":"user","locale":"ko-rKR","resourcePath":"docs/ko-rKR/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -503,12 +503,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13873}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22697}, {"id":"mqtt","title":"MQTT","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signalo", "kokyb", "signal", "reference", "power", "inut", "kelias", "reading", "traceroute", "results", "pozicijos", "duomen", "urnalas", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12447}, - {"id":"nodes","title":"Nodes","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15426}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signalo", "kokyb", "signal", "reference", "power", "inut", "kelias", "reading", "traceroute", "results", "pozicijos", "duomen", "urnalas", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12579}, + {"id":"nodes","title":"Nodes","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15733}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32314}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41241}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5214}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5263}, {"id":"tak","title":"TAK Integration","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10576}, {"id":"translate","title":"Translate the App","section":"user","locale":"lt-rLT","resourcePath":"docs/lt-rLT/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -524,12 +524,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13881}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "kanalen", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22696}, {"id":"mqtt","title":"MQTT","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signaalkwaliteit", "signal", "reference", "power", "traceroute", "reading", "results", "positie", "logboek", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12419}, - {"id":"nodes","title":"Nodes","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15391}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signaalkwaliteit", "signal", "reference", "power", "traceroute", "reading", "results", "positie", "logboek", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12551}, + {"id":"nodes","title":"Nodes","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15698}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32435}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "apparaat", "configuratie", "lora", "modem", "presets", "weergave", "positie", "energie", "netwerkconfiguratie", "bluetooth", "beveiligings", "related", "topics"],"aliases":["instellingen", "radio-config", "user-config", "lora"],"charCount":41389}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5190}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5239}, {"id":"tak","title":"TAK Integration","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10587}, {"id":"translate","title":"Translate the App","section":"user","locale":"nl-rNL","resourcePath":"docs/nl-rNL/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -545,12 +545,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13873}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22697}, {"id":"mqtt","title":"MQTT","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signalstyrke", "signal", "reference", "power", "traceroute", "reading", "results", "posisjonslogg", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12433}, - {"id":"nodes","title":"Nodes","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15387}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "signalstyrke", "signal", "reference", "power", "traceroute", "reading", "results", "posisjonslogg", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12565}, + {"id":"nodes","title":"Nodes","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15694}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32381}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41241}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5220}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5269}, {"id":"tak","title":"TAK Integration","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10618}, {"id":"translate","title":"Translate the App","section":"user","locale":"no-rNO","resourcePath":"docs/no-rNO/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -566,12 +566,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "warstwy", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13874}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "kana", "default", "channel", "bezpiecze", "stwo", "adding", "bezpo", "rednie", "wiadomo", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22708}, {"id":"mqtt","title":"MQTT","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "konfiguracja", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12371}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "metryka", "urz", "dzenia", "metryki", "rodowiskowe", "air", "quality", "jako", "sygna", "signal", "reference", "zasilania", "poka", "tras", "reading", "traceroute", "results", "historia", "pozycji", "informacje", "siadze", "statystyki", "hosta", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12599}, - {"id":"nodes","title":"Węzły","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15470}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "metryka", "urz", "dzenia", "metryki", "rodowiskowe", "air", "quality", "jako", "sygna", "signal", "reference", "zasilania", "poka", "tras", "reading", "traceroute", "results", "historia", "pozycji", "informacje", "siadze", "statystyki", "hosta", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12731}, + {"id":"nodes","title":"Węzły","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15777}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8596}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "konfiguracja", "modu", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon"],"aliases":["modules", "module-config", "administration"],"charCount":32898}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "konfiguracja", "urz", "dzenia", "lora", "modem", "presets", "wietlacza", "pozycjonowania", "zarz", "dzania", "energi", "sieci", "bluetooth", "zabezpiecze", "related", "topics"],"aliases":["ustawienia", "radio-config", "user-config", "lora"],"charCount":41857}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5232}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5281}, {"id":"tak","title":"TAK Integration","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "konfiguracja", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10684}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "metryki", "zasilania", "configuring", "choosing", "interval", "metrics", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10714}, {"id":"translate","title":"Translate the App","section":"user","locale":"pl-rPL","resourcePath":"docs/pl-rPL/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -587,12 +587,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "camadas", "mapa", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13870}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "canais", "default", "channel", "seguran", "canal", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22697}, {"id":"mqtt","title":"MQTT","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "qualidade", "sinal", "signal", "reference", "power", "tra", "rota", "reading", "traceroute", "results", "log", "posi", "informa", "vizinho", "tricas", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12434}, - {"id":"nodes","title":"Nós","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15434}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "qualidade", "sinal", "signal", "reference", "power", "tra", "rota", "reading", "traceroute", "results", "log", "posi", "informa", "vizinho", "tricas", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12566}, + {"id":"nodes","title":"Nós","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15741}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8516}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32840}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "configura", "dispositivo", "lora", "modem", "presets", "tela", "posi", "energia", "rede", "bluetooth", "seguran", "related", "topics"],"aliases":["configurações", "radio-config", "user-config", "lora"],"charCount":41695}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5190}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5239}, {"id":"tak","title":"TAK Integration","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10580}, {"id":"translate","title":"Translate the App","section":"user","locale":"pt-rBR","resourcePath":"docs/pt-rBR/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -608,12 +608,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "canal", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22694}, {"id":"mqtt","title":"MQTT","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configura", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12371}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "qualidade", "sinal", "signal", "reference", "power", "tra", "rota", "reading", "traceroute", "results", "hist", "rico", "posi", "informa", "vizinhan", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12445}, - {"id":"nodes","title":"Nodes","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15786}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "qualidade", "sinal", "signal", "reference", "power", "tra", "rota", "reading", "traceroute", "results", "hist", "rico", "posi", "informa", "vizinhan", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12577}, + {"id":"nodes","title":"Nodes","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":16093}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32871}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configura", "dispositivo", "lora", "modem", "presets", "ecr", "posi", "energia", "rede", "bluetooth", "seguran", "related", "topics"],"aliases":["definições", "radio-config", "user-config", "lora"],"charCount":41774}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5202}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5251}, {"id":"tak","title":"TAK Integration","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configura", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10684}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10587}, {"id":"translate","title":"Translate the App","section":"user","locale":"pt-rPT","resourcePath":"docs/pt-rPT/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -629,12 +629,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "canale", "default", "channel", "securitate", "canal", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22695}, {"id":"mqtt","title":"MQTT","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "valori", "dispozitiv", "indicatori", "mediu", "air", "quality", "calitatea", "semnalului", "signal", "reference", "putere", "trasare", "traseu", "reading", "traceroute", "results", "position", "log", "informa", "vecin", "gazd", "sur", "tori", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12509}, - {"id":"nodes","title":"Noduri","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/nodes.html","navOrder":4,"keywords":["noduri", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15430}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "valori", "dispozitiv", "indicatori", "mediu", "air", "quality", "calitatea", "semnalului", "signal", "reference", "putere", "trasare", "traseu", "reading", "traceroute", "results", "position", "log", "informa", "vecin", "gazd", "sur", "tori", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12641}, + {"id":"nodes","title":"Noduri","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/nodes.html","navOrder":4,"keywords":["noduri", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15737}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8481}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32974}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "configurare", "putere", "network", "bluetooth", "security", "related", "topics"],"aliases":["setari", "radio-config", "user-config", "lora"],"charCount":41625}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5214}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5263}, {"id":"tak","title":"TAK Integration","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10705}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "valori", "putere", "configuring", "choosing", "interval", "metrics", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10628}, {"id":"translate","title":"Translate the App","section":"user","locale":"ro-rRO","resourcePath":"docs/ro-rRO/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -650,12 +650,12 @@ {"id":"map-and-waypoints","title":"Карта и путевые точки","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/map-and-waypoints.html","navOrder":6,"keywords":["filtering", "the", "map", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":14676}, {"id":"messages-and-channels","title":"Сообщения и каналы","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/messages-and-channels.html","navOrder":3,"keywords":["managing", "the", "conversation", "list", "bubbles", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":23855}, {"id":"mqtt","title":"MQTT","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/mqtt.html","navOrder":11,"keywords":["mqtt", "connection", "status", "and", "test", "meshtastic", "uplink", "downlink"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12856}, - {"id":"node-metrics","title":"Метрики ноды","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/node-metrics.html","navOrder":5,"keywords":[],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":13524}, - {"id":"nodes","title":"Ноды","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/nodes.html","navOrder":4,"keywords":["choosing", "what", "the", "list", "shows", "sharing", "contact", "when", "nodes", "appear"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":16213}, + {"id":"node-metrics","title":"Метрики ноды","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/node-metrics.html","navOrder":5,"keywords":[],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":13654}, + {"id":"nodes","title":"Ноды","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/nodes.html","navOrder":4,"keywords":["choosing", "what", "the", "list", "shows", "sharing", "contact", "when", "nodes", "appear"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":16520}, {"id":"onboarding","title":"Начало работы","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/onboarding.html","navOrder":1,"keywords":["bluetooth", "reviewing", "permissions", "later"],"aliases":["first-launch", "setup", "intro"],"charCount":8982}, {"id":"settings-module-admin","title":"Настройки — Модули и администрирование","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/settings-module-admin.html","navOrder":8,"keywords":["mqtt", "store", "forward", "paxcounter", "status", "message", "module", "mesh", "beacon", "tak", "device", "actions", "app", "settings"],"aliases":["modules", "module-config", "administration"],"charCount":34423}, {"id":"settings-radio-user","title":"Настройки - Радио и пользователь","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/settings-radio-user.html","navOrder":7,"keywords":["how", "these", "screens", "work", "lora", "bluetooth"],"aliases":["настройки", "radio-config", "user-config", "lora"],"charCount":42861}, - {"id":"signal-meter","title":"Как работает измеритель сигнала Meshtastic","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/signal-meter.html","navOrder":15,"keywords":["meshtastic", "rssi", "and", "snr", "decoding", "below", "the", "noise", "floor", "rating", "signal", "quality", "diagnosing", "local", "interference"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5319}, + {"id":"signal-meter","title":"Как работает измеритель сигнала Meshtastic","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/signal-meter.html","navOrder":15,"keywords":["meshtastic", "rssi", "and", "snr", "decoding", "below", "the", "noise", "floor", "rating", "signal", "quality", "diagnosing", "local", "interference"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5368}, {"id":"tak","title":"Интеграция TAK","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/tak.html","navOrder":10,"keywords":["tak", "cot", "cursor", "target", "atak"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":11508}, {"id":"telemetry-and-sensors","title":"Телеметрия и датчики","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/telemetry-and-sensors.html","navOrder":9,"keywords":["soil", "weather", "and", "other", "readings", "choosing", "interval"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":11124}, {"id":"translate","title":"Перевод приложения","section":"user","locale":"ru-rRU","resourcePath":"docs/ru-rRU/user/translate.html","navOrder":17,"keywords":[],"aliases":["translate", "crowdin", "localization"],"charCount":5892}, @@ -671,12 +671,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "kan", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22695}, {"id":"mqtt","title":"MQTT","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "kvalita", "sign", "signal", "reference", "power", "trasovanie", "reading", "traceroute", "results", "log", "poz", "cie", "inform", "cia", "susedoch", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12444}, - {"id":"nodes","title":"Nodes","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15473}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "kvalita", "sign", "signal", "reference", "power", "trasovanie", "reading", "traceroute", "results", "log", "poz", "cie", "inform", "cia", "susedoch", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12576}, + {"id":"nodes","title":"Nodes","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15780}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32471}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "konfigur", "cia", "zariadenia", "lora", "modem", "presets", "displeju", "position", "config", "power", "siete", "bluetooth", "security", "related", "topics"],"aliases":["nastavenia", "radio-config", "user-config", "lora"],"charCount":41296}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5208}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5257}, {"id":"tak","title":"TAK Integration","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10534}, {"id":"translate","title":"Translate the App","section":"user","locale":"sk-rSK","resourcePath":"docs/sk-rSK/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -692,12 +692,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22697}, {"id":"mqtt","title":"MQTT","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "kakovost", "signala", "signal", "reference", "power", "pot", "reading", "traceroute", "results", "dnevnik", "lokacije", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12421}, - {"id":"nodes","title":"Nodes","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15404}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "kakovost", "signala", "signal", "reference", "power", "pot", "reading", "traceroute", "results", "dnevnik", "lokacije", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12553}, + {"id":"nodes","title":"Nodes","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15711}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32406}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41241}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5208}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5257}, {"id":"tak","title":"TAK Integration","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10569}, {"id":"translate","title":"Translate the App","section":"user","locale":"sl-rSI","resourcePath":"docs/sl-rSI/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -713,12 +713,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22697}, {"id":"mqtt","title":"MQTT","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "cil", "sia", "sinjalit", "signal", "reference", "power", "traceroute", "reading", "results", "regjistri", "pozit", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12421}, - {"id":"nodes","title":"Nodes","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15427}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "cil", "sia", "sinjalit", "signal", "reference", "power", "traceroute", "reading", "results", "regjistri", "pozit", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12553}, + {"id":"nodes","title":"Nodes","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/nodes.html","navOrder":4,"keywords":["nodes", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15734}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32307}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "device", "config", "lora", "modem", "presets", "display", "position", "power", "network", "bluetooth", "security", "related", "topics"],"aliases":["settings", "radio-config", "user-config", "lora"],"charCount":41241}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5196}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5245}, {"id":"tak","title":"TAK Integration","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10597}, {"id":"translate","title":"Translate the App","section":"user","locale":"sq-rAL","resourcePath":"docs/sq-rAL/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -734,12 +734,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"srp","resourcePath":"docs/srp/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"srp","resourcePath":"docs/srp/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "security", "adding", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22695}, {"id":"mqtt","title":"MQTT","section":"user","locale":"srp","resourcePath":"docs/srp/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12372}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"srp","resourcePath":"docs/srp/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "air", "quality", "signal", "reference", "reading", "traceroute", "results", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12437}, - {"id":"nodes","title":"Чворови","section":"user","locale":"srp","resourcePath":"docs/srp/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15435}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"srp","resourcePath":"docs/srp/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "air", "quality", "signal", "reference", "reading", "traceroute", "results", "neighbor", "info", "host", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12569}, + {"id":"nodes","title":"Чворови","section":"user","locale":"srp","resourcePath":"docs/srp/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15742}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"srp","resourcePath":"docs/srp/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"srp","resourcePath":"docs/srp/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "module-config", "administration"],"charCount":32422}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"srp","resourcePath":"docs/srp/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "lora", "modem", "presets", "related", "topics"],"aliases":["подешавања", "radio-config", "user-config", "lora"],"charCount":41714}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"srp","resourcePath":"docs/srp/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5214}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"srp","resourcePath":"docs/srp/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5263}, {"id":"tak","title":"TAK Integration","section":"user","locale":"srp","resourcePath":"docs/srp/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10685}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"srp","resourcePath":"docs/srp/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "configuring", "choosing", "interval", "metrics", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "окружење", "weather", "power-metrics"],"charCount":10594}, {"id":"translate","title":"Translate the App","section":"user","locale":"srp","resourcePath":"docs/srp/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -755,12 +755,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "kartlager", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13872}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "kanaler", "default", "channel", "kanals", "kerhet", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22693}, {"id":"mqtt","title":"MQTT","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "konfiguration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "fels", "kning", "not"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12367}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "enhetens", "rden", "milj", "air", "quality", "signalkvalit", "signal", "reference", "str", "mdata", "traceroute", "rutt", "reading", "results", "position", "loggbok", "granninformation", "beg", "rdens", "pax", "nyckeltal", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12434}, - {"id":"nodes","title":"Noder","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/nodes.html","navOrder":4,"keywords":["noder", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15389}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "enhetens", "rden", "milj", "air", "quality", "signalkvalit", "signal", "reference", "str", "mdata", "traceroute", "rutt", "reading", "results", "position", "loggbok", "granninformation", "beg", "rdens", "pax", "nyckeltal", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12566}, + {"id":"nodes","title":"Noder","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/nodes.html","navOrder":4,"keywords":["noder", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15696}, {"id":"onboarding","title":"Kom igång","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/onboarding.html","navOrder":1,"keywords":["kom", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8459}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":33111}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "anv", "ndarinst", "llningar", "profile", "applying", "changes", "konfiguration", "enhetskonfiguration", "lora", "config", "modem", "presets", "display", "position", "str", "minst", "network", "bluetooth", "inst", "security", "related", "topics"],"aliases":["inställningar", "radio-config", "user-config", "lora"],"charCount":41630}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5184}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "konfiguration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "fels", "kning", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10680}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "str", "mdata", "configuring", "choosing", "interval", "metrics", "viewing", "fels", "kning", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10624}, {"id":"translate","title":"Translate the App","section":"user","locale":"sv-rSE","resourcePath":"docs/sv-rSE/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -776,12 +776,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "layers", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13865}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "kanallar", "default", "channel", "security", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22697}, {"id":"mqtt","title":"MQTT","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/mqtt.html","navOrder":11,"keywords":["mqtt", "genel", "bak", "how", "works", "yap", "land", "rma", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12374}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "sinyal", "kalitesi", "signal", "reference", "power", "yol", "izle", "reading", "traceroute", "results", "konum", "kay", "tlar", "kom", "bilgisi", "sunucu", "mleri", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12434}, - {"id":"nodes","title":"Nodelar","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/nodes.html","navOrder":4,"keywords":["nodelar", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15392}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "device", "environment", "air", "quality", "sinyal", "kalitesi", "signal", "reference", "power", "yol", "izle", "reading", "traceroute", "results", "konum", "kay", "tlar", "kom", "bilgisi", "sunucu", "mleri", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12566}, + {"id":"nodes","title":"Nodelar","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/nodes.html","navOrder":4,"keywords":["nodelar", "node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15699}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8461}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":32396}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "yap", "land", "rma", "cihaz", "ayar", "lora", "modem", "presets", "akran", "konum", "bluetooth", "venlik", "related", "topics"],"aliases":["ayarlar", "radio-config", "user-config", "lora"],"charCount":41490}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5214}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5263}, {"id":"tak","title":"TAK Integration","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/tak.html","navOrder":10,"keywords":["tak", "integration", "genel", "bak", "setup", "prerequisites", "yap", "land", "rma", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10687}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "power", "metrics", "configuring", "choosing", "interval", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10523}, {"id":"translate","title":"Translate the App","section":"user","locale":"tr-rTR","resourcePath":"docs/tr-rTR/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "nas", "katk", "bulunulur", "adding", "new", "language", "how", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5433}, @@ -797,12 +797,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline", "related"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13864}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "adding", "direct", "sending", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest", "actions"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22693}, {"id":"mqtt","title":"MQTT","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/mqtt.html","navOrder":11,"keywords":["mqtt", "overview", "how", "works", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "troubleshooting", "not", "connecting", "messages"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12371}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "air", "quality", "signal", "reference", "reading", "traceroute", "results", "position", "log", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12539}, - {"id":"nodes","title":"Вузли","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15439}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "air", "quality", "signal", "reference", "reading", "traceroute", "results", "position", "log", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12671}, + {"id":"nodes","title":"Вузли","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15746}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8506}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "module", "configuration", "mqtt", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak"],"aliases":["modules", "module-config", "administration"],"charCount":33010}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "lora", "modem", "presets", "position", "config", "bluetooth", "related", "topics"],"aliases":["налаштування", "radio-config", "user-config", "lora"],"charCount":42190}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5220}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5269}, {"id":"tak","title":"TAK Integration","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/tak.html","navOrder":10,"keywords":["tak", "integration", "overview", "setup", "prerequisites", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "troubleshooting", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10684}, {"id":"telemetry-and-sensors","title":"Телеметрія і сенсори","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "configuring", "choosing", "interval", "metrics", "viewing", "troubleshooting", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10761}, {"id":"translate","title":"Translate the App","section":"user","locale":"uk-rUA","resourcePath":"docs/uk-rUA/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -818,12 +818,12 @@ {"id":"map-and-waypoints","title":"Map & Waypoints","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/map-and-waypoints.html","navOrder":6,"keywords":["map", "waypoints", "view", "node", "markers", "controls", "filtering", "the", "creating", "waypoint", "properties", "expiration", "geofences", "managing", "site", "planner", "position", "sharing", "enabling", "privacy", "considerations", "sources", "adding", "your", "own", "tile", "source", "going", "offline", "related"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":13859}, {"id":"messages-and-channels","title":"Messages & Channels","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/messages-and-channels.html","navOrder":3,"keywords":["messages", "channels", "default", "channel", "adding", "sending", "direct", "message", "managing", "the", "conversation", "list", "bubbles", "states", "delivery", "errors", "features", "quick", "chat", "searching", "text", "formatting", "mentions", "reactions", "replying", "day", "separators", "jump", "latest", "actions"],"aliases":["channels", "direct-messages", "messaging", "conversations"],"charCount":22530}, {"id":"mqtt","title":"MQTT","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/mqtt.html","navOrder":11,"keywords":["mqtt", "how", "works", "configuration", "enabling", "connection", "status", "and", "test", "proxy", "this", "phone", "default", "meshtastic", "broker", "private", "map", "reporting", "uplink", "downlink", "message", "formats", "encryption", "privacy", "best", "practices", "not", "connecting", "messages", "bridging"],"aliases":["mqtt", "internet-bridge", "broker"],"charCount":12355}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "air", "quality", "signal", "reference", "reading", "traceroute", "results", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12264}, - {"id":"nodes","title":"节点","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15378}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "air", "quality", "signal", "reference", "reading", "traceroute", "results", "pax", "related", "topics"],"aliases":["metrics", "telemetry", "device-metrics", "signal"],"charCount":12396}, + {"id":"nodes","title":"节点","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15685}, {"id":"onboarding","title":"Getting Started","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/onboarding.html","navOrder":1,"keywords":["getting", "started", "first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup", "related", "topics"],"aliases":["first-launch", "setup", "intro"],"charCount":8109}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "module-config", "administration"],"charCount":30186}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "configuration", "lora", "modem", "presets", "related", "topics"],"aliases":["设置", "radio-config", "user-config", "lora"],"charCount":40114}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5184}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears", "related", "topics"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":5233}, {"id":"tak","title":"TAK Integration","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/tak.html","navOrder":10,"keywords":["tak", "integration", "setup", "configuration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10643}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "device", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "configuring", "choosing", "interval", "metrics", "viewing", "related", "topics"],"aliases":["sensors", "环境", "weather", "power-metrics"],"charCount":10328}, {"id":"translate","title":"Translate the App","section":"user","locale":"zh-rCN","resourcePath":"docs/zh-rCN/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "how", "contribute", "adding", "new", "language", "translations", "are", "organized", "translation", "guidelines", "questions", "related", "topics"],"aliases":["translate", "crowdin", "localization"],"charCount":5427}, @@ -839,12 +839,12 @@ {"id":"map-and-waypoints","title":"地圖與航點","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/map-and-waypoints.html","navOrder":6,"keywords":["filtering", "the", "map", "waypoint", "geofences", "site", "planner", "adding", "your", "own", "tile", "source", "going", "offline"],"aliases":["map", "waypoints", "gps", "location", "site-planner", "map-layers", "geojson", "kml"],"charCount":12867}, {"id":"messages-and-channels","title":"訊息與頻道","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/messages-and-channels.html","navOrder":3,"keywords":["managing", "the", "conversation", "list", "bubbles", "searching", "messages", "text", "formatting", "mentions", "replying", "day", "separators", "jump", "latest"],"aliases":["頻道", "direct-messages", "messaging", "conversations"],"charCount":21382}, {"id":"mqtt","title":"MQTT","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/mqtt.html","navOrder":11,"keywords":["mqtt", "connection", "status", "and", "test", "proxy", "this", "phone", "meshtastic"],"aliases":["MQTT", "internet-bridge", "broker"],"charCount":10623}, - {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "air", "quality", "signal", "reference", "reading", "traceroute", "results", "pax"],"aliases":["metrics", "遙測", "device-metrics", "signal"],"charCount":12332}, - {"id":"nodes","title":"節點","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15378}, + {"id":"node-metrics","title":"Node Metrics","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/node-metrics.html","navOrder":5,"keywords":["node", "metrics", "viewing", "air", "quality", "signal", "reference", "reading", "traceroute", "results", "pax"],"aliases":["metrics", "遙測", "device-metrics", "signal"],"charCount":12464}, + {"id":"nodes","title":"節點","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/nodes.html","navOrder":4,"keywords":["node", "list", "choosing", "what", "the", "shows", "status", "indicators", "roles", "role", "encryption", "quick", "actions", "sharing", "contact", "filtering", "sorting", "text", "search", "filter", "toggles", "sort", "options", "nodes", "per", "hop", "detail", "device", "links", "want"],"aliases":["node-list", "mesh-nodes", "peers", "hop-histogram"],"charCount":15685}, {"id":"onboarding","title":"新手入門","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/onboarding.html","navOrder":999,"keywords":["first", "launch", "welcome", "screen", "permissions", "bluetooth", "permission", "location", "notifications", "critical", "alerts", "reviewing", "later", "after", "setup"],"aliases":["first-launch", "setup", "intro"],"charCount":15168}, {"id":"settings-module-admin","title":"Settings — Modules & Admin","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/settings-module-admin.html","navOrder":8,"keywords":["settings", "modules", "admin", "mqtt", "module", "serial", "external", "notification", "store", "forward", "range", "test", "telemetry", "canned", "message", "audio", "remote", "hardware", "neighbor", "info", "ambient", "lighting", "detection", "sensor", "paxcounter", "status", "mesh", "beacon", "tak", "device"],"aliases":["modules", "模組設定", "administration"],"charCount":30526}, {"id":"settings-radio-user","title":"Settings — Radio & User","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/settings-radio-user.html","navOrder":7,"keywords":["settings", "radio", "user", "how", "these", "screens", "work", "profile", "applying", "changes", "lora", "modem", "presets", "related", "topics"],"aliases":["設定", "radio-config", "user-config", "LoRa"],"charCount":40402}, - {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":50614}, + {"id":"signal-meter","title":"How the Meshtastic Signal Meter Works","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/signal-meter.html","navOrder":15,"keywords":["how", "the", "meshtastic", "signal", "meter", "works", "rssi", "and", "snr", "decoding", "below", "noise", "floor", "rating", "quality", "diagnosing", "local", "interference", "where", "information", "appears"],"aliases":["signal", "signal-meter", "snr", "rssi"],"charCount":50663}, {"id":"tak","title":"TAK Integration","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/tak.html","navOrder":10,"keywords":["tak", "integration", "local", "server", "roles", "cot", "cursor", "target", "format", "wire", "usage", "with", "atak", "security", "considerations", "related", "topics"],"aliases":["tak", "atak", "team-awareness-kit"],"charCount":10617}, {"id":"telemetry-and-sensors","title":"Telemetry & Sensors","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/telemetry-and-sensors.html","navOrder":9,"keywords":["telemetry", "sensors", "environment", "temperature", "humidity", "air", "quality", "soil", "light", "weather", "and", "other", "readings", "configuring", "choosing", "interval", "metrics", "viewing", "related", "topics"],"aliases":["sensors", "environment", "weather", "power-metrics"],"charCount":10417}, {"id":"translate","title":"Translate the App","section":"user","locale":"zh-rTW","resourcePath":"docs/zh-rTW/user/translate.html","navOrder":17,"keywords":["translate", "the", "app", "what", "gets", "translated", "adding", "new", "language", "how", "translations", "are", "organized", "translation", "guidelines", "questions"],"aliases":["translate", "crowdin", "localization"],"charCount":5403}, diff --git a/main/is-rIS/user/node-metrics.html b/main/is-rIS/user/node-metrics.html index 7490feca53..ff38d4f3ac 100644 --- a/main/is-rIS/user/node-metrics.html +++ b/main/is-rIS/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Íslenska
Meshtastic Docs ↗

🌐 Íslenska — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Lýsing
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperature BME280, BME680, SHT31
Humidity BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Lýsing
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Good < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Signal Quality

Radio signal quality information:

Metric Lýsing
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Good SNR above the preset’s limit
Fair less than 5.5 dB below the limit
Bad 5.5 dB to 7.5 dB below the limit
None more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Lýsing
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Ferilkönnun

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Position Log

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Íslenska
Meshtastic Docs ↗

🌐 Íslenska — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Lýsing
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperature BME280, BME680, SHT31
Humidity BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Lýsing
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Good < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Signal Quality

Radio signal quality information:

Metric Lýsing
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Good SNR above the preset’s limit
Fair less than 5.5 dB below the limit
Bad 5.5 dB to 7.5 dB below the limit
None more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Lýsing
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Ferilkönnun

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Position Log

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/is-rIS/user/nodes.html b/main/is-rIS/user/nodes.html index 50b26f5fd9..2cd0ccdc75 100644 --- a/main/is-rIS/user/nodes.html +++ b/main/is-rIS/user/nodes.html @@ -1 +1 @@ - Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Íslenska
Meshtastic Docs ↗

🌐 Íslenska — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Lýsing
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Remove

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filter Lýsing
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Lýsing
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Last heard Last heard
Distance Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Íslenska
Meshtastic Docs ↗

🌐 Íslenska — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Lýsing
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Remove

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filter Lýsing
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Lýsing
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Last heard Last heard
Distance Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/is-rIS/user/settings-radio-user.html b/main/is-rIS/user/settings-radio-user.html index a26a716715..ab0fab190b 100644 --- a/main/is-rIS/user/settings-radio-user.html +++ b/main/is-rIS/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Íslenska
Meshtastic Docs ↗

🌐 Íslenska — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Lýsing
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Lýsing Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Lýsing Default
Svæði Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Lýsing
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Lýsing
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Lýsing
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Lýsing
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Lýsing
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Lýsing
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Íslenska
Meshtastic Docs ↗

🌐 Íslenska — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Lýsing
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Lýsing Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Lýsing Default
Svæði Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Lýsing
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Lýsing
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Lýsing
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Lýsing
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Lýsing
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Lýsing
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/is-rIS/user/signal-meter.html b/main/is-rIS/user/signal-meter.html index 2549577dc2..249a04b1c6 100644 --- a/main/is-rIS/user/signal-meter.html +++ b/main/is-rIS/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Íslenska
Meshtastic Docs ↗

🌐 Íslenska — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Good Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Fair 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Bad 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
None 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Íslenska
Meshtastic Docs ↗

🌐 Íslenska — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Good Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Fair 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Bad 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
None 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/it-rIT/user/node-metrics.html b/main/it-rIT/user/node-metrics.html index 5c76ac6923..fd3098afe6 100644 --- a/main/it-rIT/user/node-metrics.html +++ b/main/it-rIT/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Italiano
Meshtastic Docs ↗

🌐 Italiano — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Metriche Dispositivo

Basic operating information reported by each node:

Metrico Descrizione
Battery Level Current battery percentage
Tensione Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Tempo di attività Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Metriche Ambientali

Environmental sensor data (requires compatible hardware):

Metrico Sensor Examples
Temperatura BME280, BME680, SHT31
Umidità BME280, BME680, SHT31
Pressione barometrica BME280, BMP280
Resistenza Ai Gas BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metrico Unit Descrizione
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Buono < 1000 Verde
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Rosso
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Qualità Segnale

Radio signal quality information:

Metrico Descrizione
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Conteggio Hop Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Buono SNR above the preset’s limit
Discreto less than 5.5 dB below the limit
Scarso 5.5 dB to 7.5 dB below the limit
Nessuno more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Metriche Alimentazione

Power management telemetry (requires INA sensor or compatible hardware):

Metrico Descrizione
Tensione Per-channel voltage reading
Attuale Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Registro Posizione

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitudine
  • Speed (if moving)
  • Timestamp for each position report

Informazioni Vicinato

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Metriche Host

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

Metriche PAX

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Italiano
Meshtastic Docs ↗

🌐 Italiano — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Metriche Dispositivo

Basic operating information reported by each node:

Metrico Descrizione
Battery Level Current battery percentage
Tensione Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Tempo di attività Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Metriche Ambientali

Environmental sensor data (requires compatible hardware):

Metrico Sensor Examples
Temperatura BME280, BME680, SHT31
Umidità BME280, BME680, SHT31
Pressione barometrica BME280, BMP280
Resistenza Ai Gas BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metrico Unit Descrizione
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Buono < 1000 Verde
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Rosso
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Qualità Segnale

Radio signal quality information:

Metrico Descrizione
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Conteggio Hop Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Buono SNR above the preset’s limit
Discreto less than 5.5 dB below the limit
Scarso 5.5 dB to 7.5 dB below the limit
Nessuno more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Metriche Alimentazione

Power management telemetry (requires INA sensor or compatible hardware):

Metrico Descrizione
Tensione Per-channel voltage reading
Attuale Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Registro Posizione

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitudine
  • Speed (if moving)
  • Timestamp for each position report

Informazioni Vicinato

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Metriche Host

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

Metriche PAX

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/it-rIT/user/nodes.html b/main/it-rIT/user/nodes.html index 475ce1c0e6..ea25282522 100644 --- a/main/it-rIT/user/nodes.html +++ b/main/it-rIT/user/nodes.html @@ -1 +1 @@ - Nodi | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Italiano
Meshtastic Docs ↗

🌐 Italiano — Community translation View in English

Nodi

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Ruolo Descrizione
Client Standard end-user node
Base Client Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Nascosto Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensore Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Oggetti Smarriti Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Elimina

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtro Descrizione
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Descrizione
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Livello batteria Battery
Hop count Hops
Ricevuto più di recente Last heard
Distanza Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nodi | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Italiano
Meshtastic Docs ↗

🌐 Italiano — Community translation View in English

Nodi

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Ruolo Descrizione
Client Standard end-user node
Base Client Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Nascosto Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensore Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Oggetti Smarriti Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Elimina

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtro Descrizione
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Descrizione
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Livello batteria Battery
Hop count Hops
Ricevuto più di recente Last heard
Distanza Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/it-rIT/user/settings-radio-user.html b/main/it-rIT/user/settings-radio-user.html index 8515a86f77..912d2a9a67 100644 --- a/main/it-rIT/user/settings-radio-user.html +++ b/main/it-rIT/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Italiano
Meshtastic Docs ↗

🌐 Italiano — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Impostazioni Utente

User Profile

On Settings → User.

Impostazione Descrizione
Nome Lungo Your display name (up to 39 characters)
Nome Breve 4-character abbreviated name
Messaggio di Stato A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Non messaggiabile Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Radioamatore con licenza (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configurazione

Configurazione Dispositivo

On Settings → Device configuration → Device.

Impostazione Descrizione Predefinito
Ruolo Del Dispositivo Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Modalità Ritrasmissione How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Intervallo Di Trasmissione Info Nodo How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Doppio tocco come pressione pulsante Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
Battito Cuore Led Blink the status LED periodically Abilitato
Fuso Orario POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

Configurazione LoRa

On Settings → LoRa.

Impostazione Descrizione Predefinito
Regione Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Preset Speed/range tradeoff LongFast
Numero di Hop Maximum retransmit hops 3
Potenza di Trasmissione Transmission power (dBm); 0 = max allowed for region 0 (region max)
Sovrascrivi Frequenza Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Usa Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Larghezza di banda Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Slot di Frequenza Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Trasmissione Abilitata Turning this off makes the node receive-only On
Ignora limite di Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Disattivato
Ignora MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
OK per MQTT Allow your packets to be forwarded to MQTT by gateways Disattivato
Migliora guadagno in Ricezione Extra receive gain on SX126x radios; costs a little current Disattivato
Ventola PA disabilitata Turn off the power-amplifier fan on hardware that has one Disattivato

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Velocità SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6,25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3,52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1,95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0,34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0,18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configurazione Schermo

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Impostazione Descrizione
Tieni lo schermo acceso per How long the display stays lit before sleeping
Durata di ogni schermata How often the radio cycles between screens on its own
Modalità schermo Screen layout/density used by the firmware
Unità di misura visualizzata Metric or Imperial on the radio’s screen
Usa formato orologio 12h Show the radio’s clock as 12-hour rather than 24-hour
Intestazione in grassetto Draw the screen’s heading text in bold
Capovolgi schermo Rotate the display 180° for an inverted mounting
Tipo OLED Auto, SSD1306, SH1106, SH1107
Accendi lo schermo al tocco o al movimento Light the screen when the radio is tapped or moved
Orientamento bussola Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Punta sempre a nord Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configurazione Posizione

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Impostazione Descrizione
Modalità GPS (Hardware Fisico) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Intervallo Interrogazione GPS How often the radio asks its GPS for a fix
Intervallo Di Trasmissione How often the position is shared with the mesh
Posizione Smart Broadcast based on movement rather than purely on the clock
Intervallo Intelligente With Smart Position on, the shortest gap between broadcasts
Distanza Intelligente With Smart Position on, how far you must move before broadcasting
Posizione Fissa Use a manually entered latitude, longitude and altitude instead of the GPS
Flag Di Posizione A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configurazione Alimentazione

On Settings → Device configuration → Power.

Impostazione Descrizione
Abilita modalità risparmio energetico Let the radio sleep aggressively between activity
Spegnimento in mancanza di alimentazione Power the device down after external power disappears
Durata super deep sleep How long the deepest sleep state lasts
Tempo minimo di risveglio The shortest time the radio stays awake once woken
Durata attesa Bluetooth How long to wait for a phone to connect before sleeping
Sovrascrivi moltiplicatore ADC Turn on a manual correction for battery-voltage readings
Sovrascrivi rapporto moltiplicatore ADC The correction factor itself, used only when the override is on
Indirizzo INA_2XX I2C della batteria Address of an external INA-series power sensor, if fitted

Configurazione Della Rete

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Impostazione Descrizione
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Password di rete
Ethernet abilitato Use a wired connection on hardware that has one
Modalità IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
Trasmissione UDP Share mesh traffic with other nodes over the local network
Server NTP Time synchronization server
server rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configurazione Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Impostazione Descrizione
Bluetooth attivo Enable/disable BLE radio
Modalità abbinamento Fixed PIN, Random PIN, or No PIN
PIN Fisso PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configurazione Sicurezza

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Impostazione Descrizione
Chiave Pubblica Your node’s public key (read-only)
Chiave Amministratore Keys permitted to administer this node remotely — up to three
Chiave Privata Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Rigenera Chiavi Private Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Console seriale Serial console over the Stream API
Debug log API abilitato Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Modalità Gestita Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup chiavi Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Livello di protezione How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Avvii rimanenti How many device boots the unlocked state survives
Ore alla scadenza Wall-clock lifetime of the unlocked state
Limite di sessione (minuti) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Italiano
Meshtastic Docs ↗

🌐 Italiano — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Impostazioni Utente

User Profile

On Settings → User.

Impostazione Descrizione
Nome Lungo Your display name (up to 39 characters)
Nome Breve 4-character abbreviated name
Messaggio di Stato A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Non messaggiabile Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Radioamatore con licenza (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configurazione

Configurazione Dispositivo

On Settings → Device configuration → Device.

Impostazione Descrizione Predefinito
Ruolo Del Dispositivo Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Modalità Ritrasmissione How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Intervallo Di Trasmissione Info Nodo How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Doppio tocco come pressione pulsante Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
Battito Cuore Led Blink the status LED periodically Abilitato
Fuso Orario POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

Configurazione LoRa

On Settings → LoRa.

Impostazione Descrizione Predefinito
Regione Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Preset Speed/range tradeoff LongFast
Numero di Hop Maximum retransmit hops 3
Potenza di Trasmissione Transmission power (dBm); 0 = max allowed for region 0 (region max)
Sovrascrivi Frequenza Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Usa Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Larghezza di banda Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Slot di Frequenza Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Trasmissione Abilitata Turning this off makes the node receive-only On
Ignora limite di Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Disattivato
Ignora MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
OK per MQTT Allow your packets to be forwarded to MQTT by gateways Disattivato
Migliora guadagno in Ricezione Extra receive gain on SX126x radios; costs a little current Disattivato
Ventola PA disabilitata Turn off the power-amplifier fan on hardware that has one Disattivato

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Velocità SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6,25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3,52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1,95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0,34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0,18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configurazione Schermo

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Impostazione Descrizione
Tieni lo schermo acceso per How long the display stays lit before sleeping
Durata di ogni schermata How often the radio cycles between screens on its own
Modalità schermo Screen layout/density used by the firmware
Unità di misura visualizzata Metric or Imperial on the radio’s screen
Usa formato orologio 12h Show the radio’s clock as 12-hour rather than 24-hour
Intestazione in grassetto Draw the screen’s heading text in bold
Capovolgi schermo Rotate the display 180° for an inverted mounting
Tipo OLED Auto, SSD1306, SH1106, SH1107
Accendi lo schermo al tocco o al movimento Light the screen when the radio is tapped or moved
Orientamento bussola Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Punta sempre a nord Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configurazione Posizione

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Impostazione Descrizione
Modalità GPS (Hardware Fisico) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Intervallo Interrogazione GPS How often the radio asks its GPS for a fix
Intervallo Di Trasmissione How often the position is shared with the mesh
Posizione Smart Broadcast based on movement rather than purely on the clock
Intervallo Intelligente With Smart Position on, the shortest gap between broadcasts
Distanza Intelligente With Smart Position on, how far you must move before broadcasting
Posizione Fissa Use a manually entered latitude, longitude and altitude instead of the GPS
Flag Di Posizione A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configurazione Alimentazione

On Settings → Device configuration → Power.

Impostazione Descrizione
Abilita modalità risparmio energetico Let the radio sleep aggressively between activity
Spegnimento in mancanza di alimentazione Power the device down after external power disappears
Durata super deep sleep How long the deepest sleep state lasts
Tempo minimo di risveglio The shortest time the radio stays awake once woken
Durata attesa Bluetooth How long to wait for a phone to connect before sleeping
Sovrascrivi moltiplicatore ADC Turn on a manual correction for battery-voltage readings
Sovrascrivi rapporto moltiplicatore ADC The correction factor itself, used only when the override is on
Indirizzo INA_2XX I2C della batteria Address of an external INA-series power sensor, if fitted

Configurazione Della Rete

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Impostazione Descrizione
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Password di rete
Ethernet abilitato Use a wired connection on hardware that has one
Modalità IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
Trasmissione UDP Share mesh traffic with other nodes over the local network
Server NTP Time synchronization server
server rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configurazione Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Impostazione Descrizione
Bluetooth attivo Enable/disable BLE radio
Modalità abbinamento Fixed PIN, Random PIN, or No PIN
PIN Fisso PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configurazione Sicurezza

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Impostazione Descrizione
Chiave Pubblica Your node’s public key (read-only)
Chiave Amministratore Keys permitted to administer this node remotely — up to three
Chiave Privata Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Rigenera Chiavi Private Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Console seriale Serial console over the Stream API
Debug log API abilitato Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Modalità Gestita Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup chiavi Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Livello di protezione How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Avvii rimanenti How many device boots the unlocked state survives
Ore alla scadenza Wall-clock lifetime of the unlocked state
Limite di sessione (minuti) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/it-rIT/user/signal-meter.html b/main/it-rIT/user/signal-meter.html index 41c9e20021..9e18333124 100644 --- a/main/it-rIT/user/signal-meter.html +++ b/main/it-rIT/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Italiano
Meshtastic Docs ↗

🌐 Italiano — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Buono Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Discreto 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Scarso 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Nessuno 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Italiano
Meshtastic Docs ↗

🌐 Italiano — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Buono Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Discreto 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Scarso 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Nessuno 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/iw-rIL/user/node-metrics.html b/main/iw-rIL/user/node-metrics.html index e5f25cfa0e..0ece34f9ba 100644 --- a/main/iw-rIL/user/node-metrics.html +++ b/main/iw-rIL/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 עברית
Meshtastic Docs ↗

🌐 עברית — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric תיאור
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperature BME280, BME680, SHT31
Humidity BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit תיאור
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Good < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Signal Quality

Radio signal quality information:

Metric תיאור
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Good SNR above the preset’s limit
Fair less than 5.5 dB below the limit
Bad 5.5 dB to 7.5 dB below the limit
None more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric תיאור
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

בדיקת מסלול

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Position Log

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 עברית
Meshtastic Docs ↗

🌐 עברית — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric תיאור
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperature BME280, BME680, SHT31
Humidity BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit תיאור
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Good < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Signal Quality

Radio signal quality information:

Metric תיאור
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Good SNR above the preset’s limit
Fair less than 5.5 dB below the limit
Bad 5.5 dB to 7.5 dB below the limit
None more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric תיאור
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

בדיקת מסלול

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Position Log

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/iw-rIL/user/nodes.html b/main/iw-rIL/user/nodes.html index 100003a190..5f7e91fb78 100644 --- a/main/iw-rIL/user/nodes.html +++ b/main/iw-rIL/user/nodes.html @@ -1 +1 @@ - Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 עברית
Meshtastic Docs ↗

🌐 עברית — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role תיאור
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Remove

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

פילטר תיאור
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort תיאור
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Last heard Last heard
מרחק Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 עברית
Meshtastic Docs ↗

🌐 עברית — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role תיאור
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Remove

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

פילטר תיאור
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort תיאור
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Last heard Last heard
מרחק Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/iw-rIL/user/settings-radio-user.html b/main/iw-rIL/user/settings-radio-user.html index 3f968eb9a6..39765aeb7d 100644 --- a/main/iw-rIL/user/settings-radio-user.html +++ b/main/iw-rIL/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 עברית
Meshtastic Docs ↗

🌐 עברית — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting תיאור
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting תיאור Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting תיאור Default
אזור Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting תיאור
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting תיאור
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting תיאור
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting תיאור
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting תיאור
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting תיאור
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 עברית
Meshtastic Docs ↗

🌐 עברית — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting תיאור
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting תיאור Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting תיאור Default
אזור Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting תיאור
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting תיאור
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting תיאור
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting תיאור
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting תיאור
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting תיאור
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/iw-rIL/user/signal-meter.html b/main/iw-rIL/user/signal-meter.html index 6c183c253c..36cc1adc7b 100644 --- a/main/iw-rIL/user/signal-meter.html +++ b/main/iw-rIL/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 עברית
Meshtastic Docs ↗

🌐 עברית — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Good Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Fair 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Bad 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
None 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 עברית
Meshtastic Docs ↗

🌐 עברית — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Good Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Fair 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Bad 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
None 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/ja-rJP/user/node-metrics.html b/main/ja-rJP/user/node-metrics.html index f214a71483..16d618ca7b 100644 --- a/main/ja-rJP/user/node-metrics.html +++ b/main/ja-rJP/user/node-metrics.html @@ -1 +1 @@ - ノードメトリクス | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 日本語
Meshtastic Docs ↗

🌐 日本語 — Community translation View in English

ノードメトリクス

ノードの詳細画面では、メッシュ上の各ノードについて、包括的なテレメトリとメトリクスを確認できます。

メトリクスを表示する

  1. ノード」に移動します。
  2. 確認したいノードをタップします。
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

ノードの詳細:ローカルデバイス

The Position row expands to show location data for nodes that share GPS:

位置のインラインコンテンツ

ℹ️ Note: Metrics are only available when they have been reported by the remote node. メトリクスは、各ノードのテレメトリ設定で構成された間隔で更新されます。

デバイスメトリクス

各ノードが報告する基本的な動作情報です:

メトリクス 説明
バッテリー残量 現在のバッテリー残量(%)
電圧 バッテリー電圧の測定値
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
連続稼働時間 前回の再起動からの経過時間

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

環境メトリクス

環境センサーのデータです(対応ハードウェアが必要):

メトリクス センサーの例
温度 BME280, BME680, SHT31
湿度 BME280, BME680, SHT31
大気圧 BME280, BMP280
ガス抵抗 BME680
IAQ(大気質) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

BME680 の **IAQ(室内空気質)**指数は、ガス抵抗から算出される 0〜500+ の単一の値で、非常に良い から 危険なほど汚染 までの色分けされたスケールで表示されます:

「非常に良い」から「危険なほど汚染」までの IAQ 指数スケール

💡 ヒント: 環境メトリクスには、リモートノードに接続されたセンサーが必要です。 すべてのノードが環境データを報告するわけではありません。 対応センサーの一覧については、テレメトリとセンサー を参照してください。

大気質メトリクス

大気質は、粒子状物質センサーや CO₂ センサーを搭載したノード向けの専用メトリクスビューです。 これは、環境メトリクスに記載されている BME680 の IAQ の測定値とは別のものです。IAQ はガス抵抗から算出される単一の指数であるのに対し、大気質ビューはその基となる粒子状物質と CO₂ の測定値をグラフ化します。

メトリクス 単位 説明
PM1.0 µg/m³ 1.0 ミクロンまでの粒子状物質
PM2.5 µg/m³ 2.5 ミクロンまでの粒子状物質
PM10 µg/m³ 10 ミクロンまでの粒子状物質
AQI EPA 指数 EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. 十分な測定値が蓄積されると、PM2.5 の横に表示されます。
CO₂ ppm 二酸化炭素の濃度
CO₂ 温度 °C / °F CO₂ センサー自体が報告する温度(例:SCD4x)
CO₂ 湿度 % CO₂ センサーが報告する相対湿度

CO₂ readings are color-coded by severity so you can read air quality at a glance:

区分 CO₂ の範囲(ppm)
< 1000
空気がこもる < 2000 黄色
不良 < 5000 オレンジ
危険 < 30000
退避 ≥ 30000 濃い赤

CO₂ の深刻度が色分けされた大気質の測定値

大気質のログ/メトリクスボタンは、ノードが大気質のテレメトリを報告したときにのみ、ノードの詳細画面に表示されます。 大気質ビューでは、次のことができます:

  • グラフの期間を選択します。
  • メトリクスチップで絞り込みます。データがあるメトリクスのみが表示されます。
  • 最新の大気質テレメトリを更新/要求します。
  • 表計算ソフトで分析できるよう、CSV にエクスポートします。

💡 ヒント: 大気質メトリクスには、リモートノードに対応する大気質センサーが必要です。 対応ハードウェアについては、テレメトリとセンサー を参照してください。

信号品質

無線信号の品質に関する情報です:

メトリクス 説明
SN比 信号対ノイズ比(高いほど良い)
RSSI 受信信号強度インジケーター(0 に近いほど良い)
ノイズフロア ローカルの背景 RF ノイズ(dBm、値が小さい(負が大きい)ほど静か)
ホップ数 直前のメッセージのメッシュホップ数

信号品質の目安

信号品質は、固定のしきい値ではなく、現在の LoRa モデムプリセットの復調限界に対する SNR で評価されます。同じ SNR でもプリセットによって意味が異なります(例:−15 dB は LongSlow では問題ありませんが、ShortFast では使い物になりません)。 RSSI は表示されますが、評価には含まれません。 In the table, limit is the preset’s SNR limit.

品質 基準
SNR がプリセットの限界を上回る
普通 限界より 5.5 dB 未満低い
不良 限界より 5.5 dB〜7.5 dB 低い
なし 限界より 7.5 dB を超えて低い

詳しい説明は、信号メーターを理解する を参照してください。

接続中の無線機のローカル統計も、利用可能な場合は信号品質に表示されます。 これらのログには、ノイズフロア、トラフィックカウンター、中継カウンター、オンラインノード数、無線機の連続稼働時間が含まれます。 ノイズフロアのグラフでは、混雑した RF 環境を見分けやすいよう、-85 dBm に破線の基準線が引かれます。

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

電力メトリクス

電力管理のテレメトリです(INA センサーまたは対応ハードウェアが必要):

メトリクス 説明
電圧 Per-channel voltage reading
電流 Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

ルート追跡

ルート追跡は、メッセージがメッシュ内を通る経路を表示します:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. アプリが対象のノードにルート追跡の要求を送信します。
  3. Results show each hop with its SNR.

ルート追跡の結果の見方

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

位置ログ

位置情報を共有しているノードの、過去の位置データです:

  • GPS 座標
  • 標高
  • 速度(移動中の場合)
  • 各位置報告のタイムスタンプ

隣接ノード情報

あるノードが直接受信できるノードを表示します。メッシュのトポロジーを把握するのに役立ちます。

ホストのメトリクス

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX メトリクス

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.

関連トピック


+ ノードメトリクス | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 日本語
Meshtastic Docs ↗

🌐 日本語 — Community translation View in English

ノードメトリクス

ノードの詳細画面では、メッシュ上の各ノードについて、包括的なテレメトリとメトリクスを確認できます。

メトリクスを表示する

  1. ノード」に移動します。
  2. 確認したいノードをタップします。
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

ノードの詳細:ローカルデバイス

The Position row expands to show location data for nodes that share GPS:

位置のインラインコンテンツ

ℹ️ Note: Metrics are only available when they have been reported by the remote node. メトリクスは、各ノードのテレメトリ設定で構成された間隔で更新されます。

デバイスメトリクス

各ノードが報告する基本的な動作情報です:

メトリクス 説明
バッテリー残量 現在のバッテリー残量(%)
電圧 バッテリー電圧の測定値
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
連続稼働時間 前回の再起動からの経過時間

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

環境メトリクス

環境センサーのデータです(対応ハードウェアが必要):

メトリクス センサーの例
温度 BME280, BME680, SHT31
湿度 BME280, BME680, SHT31
大気圧 BME280, BMP280
ガス抵抗 BME680
IAQ(大気質) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

BME680 の **IAQ(室内空気質)**指数は、ガス抵抗から算出される 0〜500+ の単一の値で、非常に良い から 危険なほど汚染 までの色分けされたスケールで表示されます:

「非常に良い」から「危険なほど汚染」までの IAQ 指数スケール

💡 ヒント: 環境メトリクスには、リモートノードに接続されたセンサーが必要です。 すべてのノードが環境データを報告するわけではありません。 対応センサーの一覧については、テレメトリとセンサー を参照してください。

大気質メトリクス

大気質は、粒子状物質センサーや CO₂ センサーを搭載したノード向けの専用メトリクスビューです。 これは、環境メトリクスに記載されている BME680 の IAQ の測定値とは別のものです。IAQ はガス抵抗から算出される単一の指数であるのに対し、大気質ビューはその基となる粒子状物質と CO₂ の測定値をグラフ化します。

メトリクス 単位 説明
PM1.0 µg/m³ 1.0 ミクロンまでの粒子状物質
PM2.5 µg/m³ 2.5 ミクロンまでの粒子状物質
PM10 µg/m³ 10 ミクロンまでの粒子状物質
AQI EPA 指数 EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. 十分な測定値が蓄積されると、PM2.5 の横に表示されます。
CO₂ ppm 二酸化炭素の濃度
CO₂ 温度 °C / °F CO₂ センサー自体が報告する温度(例:SCD4x)
CO₂ 湿度 % CO₂ センサーが報告する相対湿度

CO₂ readings are color-coded by severity so you can read air quality at a glance:

区分 CO₂ の範囲(ppm)
< 1000
空気がこもる < 2000 黄色
不良 < 5000 オレンジ
危険 < 30000
退避 ≥ 30000 濃い赤

CO₂ の深刻度が色分けされた大気質の測定値

大気質のログ/メトリクスボタンは、ノードが大気質のテレメトリを報告したときにのみ、ノードの詳細画面に表示されます。 大気質ビューでは、次のことができます:

  • グラフの期間を選択します。
  • メトリクスチップで絞り込みます。データがあるメトリクスのみが表示されます。
  • 最新の大気質テレメトリを更新/要求します。
  • 表計算ソフトで分析できるよう、CSV にエクスポートします。

💡 ヒント: 大気質メトリクスには、リモートノードに対応する大気質センサーが必要です。 対応ハードウェアについては、テレメトリとセンサー を参照してください。

信号品質

無線信号の品質に関する情報です:

メトリクス 説明
SN比 信号対ノイズ比(高いほど良い)
RSSI 受信信号強度インジケーター(0 に近いほど良い)
ノイズフロア ローカルの背景 RF ノイズ(dBm、値が小さい(負が大きい)ほど静か)
ホップ数 直前のメッセージのメッシュホップ数

信号品質の目安

信号品質は、固定のしきい値ではなく、現在の LoRa モデムプリセットの復調限界に対する SNR で評価されます。同じ SNR でもプリセットによって意味が異なります(例:−15 dB は LongSlow では問題ありませんが、ShortFast では使い物になりません)。 When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

品質 基準
SNR がプリセットの限界を上回る
普通 限界より 5.5 dB 未満低い
不良 限界より 5.5 dB〜7.5 dB 低い
なし 限界より 7.5 dB を超えて低い

詳しい説明は、信号メーターを理解する を参照してください。

接続中の無線機のローカル統計も、利用可能な場合は信号品質に表示されます。 これらのログには、ノイズフロア、トラフィックカウンター、中継カウンター、オンラインノード数、無線機の連続稼働時間が含まれます。 ノイズフロアのグラフでは、混雑した RF 環境を見分けやすいよう、-85 dBm に破線の基準線が引かれます。

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

電力メトリクス

電力管理のテレメトリです(INA センサーまたは対応ハードウェアが必要):

メトリクス 説明
電圧 Per-channel voltage reading
電流 Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

ルート追跡

ルート追跡は、メッセージがメッシュ内を通る経路を表示します:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. アプリが対象のノードにルート追跡の要求を送信します。
  3. Results show each hop with its SNR.

ルート追跡の結果の見方

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

位置ログ

位置情報を共有しているノードの、過去の位置データです:

  • GPS 座標
  • 標高
  • 速度(移動中の場合)
  • 各位置報告のタイムスタンプ

隣接ノード情報

あるノードが直接受信できるノードを表示します。メッシュのトポロジーを把握するのに役立ちます。

ホストのメトリクス

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX メトリクス

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.

関連トピック


diff --git a/main/ja-rJP/user/nodes.html b/main/ja-rJP/user/nodes.html index d1694cd1fa..a30b598403 100644 --- a/main/ja-rJP/user/nodes.html +++ b/main/ja-rJP/user/nodes.html @@ -1 +1 @@ - ノード | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 日本語
Meshtastic Docs ↗

🌐 日本語 — Community translation View in English

ノード

The Nodes screen lists every node visible on your mesh.

ノードリスト

ノードリストには、無線機が受信したすべてのノードが、次の情報とともに表示されます:

  • ノード名: ユーザーが設定した正式名称
  • 短縮名: 4 文字の識別子
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • 最後の通信: 最後に通信してからの経過時間
  • 距離: 推定距離(位置情報が共有されている場合)
  • バッテリー: リモートノードのバッテリー残量(テレメトリが有効な場合)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

ノードのステータス表示

指標 意味
Green last-heard time 過去 2 時間以内に受信したノード
Plain last-heard time 2 時間を超えて受信していないノード
⭐ お気に入り Node you marked as a favorite.

There is no separate “away” tier.

ノードの役割

ノードには、メッシュ上での動作に影響するさまざまな役割を設定できます:

役割 説明
クライアント Standard end-user node
クライアント・ベース お気に入りノードの通信をルーター・レイトの優先度で扱い、それ以外の通信はクライアントとして扱います
クライアント・ミュート 受信しますが、再送信はしません
クライアント・非表示 クライアント・ミュートと同様で、さらにノードリストから隠れます
ルーター メッセージの転送を優先し、中継のために起動し続けます
ルーター・レイト 1 回だけ再送信するインフラノードですが、他のすべてのモードの後にのみ行います(補助的なカバレッジを提供します)
ルーター・クライアント ⚠️ 非推奨(ファームウェア 2.3.15 で削除)。選択できなくなりました。代わりにルーターまたはクライアントを使用してください
リピーター ⚠️ 非推奨(ファームウェア 2.7.11 で削除)。選択できなくなりました。代わりにルーターを使用してください
トラッカー 一定間隔での位置報告に最適化されています
センサー テレメトリ報告に最適化されています
TAK TAK システムと相互運用します(CoT を送受信)
TAK Tracker TAK の位置報告のみ
紛失モード Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

役割を選ぶ

ほとんどのユーザーは、デフォルトのクライアント役割のままにしてください。 次のような場合は、別の役割を検討してください:

  • ルーター: 電源が安定した、固定された高所(屋上、丘の上など)にノードを設置している場合。 ルーターは他のノードのメッセージを中継するために常に起動し続け、メッシュのカバレッジ拡大に不可欠です。 Don’t use Router on battery-powered handheld radios.
  • ルーター・レイト: パケットを常に 1 回だけ再送信するインフラノードですが、他のすべてのルーティングモードの番が終わった後にのみ行います。 主要なルーターと競合することなく、ローカルのクラスターに補助的なカバレッジを提供します。
  • クライアント・ベース: お気に入りノードとの間の通信をルーター・レイトの優先度で扱い(それらのメッセージが追加の中継カバレッジを得られるようにします)、それ以外はすべて通常のクライアントとして処理します。
  • クライアント・ミュート: メッシュの通信を受信したいが、中継には貢献したくない場合。 Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). 発信の合間はスリープしてバッテリーを節約します。
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). 電力プロファイルはトラッカーと同様です。
  • TAK/TAK Tracker: ATAK/WinTAK システムと相互運用する場合にのみ必要です。 詳しくは TAK 連携 を参照してください。

💡 ヒント: メッシュは、ほとんどのノードがクライアントまたはルーターのときに最も良く機能します。 Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. 目安としては、地域内のクライアント 5〜10 台につきルーター 1 台です。

暗号化の表示

ノードは、名前の横に暗号化ステータスのアイコンを表示します:

アイコン 意味
🔒 ロック 通信は PKI(公開鍵基盤)を使用します。本人性が検証された、エンドツーエンドの暗号化です
🔓 ロック解除 No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ 不一致 公開鍵の不一致。前回確認時からノードの鍵が変わっています(信頼する前に調べてください)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. 鍵の不一致の警告が表示された場合、そのノードはリセットされたか、侵害された可能性があります。

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

クイック操作

ノードリストから、次のことができます:

  • ノードをタップすると詳細ページを表示します
  • Touch & hold for quick actions:
    • お気に入りに追加/解除
    • 通知のミュート/解除
    • ダイレクトメッセージを送信
    • 経路をトレース
    • 無視/無視の解除
    • 削除

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

絞り込みと並べ替え

テキスト検索

検索欄に入力すると、名前または短縮名でノードを絞り込めます。 絞り込みは、入力に応じてリアルタイムで更新されます。

絞り込みトグル

絞り込み 説明
Hide offline nodes 過去 2 時間以内に受信したノードのみを表示します
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
不明なノードを含む Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
インフラを除外 Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
MQTT を除外 MQTT のインターネットブリッジ経由でのみ受信したノードを非表示にします
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

並べ替えオプション

並べ替え 説明
Last heard 最近受信したノードを先頭に表示します
A-Z ノードの正式名称で並べ替えます
距離 近いノードを先頭に表示します(位置情報の共有が必要)
ホップ数 中継ホップ数が少ないノードを先頭に表示します
チャンネル チャンネルインデックスごとにグループ化します
via MQTT MQTT 経由と無線受信でグループ化します
via Favorite (default) Favorited nodes first, then the rest

ホップごとのノード数

ノードリストのアプリバーにあるホップヒストグラムのアイコンをタップすると、各ホップ距離にいくつのノードがあるかを示す棒グラフが開きます(0 = 直接、1 = 中継 1 回、以下同様)。 グラフを最後の通信の期間(すべての期間、1 時間、8 時間、24 時間)で絞り込むと、現在のメッシュの様子と、より長い期間での様子を比較できます。 ローカルメッシュがどれだけ混雑し、どれだけ広がっているかを手早く把握できます。

ノードの詳細

ノードをタップすると、詳しい情報を含む詳細ビューが開きます。 メトリクスとテレメトリの詳細については、ノードメトリクス を参照してください。

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

ノードの詳細セクション

インラインのステータス表示で、主要なメトリクスをひと目で確認できます:

指標 スクリーンショット
信号品質 信号
バッテリー残量 バッテリー
ホップ数 ホップ
最後の通信 最後の通信
距離 距離

デバイスのリンク(「購入はこちら」)

ノードのハードウェアが認識されると、詳細ビューに折りたたみ式の**「購入はこちら」**セクションが表示され、そのデバイスを購入したり詳しく知ったりできる場所(ベンダーの製品ページ、製品バリエーション、AliExpress・Amazon・対応小売店などの地域のマーケットプレイスの掲載)が、あなたの国に合わせて絞り込まれて表示されます。 各リンクは msh.to のリダイレクトサービスを通じて開きます。 一致するリンクがないデバイスでは、このセクションは表示されません。

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

関連トピック


+ ノード | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 日本語
Meshtastic Docs ↗

🌐 日本語 — Community translation View in English

ノード

The Nodes screen lists every node visible on your mesh.

ノードリスト

ノードリストには、無線機が受信したすべてのノードが、次の情報とともに表示されます:

  • ノード名: ユーザーが設定した正式名称
  • 短縮名: 4 文字の識別子
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • 最後の通信: 最後に通信してからの経過時間
  • 距離: 推定距離(位置情報が共有されている場合)
  • バッテリー: リモートノードのバッテリー残量(テレメトリが有効な場合)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

ノードのステータス表示

指標 意味
Green last-heard time 過去 2 時間以内に受信したノード
Plain last-heard time 2 時間を超えて受信していないノード
⭐ お気に入り Node you marked as a favorite.

There is no separate “away” tier.

ノードの役割

ノードには、メッシュ上での動作に影響するさまざまな役割を設定できます:

役割 説明
クライアント Standard end-user node
クライアント・ベース お気に入りノードの通信をルーター・レイトの優先度で扱い、それ以外の通信はクライアントとして扱います
クライアント・ミュート 受信しますが、再送信はしません
クライアント・非表示 クライアント・ミュートと同様で、さらにノードリストから隠れます
ルーター メッセージの転送を優先し、中継のために起動し続けます
ルーター・レイト 1 回だけ再送信するインフラノードですが、他のすべてのモードの後にのみ行います(補助的なカバレッジを提供します)
ルーター・クライアント ⚠️ 非推奨(ファームウェア 2.3.15 で削除)。選択できなくなりました。代わりにルーターまたはクライアントを使用してください
リピーター ⚠️ 非推奨(ファームウェア 2.7.11 で削除)。選択できなくなりました。代わりにルーターを使用してください
トラッカー 一定間隔での位置報告に最適化されています
センサー テレメトリ報告に最適化されています
TAK TAK システムと相互運用します(CoT を送受信)
TAK Tracker TAK の位置報告のみ
紛失モード Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

役割を選ぶ

ほとんどのユーザーは、デフォルトのクライアント役割のままにしてください。 次のような場合は、別の役割を検討してください:

  • ルーター: 電源が安定した、固定された高所(屋上、丘の上など)にノードを設置している場合。 ルーターは他のノードのメッセージを中継するために常に起動し続け、メッシュのカバレッジ拡大に不可欠です。 Don’t use Router on battery-powered handheld radios.
  • ルーター・レイト: パケットを常に 1 回だけ再送信するインフラノードですが、他のすべてのルーティングモードの番が終わった後にのみ行います。 主要なルーターと競合することなく、ローカルのクラスターに補助的なカバレッジを提供します。
  • クライアント・ベース: お気に入りノードとの間の通信をルーター・レイトの優先度で扱い(それらのメッセージが追加の中継カバレッジを得られるようにします)、それ以外はすべて通常のクライアントとして処理します。
  • クライアント・ミュート: メッシュの通信を受信したいが、中継には貢献したくない場合。 Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). 発信の合間はスリープしてバッテリーを節約します。
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). 電力プロファイルはトラッカーと同様です。
  • TAK/TAK Tracker: ATAK/WinTAK システムと相互運用する場合にのみ必要です。 詳しくは TAK 連携 を参照してください。

💡 ヒント: メッシュは、ほとんどのノードがクライアントまたはルーターのときに最も良く機能します。 Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. 目安としては、地域内のクライアント 5〜10 台につきルーター 1 台です。

暗号化の表示

ノードは、名前の横に暗号化ステータスのアイコンを表示します:

アイコン 意味
🔒 ロック 通信は PKI(公開鍵基盤)を使用します。本人性が検証された、エンドツーエンドの暗号化です
🔓 ロック解除 No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ 不一致 公開鍵の不一致。前回確認時からノードの鍵が変わっています(信頼する前に調べてください)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. 鍵の不一致の警告が表示された場合、そのノードはリセットされたか、侵害された可能性があります。

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

クイック操作

ノードリストから、次のことができます:

  • ノードをタップすると詳細ページを表示します
  • Touch & hold for quick actions:
    • お気に入りに追加/解除
    • 通知のミュート/解除
    • ダイレクトメッセージを送信
    • 経路をトレース
    • 無視/無視の解除
    • 削除

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

絞り込みと並べ替え

テキスト検索

検索欄に入力すると、名前または短縮名でノードを絞り込めます。 絞り込みは、入力に応じてリアルタイムで更新されます。

絞り込みトグル

絞り込み 説明
Hide offline nodes 過去 2 時間以内に受信したノードのみを表示します
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
不明なノードを含む Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
インフラを除外 Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
MQTT を除外 MQTT のインターネットブリッジ経由でのみ受信したノードを非表示にします
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

並べ替えオプション

並べ替え 説明
Last heard 最近受信したノードを先頭に表示します
A-Z ノードの正式名称で並べ替えます
距離 近いノードを先頭に表示します(位置情報の共有が必要)
ホップ数 中継ホップ数が少ないノードを先頭に表示します
チャンネル チャンネルインデックスごとにグループ化します
via MQTT MQTT 経由と無線受信でグループ化します
via Favorite (default) Favorited nodes first, then the rest

ホップごとのノード数

ノードリストのアプリバーにあるホップヒストグラムのアイコンをタップすると、各ホップ距離にいくつのノードがあるかを示す棒グラフが開きます(0 = 直接、1 = 中継 1 回、以下同様)。 グラフを最後の通信の期間(すべての期間、1 時間、8 時間、24 時間)で絞り込むと、現在のメッシュの様子と、より長い期間での様子を比較できます。 ローカルメッシュがどれだけ混雑し、どれだけ広がっているかを手早く把握できます。

ノードの詳細

ノードをタップすると、詳しい情報を含む詳細ビューが開きます。 メトリクスとテレメトリの詳細については、ノードメトリクス を参照してください。

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

ノードの詳細セクション

インラインのステータス表示で、主要なメトリクスをひと目で確認できます:

指標 スクリーンショット
信号品質 信号
バッテリー残量 バッテリー
ホップ数 ホップ
最後の通信 最後の通信
距離 距離

デバイスのリンク(「購入はこちら」)

ノードのハードウェアが認識されると、詳細ビューに折りたたみ式の**「購入はこちら」**セクションが表示され、そのデバイスを購入したり詳しく知ったりできる場所(ベンダーの製品ページ、製品バリエーション、AliExpress・Amazon・対応小売店などの地域のマーケットプレイスの掲載)が、あなたの国に合わせて絞り込まれて表示されます。 各リンクは msh.to のリダイレクトサービスを通じて開きます。 一致するリンクがないデバイスでは、このセクションは表示されません。

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

関連トピック


diff --git a/main/ja-rJP/user/settings-radio-user.html b/main/ja-rJP/user/settings-radio-user.html index 2319c90a6f..a6b7037bd4 100644 --- a/main/ja-rJP/user/settings-radio-user.html +++ b/main/ja-rJP/user/settings-radio-user.html @@ -1 +1 @@ - 設定:無線機とユーザー | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 日本語
Meshtastic Docs ↗

🌐 日本語 — Community translation View in English

設定:無線機とユーザー

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

設定には、標準的な設定コントロール(ドロップダウン、トグル、スライダー)を使用します:

コントロール スクリーンショット
ドロップダウン A dropdown setting, expanded to show its list of options
トグル A toggle setting in the on position
スライダー A slider setting with its current numeric value shown

ユーザー設定

ユーザープロファイル

On Settings → User.

設定項目 説明
正式名称 表示名(最大 39 文字)
短縮名 4 文字の短縮名
ステータスメッセージ A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
メッセージ不可 Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
アマチュア無線従事者 (ハム/HAM) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

変更を適用する

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

設定

デバイスの設定

On Settings → Device configuration → Device.

設定項目 説明 デフォルト
デバイスの役割 Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
再ブロードキャストモード How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
ノード情報のブロードキャスト間隔 How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
ダブルタップをボタンとして使用 Treat a double tap as a button press 無効
トリプルクリックでアドホック Ping Send an ad-hoc position ping on a triple click 無効
LED ハートビート Blink the status LED periodically 有効
タイムゾーン POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa設定

On Settings → LoRa.

設定項目 説明 デフォルト
リージョン Regulatory region for frequency bands. You must set this before transmitting 未設定(要設定)
プリセット 速度と距離のトレードオフ LongFast
ホップ数 再送信の最大ホップ数 3
送信出力 送信出力(dBm)。0 = リージョンで許可された最大値 0(リージョン最大)
周波数の上書き Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
プリセットを使用 On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
拡散率 Manual mode only: 7–12. Higher spreads further but slower From preset
符号化レート Manual mode only: 5–8. More redundancy costs airtime From preset
帯域 Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
周波数スロット Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
送信を有効化 Turning this off makes the node receive-only On
デューティサイクルを上書き Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits オフ
MQTT を無視 Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
MQTT への送信を許可 Allow your packets to be forwarded to MQTT by gateways オフ
RX ブーストゲイン Extra receive gain on SX126x radios; costs a little current オフ
PAファン無効 Turn off the power-amplifier fan on hardware that has one オフ

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. 詳しくは、meshtastic.org の リージョン設定ガイド を参照してください。

モデムプリセット

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 ヒント: SNR 限界の値は意図的に負の数になっています。 LoRa はノイズフロアを下回る信号でも復調できるため、より負の大きい限界値ほど、そのプリセットは弱くノイズの多い信号に耐えられます(より遠くまで届きます)。 詳しい説明は、信号メーターの仕組み を参照してください。

プリセット 距離 速度 SNR 限界 最適な用途
Short Turbo ~1 km 21.9 kbps −7.5 dB 見通しのある高密度な都市部。データ量の多い用途
Short Fast ~3 km 10.9 kbps −7.5 dB 都市の住宅街。数ブロック以内の建物
Short Slow ~5 km 6.25 kbps −10 dB 郊外の短距離。中程度の建物密度
Medium Fast ~5 km 3.52 kbps −12.5 dB 郊外エリア。中程度の建物密度
Medium Slow ~8 km 1.95 kbps −15 dB 郊外・地方。中程度の距離で低速
Long Turbo ~10 km 1.34 kbps −12.5 dB Long Fast と同程度の距離だが 500 kHz 帯域幅。スループットが速い
Long Fast ~10 km 1.1 kbps −17.5 dB 一般用途(デフォルト):距離と速度のバランスが良い
Long Moderate ~20 km 0.34 kbps −17.5 dB 起伏のある地方。ときどき使う用途
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD 帯(125 kHz 帯域幅)。Medium Fast に相当
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD 帯(125 kHz 帯域幅)。Long Fast に相当
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz 帯(62.5 kHz 帯域幅)。他のデバイスとの干渉を避ける
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz 帯(62.5 kHz 帯域幅)。Long Fast に相当
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ 非推奨:まだ選択できますが、将来のファームウェアリリースで削除される可能性があります
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ 非推奨:まだ選択できますが、将来のファームウェアリリースで削除される可能性があります

ℹ️ 注意: この表では、一般的な短い名前を使用しています。 The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

モデムプリセットを選ぶ

モデムプリセットは、距離データ速度の基本的なトレードオフを制御します:

  • 遅いプリセットは拡散をより多く使い、より弱い信号レベルでも復調できるようにします(SNR 限界が低い)。 これは、より遠くまで届く一方で、1 秒あたりのバイト数が少ないことを意味します。
  • 速いプリセットは 1 回の送信でより多くのデータを詰め込みますが、復調にはより強い信号が必要です。

実用的な指針:

  • 都市部のメッシュ(多数のノード、短距離): Long Fast(デフォルト)または Short Fast を使用します。 速度が速いほど、多くのノードがチャンネルを共有するときの電波利用時間の輻輳が減ります。
  • 地方・まばらなメッシュ(少数のノード、長距離): Long Moderate を使用します。 ノードが離れている場合は、速度よりも距離が重要です。
  • EU 866/868 MHz の規制対応: Lite FastLite SlowNarrow FastNarrow Slow を使用します。これらは、より狭い帯域幅で EU の SRD/868 MHz 帯に最適化されています。
  • 固定インフラのリンク: 良好なアンテナと見通しがある専用のポイントツーポイントリンクには、Short Turbo または Long Turbo を使用します。
  • 混在した環境: Long Fast のままにします。これはコミュニティのデフォルトで、地域内の他のユーザーとの互換性を確保します。

All nodes on the same channel must use the same modem preset. プリセットが一致しないノードは、同じ周波数と暗号化鍵を共有していても通信できません。

The range estimates in the Modem Presets table assume flat terrain and modest antennas. 高所(丘の上、屋上)にあると、実効的な距離が大幅に伸びます。 適切に設置された Long Fast のルーターは、地上に置かれた Long Slow のノードを上回ることがよくあります。

表示設定

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

設定項目 説明
画面オンの時間 How long the display stays lit before sleeping
カルーセルの間隔 How often the radio cycles between screens on its own
表示モード Screen layout/density used by the firmware
表示単位 Metric or Imperial on the radio’s screen
12時間の時計形式を使用 Show the radio’s clock as 12-hour rather than 24-hour
太字の見出し Draw the screen’s heading text in bold
画面反転 Rotate the display 180° for an inverted mounting
OLED タイプ 自動、SSD1306、SH1106、SH1107
タップまたは動作で起動 Light the screen when the radio is tapped or moved
コンパスの向き Rotation offset for the compass rose (0°, 90°, 180°, 270°)
常に北を上にする Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

位置情報設定

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

設定項目 説明
GPS モード(物理ハードウェア) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS ポーリング間隔 How often the radio asks its GPS for a fix
ブロードキャスト間隔 How often the position is shared with the mesh
スマート位置 Broadcast based on movement rather than purely on the clock
スマート間隔 With Smart Position on, the shortest gap between broadcasts
スマート距離 With Smart Position on, how far you must move before broadcasting
固定位置 Use a manually entered latitude, longitude and altitude instead of the GPS
位置情報フラグ A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

電源設定

On Settings → Device configuration → Power.

設定項目 説明
省電力モードを有効化 Let the radio sleep aggressively between activity
電源喪失時にシャットダウン Power the device down after external power disappears
スーパーディープスリープの時間 How long the deepest sleep state lasts
最小起動時間 The shortest time the radio stays awake once woken
Bluetooth 待機時間 How long to wait for a phone to connect before sleeping
ADC倍率のオーバーライド Turn on a manual correction for battery-voltage readings
ADC倍率のオーバーライド比 The correction factor itself, used only when the override is on
バッテリー INA_2XX I2C アドレス Address of an external INA-series power sensor, if fitted

ネットワーク設定

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

設定項目 説明
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
パスワード ネットワークのパスワード
イーサネット有効 Use a wired connection on hardware that has one
IPv4 モード DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP ブロードキャスト Share mesh traffic with other nodes over the local network
NTPサーバー 時刻同期サーバー
rsyslogサーバー リモートログサーバー

Network Config with a static IPv4 address entered

Bluetooth 設定

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

設定項目 説明
Bluetoothを有効 BLE 無線の有効/無効
ペアリングモード 固定 PIN、ランダム PIN、または PIN なし
固定 PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

セキュリティ設定

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

設定項目 説明
公開鍵 ノードの公開鍵(読み取り専用)
管理者鍵 Keys permitted to administer this node remotely — up to three
秘密鍵 Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
秘密鍵を再生成 Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
管理チャンネルを有効化 ⚠️ 削除されました:管理者キーを設定すると自動的に構成されるようになりました
シリアルコンソール Serial console over the Stream API
デバッグログAPIを有効化 Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
管理モード Restrict non-admin channel changes. Only selectable once an Admin Key is set
鍵をバックアップ Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
鍵を復元 バックアップした鍵をノードに書き戻します(バックアップがある場合に利用可能)
鍵のバックアップを削除 Remove the stored key backup from this phone
保護レベル How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field 内容
残りの起動回数 How many device boots the unlocked state survives
有効期限までの時間 Wall-clock lifetime of the unlocked state
セッション上限(分) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

関連トピック


+ 設定:無線機とユーザー | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 日本語
Meshtastic Docs ↗

🌐 日本語 — Community translation View in English

設定:無線機とユーザー

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

設定には、標準的な設定コントロール(ドロップダウン、トグル、スライダー)を使用します:

コントロール スクリーンショット
ドロップダウン A dropdown setting, expanded to show its list of options
トグル A toggle setting in the on position
スライダー A slider setting with its current numeric value shown

ユーザー設定

ユーザープロファイル

On Settings → User.

設定項目 説明
正式名称 表示名(最大 39 文字)
短縮名 4 文字の短縮名
ステータスメッセージ A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
メッセージ不可 Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
アマチュア無線従事者 (ハム/HAM) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

変更を適用する

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

設定

デバイスの設定

On Settings → Device configuration → Device.

設定項目 説明 デフォルト
デバイスの役割 Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
再ブロードキャストモード How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
ノード情報のブロードキャスト間隔 How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
ダブルタップをボタンとして使用 Treat a double tap as a button press 無効
トリプルクリックでアドホック Ping Send an ad-hoc position ping on a triple click 無効
LED ハートビート Blink the status LED periodically 有効
タイムゾーン POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa設定

On Settings → LoRa.

設定項目 説明 デフォルト
リージョン Regulatory region for frequency bands. You must set this before transmitting 未設定(要設定)
プリセット 速度と距離のトレードオフ LongFast
ホップ数 再送信の最大ホップ数 3
送信出力 送信出力(dBm)。0 = リージョンで許可された最大値 0(リージョン最大)
周波数の上書き Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
プリセットを使用 On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
拡散率 Manual mode only: 7–12. Higher spreads further but slower From preset
符号化レート Manual mode only: 5–8. More redundancy costs airtime From preset
帯域 Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
周波数スロット Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
送信を有効化 Turning this off makes the node receive-only On
デューティサイクルを上書き Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits オフ
MQTT を無視 Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
MQTT への送信を許可 Allow your packets to be forwarded to MQTT by gateways オフ
RX ブーストゲイン Extra receive gain on SX126x radios; costs a little current オフ
PAファン無効 Turn off the power-amplifier fan on hardware that has one オフ

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. 詳しくは、meshtastic.org の リージョン設定ガイド を参照してください。

モデムプリセット

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 ヒント: SNR 限界の値は意図的に負の数になっています。 LoRa はノイズフロアを下回る信号でも復調できるため、より負の大きい限界値ほど、そのプリセットは弱くノイズの多い信号に耐えられます(より遠くまで届きます)。 詳しい説明は、信号メーターの仕組み を参照してください。

プリセット 距離 速度 SNR 限界 最適な用途
Short Turbo ~1 km 21.9 kbps −7.5 dB 見通しのある高密度な都市部。データ量の多い用途
Short Fast ~3 km 10.9 kbps −7.5 dB 都市の住宅街。数ブロック以内の建物
Short Slow ~5 km 6.25 kbps −10 dB 郊外の短距離。中程度の建物密度
Medium Fast ~5 km 3.52 kbps −12.5 dB 郊外エリア。中程度の建物密度
Medium Slow ~8 km 1.95 kbps −15 dB 郊外・地方。中程度の距離で低速
Long Turbo ~10 km 1.34 kbps −17.5 dB Long Fast と同程度の距離だが 500 kHz 帯域幅。スループットが速い
Long Fast ~10 km 1.1 kbps −17.5 dB 一般用途(デフォルト):距離と速度のバランスが良い
Long Moderate ~20 km 0.34 kbps −17.5 dB 起伏のある地方。ときどき使う用途
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD 帯(125 kHz 帯域幅)。Medium Fast に相当
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD 帯(125 kHz 帯域幅)。Long Fast に相当
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz 帯(62.5 kHz 帯域幅)。他のデバイスとの干渉を避ける
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz 帯(62.5 kHz 帯域幅)。Long Fast に相当
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ 非推奨:まだ選択できますが、将来のファームウェアリリースで削除される可能性があります
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ 非推奨:まだ選択できますが、将来のファームウェアリリースで削除される可能性があります

ℹ️ 注意: この表では、一般的な短い名前を使用しています。 The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

モデムプリセットを選ぶ

モデムプリセットは、距離データ速度の基本的なトレードオフを制御します:

  • 遅いプリセットは拡散をより多く使い、より弱い信号レベルでも復調できるようにします(SNR 限界が低い)。 これは、より遠くまで届く一方で、1 秒あたりのバイト数が少ないことを意味します。
  • 速いプリセットは 1 回の送信でより多くのデータを詰め込みますが、復調にはより強い信号が必要です。

実用的な指針:

  • 都市部のメッシュ(多数のノード、短距離): Long Fast(デフォルト)または Short Fast を使用します。 速度が速いほど、多くのノードがチャンネルを共有するときの電波利用時間の輻輳が減ります。
  • 地方・まばらなメッシュ(少数のノード、長距離): Long Moderate を使用します。 ノードが離れている場合は、速度よりも距離が重要です。
  • EU 866/868 MHz の規制対応: Lite FastLite SlowNarrow FastNarrow Slow を使用します。これらは、より狭い帯域幅で EU の SRD/868 MHz 帯に最適化されています。
  • 固定インフラのリンク: 良好なアンテナと見通しがある専用のポイントツーポイントリンクには、Short Turbo または Long Turbo を使用します。
  • 混在した環境: Long Fast のままにします。これはコミュニティのデフォルトで、地域内の他のユーザーとの互換性を確保します。

All nodes on the same channel must use the same modem preset. プリセットが一致しないノードは、同じ周波数と暗号化鍵を共有していても通信できません。

The range estimates in the Modem Presets table assume flat terrain and modest antennas. 高所(丘の上、屋上)にあると、実効的な距離が大幅に伸びます。 適切に設置された Long Fast のルーターは、地上に置かれた Long Slow のノードを上回ることがよくあります。

表示設定

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

設定項目 説明
画面オンの時間 How long the display stays lit before sleeping
カルーセルの間隔 How often the radio cycles between screens on its own
表示モード Screen layout/density used by the firmware
表示単位 Metric or Imperial on the radio’s screen
12時間の時計形式を使用 Show the radio’s clock as 12-hour rather than 24-hour
太字の見出し Draw the screen’s heading text in bold
画面反転 Rotate the display 180° for an inverted mounting
OLED タイプ 自動、SSD1306、SH1106、SH1107
タップまたは動作で起動 Light the screen when the radio is tapped or moved
コンパスの向き Rotation offset for the compass rose (0°, 90°, 180°, 270°)
常に北を上にする Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

位置情報設定

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

設定項目 説明
GPS モード(物理ハードウェア) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS ポーリング間隔 How often the radio asks its GPS for a fix
ブロードキャスト間隔 How often the position is shared with the mesh
スマート位置 Broadcast based on movement rather than purely on the clock
スマート間隔 With Smart Position on, the shortest gap between broadcasts
スマート距離 With Smart Position on, how far you must move before broadcasting
固定位置 Use a manually entered latitude, longitude and altitude instead of the GPS
位置情報フラグ A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

電源設定

On Settings → Device configuration → Power.

設定項目 説明
省電力モードを有効化 Let the radio sleep aggressively between activity
電源喪失時にシャットダウン Power the device down after external power disappears
スーパーディープスリープの時間 How long the deepest sleep state lasts
最小起動時間 The shortest time the radio stays awake once woken
Bluetooth 待機時間 How long to wait for a phone to connect before sleeping
ADC倍率のオーバーライド Turn on a manual correction for battery-voltage readings
ADC倍率のオーバーライド比 The correction factor itself, used only when the override is on
バッテリー INA_2XX I2C アドレス Address of an external INA-series power sensor, if fitted

ネットワーク設定

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

設定項目 説明
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
パスワード ネットワークのパスワード
イーサネット有効 Use a wired connection on hardware that has one
IPv4 モード DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP ブロードキャスト Share mesh traffic with other nodes over the local network
NTPサーバー 時刻同期サーバー
rsyslogサーバー リモートログサーバー

Network Config with a static IPv4 address entered

Bluetooth 設定

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

設定項目 説明
Bluetoothを有効 BLE 無線の有効/無効
ペアリングモード 固定 PIN、ランダム PIN、または PIN なし
固定 PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

セキュリティ設定

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

設定項目 説明
公開鍵 ノードの公開鍵(読み取り専用)
管理者鍵 Keys permitted to administer this node remotely — up to three
秘密鍵 Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
秘密鍵を再生成 Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
管理チャンネルを有効化 ⚠️ 削除されました:管理者キーを設定すると自動的に構成されるようになりました
シリアルコンソール Serial console over the Stream API
デバッグログAPIを有効化 Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
管理モード Restrict non-admin channel changes. Only selectable once an Admin Key is set
鍵をバックアップ Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
鍵を復元 バックアップした鍵をノードに書き戻します(バックアップがある場合に利用可能)
鍵のバックアップを削除 Remove the stored key backup from this phone
保護レベル How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field 内容
残りの起動回数 How many device boots the unlocked state survives
有効期限までの時間 Wall-clock lifetime of the unlocked state
セッション上限(分) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

関連トピック


diff --git a/main/ja-rJP/user/signal-meter.html b/main/ja-rJP/user/signal-meter.html index c2c67dbcd3..ffde0082ab 100644 --- a/main/ja-rJP/user/signal-meter.html +++ b/main/ja-rJP/user/signal-meter.html @@ -1 +1 @@ - Meshtastic の信号メーターの仕組み | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 日本語
Meshtastic Docs ↗

🌐 日本語 — Community translation View in English

Meshtastic の信号メーターの仕組み

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

レベル バー 基準 意味
Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
普通 3 less than 5.5 dB below limit Decodable, but approaching the floor.
不良 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
なし 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

信号情報が表示される場所

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • ルート追跡:各中継ノードの、ホップごとの信号品質
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon

関連トピック


+ Meshtastic の信号メーターの仕組み | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 日本語
Meshtastic Docs ↗

🌐 日本語 — Community translation View in English

Meshtastic の信号メーターの仕組み

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

レベル バー 基準 意味
Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
普通 3 less than 5.5 dB below limit Decodable, but approaching the floor.
不良 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
なし 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

信号情報が表示される場所

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • ルート追跡:各中継ノードの、ホップごとの信号品質
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon

関連トピック


diff --git a/main/ko-rKR/user/node-metrics.html b/main/ko-rKR/user/node-metrics.html index 6e3b325aa1..d1eaf4f927 100644 --- a/main/ko-rKR/user/node-metrics.html +++ b/main/ko-rKR/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 한국어
Meshtastic Docs ↗

🌐 한국어 — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric 설명
Battery Level Current battery percentage
전압 Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
업타임 Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
온도 BME280, BME680, SHT31
습도 BME280, BME680, SHT31
기압 BME280, BMP280
가스 저항 BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit 설명
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
좋음 < 1000 초록
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 빨강
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

신호 감도

Radio signal quality information:

Metric 설명
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
좋음 SNR above the preset’s limit
보통 less than 5.5 dB below the limit
나쁨 5.5 dB to 7.5 dB below the limit
없음 more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric 설명
전압 Per-channel voltage reading
전류 Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

추적 루트

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

위치 로그

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

이웃 정보

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 한국어
Meshtastic Docs ↗

🌐 한국어 — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric 설명
Battery Level Current battery percentage
전압 Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
업타임 Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
온도 BME280, BME680, SHT31
습도 BME280, BME680, SHT31
기압 BME280, BMP280
가스 저항 BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit 설명
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
좋음 < 1000 초록
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 빨강
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

신호 감도

Radio signal quality information:

Metric 설명
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
좋음 SNR above the preset’s limit
보통 less than 5.5 dB below the limit
나쁨 5.5 dB to 7.5 dB below the limit
없음 more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric 설명
전압 Per-channel voltage reading
전류 Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

추적 루트

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

위치 로그

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

이웃 정보

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/ko-rKR/user/nodes.html b/main/ko-rKR/user/nodes.html index 71f858cbf8..c778d67409 100644 --- a/main/ko-rKR/user/nodes.html +++ b/main/ko-rKR/user/nodes.html @@ -1 +1 @@ - 노드 | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 한국어
Meshtastic Docs ↗

🌐 한국어 — Community translation View in English

노드

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

역할 설명
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • 지우기

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

필터 설명
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort 설명
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
최근 수신 Last heard
거리 Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ 노드 | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 한국어
Meshtastic Docs ↗

🌐 한국어 — Community translation View in English

노드

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

역할 설명
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • 지우기

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

필터 설명
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort 설명
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
최근 수신 Last heard
거리 Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/ko-rKR/user/settings-radio-user.html b/main/ko-rKR/user/settings-radio-user.html index 2d464d0b51..6db6655e54 100644 --- a/main/ko-rKR/user/settings-radio-user.html +++ b/main/ko-rKR/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 한국어
Meshtastic Docs ↗

🌐 한국어 — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting 설명
긴 이름 Your display name (up to 39 characters)
짧은 이름 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
메시지 제한 Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

설정

장치 설정

On Settings → Device configuration → Device.

Setting 설명 기본값
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
중계 모드 How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
노드 정보 발송 주기 How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically 활성화
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa 설정

On Settings → LoRa.

Setting 설명 기본값
지역 Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
전송 출력 Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
프리셋 사용 On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding rate Manual mode only: 5–8. More redundancy costs airtime From preset
대역폭 Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
주파수 슬롯 Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
전송 활성화 Turning this off makes the node receive-only On
Duty Cycle 무시 Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
MQTT로 부터 수신 무시 Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan 비활성화됨 Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

화면 설정

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting 설명
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
디스플레이 모드 Screen layout/density used by the firmware
단위 표시 Metric or Imperial on the radio’s screen
12시간제 보기 Show the radio’s clock as 12-hour rather than 24-hour
상태표시줄 볼드체 Draw the screen’s heading text in bold
화면 뒤집기 Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
나침반 방향 Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

위치 설정

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting 설명
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
전송 간격 How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

전원 설정

On Settings → Device configuration → Power.

Setting 설명
저전력 모드 설정 Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

네트워크 설정

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting 설명
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
비밀번호 네트워크 암호
이더넷 활성화 Use a wired connection on hardware that has one
IPv4 모드 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP 서버 Time synchronization server
rsyslog 서버 Remote logging server

Network Config with a static IPv4 address entered

블루투스 설정

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting 설명
블루투스 활성화 Enable/disable BLE radio
페어링 모드 Fixed PIN, Random PIN, or No PIN
고정 PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

보안 설정

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting 설명
공개 키 Your node’s public key (read-only)
Admin 키 Keys permitted to administer this node remotely — up to three
개인 키 Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
개인 키 다시 생성하기 Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
시리얼 콘솔 Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
관리 모드 Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 한국어
Meshtastic Docs ↗

🌐 한국어 — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting 설명
긴 이름 Your display name (up to 39 characters)
짧은 이름 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
메시지 제한 Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

설정

장치 설정

On Settings → Device configuration → Device.

Setting 설명 기본값
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
중계 모드 How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
노드 정보 발송 주기 How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically 활성화
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa 설정

On Settings → LoRa.

Setting 설명 기본값
지역 Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
전송 출력 Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
프리셋 사용 On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding rate Manual mode only: 5–8. More redundancy costs airtime From preset
대역폭 Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
주파수 슬롯 Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
전송 활성화 Turning this off makes the node receive-only On
Duty Cycle 무시 Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
MQTT로 부터 수신 무시 Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan 비활성화됨 Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

화면 설정

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting 설명
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
디스플레이 모드 Screen layout/density used by the firmware
단위 표시 Metric or Imperial on the radio’s screen
12시간제 보기 Show the radio’s clock as 12-hour rather than 24-hour
상태표시줄 볼드체 Draw the screen’s heading text in bold
화면 뒤집기 Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
나침반 방향 Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

위치 설정

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting 설명
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
전송 간격 How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

전원 설정

On Settings → Device configuration → Power.

Setting 설명
저전력 모드 설정 Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

네트워크 설정

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting 설명
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
비밀번호 네트워크 암호
이더넷 활성화 Use a wired connection on hardware that has one
IPv4 모드 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP 서버 Time synchronization server
rsyslog 서버 Remote logging server

Network Config with a static IPv4 address entered

블루투스 설정

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting 설명
블루투스 활성화 Enable/disable BLE radio
페어링 모드 Fixed PIN, Random PIN, or No PIN
고정 PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

보안 설정

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting 설명
공개 키 Your node’s public key (read-only)
Admin 키 Keys permitted to administer this node remotely — up to three
개인 키 Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
개인 키 다시 생성하기 Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
시리얼 콘솔 Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
관리 모드 Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/ko-rKR/user/signal-meter.html b/main/ko-rKR/user/signal-meter.html index 4fb9d6b199..a32b21e610 100644 --- a/main/ko-rKR/user/signal-meter.html +++ b/main/ko-rKR/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 한국어
Meshtastic Docs ↗

🌐 한국어 — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
좋음 Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
보통 3 less than 5.5 dB below limit Decodable, but approaching the floor.
나쁨 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
없음 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 한국어
Meshtastic Docs ↗

🌐 한국어 — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
좋음 Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
보통 3 less than 5.5 dB below limit Decodable, but approaching the floor.
나쁨 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
없음 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/lt-rLT/user/node-metrics.html b/main/lt-rLT/user/node-metrics.html index 46115e0bd7..08a3dab0ff 100644 --- a/main/lt-rLT/user/node-metrics.html +++ b/main/lt-rLT/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Lietuvių
Meshtastic Docs ↗

🌐 Lietuvių — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Aprašymas
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatūra BME280, BME680, SHT31
Drėgmė BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Aprašymas
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Geras < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Raudona
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Signalo kokybė

Radio signal quality information:

Metric Aprašymas
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Geras SNR above the preset’s limit
Pakankamas less than 5.5 dB below the limit
Silpnas 5.5 dB to 7.5 dB below the limit
Nėra more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Aprašymas
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Žinutės kelias

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Pozicijos duomenų žurnalas

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Lietuvių
Meshtastic Docs ↗

🌐 Lietuvių — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Aprašymas
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatūra BME280, BME680, SHT31
Drėgmė BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Aprašymas
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Geras < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Raudona
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Signalo kokybė

Radio signal quality information:

Metric Aprašymas
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Geras SNR above the preset’s limit
Pakankamas less than 5.5 dB below the limit
Silpnas 5.5 dB to 7.5 dB below the limit
Nėra more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Aprašymas
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Žinutės kelias

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Pozicijos duomenų žurnalas

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/lt-rLT/user/nodes.html b/main/lt-rLT/user/nodes.html index 34e67bfbed..a4407d5ba6 100644 --- a/main/lt-rLT/user/nodes.html +++ b/main/lt-rLT/user/nodes.html @@ -1 +1 @@ - Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Lietuvių
Meshtastic Docs ↗

🌐 Lietuvių — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Aprašymas
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Pašalinti

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtras Aprašymas
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Aprašymas
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Seniausiai girdėtas Last heard
Atstumas Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Lietuvių
Meshtastic Docs ↗

🌐 Lietuvių — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Aprašymas
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Pašalinti

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtras Aprašymas
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Aprašymas
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Seniausiai girdėtas Last heard
Atstumas Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/lt-rLT/user/settings-radio-user.html b/main/lt-rLT/user/settings-radio-user.html index 36b482d22b..0840511a0b 100644 --- a/main/lt-rLT/user/settings-radio-user.html +++ b/main/lt-rLT/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Lietuvių
Meshtastic Docs ↗

🌐 Lietuvių — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Aprašymas
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Aprašymas Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Aprašymas Default
Regionas Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Aprašymas
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Aprašymas
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Aprašymas
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Aprašymas
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Aprašymas
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Aprašymas
Viešasis raktas Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Privatus raktas Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Lietuvių
Meshtastic Docs ↗

🌐 Lietuvių — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Aprašymas
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Aprašymas Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Aprašymas Default
Regionas Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Aprašymas
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Aprašymas
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Aprašymas
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Aprašymas
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Aprašymas
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Aprašymas
Viešasis raktas Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Privatus raktas Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/lt-rLT/user/signal-meter.html b/main/lt-rLT/user/signal-meter.html index 2573519efc..a034547c9f 100644 --- a/main/lt-rLT/user/signal-meter.html +++ b/main/lt-rLT/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Lietuvių
Meshtastic Docs ↗

🌐 Lietuvių — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Geras Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Pakankamas 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Silpnas 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Nėra 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Lietuvių
Meshtastic Docs ↗

🌐 Lietuvių — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Geras Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Pakankamas 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Silpnas 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Nėra 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/nl-rNL/user/node-metrics.html b/main/nl-rNL/user/node-metrics.html index 123c25bb0e..f8062e60b4 100644 --- a/main/nl-rNL/user/node-metrics.html +++ b/main/nl-rNL/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Nederlands
Meshtastic Docs ↗

🌐 Nederlands — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Beschrijving
Battery Level Current battery percentage
Spanning Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Tijd online Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatuur BME280, BME680, SHT31
Vochtigheid BME280, BME680, SHT31
Luchtdruk BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Beschrijving
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Goed < 1000 Groen
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Rood
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Signaalkwaliteit

Radio signal quality information:

Metric Beschrijving
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Goed SNR above the preset’s limit
Matig less than 5.5 dB below the limit
Slecht 5.5 dB to 7.5 dB below the limit
Geen more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Beschrijving
Spanning Per-channel voltage reading
Huidige Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Positie Logboek

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Nederlands
Meshtastic Docs ↗

🌐 Nederlands — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Beschrijving
Battery Level Current battery percentage
Spanning Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Tijd online Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatuur BME280, BME680, SHT31
Vochtigheid BME280, BME680, SHT31
Luchtdruk BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Beschrijving
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Goed < 1000 Groen
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Rood
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Signaalkwaliteit

Radio signal quality information:

Metric Beschrijving
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Goed SNR above the preset’s limit
Matig less than 5.5 dB below the limit
Slecht 5.5 dB to 7.5 dB below the limit
Geen more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Beschrijving
Spanning Per-channel voltage reading
Huidige Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Positie Logboek

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/nl-rNL/user/nodes.html b/main/nl-rNL/user/nodes.html index b4f03f3bd7..1d107e4022 100644 --- a/main/nl-rNL/user/nodes.html +++ b/main/nl-rNL/user/nodes.html @@ -1 +1 @@ - Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Nederlands
Meshtastic Docs ↗

🌐 Nederlands — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Functie Beschrijving
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Verwijder

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filter Beschrijving
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Beschrijving
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Laatst gehoord Last heard
Afstand Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Nederlands
Meshtastic Docs ↗

🌐 Nederlands — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Functie Beschrijving
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Verwijder

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filter Beschrijving
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Beschrijving
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Laatst gehoord Last heard
Afstand Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/nl-rNL/user/settings-radio-user.html b/main/nl-rNL/user/settings-radio-user.html index f7210ced25..e9510b6257 100644 --- a/main/nl-rNL/user/settings-radio-user.html +++ b/main/nl-rNL/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Nederlands
Meshtastic Docs ↗

🌐 Nederlands — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Beschrijving
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Niet berichtbaar Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Apparaat Configuratie

On Settings → Device configuration → Device.

Setting Beschrijving Standaard
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Configuratie

On Settings → LoRa.

Setting Beschrijving Standaard
Regio Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandbreedte Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Overschrijf Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Negeer MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Weergave Configuratie

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Beschrijving
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Weergavemodus Screen layout/density used by the firmware
Geef eenheden weer Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Scherm omdraaien Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Kompas oriëntatie Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Positie Configuratie

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beschrijving
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Energie configuratie

On Settings → Device configuration → Power.

Setting Beschrijving
Energiebesparingsmodus inschakelen Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Netwerkconfiguratie

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Beschrijving
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Wachtwoord Network password
Ethernet ingeschakeld Use a wired connection on hardware that has one
IPv4 modus DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Configuratie

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beschrijving
Bluetooth ingeschakeld Enable/disable BLE radio
Koppelmodus Fixed PIN, Random PIN, or No PIN
Vaste PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Beveiligings Configuratie

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beschrijving
Publieke sleutel Your node’s public key (read-only)
Admin Sleutel Keys permitted to administer this node remotely — up to three
Privésleutel Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Seriële console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Beheerde modus Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Nederlands
Meshtastic Docs ↗

🌐 Nederlands — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Beschrijving
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Niet berichtbaar Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Apparaat Configuratie

On Settings → Device configuration → Device.

Setting Beschrijving Standaard
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Configuratie

On Settings → LoRa.

Setting Beschrijving Standaard
Regio Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandbreedte Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Overschrijf Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Negeer MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Weergave Configuratie

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Beschrijving
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Weergavemodus Screen layout/density used by the firmware
Geef eenheden weer Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Scherm omdraaien Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Kompas oriëntatie Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Positie Configuratie

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beschrijving
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Energie configuratie

On Settings → Device configuration → Power.

Setting Beschrijving
Energiebesparingsmodus inschakelen Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Netwerkconfiguratie

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Beschrijving
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Wachtwoord Network password
Ethernet ingeschakeld Use a wired connection on hardware that has one
IPv4 modus DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Configuratie

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beschrijving
Bluetooth ingeschakeld Enable/disable BLE radio
Koppelmodus Fixed PIN, Random PIN, or No PIN
Vaste PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Beveiligings Configuratie

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beschrijving
Publieke sleutel Your node’s public key (read-only)
Admin Sleutel Keys permitted to administer this node remotely — up to three
Privésleutel Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Seriële console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Beheerde modus Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/nl-rNL/user/signal-meter.html b/main/nl-rNL/user/signal-meter.html index a34f5a3501..7211f8da69 100644 --- a/main/nl-rNL/user/signal-meter.html +++ b/main/nl-rNL/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Nederlands
Meshtastic Docs ↗

🌐 Nederlands — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Goed Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Matig 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Slecht 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Geen 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Nederlands
Meshtastic Docs ↗

🌐 Nederlands — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Goed Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Matig 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Slecht 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Geen 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/no-rNO/user/node-metrics.html b/main/no-rNO/user/node-metrics.html index 601e7d1a8b..969aac7323 100644 --- a/main/no-rNO/user/node-metrics.html +++ b/main/no-rNO/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Norsk
Meshtastic Docs ↗

🌐 Norsk — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Beskrivelse
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatur BME280, BME680, SHT31
Luftfuktighet BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Beskrivelse
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Godt < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Signalstyrke

Radio signal quality information:

Metric Beskrivelse
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Godt SNR above the preset’s limit
Middelmådig less than 5.5 dB below the limit
Dårlig 5.5 dB to 7.5 dB below the limit
Ingen more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Beskrivelse
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Posisjonslogg

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Norsk
Meshtastic Docs ↗

🌐 Norsk — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Beskrivelse
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatur BME280, BME680, SHT31
Luftfuktighet BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Beskrivelse
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Godt < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Signalstyrke

Radio signal quality information:

Metric Beskrivelse
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Godt SNR above the preset’s limit
Middelmådig less than 5.5 dB below the limit
Dårlig 5.5 dB to 7.5 dB below the limit
Ingen more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Beskrivelse
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Posisjonslogg

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/no-rNO/user/nodes.html b/main/no-rNO/user/nodes.html index 3a2aa40c06..2053fc36b6 100644 --- a/main/no-rNO/user/nodes.html +++ b/main/no-rNO/user/nodes.html @@ -1 +1 @@ - Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Norsk
Meshtastic Docs ↗

🌐 Norsk — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Beskrivelse
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Fjern

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filter Beskrivelse
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Beskrivelse
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Sist hørt Last heard
Distanse Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Norsk
Meshtastic Docs ↗

🌐 Norsk — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Beskrivelse
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Fjern

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filter Beskrivelse
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Beskrivelse
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Sist hørt Last heard
Distanse Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/no-rNO/user/settings-radio-user.html b/main/no-rNO/user/settings-radio-user.html index fa324481f7..038cd2d8a4 100644 --- a/main/no-rNO/user/settings-radio-user.html +++ b/main/no-rNO/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Norsk
Meshtastic Docs ↗

🌐 Norsk — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Beskrivelse
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Beskrivelse Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Beskrivelse Default
Region Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Beskrivelse
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beskrivelse
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Beskrivelse
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Beskrivelse
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beskrivelse
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beskrivelse
Offentlig nøkkel Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Privat nøkkel Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Norsk
Meshtastic Docs ↗

🌐 Norsk — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Beskrivelse
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Beskrivelse Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Beskrivelse Default
Region Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Beskrivelse
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beskrivelse
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Beskrivelse
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Beskrivelse
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beskrivelse
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beskrivelse
Offentlig nøkkel Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Privat nøkkel Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/no-rNO/user/signal-meter.html b/main/no-rNO/user/signal-meter.html index e69f78b72f..fb523cf9f0 100644 --- a/main/no-rNO/user/signal-meter.html +++ b/main/no-rNO/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Norsk
Meshtastic Docs ↗

🌐 Norsk — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Godt Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Middelmådig 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Dårlig 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Ingen 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Norsk
Meshtastic Docs ↗

🌐 Norsk — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Godt Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Middelmådig 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Dårlig 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Ingen 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/pl-rPL/user/node-metrics.html b/main/pl-rPL/user/node-metrics.html index c789dbc6ef..bb58b946b1 100644 --- a/main/pl-rPL/user/node-metrics.html +++ b/main/pl-rPL/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Polski
Meshtastic Docs ↗

🌐 Polski — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Metryka urządzenia

Basic operating information reported by each node:

Metric Opis
Poziom naładowania baterii Current battery percentage
Napięcie Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Czas pracy Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Metryki środowiskowe

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatura BME280, BME680, SHT31
Wilgotność BME280, BME680, SHT31
Ciśnienie barometryczne BME280, BMP280
Rezystancja gazu BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Opis
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
dobry < 1000 Zielony
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Czerwony
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Jakość sygnału

Radio signal quality information:

Metric Opis
SNR: Signal-to-Noise Ratio (higher is better)
RSSI: Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
dobry SNR above the preset’s limit
wystarczający less than 5.5 dB below the limit
słaby 5.5 dB to 7.5 dB below the limit
Brak more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Metryki zasilania

Power management telemetry (requires INA sensor or compatible hardware):

Metric Opis
Napięcie Per-channel voltage reading
Natężenie Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Pokaż trasę

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Historia pozycji

Historical position data for nodes that share their location:

  • GPS coordinates
  • Wysokość
  • Speed (if moving)
  • Timestamp for each position report

Informacje o sąsiadze

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Statystyki hosta

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Polski
Meshtastic Docs ↗

🌐 Polski — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Metryka urządzenia

Basic operating information reported by each node:

Metric Opis
Poziom naładowania baterii Current battery percentage
Napięcie Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Czas pracy Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Metryki środowiskowe

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatura BME280, BME680, SHT31
Wilgotność BME280, BME680, SHT31
Ciśnienie barometryczne BME280, BMP280
Rezystancja gazu BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Opis
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
dobry < 1000 Zielony
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Czerwony
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Jakość sygnału

Radio signal quality information:

Metric Opis
SNR: Signal-to-Noise Ratio (higher is better)
RSSI: Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
dobry SNR above the preset’s limit
wystarczający less than 5.5 dB below the limit
słaby 5.5 dB to 7.5 dB below the limit
Brak more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Metryki zasilania

Power management telemetry (requires INA sensor or compatible hardware):

Metric Opis
Napięcie Per-channel voltage reading
Natężenie Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Pokaż trasę

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Historia pozycji

Historical position data for nodes that share their location:

  • GPS coordinates
  • Wysokość
  • Speed (if moving)
  • Timestamp for each position report

Informacje o sąsiadze

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Statystyki hosta

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/pl-rPL/user/nodes.html b/main/pl-rPL/user/nodes.html index 4f1489f7a9..3ed09bef20 100644 --- a/main/pl-rPL/user/nodes.html +++ b/main/pl-rPL/user/nodes.html @@ -1 +1 @@ - Węzły | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Polski
Meshtastic Docs ↗

🌐 Polski — Community translation View in English

Węzły

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Rola Opis
Klient Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Klient pasywny Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Czujnik Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Usuń

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtr Opis
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Opis
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Poziom naładowania baterii Battery
Hop count Hops
Aktywność Last heard
Odległość Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Węzły | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Polski
Meshtastic Docs ↗

🌐 Polski — Community translation View in English

Węzły

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Rola Opis
Klient Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Klient pasywny Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Czujnik Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Usuń

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtr Opis
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Opis
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Poziom naładowania baterii Battery
Hop count Hops
Aktywność Last heard
Odległość Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/pl-rPL/user/settings-radio-user.html b/main/pl-rPL/user/settings-radio-user.html index af9135e31d..c2e6f85eb2 100644 --- a/main/pl-rPL/user/settings-radio-user.html +++ b/main/pl-rPL/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Polski
Meshtastic Docs ↗

🌐 Polski — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Opis
Długa nazwa Your display name (up to 39 characters)
Krótka nazwa 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Nie przyjmuje wiadomości Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Konfiguracja

Konfiguracja urządzenia

On Settings → Device configuration → Device.

Setting Opis Domyślny
Rola urządzenia Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Tryb retransmisji How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Interwał transmisji informacji o węźle How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Podwójne dotknięcie jako naciśnięcie przycisku Treat a double tap as a button press Wyłączony
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Wyłączony
LED bicia serca Blink the status LED periodically Włączony
Strefa czasowa POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

Konfiguracja LoRa

On Settings → LoRa.

Setting Opis Domyślny
Region Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presety Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Moc nadawania Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Użyj predefiniowanych ustawień On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Szybkość kodowania Manual mode only: 5–8. More redundancy costs airtime From preset
Pasmo Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Slot częstotliwości Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmisja włączona Turning this off makes the node receive-only On
Nadpisz cykl pracy Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Wyłączony
Zignoruj MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok dla MQTT Allow your packets to be forwarded to MQTT by gateways Wyłączony
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Wyłączony
PA fan disabled Turn off the power-amplifier fan on hardware that has one Wyłączony

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Prędkość SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Konfiguracja wyświetlacza

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Opis
Ekran włączony na How long the display stays lit before sleeping
Interwał karuzeli How often the radio cycles between screens on its own
Tryb wyświetlania Screen layout/density used by the firmware
Wyświetlana jednostka Metric or Imperial on the radio’s screen
Użyj formatu 12-godzinnego Show the radio’s clock as 12-hour rather than 24-hour
Pogrubiony nagłówek Draw the screen’s heading text in bold
Odwróć ekran Rotate the display 180° for an inverted mounting
Typ ekranu OLED Auto, SSD1306, SH1106, SH1107
Wybudź przy dotknięciu lub ruchu Light the screen when the radio is tapped or moved
Orientacja kompasu Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Zawsze wskazywać na północ Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Konfiguracja pozycjonowania

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Interwał transmisji How often the position is shared with the mesh
Inteligentne Pozycjonowanie Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Położenie stałe Use a manually entered latitude, longitude and altitude instead of the GPS
Flagi położenia A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Konfiguracja zarządzania energią

On Settings → Device configuration → Power.

Setting Opis
Włącz tryb oszczędzania energii Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Konfiguracja sieci

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Opis
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Hasło Hasło do sieci
Ethernet włączony Use a wired connection on hardware that has one
Tryb IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Serwer NTP Time synchronization server
Serwer rsyslog Remote logging server

Network Config with a static IPv4 address entered

Konfiguracja Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
Bluetooth włączony Enable/disable BLE radio
Tryb parowania Fixed PIN, Random PIN, or No PIN
Stały PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Konfiguracja zabezpieczeń

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
Klucz publiczny Your node’s public key (read-only)
Klucz administratora Keys permitted to administer this node remotely — up to three
Klucz prywatny Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Klucze zapasowe Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Polski
Meshtastic Docs ↗

🌐 Polski — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Opis
Długa nazwa Your display name (up to 39 characters)
Krótka nazwa 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Nie przyjmuje wiadomości Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Konfiguracja

Konfiguracja urządzenia

On Settings → Device configuration → Device.

Setting Opis Domyślny
Rola urządzenia Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Tryb retransmisji How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Interwał transmisji informacji o węźle How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Podwójne dotknięcie jako naciśnięcie przycisku Treat a double tap as a button press Wyłączony
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Wyłączony
LED bicia serca Blink the status LED periodically Włączony
Strefa czasowa POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

Konfiguracja LoRa

On Settings → LoRa.

Setting Opis Domyślny
Region Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presety Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Moc nadawania Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Użyj predefiniowanych ustawień On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Szybkość kodowania Manual mode only: 5–8. More redundancy costs airtime From preset
Pasmo Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Slot częstotliwości Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmisja włączona Turning this off makes the node receive-only On
Nadpisz cykl pracy Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Wyłączony
Zignoruj MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok dla MQTT Allow your packets to be forwarded to MQTT by gateways Wyłączony
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Wyłączony
PA fan disabled Turn off the power-amplifier fan on hardware that has one Wyłączony

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Prędkość SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Konfiguracja wyświetlacza

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Opis
Ekran włączony na How long the display stays lit before sleeping
Interwał karuzeli How often the radio cycles between screens on its own
Tryb wyświetlania Screen layout/density used by the firmware
Wyświetlana jednostka Metric or Imperial on the radio’s screen
Użyj formatu 12-godzinnego Show the radio’s clock as 12-hour rather than 24-hour
Pogrubiony nagłówek Draw the screen’s heading text in bold
Odwróć ekran Rotate the display 180° for an inverted mounting
Typ ekranu OLED Auto, SSD1306, SH1106, SH1107
Wybudź przy dotknięciu lub ruchu Light the screen when the radio is tapped or moved
Orientacja kompasu Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Zawsze wskazywać na północ Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Konfiguracja pozycjonowania

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Interwał transmisji How often the position is shared with the mesh
Inteligentne Pozycjonowanie Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Położenie stałe Use a manually entered latitude, longitude and altitude instead of the GPS
Flagi położenia A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Konfiguracja zarządzania energią

On Settings → Device configuration → Power.

Setting Opis
Włącz tryb oszczędzania energii Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Konfiguracja sieci

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Opis
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Hasło Hasło do sieci
Ethernet włączony Use a wired connection on hardware that has one
Tryb IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Serwer NTP Time synchronization server
Serwer rsyslog Remote logging server

Network Config with a static IPv4 address entered

Konfiguracja Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
Bluetooth włączony Enable/disable BLE radio
Tryb parowania Fixed PIN, Random PIN, or No PIN
Stały PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Konfiguracja zabezpieczeń

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
Klucz publiczny Your node’s public key (read-only)
Klucz administratora Keys permitted to administer this node remotely — up to three
Klucz prywatny Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Klucze zapasowe Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/pl-rPL/user/signal-meter.html b/main/pl-rPL/user/signal-meter.html index 9688d7719b..37af79bcf4 100644 --- a/main/pl-rPL/user/signal-meter.html +++ b/main/pl-rPL/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Polski
Meshtastic Docs ↗

🌐 Polski — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
dobry Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
wystarczający 3 less than 5.5 dB below limit Decodable, but approaching the floor.
słaby 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Brak 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Polski
Meshtastic Docs ↗

🌐 Polski — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
dobry Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
wystarczający 3 less than 5.5 dB below limit Decodable, but approaching the floor.
słaby 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Brak 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/pt-rBR/user/node-metrics.html b/main/pt-rBR/user/node-metrics.html index 558744b7fc..073db1f272 100644 --- a/main/pt-rBR/user/node-metrics.html +++ b/main/pt-rBR/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Português (Brasil)
Meshtastic Docs ↗

🌐 Português (Brasil) — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Descrição
Battery Level Current battery percentage
Voltagem Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatura BME280, BME680, SHT31
Umidade BME280, BME680, SHT31
Pressão Barométrica BME280, BMP280
Resistência ao gás BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Descrição
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Bom < 1000 Verde
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Vermelho
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Qualidade do sinal

Radio signal quality information:

Metric Descrição
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Bom SNR above the preset’s limit
Média less than 5.5 dB below the limit
Ruim 5.5 dB to 7.5 dB below the limit
Nenhum more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Descrição
Voltagem Per-channel voltage reading
Atual Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traçar rota

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Log de Posição

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Informações do Vizinho

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Métricas do Host

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Português (Brasil)
Meshtastic Docs ↗

🌐 Português (Brasil) — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Descrição
Battery Level Current battery percentage
Voltagem Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatura BME280, BME680, SHT31
Umidade BME280, BME680, SHT31
Pressão Barométrica BME280, BMP280
Resistência ao gás BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Descrição
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Bom < 1000 Verde
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Vermelho
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Qualidade do sinal

Radio signal quality information:

Metric Descrição
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Bom SNR above the preset’s limit
Média less than 5.5 dB below the limit
Ruim 5.5 dB to 7.5 dB below the limit
Nenhum more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Descrição
Voltagem Per-channel voltage reading
Atual Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traçar rota

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Log de Posição

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Informações do Vizinho

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Métricas do Host

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/pt-rBR/user/nodes.html b/main/pt-rBR/user/nodes.html index 715d84131b..3aad829c52 100644 --- a/main/pt-rBR/user/nodes.html +++ b/main/pt-rBR/user/nodes.html @@ -1 +1 @@ - Nós | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Português (Brasil)
Meshtastic Docs ↗

🌐 Português (Brasil) — Community translation View in English

Nós

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Função Descrição
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Excluir

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtro Descrição
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Descrição
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Visto pela última vez Last heard
Distância Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nós | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Português (Brasil)
Meshtastic Docs ↗

🌐 Português (Brasil) — Community translation View in English

Nós

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Função Descrição
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Excluir

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtro Descrição
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Descrição
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Visto pela última vez Last heard
Distância Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/pt-rBR/user/settings-radio-user.html b/main/pt-rBR/user/settings-radio-user.html index 7d75878984..7866645cc3 100644 --- a/main/pt-rBR/user/settings-radio-user.html +++ b/main/pt-rBR/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Português (Brasil)
Meshtastic Docs ↗

🌐 Português (Brasil) — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descrição
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Impossível enviar mensagens Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Configuração do Dispositivo

On Settings → Device configuration → Device.

Setting Descrição Padrão
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

Configuração do LoRa

On Settings → LoRa.

Setting Descrição Padrão
Região Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Largura da banda Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Ignorar ciclo de trabalho Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignorar MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
Ventilador do PA desativado Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Velocidade SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configuração da Tela

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Descrição
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Modo da tela Screen layout/density used by the firmware
Unidades de exibição Metric or Imperial on the radio’s screen
Usar formato de relógio 12h Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Inverter tela Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Orientação da bússola Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configuração da Posição

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrição
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configuração de Energia

On Settings → Device configuration → Power.

Setting Descrição
Ativar modo de economia de energia Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
Alterar proporção do multiplicador ADC The correction factor itself, used only when the override is on
Endereço I2C da bateria INA_2XX Address of an external INA-series power sensor, if fitted

Configuração de Rede

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Descrição
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Senha Network password
Ethernet ativado Use a wired connection on hardware that has one
Modo IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Servidor NTP Time synchronization server
Servidor rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configuração do Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrição
Bluetooth habilitado Enable/disable BLE radio
Modo de pareamento Fixed PIN, Random PIN, or No PIN
PIN fixo PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configurações de Segurança

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrição
Chave Publica Your node’s public key (read-only)
Chave do Administrador Keys permitted to administer this node remotely — up to three
Chave Privada Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerar a chave privada Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Console serial Serial console over the Stream API
API de logs de depuração ativada Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Modo Administrado Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Português (Brasil)
Meshtastic Docs ↗

🌐 Português (Brasil) — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descrição
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Impossível enviar mensagens Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Configuração do Dispositivo

On Settings → Device configuration → Device.

Setting Descrição Padrão
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

Configuração do LoRa

On Settings → LoRa.

Setting Descrição Padrão
Região Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Largura da banda Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Ignorar ciclo de trabalho Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignorar MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
Ventilador do PA desativado Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Velocidade SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configuração da Tela

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Descrição
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Modo da tela Screen layout/density used by the firmware
Unidades de exibição Metric or Imperial on the radio’s screen
Usar formato de relógio 12h Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Inverter tela Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Orientação da bússola Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configuração da Posição

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrição
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configuração de Energia

On Settings → Device configuration → Power.

Setting Descrição
Ativar modo de economia de energia Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
Alterar proporção do multiplicador ADC The correction factor itself, used only when the override is on
Endereço I2C da bateria INA_2XX Address of an external INA-series power sensor, if fitted

Configuração de Rede

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Descrição
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Senha Network password
Ethernet ativado Use a wired connection on hardware that has one
Modo IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Servidor NTP Time synchronization server
Servidor rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configuração do Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrição
Bluetooth habilitado Enable/disable BLE radio
Modo de pareamento Fixed PIN, Random PIN, or No PIN
PIN fixo PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configurações de Segurança

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrição
Chave Publica Your node’s public key (read-only)
Chave do Administrador Keys permitted to administer this node remotely — up to three
Chave Privada Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerar a chave privada Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Console serial Serial console over the Stream API
API de logs de depuração ativada Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Modo Administrado Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/pt-rBR/user/signal-meter.html b/main/pt-rBR/user/signal-meter.html index 5c7e30cb67..7067643ec9 100644 --- a/main/pt-rBR/user/signal-meter.html +++ b/main/pt-rBR/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Português (Brasil)
Meshtastic Docs ↗

🌐 Português (Brasil) — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Bom Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Média 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Ruim 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Nenhum 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Português (Brasil)
Meshtastic Docs ↗

🌐 Português (Brasil) — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Bom Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Média 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Ruim 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Nenhum 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/pt-rPT/user/node-metrics.html b/main/pt-rPT/user/node-metrics.html index d8f4f48ef6..fab7e87faf 100644 --- a/main/pt-rPT/user/node-metrics.html +++ b/main/pt-rPT/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Português
Meshtastic Docs ↗

🌐 Português — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Descrição
Battery Level Current battery percentage
Voltagem Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Tempo ativo Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatura BME280, BME680, SHT31
Humidade BME280, BME680, SHT31
Pressão atmosférica BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Descrição
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Bom < 1000 Verde
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Vermelho
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Qualidade do Sinal

Radio signal quality information:

Metric Descrição
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Bom SNR above the preset’s limit
Razoável less than 5.5 dB below the limit
Mau 5.5 dB to 7.5 dB below the limit
Nenhum more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Descrição
Voltagem Per-channel voltage reading
Atual Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traçar rota

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Histórico de posição

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Informações da vizinhança

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Português
Meshtastic Docs ↗

🌐 Português — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Descrição
Battery Level Current battery percentage
Voltagem Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Tempo ativo Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatura BME280, BME680, SHT31
Humidade BME280, BME680, SHT31
Pressão atmosférica BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Descrição
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Bom < 1000 Verde
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Vermelho
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Qualidade do Sinal

Radio signal quality information:

Metric Descrição
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Bom SNR above the preset’s limit
Razoável less than 5.5 dB below the limit
Mau 5.5 dB to 7.5 dB below the limit
Nenhum more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Descrição
Voltagem Per-channel voltage reading
Atual Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traçar rota

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Histórico de posição

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Informações da vizinhança

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/pt-rPT/user/nodes.html b/main/pt-rPT/user/nodes.html index ee97cd6c67..18a3ae3f2e 100644 --- a/main/pt-rPT/user/nodes.html +++ b/main/pt-rPT/user/nodes.html @@ -1 +1 @@ - Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Português
Meshtastic Docs ↗

🌐 Português — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Papel Descrição
Cliente Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Cliente silenciado Receives but doesn’t retransmit
Cliente oculto Like Client Mute, plus hides from node list
Roteador Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Monitor Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK — ‘Kit’ de Consciencialização da Equipa Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Perdidos e Achados Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Remover

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtrar Descrição
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Descrição
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Último recebido Last heard
Distância Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Português
Meshtastic Docs ↗

🌐 Português — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Papel Descrição
Cliente Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Cliente silenciado Receives but doesn’t retransmit
Cliente oculto Like Client Mute, plus hides from node list
Roteador Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Monitor Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK — ‘Kit’ de Consciencialização da Equipa Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Perdidos e Achados Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Remover

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtrar Descrição
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Descrição
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Último recebido Last heard
Distância Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/pt-rPT/user/settings-radio-user.html b/main/pt-rPT/user/settings-radio-user.html index c91505bf14..6e8d55ee5c 100644 --- a/main/pt-rPT/user/settings-radio-user.html +++ b/main/pt-rPT/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Português
Meshtastic Docs ↗

🌐 Português — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descrição
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Impossível enviar mensagens Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuração

Configuração do Dispositivo

On Settings → Device configuration → Device.

Setting Descrição Predefinição
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

Configuração de LoRa

On Settings → LoRa.

Setting Descrição Predefinição
Região Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Largura de banda Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Ignorar ciclo de trabalho Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignorar MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configuração do Ecrã

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Descrição
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Modo de visualização Screen layout/density used by the firmware
Unidade de visualização Metric or Imperial on the radio’s screen
Usar formato de relógio 12h Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Inverter ecrã Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Orientação da bússola Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configuração da posição

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrição
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Intervalo de difusão How often the position is shared with the mesh
Posição Inteligente Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Posição fixa Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configuração de Energia

On Settings → Device configuration → Power.

Setting Descrição
Ativar modo de poupança de energia Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
Alterar rácio do multiplicador ADC The correction factor itself, used only when the override is on
Endereço I2C da bateria INA_2XX Address of an external INA-series power sensor, if fitted

Configuração de Rede

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Descrição
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Palavra-passe Network password
Ethernet ativada Use a wired connection on hardware that has one
Modo IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Servidor NTP Time synchronization server
servidor rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configuração de Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrição
Bluetooth ativado Enable/disable BLE radio
Modo de emparelhamento Fixed PIN, Random PIN, or No PIN
PIN fixo PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configuração de Segurança

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrição
Chave pública Your node’s public key (read-only)
Chave do Administrador Keys permitted to administer this node remotely — up to three
Chave privada Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Consola de série Serial console over the Stream API
API de histórico de depuração ativada Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Modo Administrado Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Português
Meshtastic Docs ↗

🌐 Português — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descrição
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Impossível enviar mensagens Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuração

Configuração do Dispositivo

On Settings → Device configuration → Device.

Setting Descrição Predefinição
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

Configuração de LoRa

On Settings → LoRa.

Setting Descrição Predefinição
Região Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Largura de banda Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Ignorar ciclo de trabalho Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignorar MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Configuração do Ecrã

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Descrição
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Modo de visualização Screen layout/density used by the firmware
Unidade de visualização Metric or Imperial on the radio’s screen
Usar formato de relógio 12h Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Inverter ecrã Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Orientação da bússola Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Configuração da posição

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrição
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Intervalo de difusão How often the position is shared with the mesh
Posição Inteligente Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Posição fixa Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configuração de Energia

On Settings → Device configuration → Power.

Setting Descrição
Ativar modo de poupança de energia Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
Alterar rácio do multiplicador ADC The correction factor itself, used only when the override is on
Endereço I2C da bateria INA_2XX Address of an external INA-series power sensor, if fitted

Configuração de Rede

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Descrição
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Palavra-passe Network password
Ethernet ativada Use a wired connection on hardware that has one
Modo IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Servidor NTP Time synchronization server
servidor rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configuração de Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrição
Bluetooth ativado Enable/disable BLE radio
Modo de emparelhamento Fixed PIN, Random PIN, or No PIN
PIN fixo PIN code for pairing. Must be exactly six digits — the field rejects anything else

Configuração de Segurança

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descrição
Chave pública Your node’s public key (read-only)
Chave do Administrador Keys permitted to administer this node remotely — up to three
Chave privada Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Consola de série Serial console over the Stream API
API de histórico de depuração ativada Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Modo Administrado Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/pt-rPT/user/signal-meter.html b/main/pt-rPT/user/signal-meter.html index 594fe9c4c3..79e5a78107 100644 --- a/main/pt-rPT/user/signal-meter.html +++ b/main/pt-rPT/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Português
Meshtastic Docs ↗

🌐 Português — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Bom Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Razoável 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Mau 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Nenhum 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Português
Meshtastic Docs ↗

🌐 Português — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Bom Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Razoável 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Mau 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Nenhum 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/ro-rRO/user/node-metrics.html b/main/ro-rRO/user/node-metrics.html index d7b7e43885..11f9603c71 100644 --- a/main/ro-rRO/user/node-metrics.html +++ b/main/ro-rRO/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Română
Meshtastic Docs ↗

🌐 Română — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Valori dispozitiv

Basic operating information reported by each node:

Metric Descriere
Battery Level Current battery percentage
Tensiune Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Timp de functionare Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Indicatori de mediu

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperature BME280, BME680, SHT31
Humidity BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Rezistența la gaz BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Descriere
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Bun < 1000 Verde
Stuffy < 2000 Amber
Poor < 5000 Portocaliu
Unsafe < 30000 Roșu
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Calitatea semnalului

Radio signal quality information:

Metric Descriere
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Bun SNR above the preset’s limit
Acceptabil less than 5.5 dB below the limit
Slab 5.5 dB to 7.5 dB below the limit
Niciunul more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Valori putere

Power management telemetry (requires INA sensor or compatible hardware):

Metric Descriere
Tensiune Per-channel voltage reading
Actual Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Trasare traseu

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Position Log

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitudine
  • Speed (if moving)
  • Timestamp for each position report

Informații vecin

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Valori Gazdă

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

Măsurători PAX

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Română
Meshtastic Docs ↗

🌐 Română — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Valori dispozitiv

Basic operating information reported by each node:

Metric Descriere
Battery Level Current battery percentage
Tensiune Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Timp de functionare Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Indicatori de mediu

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperature BME280, BME680, SHT31
Humidity BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Rezistența la gaz BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Descriere
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Bun < 1000 Verde
Stuffy < 2000 Amber
Poor < 5000 Portocaliu
Unsafe < 30000 Roșu
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Calitatea semnalului

Radio signal quality information:

Metric Descriere
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Bun SNR above the preset’s limit
Acceptabil less than 5.5 dB below the limit
Slab 5.5 dB to 7.5 dB below the limit
Niciunul more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Valori putere

Power management telemetry (requires INA sensor or compatible hardware):

Metric Descriere
Tensiune Per-channel voltage reading
Actual Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Trasare traseu

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Position Log

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitudine
  • Speed (if moving)
  • Timestamp for each position report

Informații vecin

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Valori Gazdă

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

Măsurători PAX

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/ro-rRO/user/nodes.html b/main/ro-rRO/user/nodes.html index 797b0ca71b..4040f77d57 100644 --- a/main/ro-rRO/user/nodes.html +++ b/main/ro-rRO/user/nodes.html @@ -1 +1 @@ - Noduri | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Română
Meshtastic Docs ↗

🌐 Română — Community translation View in English

Noduri

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Descriere
Client Standard end-user node
Client bază Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client mut Receives but doesn’t retransmit
Client ascuns Like Client Mute, plus hides from node list
Ruter Prioritizes message forwarding; stays awake to relay
Ruter cu întârziere Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Senzor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
Tracker TAK TAK position reporting only
Pierdut și găsit Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Eliminare

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtru Descriere
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Descriere
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Ultima recepție Last heard
Distanță Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Noduri | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Română
Meshtastic Docs ↗

🌐 Română — Community translation View in English

Noduri

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Descriere
Client Standard end-user node
Client bază Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client mut Receives but doesn’t retransmit
Client ascuns Like Client Mute, plus hides from node list
Ruter Prioritizes message forwarding; stays awake to relay
Ruter cu întârziere Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Senzor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
Tracker TAK TAK position reporting only
Pierdut și găsit Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Eliminare

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtru Descriere
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Descriere
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Ultima recepție Last heard
Distanță Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/ro-rRO/user/settings-radio-user.html b/main/ro-rRO/user/settings-radio-user.html index 245b981d6a..6a0f7b5473 100644 --- a/main/ro-rRO/user/settings-radio-user.html +++ b/main/ro-rRO/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Română
Meshtastic Docs ↗

🌐 Română — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descriere
Nume lung Your display name (up to 39 characters)
Nume scurt 4-character abbreviated name
Mesaj de stare: A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Netransmisibil Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Radioamator autorizat Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Descriere Prestabilit
Rolul dispozitivului Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Mod de redifuzare How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Intervalul de difuzare a informațiilor nodului How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Apăsare dublă ca buton Treat a double tap as a button press Disabled
Apăsare triplă pentru ping Ad Hoc Send an ad-hoc position ping on a triple click Disabled
Puls LED Blink the status LED periodically Activat
Fus orar POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Descriere Prestabilit
Regiune Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presetări Speed/range tradeoff LongFast
Numărul de Hops Maximum retransmit hops 3
Putere transmisie Transmission power (dBm); 0 = max allowed for region 0 (region max)
Suprascriere frecvență Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Utilizare presetare On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Factor de răspândire Manual mode only: 7–12. Higher spreads further but slower From preset
Rata de codificare Manual mode only: 5–8. More redundancy costs airtime From preset
Lățime bandă Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Slot pentru frecvenţă Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmisie activată Turning this off makes the node receive-only On
Suprascrie ciclul de obligații Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignoră MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Acceptă MQTT Allow your packets to be forwarded to MQTT by gateways Off
Amplificare RX amplificată Extra receive gain on SX126x radios; costs a little current Off
Ventilator PA dezactivat Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Viteza SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Descriere
Ecran pornit pentru How long the display stays lit before sleeping
Intervalul caruselului How often the radio cycles between screens on its own
Mod ecran Screen layout/density used by the firmware
Unități de măsură afișate Metric or Imperial on the radio’s screen
Utilizaţi formatul ceasului 12h Show the radio’s clock as 12-hour rather than 24-hour
Direcție îngroșat Draw the screen’s heading text in bold
Rotire ecran Rotate the display 180° for an inverted mounting
Tip OLED Auto, SSD1306, SH1106, SH1107
Trezire la apăsare sau mișcare Light the screen when the radio is tapped or moved
Orientarea busolei Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Indică mereu spre nord Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descriere
Mod GPS (hardware fizic) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Interval de actualizare GPS How often the radio asks its GPS for a fix
Interval de difuzare How often the position is shared with the mesh
Poziție inteligentă Broadcast based on movement rather than purely on the clock
Interval inteligent With Smart Position on, the shortest gap between broadcasts
Distanță inteligentă With Smart Position on, how far you must move before broadcasting
Poziție fixă Use a manually entered latitude, longitude and altitude instead of the GPS
Steaguri poziție A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configurare Putere

On Settings → Device configuration → Power.

Setting Descriere
Activează modul de economisire a energiei Let the radio sleep aggressively between activity
Închidere la pierderea de energie Power the device down after external power disappears
Durată maximă de somn How long the deepest sleep state lasts
Durata minimă a trezirii The shortest time the radio stays awake once woken
Așteptați pentru durata Bluetooth How long to wait for a phone to connect before sleeping
Suprascriere multiplicator ADC Turn on a manual correction for battery-voltage readings
Raportul suprascrierii multiplicatorului ADC The correction factor itself, used only when the override is on
Adresa baterie INA_2XX I2C Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Descriere
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
Numele rețelei Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Parolă Network password
Ethernet activat Use a wired connection on hardware that has one
Mod IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Server NTP Time synchronization server
server rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configurare Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descriere
Bluetooth activat Enable/disable BLE radio
Mod împerechere Fixed PIN, Random PIN, or No PIN
PIN fix PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descriere
Chei publice Your node’s public key (read-only)
Cheie Administrator Keys permitted to administer this node remotely — up to three
Cheia privată Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerează Cheia privată Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Consolă serială Serial console over the Stream API
Debug log API activat Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Mod Gestionat Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Română
Meshtastic Docs ↗

🌐 Română — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Descriere
Nume lung Your display name (up to 39 characters)
Nume scurt 4-character abbreviated name
Mesaj de stare: A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Netransmisibil Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Radioamator autorizat Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Descriere Prestabilit
Rolul dispozitivului Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Mod de redifuzare How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Intervalul de difuzare a informațiilor nodului How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Apăsare dublă ca buton Treat a double tap as a button press Disabled
Apăsare triplă pentru ping Ad Hoc Send an ad-hoc position ping on a triple click Disabled
Puls LED Blink the status LED periodically Activat
Fus orar POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Descriere Prestabilit
Regiune Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presetări Speed/range tradeoff LongFast
Numărul de Hops Maximum retransmit hops 3
Putere transmisie Transmission power (dBm); 0 = max allowed for region 0 (region max)
Suprascriere frecvență Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Utilizare presetare On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Factor de răspândire Manual mode only: 7–12. Higher spreads further but slower From preset
Rata de codificare Manual mode only: 5–8. More redundancy costs airtime From preset
Lățime bandă Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Slot pentru frecvenţă Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmisie activată Turning this off makes the node receive-only On
Suprascrie ciclul de obligații Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignoră MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Acceptă MQTT Allow your packets to be forwarded to MQTT by gateways Off
Amplificare RX amplificată Extra receive gain on SX126x radios; costs a little current Off
Ventilator PA dezactivat Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Viteza SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Descriere
Ecran pornit pentru How long the display stays lit before sleeping
Intervalul caruselului How often the radio cycles between screens on its own
Mod ecran Screen layout/density used by the firmware
Unități de măsură afișate Metric or Imperial on the radio’s screen
Utilizaţi formatul ceasului 12h Show the radio’s clock as 12-hour rather than 24-hour
Direcție îngroșat Draw the screen’s heading text in bold
Rotire ecran Rotate the display 180° for an inverted mounting
Tip OLED Auto, SSD1306, SH1106, SH1107
Trezire la apăsare sau mișcare Light the screen when the radio is tapped or moved
Orientarea busolei Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Indică mereu spre nord Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descriere
Mod GPS (hardware fizic) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Interval de actualizare GPS How often the radio asks its GPS for a fix
Interval de difuzare How often the position is shared with the mesh
Poziție inteligentă Broadcast based on movement rather than purely on the clock
Interval inteligent With Smart Position on, the shortest gap between broadcasts
Distanță inteligentă With Smart Position on, how far you must move before broadcasting
Poziție fixă Use a manually entered latitude, longitude and altitude instead of the GPS
Steaguri poziție A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Configurare Putere

On Settings → Device configuration → Power.

Setting Descriere
Activează modul de economisire a energiei Let the radio sleep aggressively between activity
Închidere la pierderea de energie Power the device down after external power disappears
Durată maximă de somn How long the deepest sleep state lasts
Durata minimă a trezirii The shortest time the radio stays awake once woken
Așteptați pentru durata Bluetooth How long to wait for a phone to connect before sleeping
Suprascriere multiplicator ADC Turn on a manual correction for battery-voltage readings
Raportul suprascrierii multiplicatorului ADC The correction factor itself, used only when the override is on
Adresa baterie INA_2XX I2C Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Descriere
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
Numele rețelei Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Parolă Network password
Ethernet activat Use a wired connection on hardware that has one
Mod IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
Server NTP Time synchronization server
server rsyslog Remote logging server

Network Config with a static IPv4 address entered

Configurare Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descriere
Bluetooth activat Enable/disable BLE radio
Mod împerechere Fixed PIN, Random PIN, or No PIN
PIN fix PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Descriere
Chei publice Your node’s public key (read-only)
Cheie Administrator Keys permitted to administer this node remotely — up to three
Cheia privată Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerează Cheia privată Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Consolă serială Serial console over the Stream API
Debug log API activat Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Mod Gestionat Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/ro-rRO/user/signal-meter.html b/main/ro-rRO/user/signal-meter.html index 535f0c83e9..c4dac7d136 100644 --- a/main/ro-rRO/user/signal-meter.html +++ b/main/ro-rRO/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Română
Meshtastic Docs ↗

🌐 Română — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Bun Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Acceptabil 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Slab 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Niciunul 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Română
Meshtastic Docs ↗

🌐 Română — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Bun Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Acceptabil 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Slab 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Niciunul 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/ru-rRU/user/node-metrics.html b/main/ru-rRU/user/node-metrics.html index feb3f00bd7..eabff0178a 100644 --- a/main/ru-rRU/user/node-metrics.html +++ b/main/ru-rRU/user/node-metrics.html @@ -1 +1 @@ - Метрики ноды | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Русский
Meshtastic Docs ↗

🌐 Русский — Community translation View in English

Метрики ноды

Экран сведений о ноде предоставляет подробную телеметрию и метрики для каждой ноды твоей mesh-сети.

Просмотр метрик

  1. Перейдите в раздел Ноды.
  2. Нажмите на ноду, которую хотите просмотреть.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Сведения о ноде — локальное устройство

The Position row expands to show location data for nodes that share GPS:

Встроенное содержимое о местоположении

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Метрики обновляются с интервалами, настроенными в параметрах телеметрии каждой ноды.

Интервал передачи

Основная информация о работе, сообщаемая каждой нодой:

Метрическая Описание
Уровень заряда Текущий процент заряда батареи
Напряжение Показания напряжения батареи
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Аптайм Время с момента последней перезагрузки

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Метрики окружения

Данные датчиков окружающей среды (требуется совместимое оборудование):

Метрическая Примеры сенсоров
Температура BME280, BME680, SHT31
Влажность BME280, BME680, SHT31
Давление на барометре BME280, BMP280
Сопротивление газа BME680
IAQ (Качества воздуха) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

Индекс IAQ (качество воздуха в помещении) датчика BME680 представляет собой единое значение от 0 до 500+, полученное на основе сопротивления газа, и отображается на цветовой шкале от “Отлично” до “Опасно загрязнён”:

Шкала индекса IAQ от Отлично до Опасно загрязнён

💡 Совет: Для получения метрик окружающей среды к удалённой ноде должен быть подключён датчик. Не все ноды передают данные об окружающей среде. См. Телеметрия и датчики для получения полного списка поддерживаемых датчиков.

Метрики качества воздуха

Качество воздуха — это отдельный экран метрик для нод, оснащённых датчиком взвешенных частиц и/или CO₂. Этот экран отделён от показателя IAQ датчика BME680, отображаемого в разделе “Метрики окружающей среды” — IAQ представляет собой единый индекс, основанный на сопротивлении газа, тогда как экран качества воздуха показывает графики исходных измерений взвешенных частиц и CO₂.

Метрическая Единица Описание
PM1.0 мкг/м³ Взвешенные частицы размером до 1,0 микрона
PM2.5 мкг/м³ Взвешенные частицы размером до 2,5 микрона
PM10 мкг/м³ Взвешенные частицы размером до 10 микронов
AQI Индекс EPA EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Отображается рядом с PM2.5, как только накопится достаточно показаний.
CO₂ ppm Концентрация углекислого газа
Температура CO₂ °C / °F Температура, сообщаемая самим датчиком CO₂ (например, SCD4x)
Влажность CO₂ % Относительная влажность, сообщаемая датчиком CO₂

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Диапазон Диапазон CO₂ (ppm) Цвет
Хороший < 1000 Зеленый
Душно < 2000 Янтарный
Плохо < 5000 Оранжевый
Небезопасно < 30000 Красный
Эвакуация ≥ 30000 Тёмно-красный

Показания качества воздуха с цветовой кодировкой уровня CO₂

Кнопка журнала/метрик качества воздуха появляется на экране сведений о ноде только в том случае, если нода передала телеметрию о качестве воздуха. В режиме просмотра качества воздуха ты можешь:

  • Выбрать временной интервал для графиков.
  • Фильтровать с помощью кнопок метрик — отображаются только те метрики, по которым есть данные.
  • Обновить / запросить последнюю телеметрию о качестве воздуха.
  • Экспортировать в CSV для анализа в электронных таблицах.

💡 Совет: Для получения метрик качества воздуха на удалённой ноде должен быть установлен совместимый датчик. См. Телеметрия и датчики для получения информации о поддерживаемом оборудовании.

Качество сигнала

Информация о качестве радиосигнала:

Метрическая Описание
Сигнал/шум Отношение сигнал/шум (SNR) (чем выше, тем лучше)
RSSI Индикатор уровня принимаемого сигнала (Rssi) (чем ближе к 0, тем лучше)
Уровень собственных шумов Местный фоновый радиочастотный шум в дБм (чем более отрицательное значение, тем тише)
Количество хопов Количество хопов в mesh-сети для последнего сообщения

Оценка качества сигнала

Качество сигнала оценивается по SNR относительно минимального уровня демодуляции активного пресета LoRa-модема, а не по фиксированным порогам — конкретное значение SNR означает разное на разных пресетах (например, −15 дБ нормально для LongSlow, но неприемлемо для ShortFast). RSSI отображается, но не учитывается в оценке. In the table, limit is the preset’s SNR limit.

Качество Критерии
Хороший SNR выше предела пресета
Средний менее чем на 5,5 дБ ниже предела
Плохой от 5,5 до 7,5 дБ ниже предела
Отсутствует более чем на 7,5 дБ ниже предела

См. Понимание измерителя сигнала для полного объяснения.

Локальная статистика твоего подключённого радио также отображается в разделе “Качество сигнала”, когда она доступна. Эти журналы включают уровень шума, счётчики трафика, счётчики ретрансляций, количество нод в сети и время работы радио. График уровня шума использует пунктирную опорную линию на уровне -85 дБм, чтобы помочь определить загруженность радиоэфира.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Метрики питания

Телеметрия управления питанием (требуется датчик INA или совместимое оборудование):

Метрическая Описание
Напряжение Per-channel voltage reading
Ток Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Трассировка маршрута

Трассировка показывает путь сообщения через mesh-сеть:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. Приложение отправляет запрос трассировки целевой ноде.
  3. Results show each hop with its SNR.

Чтение результатов трассировки

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Журнал местоположения

Исторические данные о местоположении для нод, которые делятся своими координатами:

  • GPS координаты
  • Высота
  • Скорость (при движении)
  • Временная метка для каждого отчёта о местоположении

Информация об окружении

Показывает, какие ноды данная нода может слышать напрямую — полезно для понимания топологии mesh-сети.

Метрики хоста

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

Метрика прохожих

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.

Связанные темы


+ Метрики ноды | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Русский
Meshtastic Docs ↗

🌐 Русский — Community translation View in English

Метрики ноды

Экран сведений о ноде предоставляет подробную телеметрию и метрики для каждой ноды твоей mesh-сети.

Просмотр метрик

  1. Перейдите в раздел Ноды.
  2. Нажмите на ноду, которую хотите просмотреть.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Сведения о ноде — локальное устройство

The Position row expands to show location data for nodes that share GPS:

Встроенное содержимое о местоположении

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Метрики обновляются с интервалами, настроенными в параметрах телеметрии каждой ноды.

Интервал передачи

Основная информация о работе, сообщаемая каждой нодой:

Метрическая Описание
Уровень заряда Текущий процент заряда батареи
Напряжение Показания напряжения батареи
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Аптайм Время с момента последней перезагрузки

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Метрики окружения

Данные датчиков окружающей среды (требуется совместимое оборудование):

Метрическая Примеры сенсоров
Температура BME280, BME680, SHT31
Влажность BME280, BME680, SHT31
Давление на барометре BME280, BMP280
Сопротивление газа BME680
IAQ (Качества воздуха) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

Индекс IAQ (качество воздуха в помещении) датчика BME680 представляет собой единое значение от 0 до 500+, полученное на основе сопротивления газа, и отображается на цветовой шкале от “Отлично” до “Опасно загрязнён”:

Шкала индекса IAQ от Отлично до Опасно загрязнён

💡 Совет: Для получения метрик окружающей среды к удалённой ноде должен быть подключён датчик. Не все ноды передают данные об окружающей среде. См. Телеметрия и датчики для получения полного списка поддерживаемых датчиков.

Метрики качества воздуха

Качество воздуха — это отдельный экран метрик для нод, оснащённых датчиком взвешенных частиц и/или CO₂. Этот экран отделён от показателя IAQ датчика BME680, отображаемого в разделе “Метрики окружающей среды” — IAQ представляет собой единый индекс, основанный на сопротивлении газа, тогда как экран качества воздуха показывает графики исходных измерений взвешенных частиц и CO₂.

Метрическая Единица Описание
PM1.0 мкг/м³ Взвешенные частицы размером до 1,0 микрона
PM2.5 мкг/м³ Взвешенные частицы размером до 2,5 микрона
PM10 мкг/м³ Взвешенные частицы размером до 10 микронов
AQI Индекс EPA EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Отображается рядом с PM2.5, как только накопится достаточно показаний.
CO₂ ppm Концентрация углекислого газа
Температура CO₂ °C / °F Температура, сообщаемая самим датчиком CO₂ (например, SCD4x)
Влажность CO₂ % Относительная влажность, сообщаемая датчиком CO₂

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Диапазон Диапазон CO₂ (ppm) Цвет
Хороший < 1000 Зеленый
Душно < 2000 Янтарный
Плохо < 5000 Оранжевый
Небезопасно < 30000 Красный
Эвакуация ≥ 30000 Тёмно-красный

Показания качества воздуха с цветовой кодировкой уровня CO₂

Кнопка журнала/метрик качества воздуха появляется на экране сведений о ноде только в том случае, если нода передала телеметрию о качестве воздуха. В режиме просмотра качества воздуха ты можешь:

  • Выбрать временной интервал для графиков.
  • Фильтровать с помощью кнопок метрик — отображаются только те метрики, по которым есть данные.
  • Обновить / запросить последнюю телеметрию о качестве воздуха.
  • Экспортировать в CSV для анализа в электронных таблицах.

💡 Совет: Для получения метрик качества воздуха на удалённой ноде должен быть установлен совместимый датчик. См. Телеметрия и датчики для получения информации о поддерживаемом оборудовании.

Качество сигнала

Информация о качестве радиосигнала:

Метрическая Описание
Сигнал/шум Отношение сигнал/шум (SNR) (чем выше, тем лучше)
RSSI Индикатор уровня принимаемого сигнала (Rssi) (чем ближе к 0, тем лучше)
Уровень собственных шумов Местный фоновый радиочастотный шум в дБм (чем более отрицательное значение, тем тише)
Количество хопов Количество хопов в mesh-сети для последнего сообщения

Оценка качества сигнала

Качество сигнала оценивается по SNR относительно минимального уровня демодуляции активного пресета LoRa-модема, а не по фиксированным порогам — конкретное значение SNR означает разное на разных пресетах (например, −15 дБ нормально для LongSlow, но неприемлемо для ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Качество Критерии
Хороший SNR выше предела пресета
Средний менее чем на 5,5 дБ ниже предела
Плохой от 5,5 до 7,5 дБ ниже предела
Отсутствует более чем на 7,5 дБ ниже предела

См. Понимание измерителя сигнала для полного объяснения.

Локальная статистика твоего подключённого радио также отображается в разделе “Качество сигнала”, когда она доступна. Эти журналы включают уровень шума, счётчики трафика, счётчики ретрансляций, количество нод в сети и время работы радио. График уровня шума использует пунктирную опорную линию на уровне -85 дБм, чтобы помочь определить загруженность радиоэфира.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Метрики питания

Телеметрия управления питанием (требуется датчик INA или совместимое оборудование):

Метрическая Описание
Напряжение Per-channel voltage reading
Ток Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Трассировка маршрута

Трассировка показывает путь сообщения через mesh-сеть:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. Приложение отправляет запрос трассировки целевой ноде.
  3. Results show each hop with its SNR.

Чтение результатов трассировки

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Журнал местоположения

Исторические данные о местоположении для нод, которые делятся своими координатами:

  • GPS координаты
  • Высота
  • Скорость (при движении)
  • Временная метка для каждого отчёта о местоположении

Информация об окружении

Показывает, какие ноды данная нода может слышать напрямую — полезно для понимания топологии mesh-сети.

Метрики хоста

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

Метрика прохожих

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.

Связанные темы


diff --git a/main/ru-rRU/user/nodes.html b/main/ru-rRU/user/nodes.html index b6ef63597a..6afc4f118f 100644 --- a/main/ru-rRU/user/nodes.html +++ b/main/ru-rRU/user/nodes.html @@ -1 +1 @@ - Ноды | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Русский
Meshtastic Docs ↗

🌐 Русский — Community translation View in English

Ноды

The Nodes screen lists every node visible on your mesh.

Список узлов

Список нод показывает все ноды, которые услышало твоё радиоустройство, включая:

  • Имя ноды — длинное имя, настроенное пользователем
  • Короткое имя — 4-символьный идентификатор
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Последнее услышанное — время с последнего общения
  • Расстояние — предполагаемое расстояние (если позиции общие)
  • Батарея — уровень заряда батареи удалённой ноды (если включена телеметрия)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Индикаторы состояния ноды

Индикатор Значение
Green last-heard time Нода слышна за последние 2 часа
Plain last-heard time Нода не отвечала больше 2 часов
⭐ Избранный Node you marked as a favorite.

There is no separate “away” tier.

Роли ноды

У нод можно настраивать разные роли, которые влияют на их поведение в сети:

Роль Описание
Client Standard end-user node
Client Base Обрабатывает трафик избранных нод как приоритет Router Late; весь остальной трафик как Client
Client Mute Принимает, но не ретранслирует
Client Hidden Как Client Mute, плюс скрыт из списка нод
Router Ставит в приоритет пересылку сообщений; не засыпает чтобы передавать их
Router Late Инфраструктурная нода, которая ретранслирует один раз, но только после всех остальных режимов (обеспечивает дополнительное покрытие)
Router Client ⚠️ Устарело (удалено в прошивке 2.3.15) — больше не выбирается; используй вместо этого Router или Client
Repeater ⚠️ Устарело (удалено в прошивке 2.7.11) — больше не выбирается; используй вместо этого Router
Tracker Оптимизировано для передачи данных о местоположении через регулярные промежутки времени
Sensor Оптимизировано для данных телеметрии
Тактический Взаимодействует с системами TAK (отправляет/принимает CoT)
TAK Tracker Только отчет о позиции TAK
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Выбор роли

Большинству пользователей стоит оставить роль Client по умолчанию. Рассмотри другую роль, когда:

  • Router — У тебя есть узел в фиксированном, высоком месте с надежным источником питания (крыша, вершина холма). Router постоянно бодрствуют, чтобы пересылать сообщения для других, и они необходимы для расширения покрытия сети. Don’t use Router on battery-powered handheld radios.
  • Router Late — инфраструктурная нода, которая всегда пересылает пакеты только один раз, но только после того, как все другие режимы маршрутизации выполнили свои ходы. Обеспечивает дополнительное покрытие для локальных кластеров, не конкурируя с основными роутерами.
  • Client Base — обрабатывает трафик от/к вашим избранным нодам с приоритетом Router Late (обеспечивая этим сообщениям дополнительное ретранслирование), а всё остальное обрабатывает как обычный Client.
  • Client Mute — хочешь принимать трафик сети, но не участвовать в его ретрансляции. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Спит между передачами для экономии батареи.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Похожий профиль мощности на Tracker.
  • TAK / TAK Tracker — нужно только если работать с системами ATAK/WinTAK. Смотри Интеграция TAK для подробностей.

💡 Совет: Сеть работает лучше, когда большинство нод Client или Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. Хорошее практическое правило: один роутер на 5–10 клиентов в вашей зоне.

Индикаторы шифрования

У нод рядом с именем отображаются значки статуса шифрования:

Значок Значение
🔒 Заблокировано Связь использует PKI (инфраструктуру публичных ключей) — сквозное шифрование с проверкой идентичности
🔓 Разблокировано No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Несовпадение Несовпадение открытого ключа — ключ ноды изменился с последнего раза (разберитесь, прежде чем доверять)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. Если видишь предупреждение о несоответствии ключа, нода могла быть сброшена или скомпрометирована.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Быстрые действия

Из списка нод ты можешь:

  • Нажмите на ноду, чтобы увидеть её страницу с деталями
  • Touch & hold for quick actions:
    • Отметить/убрать из избранного
    • Отключить/включить уведомления
    • Отправить личное сообщение
    • Трассировка
    • Игнорировать/разблокировать
    • Удалить

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Фильтрация и сортировка

Поиск текста

Введи в поле поиска, чтобы отфильтровать ноды по имени или короткому имени. Фильтр обновляется в реальном времени по мере набора текста.

Переключатели фильтра

Фильтр Описание
Hide offline nodes Показывать только ноды, услышанные за последние 2 часа
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Включить неизвестные Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Исключить инфраструктуру Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Исключить MQTT Скрыть ноды, слышимые только через интернет-мост MQTT
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Параметры сортировки

Сортировка Описание
Last heard Сначала недавно слышимые ноды
A-Z Сортировать по полному имени ноды
Расстояние Сначала ближайшие ноды (требуется обмен позициями)
Меньше хопов Сначала с наименьшим количеством ретрансляций
Канал Группировать по индексу канала
via MQTT Сгруппировать по MQTT и радиоприему
via Favorite (default) Favorited nodes first, then the rest

Нод на хоп

Нажми на значок гистограммы хопов в панели приложений списка нод, чтобы открыть столбчатую диаграмму того, сколько нод находится на каждом расстоянии хопа (0 = напрямую, 1 = через один ретранслятор и так далее). Отфильтруй график по окну последнего услышанного — за всё время, 1 час, 8 часов или 24 часа — чтобы посмотреть, как сейчас выглядит сеть по сравнению с более длительным периодом. Это быстрый способ понять, насколько занята и разветвлена твоя местная сеть.

Детали ноды

Нажатие на ноду открывает подробный вид с полной информацией. Смотри Метрики ноды для полной информации о метриках и телеметрии.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Раздел деталей ноды

Встроенные индикаторы статуса показывают ключевые показатели с первого взгляда:

Индикатор Снимок экрана
Качество сигнала Сигнал
Уровень заряда батареи Батарея
Количество хопов Хопы
Последний раз слышен Last heard
Расстояние Расстояние

Ссылки на устройства (“Хочу такое”)

Когда оборудование ноды распознано, в детальном просмотре появляется сворачиваемый раздел “Хочу такой”, содержащий ссылки на места, где можно купить или узнать больше об этом устройстве: страницу продукта у производителя, варианты продукта и объявления на региональных торговых площадках (например, AliExpress, Amazon и у поддерживаемых продавцов), отфильтрованные по твоей стране. Каждая ссылка открывается через сервис перенаправления msh.to. Устройства без подходящих ссылок не показывают этот раздел.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

Связанные темы


+ Ноды | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Русский
Meshtastic Docs ↗

🌐 Русский — Community translation View in English

Ноды

The Nodes screen lists every node visible on your mesh.

Список узлов

Список нод показывает все ноды, которые услышало твоё радиоустройство, включая:

  • Имя ноды — длинное имя, настроенное пользователем
  • Короткое имя — 4-символьный идентификатор
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Последнее услышанное — время с последнего общения
  • Расстояние — предполагаемое расстояние (если позиции общие)
  • Батарея — уровень заряда батареи удалённой ноды (если включена телеметрия)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Индикаторы состояния ноды

Индикатор Значение
Green last-heard time Нода слышна за последние 2 часа
Plain last-heard time Нода не отвечала больше 2 часов
⭐ Избранный Node you marked as a favorite.

There is no separate “away” tier.

Роли ноды

У нод можно настраивать разные роли, которые влияют на их поведение в сети:

Роль Описание
Client Standard end-user node
Client Base Обрабатывает трафик избранных нод как приоритет Router Late; весь остальной трафик как Client
Client Mute Принимает, но не ретранслирует
Client Hidden Как Client Mute, плюс скрыт из списка нод
Router Ставит в приоритет пересылку сообщений; не засыпает чтобы передавать их
Router Late Инфраструктурная нода, которая ретранслирует один раз, но только после всех остальных режимов (обеспечивает дополнительное покрытие)
Router Client ⚠️ Устарело (удалено в прошивке 2.3.15) — больше не выбирается; используй вместо этого Router или Client
Repeater ⚠️ Устарело (удалено в прошивке 2.7.11) — больше не выбирается; используй вместо этого Router
Tracker Оптимизировано для передачи данных о местоположении через регулярные промежутки времени
Sensor Оптимизировано для данных телеметрии
Тактический Взаимодействует с системами TAK (отправляет/принимает CoT)
TAK Tracker Только отчет о позиции TAK
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Выбор роли

Большинству пользователей стоит оставить роль Client по умолчанию. Рассмотри другую роль, когда:

  • Router — У тебя есть узел в фиксированном, высоком месте с надежным источником питания (крыша, вершина холма). Router постоянно бодрствуют, чтобы пересылать сообщения для других, и они необходимы для расширения покрытия сети. Don’t use Router on battery-powered handheld radios.
  • Router Late — инфраструктурная нода, которая всегда пересылает пакеты только один раз, но только после того, как все другие режимы маршрутизации выполнили свои ходы. Обеспечивает дополнительное покрытие для локальных кластеров, не конкурируя с основными роутерами.
  • Client Base — обрабатывает трафик от/к вашим избранным нодам с приоритетом Router Late (обеспечивая этим сообщениям дополнительное ретранслирование), а всё остальное обрабатывает как обычный Client.
  • Client Mute — хочешь принимать трафик сети, но не участвовать в его ретрансляции. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Спит между передачами для экономии батареи.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Похожий профиль мощности на Tracker.
  • TAK / TAK Tracker — нужно только если работать с системами ATAK/WinTAK. Смотри Интеграция TAK для подробностей.

💡 Совет: Сеть работает лучше, когда большинство нод Client или Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. Хорошее практическое правило: один роутер на 5–10 клиентов в вашей зоне.

Индикаторы шифрования

У нод рядом с именем отображаются значки статуса шифрования:

Значок Значение
🔒 Заблокировано Связь использует PKI (инфраструктуру публичных ключей) — сквозное шифрование с проверкой идентичности
🔓 Разблокировано No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Несовпадение Несовпадение открытого ключа — ключ ноды изменился с последнего раза (разберитесь, прежде чем доверять)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. Если видишь предупреждение о несоответствии ключа, нода могла быть сброшена или скомпрометирована.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Быстрые действия

Из списка нод ты можешь:

  • Нажмите на ноду, чтобы увидеть её страницу с деталями
  • Touch & hold for quick actions:
    • Отметить/убрать из избранного
    • Отключить/включить уведомления
    • Отправить личное сообщение
    • Трассировка
    • Игнорировать/разблокировать
    • Удалить

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Фильтрация и сортировка

Поиск текста

Введи в поле поиска, чтобы отфильтровать ноды по имени или короткому имени. Фильтр обновляется в реальном времени по мере набора текста.

Переключатели фильтра

Фильтр Описание
Hide offline nodes Показывать только ноды, услышанные за последние 2 часа
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Включить неизвестные Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Исключить инфраструктуру Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Исключить MQTT Скрыть ноды, слышимые только через интернет-мост MQTT
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Параметры сортировки

Сортировка Описание
Last heard Сначала недавно слышимые ноды
A-Z Сортировать по полному имени ноды
Расстояние Сначала ближайшие ноды (требуется обмен позициями)
Меньше хопов Сначала с наименьшим количеством ретрансляций
Канал Группировать по индексу канала
via MQTT Сгруппировать по MQTT и радиоприему
via Favorite (default) Favorited nodes first, then the rest

Нод на хоп

Нажми на значок гистограммы хопов в панели приложений списка нод, чтобы открыть столбчатую диаграмму того, сколько нод находится на каждом расстоянии хопа (0 = напрямую, 1 = через один ретранслятор и так далее). Отфильтруй график по окну последнего услышанного — за всё время, 1 час, 8 часов или 24 часа — чтобы посмотреть, как сейчас выглядит сеть по сравнению с более длительным периодом. Это быстрый способ понять, насколько занята и разветвлена твоя местная сеть.

Детали ноды

Нажатие на ноду открывает подробный вид с полной информацией. Смотри Метрики ноды для полной информации о метриках и телеметрии.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Раздел деталей ноды

Встроенные индикаторы статуса показывают ключевые показатели с первого взгляда:

Индикатор Снимок экрана
Качество сигнала Сигнал
Уровень заряда батареи Батарея
Количество хопов Хопы
Последний раз слышен Last heard
Расстояние Расстояние

Ссылки на устройства (“Хочу такое”)

Когда оборудование ноды распознано, в детальном просмотре появляется сворачиваемый раздел “Хочу такой”, содержащий ссылки на места, где можно купить или узнать больше об этом устройстве: страницу продукта у производителя, варианты продукта и объявления на региональных торговых площадках (например, AliExpress, Amazon и у поддерживаемых продавцов), отфильтрованные по твоей стране. Каждая ссылка открывается через сервис перенаправления msh.to. Устройства без подходящих ссылок не показывают этот раздел.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

Связанные темы


diff --git a/main/ru-rRU/user/settings-radio-user.html b/main/ru-rRU/user/settings-radio-user.html index cdd532b026..d97e5a7bf5 100644 --- a/main/ru-rRU/user/settings-radio-user.html +++ b/main/ru-rRU/user/settings-radio-user.html @@ -1 +1 @@ - Настройки - Радио и пользователь | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Русский
Meshtastic Docs ↗

🌐 Русский — Community translation View in English

Настройки - Радио и пользователь

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Настройки используют стандартные элементы управления предпочтениями — выпадающие списки, переключатели и ползунки:

Управление Снимок экрана
Выпадающий список A dropdown setting, expanded to show its list of options
Переключатель A toggle setting in the on position
Ползунок A slider setting with its current numeric value shown

Настройки пользователя

Профиль пользователя

On Settings → User.

Настройка Описание
Полное имя Ваше отображаемое имя (до 39 символов)
Короткое имя 4-символьное сокращённое имя
Состояние сообщения A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Без сообщений Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Лицензия радиолюбителя (HAM) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Применение изменений

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Настройки

Настройки устройства

On Settings → Device configuration → Device.

Настройка Описание По умолчанию
Роль устройства Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим ретрансляции How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Интервал вещания передачи информации об узле How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Двойное нажатие как кнопка Treat a double tap as a button press Включено
Маякнуть при тройном нажатии Send an ad-hoc position ping on a triple click Включено
Сердцебиение светодиодом Blink the status LED periodically Включено
Часовой пояс POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

Настройка LoRa

On Settings → LoRa.

Настройка Описание По умолчанию
Регион / Страна Regulatory region for frequency bands. You must set this before transmitting Не установлено (необходимо настроить)
Шаблоны Компромисс между скоростью и дальностью LongFast
Количество прыжков Максимальное количество ретрансляций 3
Мощность передатчика Мощность передачи (дБм); 0 = максимально разрешённая для региона 0 (максимум региона)
Переопределить частоту Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Использовать шаблон On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Коэффициент распространения Manual mode only: 7–12. Higher spreads further but slower From preset
Частота кодирования Manual mode only: 5–8. More redundancy costs airtime From preset
Ширина канала Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Частота слота Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Передача включена Turning this off makes the node receive-only On
Переопределить рабочий цикл Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Выкл
Игнорировать MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
ОК в MQTT Allow your packets to be forwarded to MQTT by gateways Выкл
Усиление RX Extra receive gain on SX126x radios; costs a little current Выкл
PA вентилятор выключен Turn off the power-amplifier fan on hardware that has one Выкл

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. Смотрите руководство по настройке региона на сайте meshtastic.org для получения подробной информации.

Предустановки модема

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Совет: Значения порога SNR специально отрицательные. LoRa может декодировать сигналы ниже уровня шума, поэтому более отрицательный предел означает, что пресет допускает более слабый, шумный сигнал (больший радиус действия). Смотрите Как работает измеритель сигнала для полного объяснения.

Предустановка Диапазон Скорость Предел SNR Лучше всего для
Short Turbo ~1 км 21.9 кб/с −7.5 дБ Плотная городская застройка с прямой видимостью; приложения, требующие высокой передачи данных
Short Fast ~3 км 10.9 кб/с −7.5 дБ Городские районы; здания в пределах нескольких кварталов
Short Slow ~5 км 6.25 kbps -10 дБ Пригородная зона с коротким диапазоном; умеренная плотность застройки
Medium Fast ~5 км 3.52 kbps −12.5 дБ Пригородные районы; умеренная плотность застройки
Medium Slow ~8 км 1.95 kbps -15 дБ Пригородный/сельский; умеренный диапазон со сниженной скоростью
Long Turbo ~10 км 1.34 kbps −12.5 дБ Диапазон, похожий на Long Fast, но с полосой пропускания 500 кГц; более высокая пропускная способность
Long Fast ~10 км 1.1 кб/с −17.5 дБ Общее использование (по умолчанию) — сбалансированный диапазон и скорость
Long Moderate ~20 км 0.34 кб/с −17.5 дБ Сельская местность с некоторым рельефом; случайное использование
Lite Fast ~5 км 1.76 kbps −12.5 дБ Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Medium Fast
Lite Slow ~10 км 0.98 kbps -15 дБ Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Long Fast
Narrow Fast ~5 км 2.28 kbps -10 дБ Диапазон RU 868 МГц (полоса пропускания 62,5 кГц); предотвращает помехи с другими устройствами
Narrow Slow ~10 км 1.30 kbps −12.5 дБ Диапазон RU 868 МГц (ширина полосы 62,5 кГц); аналогично Long Fast
Medium Turbo ~5 км 7.0 kbps −12.5 дБ Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 км 0.68 kbps −7.5 дБ Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 км 0.33 kbps -10 дБ Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 км 0.18 кб/с −20 дБ ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки
Very Long Slow ~40+ км 0.09 кб/с −20 дБ ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки

i Примечание: В этой таблице используются общие короткие имена. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Выбор предустановки модема

Предустановка модема управляет основным компромиссом между дальностью и скоростью передачи данных:

  • Медленные предустановки используют большее распространение, что позволяет декодировать сигналы при более слабых уровнях сигнала (ниже порога SNR). Это означает большую дальность, но меньше байт в секунду.
  • Быстрые предустановки передают больше данных за одну передачу, но требуют более сильного сигнала для декодирования.

Практическое руководство:

  • Городская сеть (много нод, короткие расстояния): Используй Long Fast (по умолчанию) или Short Fast. Более высокая скорость означает меньшее переполнение канала эфирного времени, когда многие ноды используют канал.
  • Сельская/разреженная сеть (мало нод, большие расстояния): Используй Long Moderate. Дальность важнее скорости, когда ноды находятся далеко друг от друга.
  • Соответствие нормативным требованиям RU 866/868 МГц: Используй Lite Fast, Lite Slow, Narrow Fast или Narrow Slow — они оптимизированы для диапазонов RU SRD/868 МГц с более узкой полосой пропускания.
  • Фиксированные инфраструктурные связи: Используй Short Turbo или Long Turbo для выделенных соединений точка-точка с хорошими антеннами и прямой видимостью.
  • Смешанные среды: Используй Long Fast — это настройка по умолчанию в сообществе и она обеспечит совместимость с другими в вашем регионе.

All nodes on the same channel must use the same modem preset. Ноды с несовпадающими предустановками не смогут обмениваться данными, даже если они используют одну частоту и ключ шифрования.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Преимущество высоты (вершина холма, крыша) значительно увеличивает эффективную дальность. Хорошо размещённый маршрутизатор с Long Fast часто может превзойти наземную ноду с Long Slow.

Параметры дисплея

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Настройка Описание
Включать экран на How long the display stays lit before sleeping
Интервал карусели How often the radio cycles between screens on its own
Режим экрана Screen layout/density used by the firmware
Система измерения Metric or Imperial on the radio’s screen
Использовать 12-часовой формат времени Show the radio’s clock as 12-hour rather than 24-hour
Выделять заголовок жирным Draw the screen’s heading text in bold
Повернуть экран Rotate the display 180° for an inverted mounting
Тип OLED Авто, SSD1306, SH1106, SH1107
Включать экран при касании или движении Light the screen when the radio is tapped or moved
Направление компаса Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Всегда указывать на север Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Настройки местоположения

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Настройка Описание
Режим GPS (физическое оборудование) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Интервал опроса GPS How often the radio asks its GPS for a fix
Период рассылки How often the position is shared with the mesh
Умная позиция Broadcast based on movement rather than purely on the clock
Умный интервал With Smart Position on, the shortest gap between broadcasts
Умное расстояние With Smart Position on, how far you must move before broadcasting
Фиксированная позиция Use a manually entered latitude, longitude and altitude instead of the GPS
Флаги позиции A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Настройка питания

On Settings → Device configuration → Power.

Настройка Описание
Включить режим энергосбережения Let the radio sleep aggressively between activity
Выключение при потере мощности Power the device down after external power disappears
Длительность супер-глубокого сна How long the deepest sleep state lasts
Минимальное время бодрствования The shortest time the radio stays awake once woken
Длительность ожидания Bluetooth How long to wait for a phone to connect before sleeping
Коэффициент переопределения ADC Turn on a manual correction for battery-voltage readings
Коэффициент переопределения ADC The correction factor itself, used only when the override is on
I2C-адрес INA_2XX батареи Address of an external INA-series power sensor, if fitted

Настройка сети

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Настройка Описание
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
Название сети Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Пароль Пароль сети
Ethernet включен Use a wired connection on hardware that has one
Режим IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP трансляция Share mesh traffic with other nodes over the local network
NTP-сервер Сервер синхронизации времени
Сервер rsyslog Удалённый сервер логирования

Network Config with a static IPv4 address entered

Настройка Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Настройка Описание
Bluetooth включен Включение/отключение BLE радиостанции
Режим сопряжения Фиксированный PIN, случайный PIN или без PIN
Фиксированный PIN-код PIN code for pairing. Must be exactly six digits — the field rejects anything else

Настройки безопасности

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Настройка Описание
Публичный ключ Публичный ключ твоей ноды (только для чтения)
Ключ администратора Keys permitted to administer this node remotely — up to three
Приватный ключ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Пересоздать приватный ключ Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Канал администратора включен ⚠️ Удалено — теперь настраивается автоматически при установке ключа администратора
Консоль COM-порта Serial console over the Stream API
API журнала отладки включен Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Управляемый режим Restrict non-admin channel changes. Only selectable once an Admin Key is set
Резервное копирование Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Восстановить ключи Запишисать сохранённые ключи обратно на ноду (доступно, как только есть резервная копия)
Удалить резервную копию ключа Remove the stored key backup from this phone
Уровень защиты How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field Что она делает
Осталось загрузок How many device boots the unlocked state survives
Часов до истечения Wall-clock lifetime of the unlocked state
Ограничение сессии (минуты) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

Связанные темы


+ Настройки - Радио и пользователь | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Русский
Meshtastic Docs ↗

🌐 Русский — Community translation View in English

Настройки - Радио и пользователь

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Настройки используют стандартные элементы управления предпочтениями — выпадающие списки, переключатели и ползунки:

Управление Снимок экрана
Выпадающий список A dropdown setting, expanded to show its list of options
Переключатель A toggle setting in the on position
Ползунок A slider setting with its current numeric value shown

Настройки пользователя

Профиль пользователя

On Settings → User.

Настройка Описание
Полное имя Ваше отображаемое имя (до 39 символов)
Короткое имя 4-символьное сокращённое имя
Состояние сообщения A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Без сообщений Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Лицензия радиолюбителя (HAM) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Применение изменений

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Настройки

Настройки устройства

On Settings → Device configuration → Device.

Настройка Описание По умолчанию
Роль устройства Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим ретрансляции How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Интервал вещания передачи информации об узле How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Двойное нажатие как кнопка Treat a double tap as a button press Включено
Маякнуть при тройном нажатии Send an ad-hoc position ping on a triple click Включено
Сердцебиение светодиодом Blink the status LED periodically Включено
Часовой пояс POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

Настройка LoRa

On Settings → LoRa.

Настройка Описание По умолчанию
Регион / Страна Regulatory region for frequency bands. You must set this before transmitting Не установлено (необходимо настроить)
Шаблоны Компромисс между скоростью и дальностью LongFast
Количество прыжков Максимальное количество ретрансляций 3
Мощность передатчика Мощность передачи (дБм); 0 = максимально разрешённая для региона 0 (максимум региона)
Переопределить частоту Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Использовать шаблон On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Коэффициент распространения Manual mode only: 7–12. Higher spreads further but slower From preset
Частота кодирования Manual mode only: 5–8. More redundancy costs airtime From preset
Ширина канала Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Частота слота Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Передача включена Turning this off makes the node receive-only On
Переопределить рабочий цикл Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Выкл
Игнорировать MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
ОК в MQTT Allow your packets to be forwarded to MQTT by gateways Выкл
Усиление RX Extra receive gain on SX126x radios; costs a little current Выкл
PA вентилятор выключен Turn off the power-amplifier fan on hardware that has one Выкл

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. Смотрите руководство по настройке региона на сайте meshtastic.org для получения подробной информации.

Предустановки модема

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Совет: Значения порога SNR специально отрицательные. LoRa может декодировать сигналы ниже уровня шума, поэтому более отрицательный предел означает, что пресет допускает более слабый, шумный сигнал (больший радиус действия). Смотрите Как работает измеритель сигнала для полного объяснения.

Предустановка Диапазон Скорость Предел SNR Лучше всего для
Short Turbo ~1 км 21.9 кб/с −7.5 дБ Плотная городская застройка с прямой видимостью; приложения, требующие высокой передачи данных
Short Fast ~3 км 10.9 кб/с −7.5 дБ Городские районы; здания в пределах нескольких кварталов
Short Slow ~5 км 6.25 kbps -10 дБ Пригородная зона с коротким диапазоном; умеренная плотность застройки
Medium Fast ~5 км 3.52 kbps −12.5 дБ Пригородные районы; умеренная плотность застройки
Medium Slow ~8 км 1.95 kbps -15 дБ Пригородный/сельский; умеренный диапазон со сниженной скоростью
Long Turbo ~10 км 1.34 kbps −17.5 дБ Диапазон, похожий на Long Fast, но с полосой пропускания 500 кГц; более высокая пропускная способность
Long Fast ~10 км 1.1 кб/с −17.5 дБ Общее использование (по умолчанию) — сбалансированный диапазон и скорость
Long Moderate ~20 км 0.34 кб/с −17.5 дБ Сельская местность с некоторым рельефом; случайное использование
Lite Fast ~5 км 1.76 kbps −12.5 дБ Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Medium Fast
Lite Slow ~10 км 0.98 kbps -15 дБ Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Long Fast
Narrow Fast ~5 км 2.28 kbps −7.5 дБ Диапазон RU 868 МГц (полоса пропускания 62,5 кГц); предотвращает помехи с другими устройствами
Narrow Slow ~10 км 1.30 kbps -10 дБ Диапазон RU 868 МГц (ширина полосы 62,5 кГц); аналогично Long Fast
Medium Turbo ~5 км 7.0 kbps −12.5 дБ Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 км 0.68 kbps −7.5 дБ Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 км 0.33 kbps -10 дБ Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 км 0.18 кб/с −20 дБ ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки
Very Long Slow ~40+ км 0.09 кб/с −20 дБ ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки

i Примечание: В этой таблице используются общие короткие имена. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Выбор предустановки модема

Предустановка модема управляет основным компромиссом между дальностью и скоростью передачи данных:

  • Медленные предустановки используют большее распространение, что позволяет декодировать сигналы при более слабых уровнях сигнала (ниже порога SNR). Это означает большую дальность, но меньше байт в секунду.
  • Быстрые предустановки передают больше данных за одну передачу, но требуют более сильного сигнала для декодирования.

Практическое руководство:

  • Городская сеть (много нод, короткие расстояния): Используй Long Fast (по умолчанию) или Short Fast. Более высокая скорость означает меньшее переполнение канала эфирного времени, когда многие ноды используют канал.
  • Сельская/разреженная сеть (мало нод, большие расстояния): Используй Long Moderate. Дальность важнее скорости, когда ноды находятся далеко друг от друга.
  • Соответствие нормативным требованиям RU 866/868 МГц: Используй Lite Fast, Lite Slow, Narrow Fast или Narrow Slow — они оптимизированы для диапазонов RU SRD/868 МГц с более узкой полосой пропускания.
  • Фиксированные инфраструктурные связи: Используй Short Turbo или Long Turbo для выделенных соединений точка-точка с хорошими антеннами и прямой видимостью.
  • Смешанные среды: Используй Long Fast — это настройка по умолчанию в сообществе и она обеспечит совместимость с другими в вашем регионе.

All nodes on the same channel must use the same modem preset. Ноды с несовпадающими предустановками не смогут обмениваться данными, даже если они используют одну частоту и ключ шифрования.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Преимущество высоты (вершина холма, крыша) значительно увеличивает эффективную дальность. Хорошо размещённый маршрутизатор с Long Fast часто может превзойти наземную ноду с Long Slow.

Параметры дисплея

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Настройка Описание
Включать экран на How long the display stays lit before sleeping
Интервал карусели How often the radio cycles between screens on its own
Режим экрана Screen layout/density used by the firmware
Система измерения Metric or Imperial on the radio’s screen
Использовать 12-часовой формат времени Show the radio’s clock as 12-hour rather than 24-hour
Выделять заголовок жирным Draw the screen’s heading text in bold
Повернуть экран Rotate the display 180° for an inverted mounting
Тип OLED Авто, SSD1306, SH1106, SH1107
Включать экран при касании или движении Light the screen when the radio is tapped or moved
Направление компаса Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Всегда указывать на север Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Настройки местоположения

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Настройка Описание
Режим GPS (физическое оборудование) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Интервал опроса GPS How often the radio asks its GPS for a fix
Период рассылки How often the position is shared with the mesh
Умная позиция Broadcast based on movement rather than purely on the clock
Умный интервал With Smart Position on, the shortest gap between broadcasts
Умное расстояние With Smart Position on, how far you must move before broadcasting
Фиксированная позиция Use a manually entered latitude, longitude and altitude instead of the GPS
Флаги позиции A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Настройка питания

On Settings → Device configuration → Power.

Настройка Описание
Включить режим энергосбережения Let the radio sleep aggressively between activity
Выключение при потере мощности Power the device down after external power disappears
Длительность супер-глубокого сна How long the deepest sleep state lasts
Минимальное время бодрствования The shortest time the radio stays awake once woken
Длительность ожидания Bluetooth How long to wait for a phone to connect before sleeping
Коэффициент переопределения ADC Turn on a manual correction for battery-voltage readings
Коэффициент переопределения ADC The correction factor itself, used only when the override is on
I2C-адрес INA_2XX батареи Address of an external INA-series power sensor, if fitted

Настройка сети

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Настройка Описание
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
Название сети Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Пароль Пароль сети
Ethernet включен Use a wired connection on hardware that has one
Режим IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP трансляция Share mesh traffic with other nodes over the local network
NTP-сервер Сервер синхронизации времени
Сервер rsyslog Удалённый сервер логирования

Network Config with a static IPv4 address entered

Настройка Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Настройка Описание
Bluetooth включен Включение/отключение BLE радиостанции
Режим сопряжения Фиксированный PIN, случайный PIN или без PIN
Фиксированный PIN-код PIN code for pairing. Must be exactly six digits — the field rejects anything else

Настройки безопасности

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Настройка Описание
Публичный ключ Публичный ключ твоей ноды (только для чтения)
Ключ администратора Keys permitted to administer this node remotely — up to three
Приватный ключ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Пересоздать приватный ключ Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Канал администратора включен ⚠️ Удалено — теперь настраивается автоматически при установке ключа администратора
Консоль COM-порта Serial console over the Stream API
API журнала отладки включен Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Управляемый режим Restrict non-admin channel changes. Only selectable once an Admin Key is set
Резервное копирование Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Восстановить ключи Запишисать сохранённые ключи обратно на ноду (доступно, как только есть резервная копия)
Удалить резервную копию ключа Remove the stored key backup from this phone
Уровень защиты How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field Что она делает
Осталось загрузок How many device boots the unlocked state survives
Часов до истечения Wall-clock lifetime of the unlocked state
Ограничение сессии (минуты) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.

Связанные темы


diff --git a/main/ru-rRU/user/signal-meter.html b/main/ru-rRU/user/signal-meter.html index a44f5273c9..a990bd22f5 100644 --- a/main/ru-rRU/user/signal-meter.html +++ b/main/ru-rRU/user/signal-meter.html @@ -1 +1 @@ - Как работает измеритель сигнала Meshtastic | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Русский
Meshtastic Docs ↗

🌐 Русский — Community translation View in English

Как работает измеритель сигнала Meshtastic

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Уровень Деления Критерии Значение
Хороший Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Средний 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Плохой 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Отсутствует 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Где появляется информация о сигнале

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Трассировка — качество сигнала на каждой промежуточной ноде
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon

Связанные темы


+ Как работает измеритель сигнала Meshtastic | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Русский
Meshtastic Docs ↗

🌐 Русский — Community translation View in English

Как работает измеритель сигнала Meshtastic

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Уровень Деления Критерии Значение
Хороший Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Средний 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Плохой 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Отсутствует 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Где появляется информация о сигнале

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Трассировка — качество сигнала на каждой промежуточной ноде
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon

Связанные темы


diff --git a/main/sk-rSK/user/node-metrics.html b/main/sk-rSK/user/node-metrics.html index 62e51a47de..2459f64df7 100644 --- a/main/sk-rSK/user/node-metrics.html +++ b/main/sk-rSK/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Slovenčina
Meshtastic Docs ↗

🌐 Slovenčina — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Popis
Battery Level Current battery percentage
Napätie Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Doba prevádzky Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Teplota BME280, BME680, SHT31
Vlhkosť BME280, BME680, SHT31
Barometrický tlak BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Popis
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Dobrý < 1000 Zelená
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Červená
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Kvalita signálu

Radio signal quality information:

Metric Popis
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Dobrý SNR above the preset’s limit
Primeraný less than 5.5 dB below the limit
Zlý 5.5 dB to 7.5 dB below the limit
Žiadny more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Popis
Napätie Per-channel voltage reading
Prúd Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Trasovanie

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Log pozície

Historical position data for nodes that share their location:

  • GPS coordinates
  • Nadmorská výška
  • Speed (if moving)
  • Timestamp for each position report

Informácia o susedoch

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Slovenčina
Meshtastic Docs ↗

🌐 Slovenčina — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Popis
Battery Level Current battery percentage
Napätie Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Doba prevádzky Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Teplota BME280, BME680, SHT31
Vlhkosť BME280, BME680, SHT31
Barometrický tlak BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Popis
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Dobrý < 1000 Zelená
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Červená
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Kvalita signálu

Radio signal quality information:

Metric Popis
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Dobrý SNR above the preset’s limit
Primeraný less than 5.5 dB below the limit
Zlý 5.5 dB to 7.5 dB below the limit
Žiadny more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Popis
Napätie Per-channel voltage reading
Prúd Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Trasovanie

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Log pozície

Historical position data for nodes that share their location:

  • GPS coordinates
  • Nadmorská výška
  • Speed (if moving)
  • Timestamp for each position report

Informácia o susedoch

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/sk-rSK/user/nodes.html b/main/sk-rSK/user/nodes.html index 082dbbf0ac..56d1a101ec 100644 --- a/main/sk-rSK/user/nodes.html +++ b/main/sk-rSK/user/nodes.html @@ -1 +1 @@ - Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Slovenčina
Meshtastic Docs ↗

🌐 Slovenčina — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Rola Popis
Klient Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Stlmený Klient Receives but doesn’t retransmit
Skrytý Klient Like Client Mute, plus hides from node list
Smerovač Prioritizes message forwarding; stays awake to relay
Smerovač s Oneskorením Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Sledovač Optimized for position reporting at regular intervals
Senzor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Sledovač TAK position reporting only
Straty a nálezy Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Odstrániť

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filter Popis
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Popis
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Posledný príjem Last heard
Vzdialenosť Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Slovenčina
Meshtastic Docs ↗

🌐 Slovenčina — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Rola Popis
Klient Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Stlmený Klient Receives but doesn’t retransmit
Skrytý Klient Like Client Mute, plus hides from node list
Smerovač Prioritizes message forwarding; stays awake to relay
Smerovač s Oneskorením Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Sledovač Optimized for position reporting at regular intervals
Senzor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Sledovač TAK position reporting only
Straty a nálezy Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Odstrániť

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filter Popis
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Popis
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Posledný príjem Last heard
Vzdialenosť Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/sk-rSK/user/settings-radio-user.html b/main/sk-rSK/user/settings-radio-user.html index 6814191483..9c77e7724d 100644 --- a/main/sk-rSK/user/settings-radio-user.html +++ b/main/sk-rSK/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Slovenčina
Meshtastic Docs ↗

🌐 Slovenčina — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Popis
Dlhé Meno Your display name (up to 39 characters)
Krátke Meno 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Konfigurácia Zariadenia

On Settings → Device configuration → Device.

Setting Popis Predvolené
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

Konfigurácia LoRa

On Settings → LoRa.

Setting Popis Predvolené
Región Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Šírka pásma Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Rýchlosť SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Konfigurácia Displeju

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Popis
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Otoč Obrazovku Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Popis
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcastový Interval How often the position is shared with the mesh
Inteligentná poloha Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixná Pozícia Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Popis
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Konfigurácia siete

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Popis
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Heslo Network password
Ethernet zapnutý Use a wired connection on hardware that has one
IPv4 režim DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Konfigurácia Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Popis
Bluetooth zapnuté Enable/disable BLE radio
Režim párovania Fixed PIN, Random PIN, or No PIN
Pevný PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Popis
Verejný kľúč Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Súkromný kľúč Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Slovenčina
Meshtastic Docs ↗

🌐 Slovenčina — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Popis
Dlhé Meno Your display name (up to 39 characters)
Krátke Meno 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Konfigurácia Zariadenia

On Settings → Device configuration → Device.

Setting Popis Predvolené
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

Konfigurácia LoRa

On Settings → LoRa.

Setting Popis Predvolené
Región Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Šírka pásma Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Rýchlosť SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Konfigurácia Displeju

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Popis
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Otoč Obrazovku Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Popis
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcastový Interval How often the position is shared with the mesh
Inteligentná poloha Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixná Pozícia Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Popis
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Konfigurácia siete

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Popis
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Heslo Network password
Ethernet zapnutý Use a wired connection on hardware that has one
IPv4 režim DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Konfigurácia Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Popis
Bluetooth zapnuté Enable/disable BLE radio
Režim párovania Fixed PIN, Random PIN, or No PIN
Pevný PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Popis
Verejný kľúč Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Súkromný kľúč Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/sk-rSK/user/signal-meter.html b/main/sk-rSK/user/signal-meter.html index 30646d6b9f..6594d046ca 100644 --- a/main/sk-rSK/user/signal-meter.html +++ b/main/sk-rSK/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Slovenčina
Meshtastic Docs ↗

🌐 Slovenčina — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Dobrý Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Primeraný 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Zlý 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Žiadny 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Slovenčina
Meshtastic Docs ↗

🌐 Slovenčina — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Dobrý Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Primeraný 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Zlý 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Žiadny 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/sl-rSI/user/node-metrics.html b/main/sl-rSI/user/node-metrics.html index 877254825e..611d41749d 100644 --- a/main/sl-rSI/user/node-metrics.html +++ b/main/sl-rSI/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Slovenščina
Meshtastic Docs ↗

🌐 Slovenščina — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Opis
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatura BME280, BME680, SHT31
Vlaga BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Opis
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Dober < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Kakovost signala

Radio signal quality information:

Metric Opis
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Dober SNR above the preset’s limit
Precejšen less than 5.5 dB below the limit
Slab 5.5 dB to 7.5 dB below the limit
Brez more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Opis
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Pot

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Dnevnik lokacije

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Slovenščina
Meshtastic Docs ↗

🌐 Slovenščina — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Opis
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatura BME280, BME680, SHT31
Vlaga BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Opis
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Dober < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Kakovost signala

Radio signal quality information:

Metric Opis
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Dober SNR above the preset’s limit
Precejšen less than 5.5 dB below the limit
Slab 5.5 dB to 7.5 dB below the limit
Brez more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Opis
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Pot

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Dnevnik lokacije

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/sl-rSI/user/nodes.html b/main/sl-rSI/user/nodes.html index 0976e9a65c..ab2872580b 100644 --- a/main/sl-rSI/user/nodes.html +++ b/main/sl-rSI/user/nodes.html @@ -1 +1 @@ - Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Slovenščina
Meshtastic Docs ↗

🌐 Slovenščina — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Opis
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Odstrani

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filter Opis
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Opis
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Nazadnje slišano Last heard
Razdalja Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Slovenščina
Meshtastic Docs ↗

🌐 Slovenščina — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Opis
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Odstrani

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filter Opis
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Opis
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Nazadnje slišano Last heard
Razdalja Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/sl-rSI/user/settings-radio-user.html b/main/sl-rSI/user/settings-radio-user.html index 4c2296ffff..5f9be0c5a3 100644 --- a/main/sl-rSI/user/settings-radio-user.html +++ b/main/sl-rSI/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Slovenščina
Meshtastic Docs ↗

🌐 Slovenščina — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Opis
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Opis Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Opis Default
Regija Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Opis
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Opis
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Opis
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
Javni ključ Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Zasebni ključ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Slovenščina
Meshtastic Docs ↗

🌐 Slovenščina — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Opis
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Opis Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Opis Default
Regija Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Opis
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Opis
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Opis
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Opis
Javni ključ Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Zasebni ključ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/sl-rSI/user/signal-meter.html b/main/sl-rSI/user/signal-meter.html index a2faec28c4..c15fe9baa1 100644 --- a/main/sl-rSI/user/signal-meter.html +++ b/main/sl-rSI/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Slovenščina
Meshtastic Docs ↗

🌐 Slovenščina — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Dober Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Precejšen 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Slab 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Brez 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Slovenščina
Meshtastic Docs ↗

🌐 Slovenščina — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Dober Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Precejšen 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Slab 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Brez 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/sq-rAL/user/node-metrics.html b/main/sq-rAL/user/node-metrics.html index d949868d99..9f7b808089 100644 --- a/main/sq-rAL/user/node-metrics.html +++ b/main/sq-rAL/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Shqip
Meshtastic Docs ↗

🌐 Shqip — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Përshkrimi
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatura BME280, BME680, SHT31
Lagështia BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Përshkrimi
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Mirë < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Cilësia e Sinjalit

Radio signal quality information:

Metric Përshkrimi
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Mirë SNR above the preset’s limit
Mesatar less than 5.5 dB below the limit
I Keq 5.5 dB to 7.5 dB below the limit
Asnjë more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Përshkrimi
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Regjistri i Pozitës

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Shqip
Meshtastic Docs ↗

🌐 Shqip — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Përshkrimi
Battery Level Current battery percentage
Voltage Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Uptime Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatura BME280, BME680, SHT31
Lagështia BME280, BME680, SHT31
Barometric Pressure BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Përshkrimi
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Mirë < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Cilësia e Sinjalit

Radio signal quality information:

Metric Përshkrimi
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Mirë SNR above the preset’s limit
Mesatar less than 5.5 dB below the limit
I Keq 5.5 dB to 7.5 dB below the limit
Asnjë more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Përshkrimi
Voltage Per-channel voltage reading
Current Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Regjistri i Pozitës

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitude
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/sq-rAL/user/nodes.html b/main/sq-rAL/user/nodes.html index 42f2101a1c..2c456984a9 100644 --- a/main/sq-rAL/user/nodes.html +++ b/main/sq-rAL/user/nodes.html @@ -1 +1 @@ - Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Shqip
Meshtastic Docs ↗

🌐 Shqip — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Përshkrimi
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Hiq

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtrimi Përshkrimi
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Përshkrimi
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
I fundit që u dëgjua Last heard
Distanca Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nodes | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Shqip
Meshtastic Docs ↗

🌐 Shqip — Community translation View in English

Nodes

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Role Përshkrimi
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Hiq

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtrimi Përshkrimi
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Përshkrimi
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
I fundit që u dëgjua Last heard
Distanca Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/sq-rAL/user/settings-radio-user.html b/main/sq-rAL/user/settings-radio-user.html index 5eb659c0e2..97773d28ac 100644 --- a/main/sq-rAL/user/settings-radio-user.html +++ b/main/sq-rAL/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Shqip
Meshtastic Docs ↗

🌐 Shqip — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Përshkrimi
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Përshkrimi Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Përshkrimi Default
Rajon Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Përshkrimi
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Përshkrimi
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Përshkrimi
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Përshkrimi
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Përshkrimi
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Përshkrimi
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Shqip
Meshtastic Docs ↗

🌐 Shqip — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Përshkrimi
Long Name Your display name (up to 39 characters)
Short Name 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Device Config

On Settings → Device configuration → Device.

Setting Përshkrimi Default
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Info Broadcast Interval How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Enabled
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Përshkrimi Default
Rajon Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bandwidth Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ignore MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fan disabled Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Përshkrimi
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Përshkrimi
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Power Config

On Settings → Device configuration → Power.

Setting Përshkrimi
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Përshkrimi
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Password Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Config

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Përshkrimi
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Përshkrimi
Public Key Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Private Key Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/sq-rAL/user/signal-meter.html b/main/sq-rAL/user/signal-meter.html index 35f634696d..3dc1482124 100644 --- a/main/sq-rAL/user/signal-meter.html +++ b/main/sq-rAL/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Shqip
Meshtastic Docs ↗

🌐 Shqip — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Mirë Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Mesatar 3 less than 5.5 dB below limit Decodable, but approaching the floor.
I Keq 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Asnjë 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Shqip
Meshtastic Docs ↗

🌐 Shqip — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Mirë Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Mesatar 3 less than 5.5 dB below limit Decodable, but approaching the floor.
I Keq 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Asnjë 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/sr-rLatn/user/node-metrics.html b/main/sr-rLatn/user/node-metrics.html index af910a918e..86687968d4 100644 --- a/main/sr-rLatn/user/node-metrics.html +++ b/main/sr-rLatn/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Српски (Latinica)
Meshtastic Docs ↗

🌐 Српски (Latinica) — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Метрика уређаја

Basic operating information reported by each node:

Метрика Опис
Ниво батерије Current battery percentage
Напон Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Време рада Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Метрике сензора

Environmental sensor data (requires compatible hardware):

Метрика Sensor Examples
Температура BME280, BME680, SHT31
Влажност BME280, BME680, SHT31
Барометарски притисак BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Метрика Unit Опис
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Боја
Dobro < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Kvalitet signala

Radio signal quality information:

Метрика Опис
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Dobro SNR above the preset’s limit
Prihvatljiv less than 5.5 dB below the limit
Loš 5.5 dB to 7.5 dB below the limit
Bez more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Мерни подаци о снази

Power management telemetry (requires INA sensor or compatible hardware):

Метрика Опис
Напон Per-channel voltage reading
Струја Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Праћење руте

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Dnevnik lokacija

Historical position data for nodes that share their location:

  • GPS coordinates
  • Висина
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Српски (Latinica)
Meshtastic Docs ↗

🌐 Српски (Latinica) — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Метрика уређаја

Basic operating information reported by each node:

Метрика Опис
Ниво батерије Current battery percentage
Напон Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Време рада Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Метрике сензора

Environmental sensor data (requires compatible hardware):

Метрика Sensor Examples
Температура BME280, BME680, SHT31
Влажност BME280, BME680, SHT31
Барометарски притисак BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Метрика Unit Опис
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Боја
Dobro < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Kvalitet signala

Radio signal quality information:

Метрика Опис
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Dobro SNR above the preset’s limit
Prihvatljiv less than 5.5 dB below the limit
Loš 5.5 dB to 7.5 dB below the limit
Bez more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Мерни подаци о снази

Power management telemetry (requires INA sensor or compatible hardware):

Метрика Опис
Напон Per-channel voltage reading
Струја Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Праћење руте

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Dnevnik lokacija

Historical position data for nodes that share their location:

  • GPS coordinates
  • Висина
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/sr-rLatn/user/nodes.html b/main/sr-rLatn/user/nodes.html index 47cb486908..0556df8f2e 100644 --- a/main/sr-rLatn/user/nodes.html +++ b/main/sr-rLatn/user/nodes.html @@ -1 +1 @@ - Чворови | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Српски (Latinica)
Meshtastic Docs ↗

🌐 Српски (Latinica) — Community translation View in English

Чворови

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Улога Опис
Клијент Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Клијент мутиран Receives but doesn’t retransmit
Скривени клијент Like Client Mute, plus hides from node list
Рутер Prioritizes message forwarding; stays awake to relay
Рутер са кашњењем Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Трекер Optimized for position reporting at regular intervals
Сензор Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
ТАК Трекер TAK position reporting only
Изгубљено и нађено Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Иконица Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Уклони

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filter Опис
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Опис
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Poslednji put viđeno Last heard
Udaljenost Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Чворови | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Српски (Latinica)
Meshtastic Docs ↗

🌐 Српски (Latinica) — Community translation View in English

Чворови

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Улога Опис
Клијент Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Клијент мутиран Receives but doesn’t retransmit
Скривени клијент Like Client Mute, plus hides from node list
Рутер Prioritizes message forwarding; stays awake to relay
Рутер са кашњењем Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Трекер Optimized for position reporting at regular intervals
Сензор Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
ТАК Трекер TAK position reporting only
Изгубљено и нађено Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Иконица Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Уклони

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filter Опис
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Опис
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Poslednji put viđeno Last heard
Udaljenost Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/sr-rLatn/user/settings-radio-user.html b/main/sr-rLatn/user/settings-radio-user.html index 933061e315..7201234749 100644 --- a/main/sr-rLatn/user/settings-radio-user.html +++ b/main/sr-rLatn/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Српски (Latinica)
Meshtastic Docs ↗

🌐 Српски (Latinica) — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Опис
Дуго име Your display name (up to 39 characters)
Кратко име 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Подешавања уређаја

On Settings → Device configuration → Device.

Setting Опис Подразумевано
Улога уређаја Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим реемитовања How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Интервал емитовања информација о чвору How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Двоструки додир као дугме Treat a double tap as a button press Онемогућено
Троструки клик за Ad Hoc пинг Send an ad-hoc position ping on a triple click Онемогућено
LED срчани откуцаји Blink the status LED periodically Омогућено
Временска зона POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRA подешавања

On Settings → LoRa.

Setting Опис Подразумевано
Регион Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Унапред подешено Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Измена фреквенције Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Користи предефинисано подешавање On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Фактор ширења Manual mode only: 7–12. Higher spreads further but slower From preset
Стопа кодирања Manual mode only: 5–8. More redundancy costs airtime From preset
Проток Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Фреквенцијски слот Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Трансмитер укључен Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Искључен
Игнориши MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Позитиван за MQTT Allow your packets to be forwarded to MQTT by gateways Искључен
Појачање пријемника Extra receive gain on SX126x radios; costs a little current Искључен
PA fan disabled Turn off the power-amplifier fan on hardware that has one Искључен

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Брзина SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Подешавања приказа

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Опис
Екран укључен за How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Увек усмеравајте на север Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Подешавања позиције

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Интервал емитовања How often the position is shared with the mesh
Паметно позиционирање Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Фиксна локација Use a manually entered latitude, longitude and altitude instead of the GPS
Заставице позиције A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Подешавања напајња

On Settings → Device configuration → Power.

Setting Опис
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Конфигурација мреже

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Опис
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Лозинка Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Блутут подешавања

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Сигурносна подешавања

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
Javni ključ Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Privatni ključ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Српски (Latinica)
Meshtastic Docs ↗

🌐 Српски (Latinica) — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Опис
Дуго име Your display name (up to 39 characters)
Кратко име 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Подешавања уређаја

On Settings → Device configuration → Device.

Setting Опис Подразумевано
Улога уређаја Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим реемитовања How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Интервал емитовања информација о чвору How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Двоструки додир као дугме Treat a double tap as a button press Онемогућено
Троструки клик за Ad Hoc пинг Send an ad-hoc position ping on a triple click Онемогућено
LED срчани откуцаји Blink the status LED periodically Омогућено
Временска зона POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRA подешавања

On Settings → LoRa.

Setting Опис Подразумевано
Регион Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Унапред подешено Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Измена фреквенције Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Користи предефинисано подешавање On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Фактор ширења Manual mode only: 7–12. Higher spreads further but slower From preset
Стопа кодирања Manual mode only: 5–8. More redundancy costs airtime From preset
Проток Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Фреквенцијски слот Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Трансмитер укључен Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Искључен
Игнориши MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Позитиван за MQTT Allow your packets to be forwarded to MQTT by gateways Искључен
Појачање пријемника Extra receive gain on SX126x radios; costs a little current Искључен
PA fan disabled Turn off the power-amplifier fan on hardware that has one Искључен

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Брзина SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Подешавања приказа

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Опис
Екран укључен за How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Увек усмеравајте на север Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Подешавања позиције

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Интервал емитовања How often the position is shared with the mesh
Паметно позиционирање Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Фиксна локација Use a manually entered latitude, longitude and altitude instead of the GPS
Заставице позиције A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Подешавања напајња

On Settings → Device configuration → Power.

Setting Опис
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Конфигурација мреже

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Опис
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Лозинка Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Блутут подешавања

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Сигурносна подешавања

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
Javni ključ Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Privatni ključ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/sr-rLatn/user/signal-meter.html b/main/sr-rLatn/user/signal-meter.html index 142bcbed6e..6fc78d6944 100644 --- a/main/sr-rLatn/user/signal-meter.html +++ b/main/sr-rLatn/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Српски (Latinica)
Meshtastic Docs ↗

🌐 Српски (Latinica) — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Ниво Bars Criteria Meaning
Dobro Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Prihvatljiv 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Loš 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Bez 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Српски (Latinica)
Meshtastic Docs ↗

🌐 Српски (Latinica) — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Ниво Bars Criteria Meaning
Dobro Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Prihvatljiv 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Loš 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Bez 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/srp/user/node-metrics.html b/main/srp/user/node-metrics.html index 4b78ebb28f..5115a216a4 100644 --- a/main/srp/user/node-metrics.html +++ b/main/srp/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Српски (Ћирилица)
Meshtastic Docs ↗

🌐 Српски (Ћирилица) — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Метрика уређаја

Basic operating information reported by each node:

Метрика Опис
Ниво батерије Current battery percentage
Напон Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Време рада Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Метрике сензора

Environmental sensor data (requires compatible hardware):

Метрика Sensor Examples
Температура BME280, BME680, SHT31
Влажност BME280, BME680, SHT31
Барометарски притисак BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Метрика Unit Опис
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Боја
Добро < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Квалитет сигнала

Radio signal quality information:

Метрика Опис
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Добро SNR above the preset’s limit
Прихватљив less than 5.5 dB below the limit
Лош 5.5 dB to 7.5 dB below the limit
Ништа more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Мерни подаци о снази

Power management telemetry (requires INA sensor or compatible hardware):

Метрика Опис
Напон Per-channel voltage reading
Струја Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Праћење руте

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Логови позиција

Historical position data for nodes that share their location:

  • GPS coordinates
  • Висина
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Српски (Ћирилица)
Meshtastic Docs ↗

🌐 Српски (Ћирилица) — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Метрика уређаја

Basic operating information reported by each node:

Метрика Опис
Ниво батерије Current battery percentage
Напон Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Време рада Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Метрике сензора

Environmental sensor data (requires compatible hardware):

Метрика Sensor Examples
Температура BME280, BME680, SHT31
Влажност BME280, BME680, SHT31
Барометарски притисак BME280, BMP280
Gas Resistance BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Метрика Unit Опис
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Боја
Добро < 1000 Green
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Red
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Квалитет сигнала

Radio signal quality information:

Метрика Опис
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Добро SNR above the preset’s limit
Прихватљив less than 5.5 dB below the limit
Лош 5.5 dB to 7.5 dB below the limit
Ништа more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Мерни подаци о снази

Power management telemetry (requires INA sensor or compatible hardware):

Метрика Опис
Напон Per-channel voltage reading
Струја Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Праћење руте

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Логови позиција

Historical position data for nodes that share their location:

  • GPS coordinates
  • Висина
  • Speed (if moving)
  • Timestamp for each position report

Neighbor Info

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Host Metrics

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/srp/user/nodes.html b/main/srp/user/nodes.html index fad90716d4..e23d274ec6 100644 --- a/main/srp/user/nodes.html +++ b/main/srp/user/nodes.html @@ -1 +1 @@ - Чворови | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Српски (Ћирилица)
Meshtastic Docs ↗

🌐 Српски (Ћирилица) — Community translation View in English

Чворови

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Улога Опис
Клијент Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Клијент мутиран Receives but doesn’t retransmit
Скривени клијент Like Client Mute, plus hides from node list
Рутер Prioritizes message forwarding; stays awake to relay
Рутер са кашњењем Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Трекер Optimized for position reporting at regular intervals
Сензор Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
ТАК Трекер TAK position reporting only
Изгубљено и нађено Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Иконица Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Уклони

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Филтер Опис
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Опис
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Последње откривање Last heard
Раздаљина Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Чворови | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Српски (Ћирилица)
Meshtastic Docs ↗

🌐 Српски (Ћирилица) — Community translation View in English

Чворови

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Улога Опис
Клијент Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Клијент мутиран Receives but doesn’t retransmit
Скривени клијент Like Client Mute, plus hides from node list
Рутер Prioritizes message forwarding; stays awake to relay
Рутер са кашњењем Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Трекер Optimized for position reporting at regular intervals
Сензор Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
ТАК Трекер TAK position reporting only
Изгубљено и нађено Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Иконица Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Уклони

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Филтер Опис
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Опис
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Последње откривање Last heard
Раздаљина Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/srp/user/settings-radio-user.html b/main/srp/user/settings-radio-user.html index 9b7d3e553d..3c17370aab 100644 --- a/main/srp/user/settings-radio-user.html +++ b/main/srp/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Српски (Ћирилица)
Meshtastic Docs ↗

🌐 Српски (Ћирилица) — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Опис
Дуго име Your display name (up to 39 characters)
Кратко име 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Подешавања уређаја

On Settings → Device configuration → Device.

Setting Опис Подразумевано
Улога уређаја Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим реемитовања How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Интервал емитовања информација о чвору How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Двоструки додир као дугме Treat a double tap as a button press Онемогућено
Троструки клик за Ad Hoc пинг Send an ad-hoc position ping on a triple click Онемогућено
LED срчани откуцаји Blink the status LED periodically Омогућено
Временска зона POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRA подешавања

On Settings → LoRa.

Setting Опис Подразумевано
Регион Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Унапред подешено Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Измена фреквенције Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Користи предефинисано подешавање On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Фактор ширења Manual mode only: 7–12. Higher spreads further but slower From preset
Стопа кодирања Manual mode only: 5–8. More redundancy costs airtime From preset
Проток Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Фреквенцијски слот Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Трансмитер укључен Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Искључен
Игнориши MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Позитиван за MQTT Allow your packets to be forwarded to MQTT by gateways Искључен
Појачање пријемника Extra receive gain on SX126x radios; costs a little current Искључен
PA fan disabled Turn off the power-amplifier fan on hardware that has one Искључен

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Брзина SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Подешавања приказа

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Опис
Екран укључен за How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Увек усмеравајте на север Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Подешавања позиције

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Интервал емитовања How often the position is shared with the mesh
Паметно позиционирање Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Фиксна локација Use a manually entered latitude, longitude and altitude instead of the GPS
Заставице позиције A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Подешавања напајња

On Settings → Device configuration → Power.

Setting Опис
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Конфигурација мреже

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Опис
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Лозинка Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Блутут подешавања

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Сигурносна подешавања

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
Јавни кључ Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Приватни кључ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Српски (Ћирилица)
Meshtastic Docs ↗

🌐 Српски (Ћирилица) — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Опис
Дуго име Your display name (up to 39 characters)
Кратко име 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Unmessageable Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

Подешавања уређаја

On Settings → Device configuration → Device.

Setting Опис Подразумевано
Улога уређаја Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим реемитовања How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Интервал емитовања информација о чвору How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Двоструки додир као дугме Treat a double tap as a button press Онемогућено
Троструки клик за Ad Hoc пинг Send an ad-hoc position ping on a triple click Онемогућено
LED срчани откуцаји Blink the status LED periodically Омогућено
Временска зона POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRA подешавања

On Settings → LoRa.

Setting Опис Подразумевано
Регион Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Унапред подешено Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Измена фреквенције Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Користи предефинисано подешавање On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Фактор ширења Manual mode only: 7–12. Higher spreads further but slower From preset
Стопа кодирања Manual mode only: 5–8. More redundancy costs airtime From preset
Проток Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Фреквенцијски слот Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Трансмитер укључен Turning this off makes the node receive-only On
Override Duty Cycle Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Искључен
Игнориши MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Позитиван за MQTT Allow your packets to be forwarded to MQTT by gateways Искључен
Појачање пријемника Extra receive gain on SX126x radios; costs a little current Искључен
PA fan disabled Turn off the power-amplifier fan on hardware that has one Искључен

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Брзина SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Подешавања приказа

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Опис
Екран укључен за How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Display mode Screen layout/density used by the firmware
Display units Metric or Imperial on the radio’s screen
Use 12h clock format Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Flip screen Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Compass orientation Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Увек усмеравајте на север Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Подешавања позиције

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Интервал емитовања How often the position is shared with the mesh
Паметно позиционирање Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Фиксна локација Use a manually entered latitude, longitude and altitude instead of the GPS
Заставице позиције A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Подешавања напајња

On Settings → Device configuration → Power.

Setting Опис
Enable power saving mode Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Battery INA_2XX I2C address Address of an external INA-series power sensor, if fitted

Конфигурација мреже

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Опис
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Лозинка Network password
Ethernet enabled Use a wired connection on hardware that has one
IPv4 mode DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP server Time synchronization server
rsyslog server Remote logging server

Network Config with a static IPv4 address entered

Блутут подешавања

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
Bluetooth enabled Enable/disable BLE radio
Pairing mode Fixed PIN, Random PIN, or No PIN
Fixed PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Сигурносна подешавања

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
Јавни кључ Your node’s public key (read-only)
Admin Key Keys permitted to administer this node remotely — up to three
Приватни кључ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Serial console Serial console over the Stream API
Debug log API enabled Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Managed Mode Restrict non-admin channel changes. Only selectable once an Admin Key is set
Backup Keys Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/srp/user/signal-meter.html b/main/srp/user/signal-meter.html index dd1ebaf8e9..28ca5e1e5b 100644 --- a/main/srp/user/signal-meter.html +++ b/main/srp/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Српски (Ћирилица)
Meshtastic Docs ↗

🌐 Српски (Ћирилица) — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Ниво Bars Criteria Meaning
Добро Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Прихватљив 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Лош 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Ништа 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Српски (Ћирилица)
Meshtastic Docs ↗

🌐 Српски (Ћирилица) — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Ниво Bars Criteria Meaning
Добро Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Прихватљив 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Лош 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Ништа 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/sv-rSE/user/node-metrics.html b/main/sv-rSE/user/node-metrics.html index c21cfcfdf1..bc7ae6e071 100644 --- a/main/sv-rSE/user/node-metrics.html +++ b/main/sv-rSE/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Svenska
Meshtastic Docs ↗

🌐 Svenska — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Enhetens mätvärden

Basic operating information reported by each node:

Metric Beskrivning
Battery Level Current battery percentage
Spänning Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Upptid Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Miljövärden

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatur BME280, BME680, SHT31
Luftfuktighet BME280, BME680, SHT31
Lufttryck BME280, BMP280
Gasmotstånd BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Beskrivning
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Bra < 1000 Grönt
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Rött
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Signalkvalité

Radio signal quality information:

Metric Beskrivning
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Bra SNR above the preset’s limit
Ok less than 5.5 dB below the limit
Dålig 5.5 dB to 7.5 dB below the limit
Ingen more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Strömdata

Power management telemetry (requires INA sensor or compatible hardware):

Metric Beskrivning
Spänning Per-channel voltage reading
Ström Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute (spåra rutt)

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Position Loggbok

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitud
  • Speed (if moving)
  • Timestamp for each position report

Granninformation

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Begär värdens värden

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX nyckeltal

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Svenska
Meshtastic Docs ↗

🌐 Svenska — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Enhetens mätvärden

Basic operating information reported by each node:

Metric Beskrivning
Battery Level Current battery percentage
Spänning Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Upptid Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Miljövärden

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Temperatur BME280, BME680, SHT31
Luftfuktighet BME280, BME680, SHT31
Lufttryck BME280, BMP280
Gasmotstånd BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Beskrivning
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Bra < 1000 Grönt
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Rött
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Signalkvalité

Radio signal quality information:

Metric Beskrivning
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Bra SNR above the preset’s limit
Ok less than 5.5 dB below the limit
Dålig 5.5 dB to 7.5 dB below the limit
Ingen more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Strömdata

Power management telemetry (requires INA sensor or compatible hardware):

Metric Beskrivning
Spänning Per-channel voltage reading
Ström Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute (spåra rutt)

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Position Loggbok

Historical position data for nodes that share their location:

  • GPS coordinates
  • Altitud
  • Speed (if moving)
  • Timestamp for each position report

Granninformation

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Begär värdens värden

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX nyckeltal

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/sv-rSE/user/nodes.html b/main/sv-rSE/user/nodes.html index 1e02524396..ffdaacb034 100644 --- a/main/sv-rSE/user/nodes.html +++ b/main/sv-rSE/user/nodes.html @@ -1 +1 @@ - Noder | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Svenska
Meshtastic Docs ↗

🌐 Svenska — Community translation View in English

Noder

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Roll Beskrivning
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Hittegods Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Ta bort

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filter Beskrivning
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Beskrivning
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Batterinivå Battery
Hop count Hops
Senast hörd Last heard
Avstånd Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Noder | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Svenska
Meshtastic Docs ↗

🌐 Svenska — Community translation View in English

Noder

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Roll Beskrivning
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Hittegods Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Ta bort

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filter Beskrivning
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Beskrivning
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Batterinivå Battery
Hop count Hops
Senast hörd Last heard
Avstånd Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/sv-rSE/user/settings-radio-user.html b/main/sv-rSE/user/settings-radio-user.html index d437729217..7f0de5d026 100644 --- a/main/sv-rSE/user/settings-radio-user.html +++ b/main/sv-rSE/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Svenska
Meshtastic Docs ↗

🌐 Svenska — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Användarinställningar

User Profile

On Settings → User.

Setting Beskrivning
Långt namn Your display name (up to 39 characters)
Kort namn 4-character abbreviated name
Statusmeddelande A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Meddelanden läses ej Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensierad radioamatör (ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Konfiguration

Enhetskonfiguration

On Settings → Device configuration → Device.

Setting Beskrivning Förvald
Enhetens roll Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Återutsändningsläge How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Sändningsintervall för nod-info How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Dubbeltryck som knapptryck Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED pulsering Blink the status LED periodically Aktiverad
Tidszon POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Beskrivning Förvald
Region Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Förval Speed/range tradeoff LongFast
Antal hopp Maximum retransmit hops 3
Sändningseffekt Transmission power (dBm); 0 = max allowed for region 0 (region max)
Åsidosätt Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Använd förinställning On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spridningsfaktor Manual mode only: 7–12. Higher spreads further but slower From preset
Kodningshastighet Manual mode only: 5–8. More redundancy costs airtime From preset
Bandbredd Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frekvens-slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Sändning aktiverad Turning this off makes the node receive-only On
Ersätt gräns för driftsperiod Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Av
Ignorera MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok till MQTT Allow your packets to be forwarded to MQTT by gateways Av
RX förstärkt gain Extra receive gain on SX126x radios; costs a little current Av
PA fan disabled Turn off the power-amplifier fan on hardware that has one Av

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Hastighet SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Beskrivning
Håll skärmen tänd How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Visningsläge Screen layout/density used by the firmware
Visa enheter Metric or Imperial on the radio’s screen
Använd 12-timmarsformat Show the radio’s clock as 12-hour rather than 24-hour
Fetstil för rubriktext Draw the screen’s heading text in bold
Vänd skärmen Rotate the display 180° for an inverted mounting
OLED-typ Auto, SSD1306, SH1106, SH1107
Vakna vid tryck eller rörelse Light the screen when the radio is tapped or moved
Kompassriktning Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Peka alltid mot norr Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beskrivning
GPS-läge (fysisk maskinvara) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Intervall för hämtning av GPS-position How often the radio asks its GPS for a fix
Sändningsintervall How often the position is shared with the mesh
Smart position Broadcast based on movement rather than purely on the clock
Smart intervall With Smart Position on, the shortest gap between broadcasts
Smart distans With Smart Position on, how far you must move before broadcasting
Fast plats Use a manually entered latitude, longitude and altitude instead of the GPS
Positionsflaggor A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Ströminställningar

On Settings → Device configuration → Power.

Setting Beskrivning
Aktivera strömsparläge Let the radio sleep aggressively between activity
Stäng av vid strömförlust Power the device down after external power disappears
Tid för djup strömsparläge How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Vänta in Bluetooth (sekunder) How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Batteriets INA_2XX I2C-adress Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Beskrivning
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Lösenord Nätverkslösenord
Ethernet är aktiverat Use a wired connection on hardware that has one
IPv4-läge DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP-server Time synchronization server
rsyslog-server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth-inställningar

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beskrivning
Bluetooth är aktiverad Enable/disable BLE radio
Parkopplingsläge Fixed PIN, Random PIN, or No PIN
Fast PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beskrivning
Publik nyckel Your node’s public key (read-only)
Admin-nyckel Keys permitted to administer this node remotely — up to three
Privat nyckel Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Förnya nyckel Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Seriell konsol Serial console over the Stream API
API för debugloggen igång Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Hanterat läge Restrict non-admin channel changes. Only selectable once an Admin Key is set
Säkerhetskopiera nycklar Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Skyddsnivå How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Svenska
Meshtastic Docs ↗

🌐 Svenska — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

Användarinställningar

User Profile

On Settings → User.

Setting Beskrivning
Långt namn Your display name (up to 39 characters)
Kort namn 4-character abbreviated name
Statusmeddelande A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Meddelanden läses ej Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensierad radioamatör (ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Konfiguration

Enhetskonfiguration

On Settings → Device configuration → Device.

Setting Beskrivning Förvald
Enhetens roll Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Återutsändningsläge How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Sändningsintervall för nod-info How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Dubbeltryck som knapptryck Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED pulsering Blink the status LED periodically Aktiverad
Tidszon POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Config

On Settings → LoRa.

Setting Beskrivning Förvald
Region Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Förval Speed/range tradeoff LongFast
Antal hopp Maximum retransmit hops 3
Sändningseffekt Transmission power (dBm); 0 = max allowed for region 0 (region max)
Åsidosätt Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Använd förinställning On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spridningsfaktor Manual mode only: 7–12. Higher spreads further but slower From preset
Kodningshastighet Manual mode only: 5–8. More redundancy costs airtime From preset
Bandbredd Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frekvens-slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Sändning aktiverad Turning this off makes the node receive-only On
Ersätt gräns för driftsperiod Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Av
Ignorera MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok till MQTT Allow your packets to be forwarded to MQTT by gateways Av
RX förstärkt gain Extra receive gain on SX126x radios; costs a little current Av
PA fan disabled Turn off the power-amplifier fan on hardware that has one Av

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Hastighet SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Display Config

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Beskrivning
Håll skärmen tänd How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Visningsläge Screen layout/density used by the firmware
Visa enheter Metric or Imperial on the radio’s screen
Använd 12-timmarsformat Show the radio’s clock as 12-hour rather than 24-hour
Fetstil för rubriktext Draw the screen’s heading text in bold
Vänd skärmen Rotate the display 180° for an inverted mounting
OLED-typ Auto, SSD1306, SH1106, SH1107
Vakna vid tryck eller rörelse Light the screen when the radio is tapped or moved
Kompassriktning Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Peka alltid mot norr Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beskrivning
GPS-läge (fysisk maskinvara) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Intervall för hämtning av GPS-position How often the radio asks its GPS for a fix
Sändningsintervall How often the position is shared with the mesh
Smart position Broadcast based on movement rather than purely on the clock
Smart intervall With Smart Position on, the shortest gap between broadcasts
Smart distans With Smart Position on, how far you must move before broadcasting
Fast plats Use a manually entered latitude, longitude and altitude instead of the GPS
Positionsflaggor A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Ströminställningar

On Settings → Device configuration → Power.

Setting Beskrivning
Aktivera strömsparläge Let the radio sleep aggressively between activity
Stäng av vid strömförlust Power the device down after external power disappears
Tid för djup strömsparläge How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Vänta in Bluetooth (sekunder) How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC multiplier override ratio The correction factor itself, used only when the override is on
Batteriets INA_2XX I2C-adress Address of an external INA-series power sensor, if fitted

Network Config

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Beskrivning
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Lösenord Nätverkslösenord
Ethernet är aktiverat Use a wired connection on hardware that has one
IPv4-läge DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP-server Time synchronization server
rsyslog-server Remote logging server

Network Config with a static IPv4 address entered

Bluetooth-inställningar

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beskrivning
Bluetooth är aktiverad Enable/disable BLE radio
Parkopplingsläge Fixed PIN, Random PIN, or No PIN
Fast PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Security Config

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Beskrivning
Publik nyckel Your node’s public key (read-only)
Admin-nyckel Keys permitted to administer this node remotely — up to three
Privat nyckel Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Förnya nyckel Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Seriell konsol Serial console over the Stream API
API för debugloggen igång Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Hanterat läge Restrict non-admin channel changes. Only selectable once an Admin Key is set
Säkerhetskopiera nycklar Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Skyddsnivå How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/sv-rSE/user/signal-meter.html b/main/sv-rSE/user/signal-meter.html index 5840024f75..313415630f 100644 --- a/main/sv-rSE/user/signal-meter.html +++ b/main/sv-rSE/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Svenska
Meshtastic Docs ↗

🌐 Svenska — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Bra Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Ok 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Dålig 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Ingen 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Svenska
Meshtastic Docs ↗

🌐 Svenska — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Bra Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Ok 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Dålig 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Ingen 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/tr-rTR/user/node-metrics.html b/main/tr-rTR/user/node-metrics.html index 05b15785b9..c29b4b6afc 100644 --- a/main/tr-rTR/user/node-metrics.html +++ b/main/tr-rTR/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Türkçe
Meshtastic Docs ↗

🌐 Türkçe — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Açıklaması
Battery Level Current battery percentage
Voltaj Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Çalışma Süresi Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Sıcaklık BME280, BME680, SHT31
Nem BME280, BME680, SHT31
Barometrik Basınç BME280, BMP280
Gaz Direnci BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Açıklaması
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
İyi < 1000 Yeşil
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Kırmızı
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Sinyal Kalitesi

Radio signal quality information:

Metric Açıklaması
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
İyi SNR above the preset’s limit
İdare Eder less than 5.5 dB below the limit
Kötü 5.5 dB to 7.5 dB below the limit
Yok more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Açıklaması
Voltaj Per-channel voltage reading
Akım Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Yol izle

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Konum Kayıtları

Historical position data for nodes that share their location:

  • GPS coordinates
  • Rakım
  • Speed (if moving)
  • Timestamp for each position report

Komşu Bilgisi

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Sunucu Ölçümleri

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Türkçe
Meshtastic Docs ↗

🌐 Türkçe — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Device Metrics

Basic operating information reported by each node:

Metric Açıklaması
Battery Level Current battery percentage
Voltaj Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
Çalışma Süresi Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environment Metrics

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Sıcaklık BME280, BME680, SHT31
Nem BME280, BME680, SHT31
Barometrik Basınç BME280, BMP280
Gaz Direnci BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Açıklaması
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
İyi < 1000 Yeşil
Stuffy < 2000 Amber
Poor < 5000 Orange
Unsafe < 30000 Kırmızı
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Sinyal Kalitesi

Radio signal quality information:

Metric Açıklaması
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
İyi SNR above the preset’s limit
İdare Eder less than 5.5 dB below the limit
Kötü 5.5 dB to 7.5 dB below the limit
Yok more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Power Metrics

Power management telemetry (requires INA sensor or compatible hardware):

Metric Açıklaması
Voltaj Per-channel voltage reading
Akım Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Yol izle

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Konum Kayıtları

Historical position data for nodes that share their location:

  • GPS coordinates
  • Rakım
  • Speed (if moving)
  • Timestamp for each position report

Komşu Bilgisi

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Sunucu Ölçümleri

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX Metrics

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/tr-rTR/user/nodes.html b/main/tr-rTR/user/nodes.html index 9c18ac7537..3d65f94393 100644 --- a/main/tr-rTR/user/nodes.html +++ b/main/tr-rTR/user/nodes.html @@ -1 +1 @@ - Nodelar | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Türkçe
Meshtastic Docs ↗

🌐 Türkçe — Community translation View in English

Nodelar

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Rol Açıklaması
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Kaldır

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtre Açıklaması
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Açıklaması
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Son duyulma Last heard
Mesafe Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Nodelar | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Türkçe
Meshtastic Docs ↗

🌐 Türkçe — Community translation View in English

Nodelar

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Rol Açıklaması
Client Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Tracker Optimized for position reporting at regular intervals
Sensor Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Kaldır

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Filtre Açıklaması
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Açıklaması
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Battery level Battery
Hop count Hops
Son duyulma Last heard
Mesafe Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/tr-rTR/user/settings-radio-user.html b/main/tr-rTR/user/settings-radio-user.html index 745115a08f..22cebfba60 100644 --- a/main/tr-rTR/user/settings-radio-user.html +++ b/main/tr-rTR/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Türkçe
Meshtastic Docs ↗

🌐 Türkçe — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Açıklaması
Uzun Ad Your display name (up to 39 characters)
Kısa Ad 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Mesaj gönderilemez Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Yapılandırma

Cihaz Ayarı

On Settings → Device configuration → Device.

Setting Açıklaması Varsayılan
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Bilgisi Yayın Aralığı How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Açık
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Ayarı

On Settings → LoRa.

Setting Açıklaması Varsayılan
Bölge Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bant genişliği Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Görev Döngüsünü Geçersiz Kıl Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
MQTT’yi Yoksay Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fanı devre dışı Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Akran Ayarı

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Açıklaması
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Görüntü Modu Screen layout/density used by the firmware
Görüntü Birimleri Metric or Imperial on the radio’s screen
12h saat formatını kullan Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Ekranı Çevir Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Pusula yönü Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Konum Ayarı

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Açıklaması
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Güç Ayarı

On Settings → Device configuration → Power.

Setting Açıklaması
Güç tasarrufu modunu etkinleştir Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC çarpanını geçersiz kılma oranı The correction factor itself, used only when the override is on
Pilin INA_2XX I2C adresi Address of an external INA-series power sensor, if fitted

Ağ Ayarı

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Açıklaması
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Şifre Ağ şifresi
Ethernet etkin Use a wired connection on hardware that has one
IPv4 modu DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP sunucusu Time synchronization server
rsyslog sunucusu Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Ayarı

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Açıklaması
Bluetooth Etkin Enable/disable BLE radio
Eşleştirme Modu Fixed PIN, Random PIN, or No PIN
Sabit PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Güvenlik Ayarı

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Açıklaması
Genel Anahtar Your node’s public key (read-only)
Yönetici Anahtarı Keys permitted to administer this node remotely — up to three
Özel Anahtar Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Seri konsol Serial console over the Stream API
Hata ayıklama kaydı API’si etkin Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Yönetilen Mod Restrict non-admin channel changes. Only selectable once an Admin Key is set
Anahtarları Yedekle Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Türkçe
Meshtastic Docs ↗

🌐 Türkçe — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Açıklaması
Uzun Ad Your display name (up to 39 characters)
Kısa Ad 4-character abbreviated name
Status Message A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Mesaj gönderilemez Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Licensed amateur radio (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Yapılandırma

Cihaz Ayarı

On Settings → Device configuration → Device.

Setting Açıklaması Varsayılan
Device Role Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Rebroadcast Mode How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Node Bilgisi Yayın Aralığı How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Double Tap as Button Treat a double tap as a button press Disabled
Triple Click Ad Hoc Ping Send an ad-hoc position ping on a triple click Disabled
LED Heartbeat Blink the status LED periodically Açık
Time Zone POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa Ayarı

On Settings → LoRa.

Setting Açıklaması Varsayılan
Bölge Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Presets Speed/range tradeoff LongFast
Number of Hops Maximum retransmit hops 3
Transmit Power Transmission power (dBm); 0 = max allowed for region 0 (region max)
Frequency Override Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Use Preset On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Spread Factor Manual mode only: 7–12. Higher spreads further but slower From preset
Coding Rate Manual mode only: 5–8. More redundancy costs airtime From preset
Bant genişliği Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Frequency Slot Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Transmit Enabled Turning this off makes the node receive-only On
Görev Döngüsünü Geçersiz Kıl Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
MQTT’yi Yoksay Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
Ok to MQTT Allow your packets to be forwarded to MQTT by gateways Off
RX Boosted Gain Extra receive gain on SX126x radios; costs a little current Off
PA fanı devre dışı Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Speed SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Akran Ayarı

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Açıklaması
Screen on for How long the display stays lit before sleeping
Carousel interval How often the radio cycles between screens on its own
Görüntü Modu Screen layout/density used by the firmware
Görüntü Birimleri Metric or Imperial on the radio’s screen
12h saat formatını kullan Show the radio’s clock as 12-hour rather than 24-hour
Bold Heading Draw the screen’s heading text in bold
Ekranı Çevir Rotate the display 180° for an inverted mounting
OLED type Auto, SSD1306, SH1106, SH1107
Wake on tap or motion Light the screen when the radio is tapped or moved
Pusula yönü Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Always point north Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Konum Ayarı

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Açıklaması
GPS Mode (Physical Hardware) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS Polling Interval How often the radio asks its GPS for a fix
Broadcast Interval How often the position is shared with the mesh
Smart Position Broadcast based on movement rather than purely on the clock
Smart Interval With Smart Position on, the shortest gap between broadcasts
Smart Distance With Smart Position on, how far you must move before broadcasting
Fixed Position Use a manually entered latitude, longitude and altitude instead of the GPS
Position Flags A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Güç Ayarı

On Settings → Device configuration → Power.

Setting Açıklaması
Güç tasarrufu modunu etkinleştir Let the radio sleep aggressively between activity
Shutdown on power loss Power the device down after external power disappears
Super deep sleep duration How long the deepest sleep state lasts
Minimum wake time The shortest time the radio stays awake once woken
Wait for Bluetooth duration How long to wait for a phone to connect before sleeping
ADC multiplier override Turn on a manual correction for battery-voltage readings
ADC çarpanını geçersiz kılma oranı The correction factor itself, used only when the override is on
Pilin INA_2XX I2C adresi Address of an external INA-series power sensor, if fitted

Ağ Ayarı

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Açıklaması
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Şifre Ağ şifresi
Ethernet etkin Use a wired connection on hardware that has one
IPv4 modu DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP sunucusu Time synchronization server
rsyslog sunucusu Remote logging server

Network Config with a static IPv4 address entered

Bluetooth Ayarı

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Açıklaması
Bluetooth Etkin Enable/disable BLE radio
Eşleştirme Modu Fixed PIN, Random PIN, or No PIN
Sabit PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Güvenlik Ayarı

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Açıklaması
Genel Anahtar Your node’s public key (read-only)
Yönetici Anahtarı Keys permitted to administer this node remotely — up to three
Özel Anahtar Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Regenerate Private Key Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Seri konsol Serial console over the Stream API
Hata ayıklama kaydı API’si etkin Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Yönetilen Mod Restrict non-admin channel changes. Only selectable once an Admin Key is set
Anahtarları Yedekle Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/tr-rTR/user/signal-meter.html b/main/tr-rTR/user/signal-meter.html index 2f819951c1..884b25e628 100644 --- a/main/tr-rTR/user/signal-meter.html +++ b/main/tr-rTR/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Türkçe
Meshtastic Docs ↗

🌐 Türkçe — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
İyi Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
İdare Eder 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Kötü 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Yok 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Türkçe
Meshtastic Docs ↗

🌐 Türkçe — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
İyi Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
İdare Eder 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Kötü 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Yok 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/uk-rUA/user/node-metrics.html b/main/uk-rUA/user/node-metrics.html index c59bb312bd..1aef8f8850 100644 --- a/main/uk-rUA/user/node-metrics.html +++ b/main/uk-rUA/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Українська
Meshtastic Docs ↗

🌐 Українська — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Показники пристрою

Basic operating information reported by each node:

Metric Опис
Battery Level Current battery percentage
Напруга Battery voltage reading
Завантаженість каналу Percentage of local airtime in use
Завантаженість ефіру Percentage of the last hour this node spent transmitting
Час роботи Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Показники довкілля

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Температура BME280, BME680, SHT31
Вологість BME280, BME680, SHT31
Атмосферний тиск BME280, BMP280
Опір газового сенсора BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Опис
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Хороший < 1000 Зелений
Stuffy < 2000 Amber
Poor < 5000 Помаранчевий
Unsafe < 30000 Червоний
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Якість сигналу

Radio signal quality information:

Metric Опис
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
Хороший SNR above the preset’s limit
Задовільний less than 5.5 dB below the limit
Поганий 5.5 dB to 7.5 dB below the limit
Жоден more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Показники живлення

Power management telemetry (requires INA sensor or compatible hardware):

Metric Опис
Напруга Per-channel voltage reading
Поточний Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Маршрут

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Position Log

Historical position data for nodes that share their location:

  • GPS coordinates
  • Висота
  • Speed (if moving)
  • Timestamp for each position report

Інформація про сусідів

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Показники хоста

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

Показники PAX

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Українська
Meshtastic Docs ↗

🌐 Українська — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

Показники пристрою

Basic operating information reported by each node:

Metric Опис
Battery Level Current battery percentage
Напруга Battery voltage reading
Завантаженість каналу Percentage of local airtime in use
Завантаженість ефіру Percentage of the last hour this node spent transmitting
Час роботи Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Показники довкілля

Environmental sensor data (requires compatible hardware):

Metric Sensor Examples
Температура BME280, BME680, SHT31
Вологість BME280, BME680, SHT31
Атмосферний тиск BME280, BMP280
Опір газового сенсора BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

Metric Unit Опис
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) Color
Хороший < 1000 Зелений
Stuffy < 2000 Amber
Poor < 5000 Помаранчевий
Unsafe < 30000 Червоний
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

Якість сигналу

Radio signal quality information:

Metric Опис
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
Хороший SNR above the preset’s limit
Задовільний less than 5.5 dB below the limit
Поганий 5.5 dB to 7.5 dB below the limit
Жоден more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

Показники живлення

Power management telemetry (requires INA sensor or compatible hardware):

Metric Опис
Напруга Per-channel voltage reading
Поточний Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Маршрут

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Position Log

Historical position data for nodes that share their location:

  • GPS coordinates
  • Висота
  • Speed (if moving)
  • Timestamp for each position report

Інформація про сусідів

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Показники хоста

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

Показники PAX

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/uk-rUA/user/nodes.html b/main/uk-rUA/user/nodes.html index 86ce648bcb..d55742e9ef 100644 --- a/main/uk-rUA/user/nodes.html +++ b/main/uk-rUA/user/nodes.html @@ -1 +1 @@ - Вузли | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Українська
Meshtastic Docs ↗

🌐 Українська — Community translation View in English

Вузли

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Роль Опис
Клієнт Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Трекер Optimized for position reporting at regular intervals
Датчик Optimized for telemetry reporting
ТАК Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Loast and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Видалити

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Фільтри Опис
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Опис
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Стрибків Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Рівень заряду батареї Battery
Hop count Hops
Востаннє в мережі Last heard
Відстань Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ Вузли | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Українська
Meshtastic Docs ↗

🌐 Українська — Community translation View in English

Вузли

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

Роль Опис
Клієнт Standard end-user node
Client Base Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Трекер Optimized for position reporting at regular intervals
Датчик Optimized for telemetry reporting
ТАК Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Loast and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • Видалити

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

Фільтри Опис
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort Опис
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Стрибків Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
Рівень заряду батареї Battery
Hop count Hops
Востаннє в мережі Last heard
Відстань Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/uk-rUA/user/settings-radio-user.html b/main/uk-rUA/user/settings-radio-user.html index e4946c7566..d69639f98f 100644 --- a/main/uk-rUA/user/settings-radio-user.html +++ b/main/uk-rUA/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Українська
Meshtastic Docs ↗

🌐 Українська — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Опис
Довга назва Your display name (up to 39 characters)
Коротка назва 4-character abbreviated name
Статус повідомлення A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Недоступний для повідомлень Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Ліцензований радіоаматор (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Налаштування

Налаштування пристрою

On Settings → Device configuration → Device.

Setting Опис За замовчуванням
Роль пристрою Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим ретрансляції How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Інтервал розсилки даних про вузол How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Подвійний дотик як натискання кнопки Treat a double tap as a button press Disabled
Швидка перевірка зв’язку потрійним натисканням Send an ad-hoc position ping on a triple click Disabled
Частота мигання світлодіоду Blink the status LED periodically Увімкнено
Часовий пояс POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

Налаштування LoRa

On Settings → LoRa.

Setting Опис За замовчуванням
Регіон Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Пресети Speed/range tradeoff LongFast
К-ть стрибків Maximum retransmit hops 3
Потужність передачі Transmission power (dBm); 0 = max allowed for region 0 (region max)
Перевизначити частоту Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Використовувати пресет On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Показник розширення сигналу Manual mode only: 7–12. Higher spreads further but slower From preset
Швидкість кодування Manual mode only: 5–8. More redundancy costs airtime From preset
Ширина смуги пропускання Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Слот частоти Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Передача активована Turning this off makes the node receive-only On
Ігнорувати обмеження завантаженості каналу Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ігнорувати MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
MQTT: Готово Allow your packets to be forwarded to MQTT by gateways Off
Підсилення передачі Extra receive gain on SX126x radios; costs a little current Off
Вентилятор вимкнений Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Швидкість SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Налаштування дисплею

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Опис
Екран включено для How long the display stays lit before sleeping
Інтервал гортання каруселі How often the radio cycles between screens on its own
Режим екрану Screen layout/density used by the firmware
Одиниці виміру Metric or Imperial on the radio’s screen
Використовувати 12-г формат часу Show the radio’s clock as 12-hour rather than 24-hour
Жирні заголовки Draw the screen’s heading text in bold
Перевернути екран Rotate the display 180° for an inverted mounting
Тип OLED Auto, SSD1306, SH1106, SH1107
Прокидання дотиком або рухом Light the screen when the radio is tapped or moved
Орієнтація компаса Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Завжди вказувати на північ Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
Режим GPS (Фізичний пристрій) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Інтервал опитування GPS How often the radio asks its GPS for a fix
Інтервал трансляції How often the position is shared with the mesh
Інтелектуальне передавання позиції Broadcast based on movement rather than purely on the clock
Інтелектуальний інтервал With Smart Position on, the shortest gap between broadcasts
Інтелектуальна дистанція With Smart Position on, how far you must move before broadcasting
Фіксована позиція Use a manually entered latitude, longitude and altitude instead of the GPS
Прапорці місцеположення A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Налаштування живлення

On Settings → Device configuration → Power.

Setting Опис
Увімкнути енергоощадний режим Let the radio sleep aggressively between activity
Вимкнути при втраті живлення Power the device down after external power disappears
Тривалість глибокого сну How long the deepest sleep state lasts
Мінімальний час в робочому режимі The shortest time the radio stays awake once woken
Тривалість очікування Bluetooth How long to wait for a phone to connect before sleeping
Корекція множника напруги Turn on a manual correction for battery-voltage readings
Множник корекції напруги The correction factor itself, used only when the override is on
I2C адреса INA_2XX батареї Address of an external INA-series power sensor, if fitted

Налаштування мережі

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Опис
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Пароль Network password
Ethernet увімкнено Use a wired connection on hardware that has one
Режим IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP-сервер Time synchronization server
rsyslog-сервер Remote logging server

Network Config with a static IPv4 address entered

Налаштування Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
Bluetooth увімкнено Enable/disable BLE radio
Режим створення пари Fixed PIN, Random PIN, or No PIN
Фіксований PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Налаштування безпеки

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
Відкритий ключ Your node’s public key (read-only)
Ключ адміністратора Keys permitted to administer this node remotely — up to three
Приватний ключ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Згенерувати закритий ключ Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Серійна консоль Serial console over the Stream API
API журналу відладки увімкнено Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Керований режим Restrict non-admin channel changes. Only selectable once an Admin Key is set
Резервні ключі Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Українська
Meshtastic Docs ↗

🌐 Українська — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

User Settings

User Profile

On Settings → User.

Setting Опис
Довга назва Your display name (up to 39 characters)
Коротка назва 4-character abbreviated name
Статус повідомлення A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
Недоступний для повідомлень Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
Ліцензований радіоаматор (Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Налаштування

Налаштування пристрою

On Settings → Device configuration → Device.

Setting Опис За замовчуванням
Роль пристрою Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
Режим ретрансляції How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
Інтервал розсилки даних про вузол How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
Подвійний дотик як натискання кнопки Treat a double tap as a button press Disabled
Швидка перевірка зв’язку потрійним натисканням Send an ad-hoc position ping on a triple click Disabled
Частота мигання світлодіоду Blink the status LED periodically Увімкнено
Часовий пояс POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

Налаштування LoRa

On Settings → LoRa.

Setting Опис За замовчуванням
Регіон Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
Пресети Speed/range tradeoff LongFast
К-ть стрибків Maximum retransmit hops 3
Потужність передачі Transmission power (dBm); 0 = max allowed for region 0 (region max)
Перевизначити частоту Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
Використовувати пресет On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
Показник розширення сигналу Manual mode only: 7–12. Higher spreads further but slower From preset
Швидкість кодування Manual mode only: 5–8. More redundancy costs airtime From preset
Ширина смуги пропускання Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
Слот частоти Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
Передача активована Turning this off makes the node receive-only On
Ігнорувати обмеження завантаженості каналу Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
Ігнорувати MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
MQTT: Готово Allow your packets to be forwarded to MQTT by gateways Off
Підсилення передачі Extra receive gain on SX126x radios; costs a little current Off
Вентилятор вимкнений Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range Швидкість SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

Налаштування дисплею

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting Опис
Екран включено для How long the display stays lit before sleeping
Інтервал гортання каруселі How often the radio cycles between screens on its own
Режим екрану Screen layout/density used by the firmware
Одиниці виміру Metric or Imperial on the radio’s screen
Використовувати 12-г формат часу Show the radio’s clock as 12-hour rather than 24-hour
Жирні заголовки Draw the screen’s heading text in bold
Перевернути екран Rotate the display 180° for an inverted mounting
Тип OLED Auto, SSD1306, SH1106, SH1107
Прокидання дотиком або рухом Light the screen when the radio is tapped or moved
Орієнтація компаса Rotation offset for the compass rose (0°, 90°, 180°, 270°)
Завжди вказувати на північ Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

Position Config

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
Режим GPS (Фізичний пристрій) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
Інтервал опитування GPS How often the radio asks its GPS for a fix
Інтервал трансляції How often the position is shared with the mesh
Інтелектуальне передавання позиції Broadcast based on movement rather than purely on the clock
Інтелектуальний інтервал With Smart Position on, the shortest gap between broadcasts
Інтелектуальна дистанція With Smart Position on, how far you must move before broadcasting
Фіксована позиція Use a manually entered latitude, longitude and altitude instead of the GPS
Прапорці місцеположення A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

Налаштування живлення

On Settings → Device configuration → Power.

Setting Опис
Увімкнути енергоощадний режим Let the radio sleep aggressively between activity
Вимкнути при втраті живлення Power the device down after external power disappears
Тривалість глибокого сну How long the deepest sleep state lasts
Мінімальний час в робочому режимі The shortest time the radio stays awake once woken
Тривалість очікування Bluetooth How long to wait for a phone to connect before sleeping
Корекція множника напруги Turn on a manual correction for battery-voltage readings
Множник корекції напруги The correction factor itself, used only when the override is on
I2C адреса INA_2XX батареї Address of an external INA-series power sensor, if fitted

Налаштування мережі

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting Опис
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
Пароль Network password
Ethernet увімкнено Use a wired connection on hardware that has one
Режим IPv4 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP broadcasting Share mesh traffic with other nodes over the local network
NTP-сервер Time synchronization server
rsyslog-сервер Remote logging server

Network Config with a static IPv4 address entered

Налаштування Bluetooth

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
Bluetooth увімкнено Enable/disable BLE radio
Режим створення пари Fixed PIN, Random PIN, or No PIN
Фіксований PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

Налаштування безпеки

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting Опис
Відкритий ключ Your node’s public key (read-only)
Ключ адміністратора Keys permitted to administer this node remotely — up to three
Приватний ключ Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
Згенерувати закритий ключ Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
Серійна консоль Serial console over the Stream API
API журналу відладки увімкнено Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
Керований режим Restrict non-admin channel changes. Only selectable once an Admin Key is set
Резервні ключі Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/uk-rUA/user/signal-meter.html b/main/uk-rUA/user/signal-meter.html index 06fe997140..3fb4ed39e9 100644 --- a/main/uk-rUA/user/signal-meter.html +++ b/main/uk-rUA/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Українська
Meshtastic Docs ↗

🌐 Українська — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Хороший Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Задовільний 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Поганий 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Жоден 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 Українська
Meshtastic Docs ↗

🌐 Українська — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
Хороший Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
Задовільний 3 less than 5.5 dB below limit Decodable, but approaching the floor.
Поганий 2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
Жоден 1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/zh-rCN/user/node-metrics.html b/main/zh-rCN/user/node-metrics.html index c65a42e83f..f8fb504a79 100644 --- a/main/zh-rCN/user/node-metrics.html +++ b/main/zh-rCN/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 中文 (简体)
Meshtastic Docs ↗

🌐 中文 (简体) — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

设备数据

Basic operating information reported by each node:

公制 说明
电池电量 Current battery percentage
电压 Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
正常运行时间 Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

传感器指标

Environmental sensor data (requires compatible hardware):

公制 Sensor Examples
温度 BME280, BME680, SHT31
湿度 BME280, BME680, SHT31
气压 BME280, BMP280
气体电阻性 BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

公制 Unit 说明
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) 颜色
良好 < 1000 绿
Stuffy < 2000 Amber
Poor < 5000 橙色
Unsafe < 30000
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

信号质量

Radio signal quality information:

公制 说明
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
良好 SNR above the preset’s limit
一般 less than 5.5 dB below the limit
5.5 dB to 7.5 dB below the limit
more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

电源计量

Power management telemetry (requires INA sensor or compatible hardware):

公制 说明
电压 Per-channel voltage reading
电流 Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

追踪器

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

定位日志

Historical position data for nodes that share their location:

  • GPS coordinates
  • 海拔高度
  • Speed (if moving)
  • Timestamp for each position report

邻居信息

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

主机测量

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX 计量

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 中文 (简体)
Meshtastic Docs ↗

🌐 中文 (简体) — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

设备数据

Basic operating information reported by each node:

公制 说明
电池电量 Current battery percentage
电压 Battery voltage reading
ChUtil Percentage of local airtime in use
AirUtil Percentage of the last hour this node spent transmitting
正常运行时间 Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

传感器指标

Environmental sensor data (requires compatible hardware):

公制 Sensor Examples
温度 BME280, BME680, SHT31
湿度 BME280, BME680, SHT31
气压 BME280, BMP280
气体电阻性 BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

公制 Unit 说明
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) 颜色
良好 < 1000 绿
Stuffy < 2000 Amber
Poor < 5000 橙色
Unsafe < 30000
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

信号质量

Radio signal quality information:

公制 说明
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
Hop Count Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
良好 SNR above the preset’s limit
一般 less than 5.5 dB below the limit
5.5 dB to 7.5 dB below the limit
more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

电源计量

Power management telemetry (requires INA sensor or compatible hardware):

公制 说明
电压 Per-channel voltage reading
电流 Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

追踪器

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

定位日志

Historical position data for nodes that share their location:

  • GPS coordinates
  • 海拔高度
  • Speed (if moving)
  • Timestamp for each position report

邻居信息

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

主机测量

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX 计量

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.


diff --git a/main/zh-rCN/user/nodes.html b/main/zh-rCN/user/nodes.html index 4d5cd2b90d..6a9ecfffcd 100644 --- a/main/zh-rCN/user/nodes.html +++ b/main/zh-rCN/user/nodes.html @@ -1 +1 @@ - 节点 | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 中文 (简体)
Meshtastic Docs ↗

🌐 中文 (简体) — Community translation View in English

节点

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

角色 说明
客户端 Standard end-user node
客户群 Treats favorited-node traffic as Router Late priority; all other traffic as Client
客户端静默 Receives but doesn’t retransmit
客户端隐藏 Like Client Mute, plus hides from node list
路由 Prioritizes message forwarding; stays awake to relay
延迟时间 Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
追踪器 Optimized for position reporting at regular intervals
传感器 Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK 追踪器 TAK position reporting only
失物招领 Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

图标 Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • 移除

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

搜索节点 说明
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort 说明
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
电池电量 Battery
Hop count Hops
最后听到 Last heard
距离 Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ 节点 | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 中文 (简体)
Meshtastic Docs ↗

🌐 中文 (简体) — Community translation View in English

节点

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

角色 说明
客户端 Standard end-user node
客户群 Treats favorited-node traffic as Router Late priority; all other traffic as Client
客户端静默 Receives but doesn’t retransmit
客户端隐藏 Like Client Mute, plus hides from node list
路由 Prioritizes message forwarding; stays awake to relay
延迟时间 Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
追踪器 Optimized for position reporting at regular intervals
传感器 Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK 追踪器 TAK position reporting only
失物招领 Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

图标 Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • 移除

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

搜索节点 说明
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort 说明
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator Screenshot
Signal quality Signal
电池电量 Battery
Hop count Hops
最后听到 Last heard
距离 Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/zh-rCN/user/settings-radio-user.html b/main/zh-rCN/user/settings-radio-user.html index 4a03be46c4..6b63c514c5 100644 --- a/main/zh-rCN/user/settings-radio-user.html +++ b/main/zh-rCN/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 中文 (简体)
Meshtastic Docs ↗

🌐 中文 (简体) — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

用户设置

User Profile

On Settings → User.

Setting 说明
长名称 Your display name (up to 39 characters)
短名称 4-character abbreviated name
状态消息 A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
无法发送消息 Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
业余无线电模式(Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

设备配置

On Settings → Device configuration → Device.

Setting 说明 默认
设备角色 Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
转播模式 How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
节点信息广播间隔 How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
双击作为按钮 Treat a double tap as a button press 禁用
快速按3下 向所有节点发送紧急广播 Send an ad-hoc position ping on a triple click 禁用
LED 心跳 Blink the status LED periodically Enabled
时区 POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa 配置

On Settings → LoRa.

Setting 说明 默认
区域 Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
预设 Speed/range tradeoff LongFast
节点数 Maximum retransmit hops 3
发送强度 Transmission power (dBm); 0 = max allowed for region 0 (region max)
频率覆盖 Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
使用预设 On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
扩散因子 Manual mode only: 7–12. Higher spreads further but slower From preset
编码率 Manual mode only: 5–8. More redundancy costs airtime From preset
带宽 Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
频率时隙 Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
启用传输 Turning this off makes the node receive-only On
覆盖占空比 Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits 关闭
忽略 MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
使用MQTT Allow your packets to be forwarded to MQTT by gateways 关闭
RX 增益 Extra receive gain on SX126x radios; costs a little current 关闭
PA风扇已禁用 Turn off the power-amplifier fan on hardware that has one 关闭

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range 速度 SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

屏幕配置

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting 说明
开启屏幕 How long the display stays lit before sleeping
轮播间隔 How often the radio cycles between screens on its own
显示模式 Screen layout/density used by the firmware
显示单位 Metric or Imperial on the radio’s screen
使用 12 小时制格式 Show the radio’s clock as 12-hour rather than 24-hour
加粗标题 Draw the screen’s heading text in bold
翻转屏幕 Rotate the display 180° for an inverted mounting
OLED 类型 Auto, SSD1306, SH1106, SH1107
点击或移动时唤醒屏幕 Light the screen when the radio is tapped or moved
罗盘方向 Rotation offset for the compass rose (0°, 90°, 180°, 270°)
总是朝北 Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

定位配置

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting 说明
GPS 模式 (物理硬件) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS 轮询间隔 How often the radio asks its GPS for a fix
广播间隔 How often the position is shared with the mesh
智能位置 Broadcast based on movement rather than purely on the clock
自动时间间隔 With Smart Position on, the shortest gap between broadcasts
自动距离大小 With Smart Position on, how far you must move before broadcasting
固定位置 Use a manually entered latitude, longitude and altitude instead of the GPS
位置信息数据包 A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

电源配置

On Settings → Device configuration → Power.

Setting 说明
启用节能模式 Let the radio sleep aggressively between activity
断电时关机 Power the device down after external power disappears
深度睡眠时间 How long the deepest sleep state lasts
最小唤醒时间 The shortest time the radio stays awake once woken
等待蓝牙持续时间 How long to wait for a phone to connect before sleeping
ADC 倍数覆盖 Turn on a manual correction for battery-voltage readings
ADC乘数修正比率 The correction factor itself, used only when the override is on
电池INA_2XX I2C 地址 Address of an external INA-series power sensor, if fitted

网络配置

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting 说明
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
密码 网络密码
启用以太网 Use a wired connection on hardware that has one
IPv4模式 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP 广播 Share mesh traffic with other nodes over the local network
NTP 服务器 Time synchronization server
rsyslog 服务器 Remote logging server

Network Config with a static IPv4 address entered

蓝牙配置

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting 说明
启用蓝牙 Enable/disable BLE radio
配对模式 Fixed PIN, Random PIN, or No PIN
固定PIN码 PIN code for pairing. Must be exactly six digits — the field rejects anything else

安全配置

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting 说明
公钥 Your node’s public key (read-only)
管理员密钥 Keys permitted to administer this node remotely — up to three
私钥 Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
重新生成私钥 Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
串口控制 Serial console over the Stream API
启用调试日志 API Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
管理模式 Restrict non-admin channel changes. Only selectable once an Admin Key is set
备份密钥 Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
恢复密钥 Write the backed-up keys back to the node (available once a backup exists)
删除密钥备份 Remove the stored key backup from this phone
安全等级 How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
剩余启动次数 How many device boots the unlocked state survives
距离失效还有多少小时 Wall-clock lifetime of the unlocked state
会话上限 (分钟) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 中文 (简体)
Meshtastic Docs ↗

🌐 中文 (简体) — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control Screenshot
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

用户设置

User Profile

On Settings → User.

Setting 说明
长名称 Your display name (up to 39 characters)
短名称 4-character abbreviated name
状态消息 A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
无法发送消息 Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
业余无线电模式(Ham) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

Configuration

设备配置

On Settings → Device configuration → Device.

Setting 说明 默认
设备角色 Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
转播模式 How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
节点信息广播间隔 How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
双击作为按钮 Treat a double tap as a button press 禁用
快速按3下 向所有节点发送紧急广播 Send an ad-hoc position ping on a triple click 禁用
LED 心跳 Blink the status LED periodically Enabled
时区 POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa 配置

On Settings → LoRa.

Setting 说明 默认
区域 Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
预设 Speed/range tradeoff LongFast
节点数 Maximum retransmit hops 3
发送强度 Transmission power (dBm); 0 = max allowed for region 0 (region max)
频率覆盖 Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
使用预设 On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
扩散因子 Manual mode only: 7–12. Higher spreads further but slower From preset
编码率 Manual mode only: 5–8. More redundancy costs airtime From preset
带宽 Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
频率时隙 Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
启用传输 Turning this off makes the node receive-only On
覆盖占空比 Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits 关闭
忽略 MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
使用MQTT Allow your packets to be forwarded to MQTT by gateways 关闭
RX 增益 Extra receive gain on SX126x radios; costs a little current 关闭
PA风扇已禁用 Turn off the power-amplifier fan on hardware that has one 关闭

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset Range 速度 SNR Limit Best For
Short Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
Short Fast ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
Short Slow ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
Medium Fast ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
Medium Slow ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
Long Moderate ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

屏幕配置

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

Setting 说明
开启屏幕 How long the display stays lit before sleeping
轮播间隔 How often the radio cycles between screens on its own
显示模式 Screen layout/density used by the firmware
显示单位 Metric or Imperial on the radio’s screen
使用 12 小时制格式 Show the radio’s clock as 12-hour rather than 24-hour
加粗标题 Draw the screen’s heading text in bold
翻转屏幕 Rotate the display 180° for an inverted mounting
OLED 类型 Auto, SSD1306, SH1106, SH1107
点击或移动时唤醒屏幕 Light the screen when the radio is tapped or moved
罗盘方向 Rotation offset for the compass rose (0°, 90°, 180°, 270°)
总是朝北 Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

定位配置

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

Setting 说明
GPS 模式 (物理硬件) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS 轮询间隔 How often the radio asks its GPS for a fix
广播间隔 How often the position is shared with the mesh
智能位置 Broadcast based on movement rather than purely on the clock
自动时间间隔 With Smart Position on, the shortest gap between broadcasts
自动距离大小 With Smart Position on, how far you must move before broadcasting
固定位置 Use a manually entered latitude, longitude and altitude instead of the GPS
位置信息数据包 A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

电源配置

On Settings → Device configuration → Power.

Setting 说明
启用节能模式 Let the radio sleep aggressively between activity
断电时关机 Power the device down after external power disappears
深度睡眠时间 How long the deepest sleep state lasts
最小唤醒时间 The shortest time the radio stays awake once woken
等待蓝牙持续时间 How long to wait for a phone to connect before sleeping
ADC 倍数覆盖 Turn on a manual correction for battery-voltage readings
ADC乘数修正比率 The correction factor itself, used only when the override is on
电池INA_2XX I2C 地址 Address of an external INA-series power sensor, if fitted

网络配置

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

Setting 说明
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
密码 网络密码
启用以太网 Use a wired connection on hardware that has one
IPv4模式 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP 广播 Share mesh traffic with other nodes over the local network
NTP 服务器 Time synchronization server
rsyslog 服务器 Remote logging server

Network Config with a static IPv4 address entered

蓝牙配置

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

Setting 说明
启用蓝牙 Enable/disable BLE radio
配对模式 Fixed PIN, Random PIN, or No PIN
固定PIN码 PIN code for pairing. Must be exactly six digits — the field rejects anything else

安全配置

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

Setting 说明
公钥 Your node’s public key (read-only)
管理员密钥 Keys permitted to administer this node remotely — up to three
私钥 Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
重新生成私钥 Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
串口控制 Serial console over the Stream API
启用调试日志 API Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
管理模式 Restrict non-admin channel changes. Only selectable once an Admin Key is set
备份密钥 Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
恢复密钥 Write the backed-up keys back to the node (available once a backup exists)
删除密钥备份 Remove the stored key backup from this phone
安全等级 How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
剩余启动次数 How many device boots the unlocked state survives
距离失效还有多少小时 Wall-clock lifetime of the unlocked state
会话上限 (分钟) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/zh-rCN/user/signal-meter.html b/main/zh-rCN/user/signal-meter.html index 9da846267a..55d58b96ee 100644 --- a/main/zh-rCN/user/signal-meter.html +++ b/main/zh-rCN/user/signal-meter.html @@ -1 +1 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 中文 (简体)
Meshtastic Docs ↗

🌐 中文 (简体) — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
良好 Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
一般 3 less than 5.5 dB below limit Decodable, but approaching the floor.
2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


+ How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 中文 (简体)
Meshtastic Docs ↗

🌐 中文 (简体) — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

Level Bars Criteria Meaning
良好 Full SNR above limit Comfortably above the demodulation floor — a healthy connection.
一般 3 less than 5.5 dB below limit Decodable, but approaching the floor.
2 5.5 dB to 7.5 dB below limit At the edge of what the preset can recover.
1 more than 7.5 dB below limit Far below the preset’s floor; further packets from this node are likely to be lost.

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon


diff --git a/main/zh-rTW/user/node-metrics.html b/main/zh-rTW/user/node-metrics.html index aeb43936e9..206e9f2e0e 100644 --- a/main/zh-rTW/user/node-metrics.html +++ b/main/zh-rTW/user/node-metrics.html @@ -1 +1 @@ - Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 中文 (繁體)
Meshtastic Docs ↗

🌐 中文 (繁體) — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

裝置計量資料

Basic operating information reported by each node:

公制(公里/公尺) 描述說明
Battery Level Current battery percentage
電壓 Battery voltage reading
頻道利用率 Percentage of local airtime in use
空中時間使用率 Percentage of the last hour this node spent transmitting
運行時間 Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

環境計量資料

Environmental sensor data (requires compatible hardware):

公制(公里/公尺) Sensor Examples
溫度 BME280, BME680, SHT31
濕度 BME280, BME680, SHT31
大氣壓力 BME280, BMP280
氣體感測器 BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

公制(公里/公尺) 單位 描述說明
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) 顏色
良好 < 1000 Green - 綠色
Stuffy < 2000 Amber
Poor < 5000 橙色
Unsafe < 30000 Red - 紅色
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

信號品質

Radio signal quality information:

公制(公里/公尺) 描述說明
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
跳躍次數 Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset’s SNR limit.

Quality Criteria
良好 SNR above the preset’s limit
普通 less than 5.5 dB below the limit
不良 5.5 dB to 7.5 dB below the limit
more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

電源計量資料

Power management telemetry (requires INA sensor or compatible hardware):

公制(公里/公尺) 描述說明
電壓 Per-channel voltage reading
目前 Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

路由追蹤

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

定位日誌

Historical position data for nodes that share their location:

  • GPS 座標
  • 海拔高度
  • Speed (if moving)
  • Timestamp for each position report

鄰近節點資訊

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

主機資訊

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX 人流計量

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.

相關主題


+ Node Metrics | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 中文 (繁體)
Meshtastic Docs ↗

🌐 中文 (繁體) — Community translation View in English

Node Metrics

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

Viewing Metrics

  1. Navigate to Nodes.
  2. Tap the node you want to inspect.
  3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.
  4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry.

Node detail — local device

The Position row expands to show location data for nodes that share GPS:

Position inline content

ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings.

裝置計量資料

Basic operating information reported by each node:

公制(公里/公尺) 描述說明
Battery Level Current battery percentage
電壓 Battery voltage reading
頻道利用率 Percentage of local airtime in use
空中時間使用率 Percentage of the last hour this node spent transmitting
運行時間 Time since last reboot

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

環境計量資料

Environmental sensor data (requires compatible hardware):

公制(公里/公尺) Sensor Examples
溫度 BME280, BME680, SHT31
濕度 BME280, BME680, SHT31
大氣壓力 BME280, BMP280
氣體感測器 BME680
IAQ (Air Quality) BME680

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

IAQ index scale from Excellent to Dangerously Polluted

💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors.

Air Quality Metrics

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

公制(公里/公尺) 單位 描述說明
PM1.0 µg/m³ Particulate matter up to 1.0 micron
PM2.5 µg/m³ Particulate matter up to 2.5 microns
PM10 µg/m³ Particulate matter up to 10 microns
AQI EPA index EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated.
CO₂ ppm Carbon dioxide concentration
CO₂ temperature °C / °F Temperature reported by the CO₂ sensor itself (e.g. SCD4x)
CO₂ humidity % Relative humidity reported by the CO₂ sensor

CO₂ readings are color-coded by severity so you can read air quality at a glance:

Band CO₂ Range (ppm) 顏色
良好 < 1000 Green - 綠色
Stuffy < 2000 Amber
Poor < 5000 橙色
Unsafe < 30000 Red - 紅色
Evacuate ≥ 30000 Dark red

Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

  • Select a time frame for the charts.
  • Filter with metric chips — only metrics that have data are shown.
  • Refresh / request the latest air-quality telemetry.
  • Export to CSV for analysis in a spreadsheet.

💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware.

信號品質

Radio signal quality information:

公制(公里/公尺) 描述說明
SNR Signal-to-Noise Ratio (higher is better)
RSSI Received Signal Strength Indicator (closer to 0 is better)
Noise Floor Local background RF noise in dBm (more negative is quieter)
跳躍次數 Number of mesh hops for last message

Signal Quality Reference

Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit.

Quality Criteria
良好 SNR above the preset’s limit
普通 less than 5.5 dB below the limit
不良 5.5 dB to 7.5 dB below the limit
more than 7.5 dB below the limit

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

  • Request — ask the connected radio for a fresh Local Stats telemetry report
  • Clear — remove Local Stats logs for that node
  • Save — export the visible Local Stats history as CSV

電源計量資料

Power management telemetry (requires INA sensor or compatible hardware):

公制(公里/公尺) 描述說明
電壓 Per-channel voltage reading
目前 Per-channel draw, in milliamps

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

路由追蹤

Traceroute shows the path a message takes through the mesh:

  1. From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.
  2. The app sends a traceroute request to the target node.
  3. Results show each hop with its SNR.

Reading Traceroute Results

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

定位日誌

Historical position data for nodes that share their location:

  • GPS 座標
  • 海拔高度
  • Speed (if moving)
  • Timestamp for each position report

鄰近節點資訊

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

主機資訊

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

PAX 人流計量

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.

相關主題


diff --git a/main/zh-rTW/user/nodes.html b/main/zh-rTW/user/nodes.html index e094a02872..702c72ced0 100644 --- a/main/zh-rTW/user/nodes.html +++ b/main/zh-rTW/user/nodes.html @@ -1 +1 @@ - 節點 | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 中文 (繁體)
Meshtastic Docs ↗

🌐 中文 (繁體) — Community translation View in English

節點

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

角色 描述說明
用戶端 Standard end-user node
客戶端基礎模式 Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Repeater Optimized for position reporting at regular intervals
感測器 Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • 移除

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

過濾器 描述說明
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort 描述說明
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator 螢幕截圖
Signal quality Signal
電池電量 Battery
Hop count Hops
最近一次收到排序 Last heard
距離 Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

+ 節點 | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 中文 (繁體)
Meshtastic Docs ↗

🌐 中文 (繁體) — Community translation View in English

節點

The Nodes screen lists every node visible on your mesh.

Node List

The node list shows every node your radio has heard, including:

  • Node name — user-configured long name
  • Short name — 4-character identifier
  • Signal quality — SNR, RSSI, and a quality word, shown only for nodes your radio heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither
  • Last heard — time since last communication
  • Distance — estimated distance (if positions are shared)
  • Battery — remote node battery level (if telemetry is enabled)

Choosing What the List Shows

The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen.

Node Status Indicators

Indicator Meaning
Green last-heard time Node heard within the last 2 hours
Plain last-heard time Node not heard for over 2 hours
⭐ Favorite Node you marked as a favorite.

There is no separate “away” tier.

Node Roles

Nodes can be configured with different roles that affect their mesh behavior:

角色 描述說明
用戶端 Standard end-user node
客戶端基礎模式 Treats favorited-node traffic as Router Late priority; all other traffic as Client
Client Mute Receives but doesn’t retransmit
Client Hidden Like Client Mute, plus hides from node list
Router Prioritizes message forwarding; stays awake to relay
Router Late Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage)
Router Client ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead
Repeater ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead
Repeater Optimized for position reporting at regular intervals
感測器 Optimized for telemetry reporting
TAK Interoperates with TAK systems (sends/receives CoT)
TAK Tracker TAK position reporting only
Lost and Found Sends its position to the default channel as a text message at regular intervals, to help recover a lost radio

Choosing a Role

Most users should keep the default Client role. Consider a different role when:

  • Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don’t use Router on battery-powered handheld radios.
  • Router Late — An infrastructure node that always rebroadcasts packets once but only after all other routing modes have had their turn. Provides supplemental coverage for local clusters without competing with primary routers.
  • Client Base — Treats traffic from/to your favorited nodes with Router Late priority (ensuring those messages get extra relay coverage) while handling everything else as a normal Client.
  • Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only radios or to reduce congestion in dense areas.
  • Tracker — An unattended radio whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
  • Sensor — An unattended radio reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
  • TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.

💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.

Encryption Indicators

Nodes display encryption status icons next to their name:

Icon Meaning
🔒 Locked Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity
🔓 Unlocked No public key has been received for this node, so it cannot be direct messaged — use Request User Info on the node detail page to ask for one
⚠️ Mismatch Public key mismatch — the node’s key has changed since last seen (investigate before trusting)

💡 Tip: Direct messages always use PKI, so the radio needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. If you see a key mismatch warning, the node may have been reset or compromised.

To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two radios exchange keys again the next time yours hears it.

Quick Actions

From the node list, you can:

  • Tap a node to view its detail page
  • Touch & hold for quick actions:
    • Mark/remove favorite
    • Mute/unmute notifications
    • Send a direct message
    • Trace route
    • Ignore/unignore
    • 移除

Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the radio is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself.

Sharing a Contact

On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Write to NFC tag saves the link to a writable NFC tag that anyone can tap to open.

To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have.

Filtering & Sorting

Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.

Filter Toggles

過濾器 描述說明
Hide offline nodes Show only nodes heard within the last 2 hours
Only show direct nodes Show only nodes your radio heard directly, with no relay in between
Include unknown Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and cannot be direct messaged until their user info brings a public key
Exclude infrastructure Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that cannot be messaged, whatever its role
Exclude MQTT Hide nodes heard only via MQTT internet bridge
Only show ignored Nodes Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back

Sort Options

Sort 描述說明
Last heard Most recently heard nodes first
A-Z Sorted by node long name
Distance Nearest nodes first (requires position sharing)
Hops away Fewest relay hops first
Channel Grouped by channel index
via MQTT Grouped by MQTT vs. radio-heard
via Favorite (default) Favorited nodes first, then the rest

Nodes per Hop

Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All time, 1 hour, 8 hours, or 24 hours — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is.

Node Detail

Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.

Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available.

The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI:

Node detail section

Inline status indicators show key metrics at a glance:

Indicator 螢幕截圖
Signal quality Signal
電池電量 Battery
Hop count Hops
最近一次收到排序 Last heard
距離 Distance

When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section.

A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node.

Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission.

When No Nodes Appear

The list stays empty until your radio hears another node.

  • No device connected — the app is not connected to a radio. See Connections.
  • Searching for nodes — the radio is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that has not yet sent its name still appears. See Settings — Radio & User.
  • A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node.

diff --git a/main/zh-rTW/user/settings-radio-user.html b/main/zh-rTW/user/settings-radio-user.html index 917a70572f..29b5dda7c0 100644 --- a/main/zh-rTW/user/settings-radio-user.html +++ b/main/zh-rTW/user/settings-radio-user.html @@ -1 +1 @@ - Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 中文 (繁體)
Meshtastic Docs ↗

🌐 中文 (繁體) — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control 螢幕截圖
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

使用者設定

User Profile

On Settings → User.

設定 描述說明
長名稱 Your display name (up to 39 characters)
簡短名稱 4-character abbreviated name
狀態訊息 A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
不接收訊息 Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
領有執照的業餘無線電台 (HAM) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

設定

設備設置

On Settings → Device configuration → Device.

設定 描述說明 默認
裝置角色 Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
## Rebroadcast Mode轉發廣播模式 How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
節點資訊廣播間隔 How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
雙擊觸發按鈕功能 Treat a double tap as a button press Disabled
三擊執行 Ad Hoc Ping Send an ad-hoc position ping on a triple click 已停用
LED 心跳指示 Blink the status LED periodically 已啟用
時區 POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa規劃

On Settings → LoRa.

設定 描述說明 默認
地區 Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
預設配置 Speed/range tradeoff LongFast
中繼次數 Maximum retransmit hops 3
傳輸功率 Transmission power (dBm); 0 = max allowed for region 0 (region max)
手動設定頻率 Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
使用預設值 On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
擴頻因子 Manual mode only: 7–12. Higher spreads further but slower From preset
編碼率 Manual mode only: 5–8. More redundancy costs airtime From preset
頻寬 Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
頻率槽 Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
已啟用發射 Turning this off makes the node receive-only On
覆蓋工作週期/佔空比 Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
忽略 MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
允許轉發至 MQTT Allow your packets to be forwarded to MQTT by gateways Off
接收增益提升 Extra receive gain on SX126x radios; costs a little current Off
停用PA風扇 Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset 範圍 速度 SNR Limit Best For
短 Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
短 快 ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
短 慢 ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
中等快 ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
中等慢 ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −12.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
長度中等的 ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −10 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −12.5 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

顯示設置

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

設定 描述說明
螢幕開啟持續時間 How long the display stays lit before sleeping
輪播間隔 How often the radio cycles between screens on its own
顯示模式 Screen layout/density used by the firmware
顯示單位 Metric or Imperial on the radio’s screen
使用12小時制 Show the radio’s clock as 12-hour rather than 24-hour
粗體字 Draw the screen’s heading text in bold
翻轉畫面 Rotate the display 180° for an inverted mounting
OLED 類型 Auto, SSD1306, SH1106, SH1107
輕觸或移動喚醒 Light the screen when the radio is tapped or moved
羅盤朝向 Rotation offset for the compass rose (0°, 90°, 180°, 270°)
始終指向北方 Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

位置設定

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

設定 描述說明
GPS 模式(實體硬體) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS 輪詢間隔 How often the radio asks its GPS for a fix
廣播間隔 How often the position is shared with the mesh
智慧定位 Broadcast based on movement rather than purely on the clock
智慧間隔 With Smart Position on, the shortest gap between broadcasts
智慧距離 With Smart Position on, how far you must move before broadcasting
固定位置 Use a manually entered latitude, longitude and altitude instead of the GPS
位置旗標 A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

電源設定

On Settings → Device configuration → Power.

設定 描述說明
啟用省電模式 Let the radio sleep aggressively between activity
電源中斷時關機 Power the device down after external power disappears
超深度睡眠時長 How long the deepest sleep state lasts
最小喚醒時間 The shortest time the radio stays awake once woken
藍牙等待持續時間 How long to wait for a phone to connect before sleeping
ADC 校正係數 Turn on a manual correction for battery-voltage readings
ADC乘數修正比率 The correction factor itself, used only when the override is on
電池 INA_2XX I2C 地址 Address of an external INA-series power sensor, if fitted

網路配置

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

設定 描述說明
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
密碼 網路密碼
啟用以太網 Use a wired connection on hardware that has one
第四代IP模式 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP 廣播 Share mesh traffic with other nodes over the local network
時間伺服器 Time synchronization server
rsyslog伺服器 Remote logging server

Network Config with a static IPv4 address entered

藍牙配置

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

設定 描述說明
藍牙已啟用 Enable/disable BLE radio
配對模式 Fixed PIN, Random PIN, or No PIN
固定 PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

安全性設定

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

設定 描述說明
公鑰 Your node’s public key (read-only)
管理金鑰 Keys permitted to administer this node remotely — up to three
私鑰 Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
重新產生私鑰 Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
序列控制台 Serial console over the Stream API
啟用除錯日誌 API Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
管理模式 Restrict non-admin channel changes. Only selectable once an Admin Key is set
備份金鑰 Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


+ Settings — Radio & User | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 中文 (繁體)
Meshtastic Docs ↗

🌐 中文 (繁體) — Community translation View in English

Settings — Radio & User

Configure your radio’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings.

How These Screens Work

Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on radios with Wi-Fi or Ethernet, and Bluetooth only on radios with Bluetooth.

Settings use standard preference controls — dropdowns, toggles, and sliders:

Control 螢幕截圖
Dropdown A dropdown setting, expanded to show its list of options
Toggle A toggle setting in the on position
Slider A slider setting with its current numeric value shown

使用者設定

User Profile

On Settings → User.

設定 描述說明
長名稱 Your display name (up to 39 characters)
簡短名稱 4-character abbreviated name
狀態訊息 A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the in the field. The radio broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise
不接收訊息 Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware
領有執照的業餘無線電台 (HAM) Enable if you hold an amateur radio license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own radio it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name

Applying Changes

The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the radio: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else.

The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own radio there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected radio have no shortcut — the field above is still the way in.

設定

設備設置

On Settings → Device configuration → Device.

設定 描述說明 默認
裝置角色 Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first CLIENT
## Rebroadcast Mode轉發廣播模式 How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one ALL
節點資訊廣播間隔 How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds 3 hours
雙擊觸發按鈕功能 Treat a double tap as a button press Disabled
三擊執行 Ad Hoc Ping Send an ad-hoc position ping on a triple click 已停用
LED 心跳指示 Blink the status LED periodically 已啟用
時區 POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it
Button / Buzzer GPIO Advanced: which pins the button and buzzer are wired to

LoRa規劃

On Settings → LoRa.

設定 描述說明 默認
地區 Regulatory region for frequency bands. You must set this before transmitting Unset (must configure)
預設配置 Speed/range tradeoff LongFast
中繼次數 Maximum retransmit hops 3
傳輸功率 Transmission power (dBm); 0 = max allowed for region 0 (region max)
手動設定頻率 Overrides the computed operating frequency outright (MHz). It does not offset the calculated value — leave at 0 unless you know you need a specific frequency 0 (use calculated)
使用預設值 On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset On
擴頻因子 Manual mode only: 7–12. Higher spreads further but slower From preset
編碼率 Manual mode only: 5–8. More redundancy costs airtime From preset
頻寬 Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your radio supports instead, and a stored value that is not on that list shows as Unsupported and blocks saving until you pick a supported one From preset
頻率槽 Which slot within the region’s band to use. 0 derives it from the primary channel name 0 (automatic)
已啟用發射 Turning this off makes the node receive-only On
覆蓋工作週期/佔空比 Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits Off
忽略 MQTT Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 Off, until you set a duty-cycle-limited region
允許轉發至 MQTT Allow your packets to be forwarded to MQTT by gateways Off
接收增益提升 Extra receive gain on SX126x radios; costs a little current Off
停用PA風扇 Turn off the power-amplifier fan on hardware that has one Off

Some regions are amateur-radio allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur radio (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out.

⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details.

Modem Presets

The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older radios.

💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation.

Preset 範圍 速度 SNR Limit Best For
短 Turbo ~1 km 21.9 kbps −7.5 dB Dense urban with line-of-sight; data-heavy applications
短 快 ~3 km 10.9 kbps −7.5 dB Urban neighborhoods; buildings within a few blocks
短 慢 ~5 km 6.25 kbps −10 dB Suburban short-range; moderate building density
中等快 ~5 km 3.52 kbps −12.5 dB Suburban areas; moderate building density
中等慢 ~8 km 1.95 kbps −15 dB Suburban/rural; moderate range with slower speed
Long Turbo ~10 km 1.34 kbps −17.5 dB Similar range to Long Fast but with 500 kHz bandwidth; faster throughput
Long Fast ~10 km 1.1 kbps −17.5 dB General use (default) — balanced range and speed
長度中等的 ~20 km 0.34 kbps −17.5 dB Rural with some terrain; occasional use
Lite Fast ~5 km 1.76 kbps −12.5 dB EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast
Lite Slow ~10 km 0.98 kbps −15 dB EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast
Narrow Fast ~5 km 2.28 kbps −7.5 dB EU 868 MHz band (62.5 kHz BW); avoids interference with other devices
Narrow Slow ~10 km 1.30 kbps −10 dB EU 868 MHz band (62.5 kHz BW); comparable to Long Fast
Medium Turbo ~5 km 7.0 kbps −12.5 dB Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer
Tiny Fast ~10 km 0.68 kbps −7.5 dB Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better
Tiny Slow ~20 km 0.33 kbps −10 dB Same band restrictions as Tiny Fast, longer range. Same firmware, radio, and TCXO requirements
Long Slow ~30 km 0.18 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release
Very Long Slow ~40+ km 0.09 kbps −20 dB ⚠️ Deprecated — still selectable but may be removed in a future firmware release

ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo.

Choosing a Modem Preset

The modem preset controls the fundamental tradeoff between range and data rate:

  • Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second.
  • Faster presets pack more data per transmission but require a stronger signal to decode.

Practical guidance:

  • Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel.
  • Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart.
  • EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths.
  • Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight.
  • Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area.

All nodes on the same channel must use the same modem preset. Nodes with mismatched presets cannot communicate even if they share the same frequency and encryption key.

The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow.

顯示設置

On Settings → Device configuration → Display. These control the radio’s own screen, not the app’s.

設定 描述說明
螢幕開啟持續時間 How long the display stays lit before sleeping
輪播間隔 How often the radio cycles between screens on its own
顯示模式 Screen layout/density used by the firmware
顯示單位 Metric or Imperial on the radio’s screen
使用12小時制 Show the radio’s clock as 12-hour rather than 24-hour
粗體字 Draw the screen’s heading text in bold
翻轉畫面 Rotate the display 180° for an inverted mounting
OLED 類型 Auto, SSD1306, SH1106, SH1107
輕觸或移動喚醒 Light the screen when the radio is tapped or moved
羅盤朝向 Rotation offset for the compass rose (0°, 90°, 180°, 270°)
始終指向北方 Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other

位置設定

On Settings → Device configuration → Position.

⚠️ Important: Saving this screen always reboots the radio.

設定 描述說明
GPS 模式(實體硬體) Three-state: GPS enabled, disabled, or not present. Not a simple on/off
GPS 輪詢間隔 How often the radio asks its GPS for a fix
廣播間隔 How often the position is shared with the mesh
智慧定位 Broadcast based on movement rather than purely on the clock
智慧間隔 With Smart Position on, the shortest gap between broadcasts
智慧距離 With Smart Position on, how far you must move before broadcasting
固定位置 Use a manually entered latitude, longitude and altitude instead of the GPS
位置旗標 A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on
GPS EN / Receive / Transmit GPIO Advanced: the pins the GPS module is wired to

電源設定

On Settings → Device configuration → Power.

設定 描述說明
啟用省電模式 Let the radio sleep aggressively between activity
電源中斷時關機 Power the device down after external power disappears
超深度睡眠時長 How long the deepest sleep state lasts
最小喚醒時間 The shortest time the radio stays awake once woken
藍牙等待持續時間 How long to wait for a phone to connect before sleeping
ADC 校正係數 Turn on a manual correction for battery-voltage readings
ADC乘數修正比率 The correction factor itself, used only when the override is on
電池 INA_2XX I2C 地址 Address of an external INA-series power sensor, if fitted

網路配置

On Settings → Device configuration → Network, on radios with Wi-Fi or Ethernet.

⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the radio. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the radio’s own screen or over USB. Saving this screen also always reboots the radio.

設定 描述說明
Wi-Fi enabled Enable the Wi-Fi radio (ESP32 radios)
SSID Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off
密碼 網路密碼
啟用以太網 Use a wired connection on hardware that has one
第四代IP模式 DHCP, or a static address configured with the four fields that follow
Wi-Fi IP / Subnet / Gateway / DNS The static address, only used when IPv4 mode is static
UDP 廣播 Share mesh traffic with other nodes over the local network
時間伺服器 Time synchronization server
rsyslog伺服器 Remote logging server

Network Config with a static IPv4 address entered

藍牙配置

On Settings → Device configuration → Bluetooth, on radios with Bluetooth.

⚠️ Important: Saving this screen always reboots the radio.

設定 描述說明
藍牙已啟用 Enable/disable BLE radio
配對模式 Fixed PIN, Random PIN, or No PIN
固定 PIN PIN code for pairing. Must be exactly six digits — the field rejects anything else

安全性設定

On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration.

⚠️ Important: Saving this screen always reboots the radio.

設定 描述說明
公鑰 Your node’s public key (read-only)
管理金鑰 Keys permitted to administer this node remotely — up to three
私鑰 Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware does not send it
重新產生私鑰 Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one
Admin Channel Enabled ⚠️ Removed — now configured automatically when an admin key is set
序列控制台 Serial console over the Stream API
啟用除錯日誌 API Output live debug logging over serial, and view and export position-redacted radio logs over Bluetooth
管理模式 Restrict non-admin channel changes. Only selectable once an Admin Key is set
備份金鑰 Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node)
Restore Keys Write the backed-up keys back to the node (available once a backup exists)
Delete Key Backup Remove the stored key backup from this phone
Protection level How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation)

Lockdown Mode

Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row does not appear otherwise.

Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware that supports locking. You can turn lockdown off again at any time with the passphrase, and a full device erase restores the hardware regardless.

Alongside the passphrase you set the limits that end a session automatically:

Field What it does
Boots remaining How many device boots the unlocked state survives
Hours until expiry Wall-clock lifetime of the unlocked state
Session cap (minutes) A per-boot uptime cap on the unlocked state. 0, the default, means no cap

Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again.

⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings.


diff --git a/main/zh-rTW/user/signal-meter.html b/main/zh-rTW/user/signal-meter.html index 83d5e16fd4..720c3d1a84 100644 --- a/main/zh-rTW/user/signal-meter.html +++ b/main/zh-rTW/user/signal-meter.html @@ -1,4 +1,4 @@ - How the Meshtastic Signal Meter Works | Meshtastic Android Skip to main content Link Menu Expand (external link) Document Search Copy Copied
🌐 中文 (繁體)
Meshtastic Docs ↗

🌐 中文 (繁體) — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR alone, measured against the active preset’s SNR limit. It does not factor in RSSI: without knowing the local noise floor, RSSI alone cannot say whether a signal is decodable. RSSI is still available — on the node detail screen and in the metrics charts.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

| Level | Bars | Criteria | Meaning | | —– | ————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————– | ————————————————————– | ————————————————————————————————— | | 良好 | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | | 普通 | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | | 不良 | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | | 無 | 1. Overview Meshtastic is a project that allows you to use inexpensive LoRa radios as a long range, off-grid, decentralized communication platform. These radios, combined with readily available and very affordable microcontrollers like the ESP32, nRF52, and RP2040, create a network that can be used to send text messages, share locations, and more without relying on cellular or WiFi infrastructure. It's perfect for hiking, camping, or any situation where you need to stay connected beyond the reach of traditional networks. 2. Key Components```

  • LoRa Radios: These radios provide the long-range communication capabilities. The RAK Wireless modules are a popular choice.
  • Microcontrollers: The brains of the operation. ESP32, nRF52, and RP2040 are commonly used due to their low cost and capabilities.
  • GPS (Optional): For location sharing. Many devices, like the T-Beam, have built-in GPS.
  • Battery (Optional): For portable use.
  • Enclosure (Optional): To protect the hardware. 3. **Popular Devices**
  • T-Beam: A popular board with ESP32, LoRa, and GPS.
  • Heltec WiFi LoRa 32: Another popular ESP32-based board with LoRa.
  • LilyGo Boards: LilyGo offers a variety of ESP32 and nRF52 based boards with LoRa. 4. **Features**
  • Text Messaging: Send and receive text messages over the LoRa network.
  • Location Sharing: Share your location with other users on the network (requires GPS).
  • Encryption: Messages can be encrypted for privacy.
  • Mesh Networking: The network automatically routes messages through other nodes to reach the destination.
  • Off-Grid Communication: No cellular or WiFi required.
  • Channel Settings: Customize channel settings for different regions and use cases (Long Fast, Mid Slow, etc.). 5. **Software & Firmware**
  • Meshtastic Firmware: The core software that runs on the microcontrollers.
  • Meshtastic Mobile App: For configuring and interacting with the devices. Available on Android and iOS.
  • CLI (Command Line Interface): For advanced configuration and debugging.
  • API (Application Programming Interface): For integrating Meshtastic with other applications. 6. **Hardware Setup**
  • Flashing Firmware: You’ll need to flash the Meshtastic firmware onto your microcontroller. This is typically done using a USB connection and a flashing tool.
  • Connecting Peripherals: Connect the LoRa radio and any other peripherals (GPS, battery) to the microcontroller.
  • Antenna: Attach an appropriate antenna to the LoRa radio. 7. **Configuration**
  • Region Settings: Configure the correct region settings for your location.
  • Channel Settings: Choose a channel or create a custom channel.
  • Encryption: Enable encryption for secure communication.
  • Power Settings: Adjust power settings to optimize battery life. 8. **Technical Details**
  • LoRa Modulation: Uses LoRa modulation for long-range communication.
  • Frequency Bands: Operates on various frequency bands depending on the region (e.g., 915 MHz in North America, 868 MHz in Europe).
  • Microcontroller Interfaces: Uses various interfaces for communication between the microcontroller and peripherals, including GPIO, USB, UART, SPI, and I2C.
  • BLE (Bluetooth Low Energy): Used for initial configuration and communication with the mobile app.
  • WiFi: Some devices support WiFi for OTA (Over-The-Air) firmware updates.
  • MQTT: Supports MQTT for integration with other systems. 9. **Use Cases**
  • Hiking and Camping: Stay connected with your group in areas without cellular coverage.
  • Emergency Communication: Provide a backup communication system in case of emergencies.
  • Disaster Relief: Establish communication networks in areas affected by disasters.
  • Rural Communication: Connect communities in remote areas.
  • IoT Applications: Use Meshtastic for various IoT applications that require long-range communication. 10. **Resources**
  • Meshtastic Website: https://meshtastic.org/
  • Meshtastic Documentation: https://meshtastic.org/docs/
  • Meshtastic Forums: https://meshtastic.discourse.group/ ```1) 概觀

Meshtastic 是一個專案,讓你可以使用便宜的 LoRa 無線電作為長距離、離線、去中心化的通訊平台。這些無線電,結合了容易取得且非常實惠的微控制器,像是 ESP32、nRF52 和 RP2040,創建了一個網路,可以用來傳送簡訊、分享位置等等,而不需要依賴行動網路或 WiFi 基礎設施。它非常適合健行、露營,或任何你需要保持連線,但又超出傳統網路覆蓋範圍的情況。

2) 主要組件

  • LoRa 無線電: 提供長距離通訊能力。 RAK Wireless 模組是一個很受歡迎的選擇。
  • 微控制器: 運作的大腦。 ESP32、nRF52 和 RP2040 因為它們的低成本和功能而被廣泛使用。
  • GPS (可選): 用於位置分享。 許多裝置,像是 T-Beam,都有內建 GPS。
  • 電池 (可選): 用於攜帶型使用。
  • 外殼 (可選): 保護硬體。

3) 熱門裝置

  • T-Beam: 一個受歡迎的板子,具有 ESP32、LoRa 和 GPS。
  • Heltec WiFi LoRa 32: 另一個受歡迎的基於 ESP32 的板子,具有 LoRa。
  • LilyGo Boards: LilyGo 提供各種基於 ESP32 和 nRF52 的板子,具有 LoRa。

4) 功能

  • 簡訊傳輸: 透過 LoRa 網路傳送和接收簡訊。
  • 位置分享: 與網路上其他使用者分享你的位置 (需要 GPS)。
  • 加密: 可以加密訊息以保護隱私。
  • 網狀網路: 網路會自動透過其他節點路由訊息,以到達目的地。
  • 離線通訊: 不需要行動網路或 WiFi。
  • 頻道設定: 客製化不同地區和使用案例的頻道設定 (Long Fast、Mid Slow 等)。

5) 軟體與 Firmware

  • Meshtastic Firmware: 在微控制器上執行的核心軟體。
  • Meshtastic Mobile App: 用於配置和與裝置互動。 可在 Android 和 iOS 上使用。
  • CLI (Command Line Interface): 用於進階配置和除錯。
  • API (Application Programming Interface): 用於將 Meshtastic 與其他應用程式整合。

6) 硬體設定

  • 刷入 Firmware: 你需要將 Meshtastic firmware 刷入你的微控制器。 這通常是使用 USB 連線和刷入工具來完成的。
  • 連接週邊設備: 將 LoRa 無線電和任何其他週邊設備 (GPS、電池) 連接到微控制器。
  • 天線: 將適當的天線連接到 LoRa 無線電。

7) 配置

  • 區域設定: 為你的位置配置正確的區域設定。
  • 頻道設定: 選擇一個頻道或創建一個自定義頻道。
  • 加密: 啟用加密以進行安全通訊。
  • 電源設定: 調整電源設定以優化電池壽命。

8) 技術細節

  • LoRa 調變: 使用 LoRa 調變進行長距離通訊。
  • 頻率範圍: 根據地區在不同的頻率範圍上運作 (例如,北美為 915 MHz,歐洲為 868 MHz)。
  • 微控制器介面: 使用各種介面在微控制器和週邊設備之間進行通訊,包括 GPIO、USB、UART、SPI 和 I2C。
  • BLE (Bluetooth Low Energy): 用於初始配置和與行動應用程式的通訊。
  • WiFi: 某些裝置支援 WiFi 用於 OTA (Over-The-Air) firmware 更新。
  • MQTT: 支援 MQTT 用於與其他系統整合。

9) 使用案例

  • 健行和露營: 在沒有行動網路覆蓋的地區與你的團隊保持聯繫。
  • 緊急通訊: 在緊急情況下提供備份通訊系統。
  • 災害救援: 在受災害影響的地區建立通訊網路。
  • 農村通訊: 連接偏遠地區的社群。
  • IoT 應用: 將 Meshtastic 用於各種需要長距離通訊的 IoT 應用。

10) 資源

- **Meshtastic Website:** [https://meshtastic.org/](https://meshtastic.org/)
+            How the Meshtastic Signal Meter Works | Meshtastic Android                      Skip to main content   Link      Menu      Expand       (external link)    Document      Search       Copy       Copied        
🌐 中文 (繁體)
Meshtastic Docs ↗

🌐 中文 (繁體) — Community translation View in English

How the Meshtastic Signal Meter Works

The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset.

RSSI and SNR

Every time the LoRa radio receives a message, it reports two measurements:

  • RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna.
  • SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise.

💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR).

Decoding Below the Noise Floor

Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise.

Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range).

Rating Signal Quality

The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone.

Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit:

| Level | Bars | Criteria | Meaning | | —– | ————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————– | ————————————————————– | ————————————————————————————————— | | 良好 | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | | 普通 | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | | 不良 | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | | 無 | 1. Overview Meshtastic is a project that allows you to use inexpensive LoRa radios as a long range, off-grid, decentralized communication platform. These radios, combined with readily available and very affordable microcontrollers like the ESP32, nRF52, and RP2040, create a network that can be used to send text messages, share locations, and more without relying on cellular or WiFi infrastructure. It's perfect for hiking, camping, or any situation where you need to stay connected beyond the reach of traditional networks. 2. Key Components```

  • LoRa Radios: These radios provide the long-range communication capabilities. The RAK Wireless modules are a popular choice.
  • Microcontrollers: The brains of the operation. ESP32, nRF52, and RP2040 are commonly used due to their low cost and capabilities.
  • GPS (Optional): For location sharing. Many devices, like the T-Beam, have built-in GPS.
  • Battery (Optional): For portable use.
  • Enclosure (Optional): To protect the hardware. 3. **Popular Devices**
  • T-Beam: A popular board with ESP32, LoRa, and GPS.
  • Heltec WiFi LoRa 32: Another popular ESP32-based board with LoRa.
  • LilyGo Boards: LilyGo offers a variety of ESP32 and nRF52 based boards with LoRa. 4. **Features**
  • Text Messaging: Send and receive text messages over the LoRa network.
  • Location Sharing: Share your location with other users on the network (requires GPS).
  • Encryption: Messages can be encrypted for privacy.
  • Mesh Networking: The network automatically routes messages through other nodes to reach the destination.
  • Off-Grid Communication: No cellular or WiFi required.
  • Channel Settings: Customize channel settings for different regions and use cases (Long Fast, Mid Slow, etc.). 5. **Software & Firmware**
  • Meshtastic Firmware: The core software that runs on the microcontrollers.
  • Meshtastic Mobile App: For configuring and interacting with the devices. Available on Android and iOS.
  • CLI (Command Line Interface): For advanced configuration and debugging.
  • API (Application Programming Interface): For integrating Meshtastic with other applications. 6. **Hardware Setup**
  • Flashing Firmware: You’ll need to flash the Meshtastic firmware onto your microcontroller. This is typically done using a USB connection and a flashing tool.
  • Connecting Peripherals: Connect the LoRa radio and any other peripherals (GPS, battery) to the microcontroller.
  • Antenna: Attach an appropriate antenna to the LoRa radio. 7. **Configuration**
  • Region Settings: Configure the correct region settings for your location.
  • Channel Settings: Choose a channel or create a custom channel.
  • Encryption: Enable encryption for secure communication.
  • Power Settings: Adjust power settings to optimize battery life. 8. **Technical Details**
  • LoRa Modulation: Uses LoRa modulation for long-range communication.
  • Frequency Bands: Operates on various frequency bands depending on the region (e.g., 915 MHz in North America, 868 MHz in Europe).
  • Microcontroller Interfaces: Uses various interfaces for communication between the microcontroller and peripherals, including GPIO, USB, UART, SPI, and I2C.
  • BLE (Bluetooth Low Energy): Used for initial configuration and communication with the mobile app.
  • WiFi: Some devices support WiFi for OTA (Over-The-Air) firmware updates.
  • MQTT: Supports MQTT for integration with other systems. 9. **Use Cases**
  • Hiking and Camping: Stay connected with your group in areas without cellular coverage.
  • Emergency Communication: Provide a backup communication system in case of emergencies.
  • Disaster Relief: Establish communication networks in areas affected by disasters.
  • Rural Communication: Connect communities in remote areas.
  • IoT Applications: Use Meshtastic for various IoT applications that require long-range communication. 10. **Resources**
  • Meshtastic Website: https://meshtastic.org/
  • Meshtastic Documentation: https://meshtastic.org/docs/
  • Meshtastic Forums: https://meshtastic.discourse.group/ ```1) 概觀

Meshtastic 是一個專案,讓你可以使用便宜的 LoRa 無線電作為長距離、離線、去中心化的通訊平台。這些無線電,結合了容易取得且非常實惠的微控制器,像是 ESP32、nRF52 和 RP2040,創建了一個網路,可以用來傳送簡訊、分享位置等等,而不需要依賴行動網路或 WiFi 基礎設施。它非常適合健行、露營,或任何你需要保持連線,但又超出傳統網路覆蓋範圍的情況。

2) 主要組件

  • LoRa 無線電: 提供長距離通訊能力。 RAK Wireless 模組是一個很受歡迎的選擇。
  • 微控制器: 運作的大腦。 ESP32、nRF52 和 RP2040 因為它們的低成本和功能而被廣泛使用。
  • GPS (可選): 用於位置分享。 許多裝置,像是 T-Beam,都有內建 GPS。
  • 電池 (可選): 用於攜帶型使用。
  • 外殼 (可選): 保護硬體。

3) 熱門裝置

  • T-Beam: 一個受歡迎的板子,具有 ESP32、LoRa 和 GPS。
  • Heltec WiFi LoRa 32: 另一個受歡迎的基於 ESP32 的板子,具有 LoRa。
  • LilyGo Boards: LilyGo 提供各種基於 ESP32 和 nRF52 的板子,具有 LoRa。

4) 功能

  • 簡訊傳輸: 透過 LoRa 網路傳送和接收簡訊。
  • 位置分享: 與網路上其他使用者分享你的位置 (需要 GPS)。
  • 加密: 可以加密訊息以保護隱私。
  • 網狀網路: 網路會自動透過其他節點路由訊息,以到達目的地。
  • 離線通訊: 不需要行動網路或 WiFi。
  • 頻道設定: 客製化不同地區和使用案例的頻道設定 (Long Fast、Mid Slow 等)。

5) 軟體與 Firmware

  • Meshtastic Firmware: 在微控制器上執行的核心軟體。
  • Meshtastic Mobile App: 用於配置和與裝置互動。 可在 Android 和 iOS 上使用。
  • CLI (Command Line Interface): 用於進階配置和除錯。
  • API (Application Programming Interface): 用於將 Meshtastic 與其他應用程式整合。

6) 硬體設定

  • 刷入 Firmware: 你需要將 Meshtastic firmware 刷入你的微控制器。 這通常是使用 USB 連線和刷入工具來完成的。
  • 連接週邊設備: 將 LoRa 無線電和任何其他週邊設備 (GPS、電池) 連接到微控制器。
  • 天線: 將適當的天線連接到 LoRa 無線電。

7) 配置

  • 區域設定: 為你的位置配置正確的區域設定。
  • 頻道設定: 選擇一個頻道或創建一個自定義頻道。
  • 加密: 啟用加密以進行安全通訊。
  • 電源設定: 調整電源設定以優化電池壽命。

8) 技術細節

  • LoRa 調變: 使用 LoRa 調變進行長距離通訊。
  • 頻率範圍: 根據地區在不同的頻率範圍上運作 (例如,北美為 915 MHz,歐洲為 868 MHz)。
  • 微控制器介面: 使用各種介面在微控制器和週邊設備之間進行通訊,包括 GPIO、USB、UART、SPI 和 I2C。
  • BLE (Bluetooth Low Energy): 用於初始配置和與行動應用程式的通訊。
  • WiFi: 某些裝置支援 WiFi 用於 OTA (Over-The-Air) firmware 更新。
  • MQTT: 支援 MQTT 用於與其他系統整合。

9) 使用案例

  • 健行和露營: 在沒有行動網路覆蓋的地區與你的團隊保持聯繫。
  • 緊急通訊: 在緊急情況下提供備份通訊系統。
  • 災害救援: 在受災害影響的地區建立通訊網路。
  • 農村通訊: 連接偏遠地區的社群。
  • IoT 應用: 將 Meshtastic 用於各種需要長距離通訊的 IoT 應用。

10) 資源

- **Meshtastic Website:** [https://meshtastic.org/](https://meshtastic.org/)
 - **Meshtastic Documentation:** [https://meshtastic.org/docs/](https://meshtastic.org/docs/)
 - **Meshtastic Forums:** [https://meshtastic.discourse.group/](https://meshtastic.discourse.group/) | more than 7.5 dB below `limit`                 | Far below the preset's floor; further packets from this node are likely to be lost. |
-

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute hop colors use fixed thresholds (−7 dB / −15 dB); the per-node signal meter uses the preset-relative rating instead.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon

相關主題


+

The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak.

ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm.

Diagnosing Local Interference

A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal.

Where Signal Information Appears

In the app, signal data appears in several places:

  • Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path
  • Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen
  • Traceroute — per-hop signal quality for each relay node
  • Signal Quality — historical SNR and RSSI data in the metrics charts

Node list entry showing a Good signal rating: 12.5 dB SNR, −42 dBm RSSI, and the green signal-strength icon

相關主題